How to replace a domain controller

[Guest]

I have a customer with a Windows 2000 domain - just one server and it is the
domain controller. The server is failing but, with the aid of several big
fans, is managing to limp along for today. A replacement motherboard is not
available so we are getting a new server.

It is my intention to install Windows 2000 on the new server, promote it to
be a domain controller, install their apps and restore their data, and then
remove the old domain controller.

What do I need to do to make sure the new domain controller is the master
and that I can totally remove the old server? Any links? Answers? Any help
at all would be greatly appreciated.

Dale

 

[Danny Sanders]

See:
http://support.microsoft.com/kb/555549/en-us

hth
DDS

 

[Guest]

Thanks, Danny, for the reply.

I had previously looked at that article but it specifically states that the
server must be running Windows Server 2003 or newer for those instructions.
I was hoping there would be something similar for Windows 2000 Server.

If there is nothing for Windows 2000 Server, are the basic steps the same?
If the basic steps are the same, the statement about the article only
referring to Windows Server 2003 or newer may only apply to the specifics of
each step. Do you know if this is the case?

Thanks,

Dale
--
Dale Preston
MCAD C#
MCSE, MCDBA

See:
http://support.microsoft.com/kb/555549/en-us

hth
DDS

 

[Danny Sanders]

From what I see in the article these steps should work with 2 Win 2k
servers.

Step 4 is about how to Integrate Windows Server 2003 DNS with an Existing
DNS Infrastructure. If you install DNS on the new server and set the DNS
zone to AD integrated the DNS info will replicate to the new server.

Step 10 mentions the Win 2k3 Print migrator. You can just install the
printers on the new server.


hth
DDS

Thanks, Danny, for the reply.

I had previously looked at that article but it specifically states that
the
server must be running Windows Server 2003 or newer for those
instructions.
I was hoping there would be something similar for Windows 2000 Server.

If there is nothing for Windows 2000 Server, are the basic steps the same?
If the basic steps are the same, the statement about the article only
referring to Windows Server 2003 or newer may only apply to the specifics
of
each step. Do you know if this is the case?

Thanks,

Dale

 

[Harj]

From what I see in the article these steps should work with 2 Win 2k
servers.

Step 4 is about how to Integrate Windows Server 2003 DNS with an Existing
DNS Infrastructure. If you install DNS on the new server and set the DNS
zone to AD integrated the DNS info will replicate to the new server.

Step 10 mentions the Win 2k3 Print migrator. You can just install the
printers on the new server.

hth
DDS









- Show quoted text -

Hi,

On the Active Directory side, this should be not a problem what so
ever.
Point the new server to the old DC for primary DNS and promote it to a
Domain controller.
Make sure we install DNS on this new server as well and point it to
itself for secondary DNS, making the DNS AD integrated.
Wait for replication between the two machines....now, you have two
domain controllers in the environment
You will then want to transfer the 5 FSMO roles over to the new DC as
well as make this new DC a Global Catalog server.
Once you are comfortable that there are no errors on either machine
point the new DC to itself for primary DNS and run the following
ipconfig /flushdns & ipconfig /registerdns & net stop netlogon & net
start netlogon.

You are now ready to dcpromo the old machine down to a server. Mind
you you still have to deal with the other applications the users
share.
Remember to point your clients to the new DNS/DC for DNS

Using Ntdsutil.exe to transfer or seize FSMO roles to a domain
controller
http://support.microsoft.com/kb/255504

Good luck

Harj Singh
Power Your Active Directory Investment.
www.specopssoft.com