Adjust the maintenance schedule and task concurrency based on observed system capacity. This can be appropriate when a central management appliance exhausts resources during a firmware rollout because all managed devices were scheduled at once. It does not directly address the present situation, where the required correction is review disk usage and retention settings and remove only approved obsolete data.

Use the supported replacement-device workflow and update the registered managed identity. This can be appropriate when a firewall replacement boots successfully, yet FortiManager continues sending tasks to the failed old serial. It does not directly address the present situation, where the required correction is review disk usage and retention settings and remove only approved obsolete data.

Run documented filesystem integrity checks and restore affected management databases when justified. This can be appropriate when after unexpected power loss, FortiManager displays inconsistent database errors in installation tasks. It does not directly address the present situation, where the required correction is review disk usage and retention settings and remove only approved obsolete data.

Management connections remain stable under the monitored test period with expected keepalives. That observation is relevant for the separate case multiple managed FortiGates disconnect periodically but no physical interface alarms exist on FortiManager. Here the decisive evidence is fortiGuard downloads recover and existing managed-device connections stay healthy.

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 fortiGuard downloads recover and existing managed-device connections stay healthy.

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 fortiGuard downloads recover and existing managed-device connections stay healthy.

ADOM operation and device modes influence allowed FortiManager management behavior. This mechanism instead applies when a branch FortiGate is registered under an ADOM whose device operating mode does not support an expected workflow. The current correction relies on device grouping by ADOM supports organizational separation within one FortiManager instance.

Privilege restrictions must address both administrative domain boundaries and global management rights. This mechanism instead applies when a restricted administrative team wants to use only one ADOM but its credentials can still view unrelated system settings. The current correction relies on device grouping by ADOM supports organizational separation within one FortiManager instance.

Installation targets are maintained in ADOM-scoped policy management records. This mechanism instead applies when an administrator expects a FortiGate moved between ADOMs to retain an old package's installation targets automatically. The current correction relies on device grouping by ADOM supports organizational separation within one FortiManager instance.

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 reusing interface-specific commands blindly can produce configuration failures on different models.

Missing device revisions obstruct postincident configuration reconstruction. That consequence is more specific to a customer asks which FortiGate configuration was in force when an incident began, but the registration record lacks recent retrieved revisions. For this case, the most direct exposure is reusing interface-specific commands blindly can produce configuration failures on different models.

Continuing to target a failed device record can leave the replacement outside central control. That consequence is more specific to a FortiGate was replaced after hardware failure, and the new unit is still associated with a stale device identity. For this case, the most direct exposure is reusing interface-specific commands blindly can produce configuration failures on different models.

Policy installation resolves the logical interface to an existing interface or zone on the target. That observation is relevant for the separate case a FortiManager policy package uses a zone name that does not exist on one target FortiGate. Here the decisive evidence is installation preview resolves the policy interfaces correctly without fallback guesses.

Each installation resolves the address object to the intended local network for its target. That observation is relevant for the separate case a policy rule references the same named address object but the underlying subnet differs at two branches. Here the decisive evidence is installation preview resolves the policy interfaces correctly without fallback guesses.

The matching traffic hits the reviewed deny rule before broader permission is considered. That observation is relevant for the separate case a security engineer adds a deny rule under a broad permissive rule but sees no change in traffic decisions. Here the decisive evidence is installation preview resolves the policy interfaces correctly without fallback guesses.

Untracked device membership can let gateways miss centrally controlled security updates. That consequence is more specific to an organization operates hundreds of managed devices but cannot determine which FortiManager ADOM is responsible for an orphaned gateway. For this case, the most direct exposure is version mismatch can prevent accurate interpretation or installation of managed configuration.

Restoring the wrong ADOM revision can omit recent approved objects. That consequence is more specific to an ADOM backup was restored but some custom objects appear missing from the active policy view. For this case, the most direct exposure is version mismatch can prevent accurate interpretation or installation of managed configuration.

Forcing an unknown lock can discard work or interrupt an active administrator. That consequence is more specific to a user needs to identify which administrator session holds a lock before emergency maintenance. For this case, the most direct exposure is version mismatch can prevent accurate interpretation or installation of managed configuration.

