Comprehensive and Detailed 150 to 200 words of Explanation From Exact Extract of Enterprise Firewall 7.6 Administrator documents:
According to the FortiManager 7.6 Study Guide regarding Object Management and the Import Device Wizard, FortiManager uses a centralized database where objects are shared across an ADOM. When importing a configuration from a FortiGate, the wizard compares local objects with those already existing in the FortiManager ADOM database.
As shown in the exhibit, conflicts exist for the Web_restrictions and deep-inspection profiles. Since these profiles are shared with other FortiGate devices, a decision must be made:
Selecting " FortiManager " : The local FortiGate settings will be overwritten by the FortiManager ' s database version upon the next installation, potentially losing site-specific configurations.
Selecting " FortiGate " : The FortiManager ADOM database is updated with the new values. This causes all other FortiGate devices using these shared objects to move into a " Modified " status, as their local configurations no longer match the updated central database.
To resolve this conflict properly when different devices require different settings for the same profile type, the best practice is to create uniquely named objects (Option B) on the FortiGate before re-importing. This ensures that the specific requirements for the Core1 VDOM are met without affecting the global objects used by the rest of the enterprise network.
