A FortiManager administrator has moved a FortiGate device to a new ADOM, but they cannot see the policy or object configurations for that FortiGate…

When a managed FortiGate device is relocated from one ADOM to another within FortiManager, only its device-level management settings (Device Manager profile) are transferred to the target ADOM. FortiManager does not automatically copy or create policy packages or policy objects in the new ADOM database. To populate and view the policy and object configurations associated with the FortiGate in the new ADOM, the administrator must run the Import Configuration wizard. This wizard imports the policy package, firewall rules, and associated objects directly from the FortiGate into the new ADOM database.

A: Shared objects cannot dynamically construct or import a device's specific policy package structure.

B: Resetting and re-adding the FortiGate causes unnecessary disruption when the policy import wizard is standard.

D: ADOM sync is not an existing FortiManager function for migrating policy packages between ADOMs.

- Fortinet FortiManager 7.2.0 Administration Guide

Section: "Moving a device to a new ADOM"

pp. 132-134.

- Fortinet FortiManager 7.4.0 Study Guide

Chapter: "ADOM Management"

Section: "Moving Devices Between ADOMs"

pp. 68-71.