The install operation pushes device configuration from the FortiManager to a FortiGate device.
The FortiManager compares the configuration information that it has with the current configuration on the FortiGate. It then pushes the necessary configuration changes to the FortiGate to ensure that the FortiGate is synchronized with the FortiManager.
The install operation can include only device settings, or device settings and policy packages.
For more information, see Installing to devices.
The re-install operation reinstalls a policy package on a FortiGate device. For more information, see Reinstall a policy package.
The import operation copies policies and policy-related objects from the device database into the ADOM, creating a policy package that reflects the current configuration of the FortiGate device.
For more information, see Import policy wizard.
The retrieve operation retrieves the FortiGate configuration and stores it in the device database on the FortiManager.
When there is a change on the FortiGate that is not initiated by an install operation, the FortiGate automatically sends the configuration changes to the FortiManager.
The auto-update operation is enabled by default. To disable auto-update and allow the administrator to accept or refuse updates, use the following CLI commands:
config system admin settings
set auto-update disable
The auto-backup operation is similar to auto-update, but only available when the FortiManager is in backup mode. The FortiGate device will wait until the FortiGate admin user has logged out before performing the backup.
For more information, see ADOM modes.
The auto-retrieve operation is only invoked if the FortiGate fails to initiate an auto-update operation. When the FortiManager detects a change on the FortiGate, it automatically retrieves the full configuration.
The FortiManager queries the FortiGate to update that FortiGate's current synchronization status. For more information, see Refreshing a device.
The revert operation loads a saved configuration revision into the device database. For more information, see Managing configuration revision history.