Hello everyone.
One of the RODC has a "ghost" site object under AD Sites and Services.
This RODC has been problematic from start. After running some scheduled replication tests I found that the site where RODC resided had invalid ntds data. You could tell that the object was corrupt. So I moved the RODC temporarily into another site, deleted the bad site, created a new site with the same name, linked it to the subnet, and threw the RODC back into it.
All changes were performed on the root domain FSMO DC.
Then I let the replication take care of the rest. All 20 domain controllers across the whole forest have replicated the change successfully. When I checked AD Sites and Serives on the RODC there were problems:
There was a good site object created and RODC was in it. So replication worked. But the new site name was altered (ex: instead of SITE7 it was SITE7:fc:3a:13:01:dc and so on...)
Then I noticed that the old bad site object SITE7 was still present. This time it didn't have any NTDS in it. Just an empty container. But this explained why the new object name was automatically altered - two objects with the same name.
So to avoid problems with that weird name and potential name conflict I went back onto root domain fsmo and recreated the good site again, and named it SITE7-2. So now all my domain controllers have one site SITE7-2 with RODC in it.
But the RODC has 2 sites. SITE7 - "ghost" and SITE7-2.
Replication to this RODC works fine but the ghost object doesn't go away.
All DC's are Windows Server 2008.
Thanks!