A test run authenticates, completes its required operation and explicitly closes its session. That observation is relevant for the separate case a scripted FortiManager login succeeds but the automation never terminates its administrative session. Here the decisive evidence is the client stops on nonretryable errors and logs the rejected operation without repeating changes.

The automation records the operation-specific result and confirms completion through task evidence. That observation is relevant for the separate case an API client treats every HTTP success response as proof that an installation operation completed successfully. Here the decisive evidence is the client stops on nonretryable errors and logs the rejected operation without repeating changes.

Operators can review device inventory and deploy scoped changes from one management system. That observation is relevant for the separate case a managed-services provider needs to administer dozens of customer FortiGates without signing into each firewall separately. Here the decisive evidence is the client stops on nonretryable errors and logs the rejected operation without repeating changes.

The arriving unit matches its model record and receives the planned baseline configuration. That observation is relevant for the separate case an organization wants to preconfigure a FortiGate before hardware reaches a remote branch. Here the decisive evidence is the device can be matched to its authorized model record during registration.

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 device can be matched to its authorized model record during registration.

The approved FortiGate appears in the appropriate managed device inventory with healthy management status. That observation is relevant for the separate case a branch FortiGate requests authorization from FortiManager but does not appear among managed devices. Here the decisive evidence is the device can be matched to its authorized model record during registration.

Initial FortiManager provisioning establishes network prerequisites for secure centralized administration. This mechanism instead applies when a newly deployed FortiManager appliance is reachable only through an unplanned factory addressing scheme. The current correction relies on FortiManager bootstrap security requires hardening its privileged authentication surface.

A complete migration includes dependent services beyond transferring configuration files. This mechanism instead applies when FortiManager configuration is migrated to replacement hardware but administrators forget to validate device entitlements and reachability. The current correction relies on FortiManager bootstrap security requires hardening its privileged authentication surface.

FortiManager can perform core management in environments with restricted external connectivity. This mechanism instead applies when a deployment in a restricted network has no direct internet access but needs centrally managed device configuration. The current correction relies on FortiManager bootstrap security requires hardening its privileged authentication surface.

Investigate peer network reachability and HA configuration before relying on failover. This can be appropriate when a FortiManager HA secondary has stopped receiving heartbeat packets but the primary remains online. It does not directly address the present situation, where the required correction is investigate management data synchronization status and underlying connectivity or load.

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 investigate management data synchronization status and underlying connectivity or load.

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 investigate management data synchronization status and underlying connectivity or load.

Cluster-aware management tracks both the logical HA cluster and individual member identities. This mechanism instead applies when a FortiGate HA cluster adds a replacement secondary member, but FortiManager still displays the old member inventory. The current correction relies on FortiManager manages FortiGate HA cluster metadata and members as a coordinated security device.

Onboarding imports existing device state into FortiManager's device management database. This mechanism instead applies when a FortiGate has been discovered, but its import report shows inconsistent settings compared with the planned baseline. The current correction relies on FortiManager manages FortiGate HA cluster metadata and members as a coordinated security device.

FortiManager tracks managed devices by identity and can support controlled device replacement. This mechanism instead applies when a FortiGate was replaced after hardware failure, and the new unit is still associated with a stale device identity. The current correction relies on FortiManager manages FortiGate HA cluster metadata and members as a coordinated security device.

ADOM revisions capture snapshots of policy and object management state. This mechanism instead applies when an ADOM backup was restored but some custom objects appear missing from the active policy view. The current correction relies on privilege restrictions must address both administrative domain boundaries and global management rights.

Device grouping by ADOM supports organizational separation within one FortiManager instance. This mechanism instead applies when a retail enterprise needs one ADOM per regional division while sharing a common FortiManager appliance. The current correction relies on privilege restrictions must address both administrative domain boundaries and global management rights.

Workflow mode introduces an approval lifecycle beyond ordinary workspace locking. This mechanism instead applies when an MSSP needs approval before policy changes become deployable in sensitive customer ADOMs. The current correction relies on privilege restrictions must address both administrative domain boundaries and global management rights.

