Server Nearly Dead

  • Thread starter Thread starter Graham
  • Start date Start date
G

Graham

Hi All
I need a bit of advice in how to approach removing a DC with AD from the
Domain and installing another.

The story is I have 2 DC replicating AD atm and a 2000 Member server that i
want to up grade to AD.
The existing AD servers are called "Server" and "File Server" The member
server is called "appsserver"
Server is about to drop its HDD (I carnt even ghost it as i keep, getting IO
errors)

I have transferred most main services over to fileserver.

I would like to know what is the best way to approach this ie:
dcpromo "server" first and then dcpromo "appsserver" to replicate with
"fileserver".
or
dcpromo "appsserver" first so a have 3 DC then dcpromo 'server" (this way
sounds safer to me)

Which ever way I do it ,is there anything I should know about that could be
a trap for the unknowing.

thanks for your help. :)
 
I would first promote another server to DC, and then proceed with DC
demotion. To be on the safe side, do a netdom query fsmo to see which server
is holding your FSMO roles. If they are held on a dying server, then
transfer them to another one. After that you can de-dcpromo your dying
server. Don't forget to transfer DNS server and change clients IP addresses
if the dying server was also a DNS server.

--
Regards

Matjaz Ladava, MCSE (NT4 & 2000), Windows MVP
(e-mail address removed)
http://ladava.com
 
I asked basically the same question you are asking in the
last few days. The answers given worked perfectly.
Basically, if the dying server is your original "First" AD
server, it holds the 5 FSMO roles and your Global Catalog
(GC). You have to transfer the 5 FSMO roles to the other
server that is still working. You then have to move your
GC to the other server. You can then use dcpromo to
remove AD from the dying server. The answers I was given
referred to specific KB TIDs that were perfect, step-by-
step descriptions of what to do.
 
Back
Top