Assuming private addresses are reachable across NAT can prevent remote gateway management. That consequence is more specific to a FortiGate behind a branch NAT device cannot establish central management to FortiManager at headquarters. For this case, the most direct exposure is unexamined WAN dependencies can interrupt centralized change deployment across many sites.

Incorrect translated identity or return routing can break management connectivity at either side. That consequence is more specific to both a remote FortiGate and the centralized FortiManager sit behind separate NAT gateways with overlapping private addresses. For this case, the most direct exposure is unexamined WAN dependencies can interrupt centralized change deployment across many sites.

Internal-only DNS answers can defeat an otherwise valid internet-side management path. That consequence is more specific to a management network uses split-horizon DNS, but remote FortiGates resolve the FortiManager name to an unreachable inside address. For this case, the most direct exposure is unexamined WAN dependencies can interrupt centralized change deployment across many sites.

Policy packages have managed installation targets that automation must resolve explicitly. This mechanism instead applies when an automation needs to determine the eligible devices for a firewall policy package before scheduling installation. The current correction relies on FortiManager centralizes configurations while FortiAnalyzer capabilities address logging and analytics needs.

FortiManager topology visualization complements centralized configuration and device records. This mechanism instead applies when a central administrator cannot see network connectivity among managed devices needed for a security review. The current correction relies on FortiManager centralizes configurations while FortiAnalyzer capabilities address logging and analytics needs.

FortiManager maintains central management databases and installation workflows for managed devices. This mechanism instead applies when a managed-services provider needs to administer dozens of customer FortiGates without signing into each firewall separately. The current correction relies on FortiManager centralizes configurations while FortiAnalyzer capabilities address logging and analytics needs.

FortiManager centrally manages devices without replacing their security gateway forwarding function. This mechanism instead applies when an enterprise incorrectly treats FortiManager as the live traffic gateway and routes branch user packets through its management interface. The current correction relies on FortiManager architecture depends on operational reachability between management and distributed FortiGates.

NATed FortiManager scenarios rely on supported endpoint discovery and routing across translated links. This mechanism instead applies when FortiManager is located behind a data-center NAT device, and newly installed remote gateways cannot complete registration. The current correction relies on FortiManager architecture depends on operational reachability between management and distributed FortiGates.

Management over NAT requires appropriate name resolution as well as IP translation. This mechanism instead applies when a management network uses split-horizon DNS, but remote FortiGates resolve the FortiManager name to an unreachable inside address. The current correction relies on FortiManager architecture depends on operational reachability between management and distributed FortiGates.

A task marked complete without matching device state can conceal unresolved synchronization. That consequence is more specific to an engineer edits the central policy but an installation task shows the same diff repeatedly despite its claimed success. For this case, the most direct exposure is broad reruns without target evidence can cause unnecessary production churn.

Unsupported object attributes can block installation or produce incomplete device configuration. That consequence is more specific to an installation task fails during object-copy processing because the target device rejects an unsupported security profile field. For this case, the most direct exposure is broad reruns without target evidence can cause unnecessary production churn.

Fleet-wide deployment without a representative validation may spread a bad object change. That consequence is more specific to a security engineer changes a policy object but never validates the installation on a representative target. For this case, the most direct exposure is broad reruns without target evidence can cause unnecessary production churn.

Whole-database rollback for a narrow error can damage otherwise correct configuration. That consequence is more specific to after a configuration outage, an engineer wants to restore one changed object but proposes replacing all FortiManager device records. For this case, the most direct exposure is assuming instantaneous revision collection can cause administrators to overlook pending local changes.

Assuming the backup is the newest device state can erase legitimate recent changes. That consequence is more specific to a restored FortiManager database contains imported revisions but the newest branch firewall configuration was changed after the backup. For this case, the most direct exposure is assuming instantaneous revision collection can cause administrators to overlook pending local changes.

Confusing saved policy intent with installed device state creates inaccurate compliance claims. That consequence is more specific to an auditor asks whether a FortiManager policy database reflects what is actually running on a managed FortiGate. For this case, the most direct exposure is assuming instantaneous revision collection can cause administrators to overlook pending local changes.