Remove pendent forest update using ADSI Edit

  • Thread starter Thread starter salva.gomez
  • Start date Start date
S

salva.gomez

Hi all,
last week we tried to add a secondary DC in a child domain and we got
an error. All seems to work fine in the DCPROMO operation but after
restart the server we cannot open the DNS (it was installed but it is
integrated in the AD) and users cannot login using this server.
The person who was doing this task decided to do other DCPROMO to
demote the new DC.
Now i'm checking if there's some "trash" after the demotion and i see
this in the ADSIEdit Configuration Container option (connected to the
domain that will have a secondary dc)

LDAP://childdomain/CN=a8999867-78b8-402c-84ea-7b79a1d2627e,CN=Operations,CN=ForestUpdates,CN=Configuration,DC=mycompany,DC=org


If I get the properties i can see in the security tab that the
CHILDDOMAIN's administrators have rights on it. I this it is the first
promoting attemp and i cannot be "updated"

I think : if I delete it and try again the promotion it will work,
but...i'm not sure.
What do you think?

I've connected to other child domain (also my parent domain) and i can
see the same operation.
It is a PENDENT UPDATE, isn't it?

Thanks a lot

Salva.
 
Sorry. I forgot to say all DCs in the domain ( childs and parent) have
Windows 2000

Thanks
 
If you have done a demotion and you are unsure if there are any lingering
objects you should be able to follow the metadata cleanup procedure to
validate that everything is clean.

Metadata cleanup
http://support.microsoft.com/default.aspx?scid=kb;en-us;216498

--
Paul Bergson
MVP - Directory Services
MCT, MCSE, MCSA, Security+, BS CSci
2003, 2000 (Early Achiever), NT

http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup
This posting is provided "AS IS" with no warranties, and confers no rights.
 
Back
Top