Skip to main content
agrakov
Staff
Staff
April 14, 2025

Troubleshooting Tip: Global ADOM – Installation failed because of a duplicate UUID

  • April 14, 2025
  • 0 replies
  • 827 views
Description This article describes how to resolve Global ADOM installation failure due to duplicate UUIDs with instructions on how to regenerate a UUID.
Scope FortiManager.
Solution

A Global CLI script can regenerate the UUID of all addresses and groups by unsetting it.

  1. Dump the global firewall.address and firewall.addrgrp tables in the CLI to file:


execute fmpolicy print-adom-object Global 140 all

140 "firewall address"

execute fmpolicy print-adom-object Global 142 all
142 "firewall addrgrp"

For example:

 

agrakov_0-1744633497897.png

 

  1. Run a regex replace operation in notepad++ like the following:


FIND: ^set uuid.*$
REPLACE: unset uuid

agrakov_1-1744633497898.png

 

  1. Use the final text to create a CLI script in the Global GUI.

agrakov_2-1744633497901.png

 

agrakov_3-1744633497901.png

 

Run a script on the policy package.

 

agrakov_4-1744633497902.png

 

Check for a new UUID:

 

Old UUID:

 

agrakov_5-1744633497903.png

 

New UUID:

 

agrakov_6-1744633497905.png

 

  1. Assign a Global policy again. Go to Assignment -> Action -> Assign.
    Virtual event | September 2026. SASE summit. The age of autonomous trust. Register here!