Separate unmanaged records for one HA pair can create inconsistent member targeting. That consequence is more specific to two new FortiGates in a high-availability pair are being registered independently with conflicting configuration records. For this case, the most direct exposure is incorrect management addressing prevents discovery even if the firewall's data interfaces are healthy.

Unreviewed import differences can overwrite local configuration or central assumptions. That consequence is more specific to a FortiGate has been discovered, but its import report shows inconsistent settings compared with the planned baseline. For this case, the most direct exposure is incorrect management addressing prevents discovery even if the firewall's data interfaces are healthy.

Incorrect ADOM membership can expose customer configuration to unrelated administrators. That consequence is more specific to an administrator imports a FortiGate into the wrong tenant ADOM and later notices a policy scope mismatch. For this case, the most direct exposure is incorrect management addressing prevents discovery even if the firewall's data interfaces are healthy.

FortiManager represents the intended cluster and applies appropriate cluster-aware management. That observation is relevant for the separate case two new FortiGates in a high-availability pair are being registered independently with conflicting configuration records. Here the decisive evidence is the HA cluster inventory contains the correct primary and replacement secondary identities.

The replacement device is managed under the authorized record with current configuration restored. That observation is relevant for the separate case a FortiGate was replaced after hardware failure, and the new unit is still associated with a stale device identity. Here the decisive evidence is the HA cluster inventory contains the correct primary and replacement secondary identities.

Finance devices receive only reviewed settings consistent with their own network requirements. That observation is relevant for the separate case a provisioning engineer copies a system template from a retail ADOM into a finance ADOM without checking environment differences. Here the decisive evidence is the HA cluster inventory contains the correct primary and replacement secondary identities.

Workspace locks preserve exclusive edit control during an administrative session. This mechanism instead applies when an administrator tries to edit a locked ADOM while another engineer is performing critical maintenance. The current correction relies on workspace sessions carry pending edits and lock ownership until explicitly completed.

Workspace locks serialize supported configuration edits on shared policy resources. This mechanism instead applies when two administrators edit one FortiManager policy package simultaneously and overwrite each other's work. The current correction relies on workspace sessions carry pending edits and lock ownership until explicitly completed.

Some FortiManager operations require an ADOM lock even when individual resource locks are supported. This mechanism instead applies when a team wants to create a new device in an unlocked ADOM while only a different package is locked. The current correction relies on workspace sessions carry pending edits and lock ownership until explicitly completed.

Reassign the managed device through a supported ADOM move after validating target packages and permissions. This can be appropriate when an administrator imports a FortiGate into the wrong tenant ADOM and later notices a policy scope mismatch. It does not directly address the present situation, where the required correction is create an eligible model device and populate a supported device blueprint for initial provisioning.

Verify network routing and required FGFM service reachability between the gateway and FortiManager. This can be appropriate when a device registration wizard cannot discover a branch gateway because the management path crosses a blocked security segment. It does not directly address the present situation, where the required correction is create an eligible model device and populate a supported device blueprint for initial provisioning.

Give each model appliance a unique verified identity and inspect its blueprint metadata before onboarding. This can be appropriate when an offline branch uses a model device entry, but two appliances share a reused blueprint identifier in a batch import. It does not directly address the present situation, where the required correction is create an eligible model device and populate a supported device blueprint for initial provisioning.

Trial FortiManager VM limitations can make the planned local FortiGuard service unavailable. That consequence is more specific to a FortiManager-VM trial license is deployed as a local FortiGuard server for dozens of production devices. For this case, the most direct exposure is distributing the wrong firmware to mixed hardware may cause failed upgrades or outages.

No fallback route may leave update and rating lookups unavailable during a private server outage. That consequence is more specific to a managed firewall is configured to query a private FortiGuard service but the local FDS is unreachable during an outage. For this case, the most direct exposure is distributing the wrong firmware to mixed hardware may cause failed upgrades or outages.

Expired FortiGuard rights can block expected content even when transport connectivity works. That consequence is more specific to an operator sees FortiGuard license-expired warnings but continues treating signature download failures as network-only issues. For this case, the most direct exposure is distributing the wrong firmware to mixed hardware may cause failed upgrades or outages.

Enable workspace locking on the package or its ADOM before concurrent policy edits. This can be appropriate when two administrators edit one FortiManager policy package simultaneously and overwrite each other's work. It does not directly address the present situation, where the required correction is select workspace for locking control or workflow for a documented change-approval lifecycle as appropriate.