Preserve a backup and diagnose the concrete installation error before any database repair operation. This can be appropriate when an operator tries to fix a policy installation error by clearing the FortiManager database immediately. It does not directly address the present situation, where the required correction is inspect per-target task results and isolate only the failed device for repair.

Use a scoped preview and test install against a compatible representative device before wide deployment. This can be appropriate when a security engineer changes a policy object but never validates the installation on a representative target. It does not directly address the present situation, where the required correction is inspect per-target task results and isolate only the failed device for repair.

Retrieve current device changes and reconcile them with the central database before installing. This can be appropriate when a firewall was modified locally during emergency response and its next central install preview threatens to revert that approved local fix. It does not directly address the present situation, where the required correction is inspect per-target task results and isolate only the failed device for repair.

Bind external authentication to a narrowly scoped FortiManager administrator profile and ADOM access. This can be appropriate when a remote administrator receives broad permissions after external authentication succeeds against a corporate identity source. It does not directly address the present situation, where the required correction is adjust the scoped administrator profile to include required device privileges without granting other ADOMs.

Apply an appropriately limited administrator profile and test system-level access restrictions. This can be appropriate when a restricted administrative team wants to use only one ADOM but its credentials can still view unrelated system settings. It does not directly address the present situation, where the required correction is adjust the scoped administrator profile to include required device privileges without granting other ADOMs.

Follow FortiManager's supported device move procedure and review destination ADOM objects and policy assignment. This can be appropriate when a device needs to move from one customer ADOM to another due to a contract transfer. It does not directly address the present situation, where the required correction is adjust the scoped administrator profile to include required device privileges without granting other ADOMs.

Collected diagnostics identify the component responsible or justify the controlled restart. That observation is relevant for the separate case an operator sees high memory usage but immediately reboots FortiManager without collecting diagnostic evidence. Here the decisive evidence is support evidence identifies the precise subsystem and time of the reproducible fault.

Disk utilization returns to a supported level without deleting current management databases. That observation is relevant for the separate case a FortiManager VM approaches full disk capacity after accumulating backups and operational logs. Here the decisive evidence is support evidence identifies the precise subsystem and time of the reproducible fault.

Resource monitoring identifies the process or scheduled load responsible for the slowdown. That observation is relevant for the separate case the FortiManager GUI becomes slow while CPU usage spikes during a large scheduled operation. Here the decisive evidence is support evidence identifies the precise subsystem and time of the reproducible fault.

HA synchronization replicates management datasets between primary and backup units. This mechanism instead applies when a secondary FortiManager reports a large pending module synchronization backlog during peak network usage. The current correction relies on rejoined management HA units require coordinated role and data synchronization checks.

Management availability includes both HA peer health and reachable administrative services. This mechanism instead applies when an enterprise plans to test FortiManager HA but has not checked how administrative sessions reconnect to the promoted unit. The current correction relies on rejoined management HA units require coordinated role and data synchronization checks.

FortiManager HA cluster status reflects heartbeat reception from configured peers. This mechanism instead applies when a FortiManager HA secondary has stopped receiving heartbeat packets but the primary remains online. The current correction relies on rejoined management HA units require coordinated role and data synchronization checks.

Removing apparently idle policies without measured evidence may disrupt legitimate traffic. That consequence is more specific to a network team wants to compare expected policy use across several branches but never reviews rule hit counts. For this case, the most direct exposure is deleting rules from an incomplete view can break connectivity at a different site.

Missing policy object dependencies can cause installations to fail or omit intended inspection. That consequence is more specific to a managed firewall requires IPS protection but the policy package references a profile missing from the ADOM object inventory. For this case, the most direct exposure is deleting rules from an incomplete view can break connectivity at a different site.

Leaving legacy group members can preserve unauthorized access after server decommissioning. That consequence is more specific to a shared policy contains an address group with one obsolete member that could allow traffic to a retired server. For this case, the most direct exposure is deleting rules from an incomplete view can break connectivity at a different site.