To configure automatic deletion:
- Open the ADOM Revisions
- Right-click on any revision in the table and select Edit from the menu.
- In the Edit ADOM Revision dialog box select [Details]. The Configuration dialog box opens.
ADOM revision deletion configuration
- To enable to automatic deletion of revisions, select Auto Delete Revisions.
- Select one of the two available options for automatic deletion of revisions:
- Keep last x Revisions: Only keep the entered numbered of revisions, deleting the oldest revision when a new revision is created.
- Delete revision olderthan x Days: Delete all revisions that are older than the entered number of days.
- Select OK to apply the changes, then select OK again in the Edit ADOM Revision dialog box.
To restore a previous ADOM revision:
- Open the ADOM Revisions
- Right-click on a revision in the table and select Restore from the menu. A confirmation dialog box will appear.
- Select OK to continue.
The Restore Revision dialog box will appear. Restoring a revision will revert policy packages, objects and VPN console to the selected version.
Restore Revision
- Select OK to continue.
To lock or unlock an ADOM revision:
- Open the ADOM Revisions
- Do one of the following:
- Right-click on a revision in the table and select Lock or Unlock from the menu.
- Edit the revision and select or deselect Lock this revision from auto deletion from the Edit ADOM Revision dialog box. See To edit an ADOM revision:. The ADOM revision is locked.
To view ADOM revision diff:
- Open the ADOM Revisions
- Right-click on a revision in the table and select View Revision Diff from the menu. The Summary page will load.
ADOM Revision Diff
This page displays all Policy Package and Policy Object changes between the revision selected and the current database.
- Select [Details] to view all details on the changes made to policies and objects.
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 ?