Make sure you move all roles (GC, FSMO) and services (DHCP, WINS, DNS, DFS,
etc.) to other DCs or servers.
Also think how the DC to be removed is used by other servers and clients.
After determining and moving roles and services DEMOTE the DC to a member,
remove the member server from the domain, delete computer account

If that DC hosts FSMO roles, move them manually as that is a best practice
because then YOU determine where the FSMO roles end up!

Want to be sure what happens if the server is gone? Do your work as
mentioned above, then shutdown the server for a week. If nothing or nobody
starts shouting, restart the DC and demote it

--

Cheers,
(HOPEFULLY THIS INFORMATION S YOU!)

# Jorge de Almeida Pinto # MVP Windows Server - Directory Services

BLOG --> http://blogs.dirteam.com/blogs/jorge/default.aspx
-----------------------------------------------------------------------------
* This posting is provided "AS IS" with no warranties and confers no rights!
* Always test before implementing!
-----------------------------------------------------------------------------


-----------------------------------------------------------------------------
"M P" <mark@textguru.ph> wrote in message
news:ulvvBN6UGHA.4900@TK2MSFTNGP12.phx.gbl...
> 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 .
>
> MP
>