Replace Win2000 PDC with Win2003 PDC

[seands]

Hi All

I need some help with setting up the following.

Here is a list of our active directory servers.

1. PDC running Win2000, which is also Primary DNS server
2. Exchange 2003 on Win2003 server

we also have the following

3. BDC running WinNT4 SP4, which is our DHCP and Primary WINS

we have no secondary DNS or WINS servers, but I can set these up if it helps

I want to decommission server 1 and 3, and move all the above services to one new server running 2003 server, which I already have. But is there a best way to proceed as I was thinking of doing the following.

Setup the new server and run dcpromo
Setup a secondary DNS server, and add the entry to all client pc's
Run dcpromo to demote server 1 and power off.
Setup the new server as our Primary DNS, and change the entry on client’s pc's to the new primary DNS.
Switch off server 3, and setup DHCP on the new server
Then setup the new server as the primary WINS.

Not sure if the above sounds okay, but would like a second opinion

Thanks
Sean

 

[PatWilson]

I am assuming from your description above, that the Exchange 2003 server is a domain controller, and that your Windows 2000 server holds all the FSMO roles (PDC emulator, Schema Master, Operations Master, Infrastructure Master) - correct?
I am also assuming the you have run the 'adprep /forestprep' and 'adprep /domainprep' and 'adprep /gpprep' commands from a Windows Server 2003 SP1 CD to update the schema to receive a Windows server 2003 domain controller - correct?

MAKE SURE YOU DO FURTHER RESEARCH ON MICROSOFT's TECHNET SITE FOR MORE DETAILED INFORMATION BEFORE COMPLETING THE SEQUENCE BELOW !!

Not complete instructions, but a sequence to follow:
01) Install Windows Server 2003 on your new system, but do NOT run dcpromo yet.
02) Install DNS, WINS, and DHCP on your new server.
03) Set all DNS zones as Active Directory integrated on the Win2000 server (if you have not done so already).
04) Export your DHCP database from NT4 server, and import it to the new Windows 2003 server. Disable DHCP on NT4 server.
05) Set up replication of WINS to the new Windows 2003 server.
06) Run dcpromo on new Windows Server 2003 to make it a domain controller.
07) Update DHCP to point to the new server for both DNS and WINS.
08) Move all FSMO roles to the new Windows Server 2003 domain controller.
09) Shut down the Windows NT4 BDC.
10) Run dcpromo to demote the Windows 2000 server to a domain member.

Assuming there are sufficient free resources, I suggest that you add the DNS and WINS services to your Exchange 2003 server, and configure it as the secondary on your clients. The Exchange server should look at itself for DNS to reduce workload on the 'primary'. Otherwise your 'primary' will be a single-point-of-failure. Even with a second domain controller (the Exchange Server), everything will grind to a halt without a source for DNS and WINS resolution if the 'primary' is shut down.

Good Luck !!

 

[markdmac]

Step 6A Set the new server as a Global Catalog.
Step 6B Wait for AD Replication. Verify replication in logs.

I hope you find this post helpful.

Regards,

Mark

 

[seands]

Hi

Thank you for the help, this is definitely helping me in the right direction.

Sean

 

[58sniper]

In addition to Pat Wilson's tips:

00. If you have Exchange 2000 in your AD, prevent attribute

http://support.microsoft.com/kb/314649

00a. Run ADPREP:

http://technet2.microsoft.com/WindowsServer/en/Library/aaa295b8-1123-4bc4-9ffc-3b3bcf7202251033.mspx

04. Move DHCP

http://support.microsoft.com/kb/325473

05. If you're using all Win32 machines, WINS isn't needed.

06a. Move the Global Catalog server:

http://support.microsoft.com/kb/313994

08. Move the FSMO roles

http://support.microsoft.com/kb/324801

Pat Richard, MCSE(2) MCSA:Messaging, CNA(2)