Display options
The policy and objects that are displayed in the Policy & Objects page can be customized by selecting the Tools > Display Options menu option in the toolbar. Customizations are either per ADOM or at the global level.
Display options
Global level display options
Turn the various options on or off (visible or hidden) by clicking the on/off button next to feature name. Turn all of the options in a category on by selecting All On under the category name, or turn all of the categories on by selecting All On at the bottom of the window.
Once turned on, the corresponding options settings will be configurable from the appropriate location in the Policy & Objects tab.
Reset all of the options by selecting Reset at the bottom of the screen, or reset only the options in a category by selecting Reset under the category name.
Managing policy packages
Policy packages can be created and edited and then assigned to specific devices in the ADOM. Folders can be created for the policy packages to aid in the organization and management of the packages.
Lock an ADOM or policy package
If workspace is enabled, you must lock an ADOM/Policy Package prior to performing any management tasks on it. For more information, see Concurrent ADOM access.
To lock an ADOM:
- Select the specific ADOM on which you will be making changes from the drop-down list in the toolbar, or select Global.
- Select the lock icon next to the drop-down list to lock the selected ADOM.
The ADOM will now be locked, allowing you to make changes to it, and preventing other administrators from making any changes, unless lock override is enabled (see Extend workspace to entire ADOM).
Question about ADOMs. In previous versions of FortiOS 4.3 maybe earlier. When you had multiple devices under an ADOM the policies and objects were clearly separated per device being managed. With the newer FortiOS it seems as though there is overlapping and my policies and objects seem to be cross contaminated between devices. What is your perspective on this and/or work around? Thank you in advance – Richard
I always keep my devices separated by Firmware version. ADOM 4.3 ADOM 5.2 ADOM 5.4 etc to keep things nice and neat.
I have an issue for deleting the V4.2 ADOMs from FMG V5.2 getting the below error.
Some ADOM(s) were not deleted successfully because they are not empty
But those ADOMs are not used anywhere. How to find out where it is used?
No admin accounts having access to the ADOM, No policy package for the ADOM.
Usually, it experiences this issue because something somewhere is still referencing it. Whether that item be a policy package as you mentioned before or a group etc.
Is there any possibilities to find out the references for that ADOM on the FMG.
Hi Mike,
We use fortimanager v5.4.1-build1082 160629 (GA) FMG-VM64 but we cant drag and drop within the rule base. (drag en drop from the object side plain does work) I have seen a instruction video were they lock the adom but also that future is non exsistent in our GUI.
You have any idea what this could be ? I did not see any issues on this subject on the fortinet site. We have upgraded from a older version FM.
kind regards and thanks for this great support site, i look here first!
Did you follow the supported upgrade path when you moved your FortiManager up through the code?
Not sure ( I was not involved and there is no change history) but i did found this in the “alert message console”
Upgrade image from v5.2.7-build0757-160408(GA) to v5.4.1-build1082-160629
Hello,
HELP !! we have multiple firewalls we would like to upload on our Fortimanager in the same ADOM.
The problem is that some objects have the same names but different IPs adresses. i read that the only solution is mapping the objects. if we do so we will have to it manually on every object (more than ~200) which is not an option for me. Can you please help me with this problem ?