2003 server upgrade new hardware

[3rdJoey]

Current setup

Server 1 DC 2000 standard (DHCP)(DNS)(WINS) Currently holds all 5 fsmo rolls

Server 2 DC 2000 standard

Server 3 2000 member server Exchange 2000

Server 4 2003 Standard R2 Member server
Server 5 2003 Standard R2 Member server

We want to promote the 2003 R2 servers to DC's

Current Plan of action

Put 2003 R2 cd in Server 1
Run D:\i386\adprep.exe /forestprep
Run D:\i386\adprep.exe /domainprep
Run DCPROMO on Server 1
Run DCPROMO on Server 2
Move 5 fsmo rolls to server 1

We plan on keeping the exchange 2000 active for at least 3 months. Is that ok?

Can anyone explain how to migrate dns/dhcp/wins?

I really appreciate any help

Thanks

 

[LWComputingMVP]

You are essentially upgrading your domain to Windows Server 2003 Active Directory. I have several links and checklists I would suggest you run through. Keep in mind, a site really only needs 2 DC (unless you some HUGE, HUGE company).

Here are some links that should get you going for upgrading a 2000 domain to 2003:

Common Mistakes When Upgrading a Windows 2000 Domain To a Windows 2003 Domain

http://support.microsoft.com/default.aspx?scid=kb;en-us;555040

How to upgrade Windows 2000 domain controllers to Windows Server 2003

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

[If using R2 release of Windows 2003] Extending Your Active Directory Schema for New Features in Windows Server 2003 R2

http://www.microsoft.com/downloads/...03-84DD-480F-98F9-526EC09E9BA8&displaylang=en

Hotfixes to install before you run adprep /Forestprep on a Windows 2000 domain controller to prepare the Forest and domains for the addition of Windows Server 2003-based domain controllers

http://support.microsoft.com/?kbid=331161

Commodore.ca | Windows | How To Upgrade Windows 2000 Domain to Windows 2003 Server
Quote from the top of this article: "Several glossy Microsoft presenters have stated that all you need to do to complete a Windows 2003 Domain upgrade is run ADPREP and then upgrade away. This may work for very small / simple environments but it is definitely not good advice for most companies. After upgrading five servers in two unrelated domains and installing many fresh copies of 2003 I can say that I personally would not skip a single step in the process I have developed below."

http://www.commodore.ca/windows/windows_2003_upgrade.htm

Windows Server 2003 Upgrade Assistance Center

http://www.microsoft.com/windowsserver2003/upgrading/nt4/upgradeassistance/default.mspx

Here are some links that should help you in replacing existing domain controllers and/or transferring services and Active Directory functions to another/new system:

How can I transfer some or all of the FSMO Roles from one DC to another?

http://www.petri.co.il/transferring_fsmo_roles.htm

How To Create or Move a Global Catalog in Windows 2000

http://support.microsoft.com/?kbid=313994

How to move a DHCP database from a computer that is running Windows NT Server 4.0, Windows 2000, or Windows Server 2003 to a computer that is running Windows Server 2003

http://support.microsoft.com/?id=325473

How can I move a DHCP database from one server to another?

http://www.windowsitpro.com/Article/ArticleID/13473/13473.html

How can I move DNS from one Windows 2000 Server to another Windows 2000 Server?
(Two Related if going 2000 to 2003 - read both before moving)

http://www.jsifaq.com/subG/TIP3300/rh3357.htm

http://www.jsifaq.com/SUBN/tip6700/rh6731.htm

Exchange Considerations:
[If you run Exchange 2000] Windows Server 2003 adprep /forestprep Command Causes Mangled Attributes in Windows 2000 Forests That Contain Exchange 2000 Servers

http://support.microsoft.com/default.aspx?kbid=314649