nasty Bug with FortiManager and global Addressobjects

[sw2090]

We just ran into this issue and I just wanted to warn you to not do so too:

if you rename global address objects in FMG you can only do that via script (TAC said this).

If you assign this to an adom afterwards it will be correctly assigned.

You will have the renamed object in the adom and if you right-click that object and choose "where used" it will show you the correct references.

However if that is a policy and you edit that policy the corresponding field will be empty. 

You will not be able to deploy policy package until you correct that because it will fail because of the empty fields in your policies.

This at least affects global address objects. Cannot say about service objects as we haven't checked that yet and upon deployment it didn't complain about services.

Accoarding to TAC this is a known Bug that at least affects FMG v7.0 (cannot say anything about 7.2 or 7.4).

This also let's me wonder why TAC suggests renaming global objects by script when they know there is a nasty bug with that.

I still have a Ticket and a case open (which now got Priority C1!) with TAC and am waiting for news.

[boneyard]

i was using the global address of course (it had references), so the issue seems solved.