The following options are available:
| Edit | Right-click on a revision in the table and select Edit in the menu to edit the ADOM revision. See To edit an ADOM revision:. | |
| Delete | Right-click on a revision in the table and select Delete in the menu to delete the ADOM revision. See To delete ADOM revisions:
When Lock this revision from auto deletion is selected, you are not able to delete the ADOM revision. |
|
| Restore | Right-click on a revision in the table and select Restore in the menu to restore the ADOM revision. Restoring a revision will revert policy packages, objects and VPN console to the selected version. Select OK to continue. See To restore a previous ADOM revision:. | |
| Lock | Right-click on a revision in the table and select Lock in the menu to lock this revision from auto deletion. See To lock or unlock an ADOM revision:. | |
| Unlock | Right-click on a revision in the table and select Unlock in the menu to unlock this revision. When the ADOM revision is in an unlocked state, auto deletion will occur in accordance with your auto deletion settings. See To lock or unlock an ADOM revision: | |
| View Revision Diff | Right-click on a revision in the table and select View Revision Diff in the menu. The Summary page will be displayed. This page shows the revision differences between the selected revision and the current database. See “Policy & Objects” on page 374. | |
| Select All | Right-click on a revision in the table and select Select All in the menu. You can then select to Delete all unlocked ADOM revisions. | |
| Create New | Select to create a new ADOM revision. | |
| Close | Select to close the ADOM Revision dialog box and return to the Policy & Objects tab. | |
To create a new ADOM revision:
- Go to the Policy & Objects tab and select Tools > ADOM Revisions in the toolbar. The ADOM Revisions window opens.
- Select Create New. The Create New ADOM Revision dialog box opens.
Create new ADOM revision
- Type a name for the revisions in the Name
- Optionally, type a description of the revision in the Description
- To prevent the revision from being automatically deleted, select Lock this revision from auto deletion.
ADOM revisions
- To configure the automatic deletion of revisions, select [Details]. See “Policy & Objects” on page 373.
- Select OK to create the new ADOM revision.
To edit an ADOM revision:
- Open the ADOM Revisions window and either double-click on the revision, or right-click on the revision and select Edit from the menu. The Edit ADOM Revision dialog box opens.
- Edit the revision details as required, then select OK to apply your changes.
To delete ADOM revisions:
- Open the ADOM Revisions
- To delete a single revision, right-click on the revision and select Delete from the menu.
- To delete multiple revisions, use the Control or Shift keys on your keyboard to select multiple revisions, or rightclick on a revision and select Select All from the menu to select all of the revision. Then, right-click on any one of the selected revisions and select Delete from the menu.
Select OK in the confirmation dialog box to delete the selected revision or revisions.
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 ?