Remove a policy package or folder
To remove a policy package or folder, right-click on the package or folder name in the policy package pane and select Delete from the menu.
Rename a policy package or folder
To rename a global policy package or policy package folder, right-click on the package or folder name in the policy package pane and select Rename from the menu. Type the new name for the global policy package or policy package folder in the dialog box and select OK.
To rename a local policy package, right-click on the policy package and select Rename. Type the new name (or edit the current name) in the Name field of the Rename dialog box and select Apply.
Assign a global policy package
Global policy packages can be assigned, or installed, to specific ADOMs.
To assign a global policy package:
- Select Global from the drop-down ADOM list and select the policy package in the Global Policy Package tree menu.
- Select Assignment in the Policy Package tab bar to view the ADOM assignment list.
- If required, select Add ADOM from the content toolbar to add an ADOM to the assignment list.
- Select the ADOM you would like to assign from the list, or select Select All from the toolbar to select all of the ADOMs in the list.
- Select Assign Selected from the content toolbar. The Assign dialog box opens.
Assign dialog box
- Select whether you want to assign only used objects or all objects, and if policies will be automatically installed to ADOM devices.
- Select OK to assign the policy package to the selected ADOM or ADOMs.
Install a policy package
To install a policy package to a target device:
- Select the specific ADOM that contains the policy package you are installing from the drop-down list in the toolbar.
- Right-click on a policy package or folder in the Policy Package
- Under the Policy Package heading in the menu, select Install Wizard. The install wizard opens.
- Follow the steps in the install wizard to install the policy package. You can select to install policy package and device settings or install the interface policy only.
For more information on the install wizard, see Install wizard. For more information on editing the installation targets, see Edit the installation targets for a policy package.
Reinstall a policy package
To reinstall a policy package to a target device:
- Select the specific ADOM that contains the policy package you are installing from the drop-down list in the toolbar.
- Right-click on a policy package or folder in the Policy Package
- Under the Policy Package heading in the menu, select Re-install. The policy package will be reinstalled to the target device.
Having trouble configuring your Fortinet hardware or have some questions you need answered? Check Out The Fortinet Guru Youtube Channel! Want someone else to deal with it for you? Get some consulting from Fortinet GURU!
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 ?