Removing a DC will not completey remove that from AD Metabase, you have got to remove that either using NTDSUTIL from command line or ADSIEDIT, GUI. Its all there in MS KB.
I have no idea of how to remove that from authorized DHCP Servers.
Cheers,
Athif
-----Original Message-----
From: Graham Turner [mailto:[EMAIL PROTECTED]]
Sent: Monday, July 12, 2004 9:35 PM
To: [EMAIL PROTECTED]
Subject: [ActiveDir] a bit of AD admin
just wanted to run this by the mailing list
i know there to be a whole raft of objects left behind in the directory after unorderly shutdown of DC
however even in an orderly demotion seems there is a server object left behind at;
CN=servername.,CN=servers,CN=site,CN=configuration,DC=xxxx
i assume we are safe to delete this and there are no AD dependencies on this object - if there are begs the question why it has been left behind ???
on a similar (perhaps ?) vain i have now contrived to get a couple of "duplicate" local groups "DHCP Users CNF ...." and ditto for "DHCP ADministrators CNF ..."
seems a bit of a coincidence that the server i have removed was a DHCP server
is it that the server has not been removed from the list of authorised DHCP servers that these groups have appearred
GT
-----------------------------------------------------
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom/which they are addressed. If you have received this email in error please notify the system manager at the following email address: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Al Faisaliah Group. Internet communications cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, arrive late or contain viruses. The sender therefore does not accept liability for any errors or omissions in the context of this message, which arise as a result of Internet transmission. Finally, the recipient should check this email and any attachments for the presence of viruses. Al Faisaliah Group accepts no liability for any damage caused by any virus transmitted by this email.
-----------------------------------------------------
