In FortiManager, global policy packages are not automatically assigned to new policy packages created in an ADOM. To apply a global policy (like "Training") to a new policy package (like
"Remotes"), the administrator must manually assign the global policy to that policy package.
Therefore, the correct step is to assign the Training global policy package to the Remotes policy package.

When you run a script using "Remote FortiGate Directly (via CLI)", FortiManager logs the configuration changes and creates a new revision history for the device.
Since the script is executed directly on the FortiGate, the FortiGate device automatically updates FortiManager's device-level database after the script is successfully applied.

lf FortiAnalyzer features are enabled, you cannot add FortiAnalyzer to FortiManager. You will also not be able to configure FortiManager high availability (HA).

The import process shows that FortiManager will create normalized interfaces named LAN, port4, and port6 at the ADOM layer, mapping them to the corresponding device interfaces based on the import settings.

When you add the root FortiGate device of a Security Fabric group to an ADOM (in this case, Training), FortiManager:
- Automatically detects the downstream FortiGate devices in the Security Fabric.
- However, those downstream devices are not automatically added or authorized.
- They will appear as unauthorized devices under the root FortiGate in the Training ADOM, not in the root ADOM.
You must manually authorize each downstream device if you want FortiManager to manage them.