Hi All
Oh Wow, I don't even know where to start, but I'll try to explain my predicament.
I have a forest root called holdingco.int . Then I have a subdomain calledsap.holdingco.int . I then have separate trees called ccs.africa andccs.asia (this domain is to be decommissioned though, so not included in this example ) Here is my logical structure:
Indside the sap.holdingco.int domain, I have a conflicting crossref object because of a botched DC demotion about 5 years ago ( before I started working here ). Someone apparently ticked the box "This is the last DC in the domain" and realised their mistake and stopped the demotion before it completed....or so the story goes. The domain functions OK at the moment, and there is only ONE Global Catalog in this domain. There are other GC's from other domains in the same site, so no train smash ..yet
They now want me to try and fix the conflicting crossref object because I cannot bring any new GC's intosap.holdingco.int due to the broken crossref. I did a Semantec Database Analysis with a go fix and this converted the mangled crossref back to the way it should be, but it seems that the conflict comes back as soon as the Infrastructure master updates itself.
I have cloned the holdingco.int and sap.holdingco.int domain controllers to an isolated environment on Vmware to do some tests, and what I have basically done was to disable replication between all DC's in sap, then did the fixup, restarted and kept replication disabled ( both ways ). After a few minutes, the Infrastructure master shows theccs.africa ncName as conflicting, however this ncName is still intact on the other DC's, Proving that the source of the conflict is coming from the Infrastructure Master.
Even if I move the IM FSMO role to another DC and do the fix all over again, the DC with the IM FSMO role always conflicts first, and this then gets replicated out to the other DC's insap.holdingco.int.
Note, neither ccs.africa, nor holdingco.int has this conflict on the partitions node if I look at it through adsiedit.
I assume there are still references in sap.holdingco.int somewhere that causes the conflict, but I just cannot see how this can be fixed. I have NO healthysap.holdingco.int backup to fall back on, so I cannot even do an authoritative restore.
I'm taking a long shot here, and I hope someone may be able to help me before I will be forced to log a ticket with MS. Here is a screenshot of where the issue lies :
Thanks in advance for your help.
Pieter