Technical Tip: How to enable Workspace ADOM lock mode and Policy package locking in FortiManager

[mmaubert]

Description
The ADOM lockout feature, also known as Workspace mode, has to be enabled to prevent database corruption in the event that multiple system administrators have write access to an ADOM and are therefore in a potential situation to make concurrent changes on this ADOM objects.

Solution
To enable this feature, type the following command at the CLI console:
1) On FortiManager 5.0.6 and older releases

# config system global
    set workspace enable
end

2) On FortiManager 5.0.7 and newer releases including 5.2.x, 5.4.x, 5.6.x, 6.0.x, 6.2.x, and 6.4.x.

# config system global
    set workspace-mode normal
end

From GUI, the location of the 'Lock ADOM' feature is dependent of the release number as well:

1) On FortiManager release 5.0, the Lock option is accessible via the ADOM select contextual menu.

2) On FortiManager release 5.2, the Lock option is accessible using the 'Lock ADOM' button that is located next to the ADOM selection drop-down menu.

3) On FortiManager release 5.4.x and above (5.6.x, 6.0.x, 6.2.x, and 6.4.x) the Lock option is accessible from several locations.

- From the 'Lock' button that is located next to the ADOM currently selected.

- From the System Settings 'All ADOMs' window using the ADOM select contextual menu.

Note that the All ADOMs windows provides a quick overview of the Lock option status for all ADOMs.

A quick overview of the Lock option status for all ADOMs can be displayed as well by selecting  the currently selected ADOM and opening the ADOM selection popup window.