Title: New DC with old DC name...
Usually this happens when your demotion takes place within a remote site and the computer account is still registers in your pdce?
 
When this happens joining the computer to the domain usually gives lots of errors - one of it is during joining "User already exist" error or it could be the dropout issues you mentioned. It is in my environment at least..
 

Thank you and have a splendid day!

 

Kind Regards,

 

Freddy Hartono

Group Support Engineer

InternationalSOS Pte Ltd

mail: [EMAIL PROTECTED]

phone: (+65) 6330-9785

 

 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of RM
Sent: Saturday, February 25, 2006 12:19 PM
To: [email protected]
Subject: [ActiveDir] New DC with old DC name...

Got some weirdness here....

We decided to nuke-n-pave a 2000 DC and bring it back up as 2003.  I DCPROMO'd it down to a member server and shut it down.  I deleted its computer account and DNS records.  I checked the dc _msdcs gc tcp blah blah DNS records to verify that there was no trace of this old DC and that the appropriate DC's were providing site coverage in the interim (they were).

I then formatted it, installed 2003, named it with the old DC name, and joined it to the domain.  That's when the trouble started.  First the computer account was spontaneously deleted.  I joined it again and saw dnsapi, netlogon, and userenv errors in the event log.  %LOGONSERVER% was the wrong DC and gpresult was giving the wrong site name.  I then lost the computer account again.

I finally gave up and selected a new name for the machine and all was well.

I had thought that after a successful downward DCPROMO, all traces of the old system would be gone from AD.  What step did I miss?

RM

Reply via email to