Checking Win2K AD Functionality

  • Thread starter Thread starter M P
  • Start date Start date
M

M P

Hi!

I am from WinNT domain and migrated to Win2K AD Domain, years ago. I have 2
Win2K DC (DC01 and DC02) and I am now planning to retire the first W2K
Domain on my network so I've transferred all Operations Master to new
machine (DC03). I now have 3 DCs, and still uneasy if I will not encounter
problem if I will remove the 1st DC of my domain. What is the best way to
remove DC to the network? is it dcpromo? How can I check that all roles from
the 1st DC was already transferred and will not encounter problem? I need
your help.

MP
 
netdom query fsmo will tell you the FSMO role holders.
DCPROMO is your way to go to demote the DC.
 
if all roles are already on my new server, does it mean I can demote the
first W2K AD?

Just to double check so that i will not encounter problem when I execute the
demotion.

MP
 
From an AD perspective, this will suffice.

M P said:
if all roles are already on my new server, does it mean I can demote the
first W2K AD?

Just to double check so that i will not encounter problem when I execute the
demotion.

MP
Click to expand...
 
M P said:
if all roles are already on my new server, does it mean I can demote the
first W2K AD?

Just to double check so that i will not encounter problem when I execute
the demotion.
Click to expand...

It's about more than roles. First, make sure you have a GC
(or all DCs are GCs in a small or single domain forest.)

Also make sure you have DNS covered. While DNS is not
(always) technically part of being a DC it is common for the
DC to also be the DNS Server (or even an AD Integrated DNS
server) and AD is dependent on DNS.

Make sure you DNS is correct and functionally without the
departing DC. Make sure all "DNS Clients" no longer point
to that DNS server if it is to be removed.

Also, keep telling yourself, "DCs are DNS clients too!!!".
 
Back
Top