Deleting a demoted DC from AD Sites and services

[Danny Sanders]

I was going through the process of replacing a DC at a remote site. I needed
to keep the same server name so I demoted the DC and renamed it. Then I went
to AD Sites and services to delete the server from there.

The first time I selected delete I got a message about this may take some
time, something about the number of objects that need to be deleted, I can't
recall exactly what it said.
Not being totally sure what was going on or what was to be delete, I
canceled. Later I went back to delete it again and this time the NDIS
settings was *not* listed when I highlighted the server this time. I
selected delete. This time there was no message about it taking a long time,
and the server deleted immediately.

Obviously replication had occurred and it now sow the server as a member
server no a DC.


The question is what would have happened if I had deleted the server the
first time when I got the message about it taking a long time?

I've got the new server up and taking the old server's place and it seems to
be functioning correctly. What would have happened if I deleted it the first
time? Is there cleanup I need to do? Was I right to wait for replication
then delete?

TIA
DDS

 

[Herb Martin]

I was going through the process of replacing a DC at a remote site. I
needed to keep the same server name so I demoted the DC and renamed it.
Then I went to AD Sites and services to delete the server from there.

The first time I selected delete I got a message about this may take some
time, something about the number of objects that need to be deleted, I
can't recall exactly what it said.
Not being totally sure what was going on or what was to be delete, I
canceled. Later I went back to delete it again and this time the NDIS

settings was *not* listed when I highlighted the server this time. I
selected delete. This time there was no message about it taking a long
time, and the server deleted immediately.

Obviously replication had occurred and it now sow the server as a member
server no a DC.

Makes perfect sense. Generally you shouldn't need to delete
anything in Sites and Services for such.

The question is what would have happened if I had deleted the server the
first time when I got the message about it taking a long time?

I don't know. I don't do that. I don't recommend that.

Do a proper DCPromo (online while DNS is working) and let the
Server plus AD get it right.

Let it replicate.

Rename the server and make sure it's account gets replicated.

Should be done.

(Add new server or rename existing one etc.)

I've got the new server up and taking the old server's place and it seems
to be functioning correctly. What would have happened if I deleted it the
first time? Is there cleanup I need to do? Was I right to wait for
replication then delete?

If you do it, let us know <grin>

--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

TIA

 

[Danny Sanders]

Makes perfect sense. Generally you shouldn't need to delete

anything in Sites and Services for such.

I'm fairly new here and the last time they did this (replace a DC with one
with the same name) they said there were problems with remnants in DNS. Not
totally sure what they were talking about but it had something to do with
collisions? I was not here so I'm not sure where they saw the remnants, but
one of the last times they did this they deleted the object from ADS&S and
those remnants and the DNS issues did not happen. Naturally they
incorporated this step in their process.

If you do it, let us know <grin>

So far those issues have not surfaced. Seems to be working just fine and I
can't see anything wrong with DNS.
I'm guessing if you are going to delete, wait till replication!

Thanx
DDS

I was going through the process of replacing a DC at a remote site. I
needed to keep the same server name so I demoted the DC and renamed it.
Then I went to AD Sites and services to delete the server from there.

The first time I selected delete I got a message about this may take some
time, something about the number of objects that need to be deleted, I
can't recall exactly what it said.
Not being totally sure what was going on or what was to be delete, I
canceled. Later I went back to delete it again and this time the NDIS

settings was *not* listed when I highlighted the server this time. I
selected delete. This time there was no message about it taking a long
time, and the server deleted immediately.

Obviously replication had occurred and it now sow the server as a member
server no a DC.

Makes perfect sense. Generally you shouldn't need to delete
anything in Sites and Services for such.

The question is what would have happened if I had deleted the server the
first time when I got the message about it taking a long time?

I don't know. I don't do that. I don't recommend that.

Do a proper DCPromo (online while DNS is working) and let the
Server plus AD get it right.

Let it replicate.

Rename the server and make sure it's account gets replicated.

Should be done.

(Add new server or rename existing one etc.)

I've got the new server up and taking the old server's place and it seems
to be functioning correctly. What would have happened if I deleted it the
first time? Is there cleanup I need to do? Was I right to wait for
replication then delete?

If you do it, let us know <grin>

--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

TIA

DDS

 

[Herb Martin]

I'm fairly new here and the last time they did this (replace a DC with one
with the same name) they said there were problems with remnants in DNS.

First, that's DNS not Sites and Services or the general AD database.

Second, if they had done it correctly (online DCPromo) this probably
would not have happened either.

People frequently do things wrong without noticing, see undesirable
results and then invent superstitious reasons that they pass on too
others --

Not totally sure what they were talking about but it had something to do
with collisions? I was not here so I'm not sure where they saw the
remnants, but one of the last times they did this they deleted the object
from ADS&S and those remnants and the DNS issues did not happen. Naturally
they incorporated this step in their process.

Well, deleted extraneous records in DNS is never a big deal anyway
so if this ever does happen you can always just clean that up. DNS is
not nearly as sensitive a database as AD.

So far those issues have not surfaced. Seems to be working just fine and I
can't see anything wrong with DNS.
I'm guessing if you are going to delete, wait till replication!

When you think you are finished, run DCDiag on ALL DCs.
(This is a good thing to do on a regular bases, and especially
before and after any changes.)

DCDiag in your friend (See: Support Tools on the Server CDROM.)

--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

Thanx
DDS

I was going through the process of replacing a DC at a remote site. I
needed to keep the same server name so I demoted the DC and renamed it.
Then I went to AD Sites and services to delete the server from there.

The first time I selected delete I got a message about this may take
some time, something about the number of objects that need to be
deleted, I can't recall exactly what it said.
Not being totally sure what was going on or what was to be delete, I
canceled. Later I went back to delete it again and this time the NDIS

settings was *not* listed when I highlighted the server this time. I
selected delete. This time there was no message about it taking a long
time, and the server deleted immediately.

Obviously replication had occurred and it now sow the server as a member
server no a DC.

Makes perfect sense. Generally you shouldn't need to delete
anything in Sites and Services for such.

The question is what would have happened if I had deleted the server the
first time when I got the message about it taking a long time?

I don't know. I don't do that. I don't recommend that.

Do a proper DCPromo (online while DNS is working) and let the
Server plus AD get it right.

Let it replicate.

Rename the server and make sure it's account gets replicated.

Should be done.

(Add new server or rename existing one etc.)

I've got the new server up and taking the old server's place and it
seems to be functioning correctly. What would have happened if I deleted
it the first time? Is there cleanup I need to do? Was I right to wait
for replication then delete?

If you do it, let us know <grin>

--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

TIA

DDS