Identify the lock holder and coordinate release rather than forcibly breaking the lock. This can be appropriate when an administrator tries to edit a locked ADOM while another engineer is performing critical maintenance. It does not directly address the present situation, where the required correction is select workspace for locking control or workflow for a documented change-approval lifecycle as appropriate.

Configure supported per-ADOM workspace settings and validate the behavior of each delegated tenant. This can be appropriate when an MSP wants each tenant ADOM to use a different editing collaboration model. It does not directly address the present situation, where the required correction is select workspace for locking control or workflow for a documented change-approval lifecycle as appropriate.

Confirm the peer has current synchronized modules before initiating the approved failover procedure. This can be appropriate when a maintenance window requires promoting a secondary FortiManager with unconfirmed synchronized policy data. It does not directly address the present situation, where the required correction is include administrator access and management-task continuity in the HA acceptance plan.

Use the supported `get system ha` diagnostic command on the relevant appliance. This can be appropriate when a new administrator needs a CLI confirmation of FortiManager HA state when the graphical interface cannot load. It does not directly address the present situation, where the required correction is include administrator access and management-task continuity in the HA acceptance plan.

Configure a supported FortiManager HA pair with proper primary and secondary members. This can be appropriate when two FortiManager appliances must protect centralized policy administration from a single management-server failure. It does not directly address the present situation, where the required correction is include administrator access and management-task continuity in the HA acceptance plan.

Device configuration names must align with ADOM logical interface mappings during installation. This mechanism instead applies when a FortiGate uses a different interface alias than the central ADOM policy expects. The current correction relies on FortiManager validates device-level and policy-level configuration through distinct processes.

ADOM objects are centrally authored and deployed through policy installation operations. This mechanism instead applies when a new policy object is created in an ADOM but the managed FortiGate still shows the original object value. The current correction relies on FortiManager validates device-level and policy-level configuration through distinct processes.

FortiManager device inventory and ADOM package targets need deliberate lifecycle reconciliation. This mechanism instead applies when a branch FortiGate is removed from FortiManager but its policy package installation target remains in historical reports. The current correction relies on FortiManager validates device-level and policy-level configuration through distinct processes.

Missing peer heartbeats can leave the redundant management unit unavailable for takeover. That consequence is more specific to a FortiManager HA secondary has stopped receiving heartbeat packets but the primary remains online. For this case, the most direct exposure is healthy heartbeat alone does not guarantee the secondary holds all current management data.

One management appliance without redundancy becomes a single point of administrative failure. That consequence is more specific to two FortiManager appliances must protect centralized policy administration from a single management-server failure. For this case, the most direct exposure is healthy heartbeat alone does not guarantee the secondary holds all current management data.

A sustained synchronization backlog can weaken disaster recovery readiness. That consequence is more specific to a secondary FortiManager reports a large pending module synchronization backlog during peak network usage. For this case, the most direct exposure is healthy heartbeat alone does not guarantee the secondary holds all current management data.

Uncontrolled script timing can disrupt production networking or compliance controls. That consequence is more specific to a scheduled script changes a network parameter outside an authorized maintenance window. For this case, the most direct exposure is using configuration-changing commands for observation can create unintended drift.

Unreviewed automation changes can spread a faulty command to many managed devices. That consequence is more specific to an engineer edits a saved script without updating its documented purpose and target risk. For this case, the most direct exposure is using configuration-changing commands for observation can create unintended drift.

Repeated manual CLI work increases inconsistency and accidental device omission. That consequence is more specific to an engineer plans to change the same NTP server on 60 gateways using manual command-line sessions. For this case, the most direct exposure is using configuration-changing commands for observation can create unintended drift.

Session state is finalized and another authorized administrator can edit the resource. That observation is relevant for the separate case a policy author leaves an uncommitted workspace session open during a long absence. Here the decisive evidence is the original holder completes or discards changes before the next operator acquires access.

One ADOM enforces locks while another follows its separately approved workflow arrangement. That observation is relevant for the separate case an MSP wants each tenant ADOM to use a different editing collaboration model. Here the decisive evidence is the original holder completes or discards changes before the next operator acquires access.

The chosen mode enforces the organization's intended edit and approval behavior in a test session. That observation is relevant for the separate case an engineer claims workspace and workflow modes are identical and chooses the mode without considering approval needs. Here the decisive evidence is the original holder completes or discards changes before the next operator acquires access.