DC demotion question - AD cleanup

G

gm

I have a Windows 2003 SP1 domain running in Win2k mode. It's an upgrade
from NT to Win2k, then to Win2k3 - I did it by the book 3 months ago: I ran
all required diagnostics first - were OK, did forestprep and domainprep -
worked fine, then upgraded the main DC from Win2k to Win2k3. Everything
worked beautifully. I did not upgrade a second DC at this time. I set up a
new W2k3 SP1 server and promoted it to be a new DC. Then I moved all forest
and domain roles from the old PDC to the new one. Worked fine. I gave it a
few weeks, everything worked fine, then I demoted the old PDC. Worked
great, removed itself from Domain Controllers container to Computers
container, removed itself from DNS zones. The network works great, is
stable, etc. I also have Exchange 2003 Ent. in this site, but I nothing in
its config is pointing to the old PDC.

I want to remove the old PDC object from AD. I shut down the server,
removed from rack. Then I wanted to delete it in AD, got a message, that
the object is a container, contains other objects, etc. So I googled the
message and followed the article here:
http://www.jsifaq.com/subL/tip5800/rh5890.htm. There were no objects under
the OldSErver object in AD Sites & Services. I deleted the server object
without any errors or warnings. It's been a few days since then. But when
I go back to the Computers container in AD and try to delete the OldServer
object, I am still getting the message that the object is a container,
contains other objects, etc.

Is it safe to delete it? Any tests I need to run to verify?

I appreciate pointers to articles or direct advice,
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top