The easiest option is usually to upgrade your current domain.
Get some more or less decent hardware, and install Virtual Server/Virtual PC on it (do *not* use the new DC-to-be, though).
Create a new virtual machine (256MB should work, 512MB is enough), and install it as NT4 BDC (create a 4GB C: partition during setup; the upgrade needs lots of free disk space!). Apply SP6a, install the VM additions, install IE6. Set the primary domain suffix to your new AD domain name. Let the machine point to your W2k3 DC-to-be for DNS.
Promote it to PDC.
Microsoft Virtual Server 2005 R2
http://www.microsoft.com/w
Install DNS on the W2k3 DC-to-be. Create a primary forward lookup zone for your new AD domain name, and make sure dynamic updates are allowed. Create (a) reverse lookup zone(s) as well, while you're at it, and allow dynamic updates. Let this machine point only to itself for DNS, and configure forwarders to point to your ISP's DNS. Let all your domain members point to this machine *only* for DNS as well.
Frequently Asked Questions About Windows 2000 DNS and Windows Server 2003 DNS
http://support.microsoft.c
Best practices for DNS client settings in Windows 2000 Server and in Windows Server 2003
http://support.microsoft.c
The Domain Name System name recommendations for Small Business Server 2000 and Windows Small Business Server 2003
http://support.microsoft.c
If you already have W2k/XP clients, you might have a look at this article (and set the registry keys on your PDC) *before* starting the upgrade, just in case you want/have to roll back:
How to prevent overloading on the first domain controller during domain upgrade
http://support.microsoft.c
Now take the BDC (former PDC) offline, just in case. Upgrade the virtual PDC to W2k3. Once the upgrade is complete, uninstall the VM additions, reinstall them.
Install the W2k3 Support Tools (on the CD in the \Support\tools folder), start dcdiag to make sure everything is running okay.
dcpromo the W2k3 machine.
Install the W2k3 Support Tools (on the CD in the \Support\tools folder), start dcdiag to make sure everything is running okay.
Transfer the FSMO roles to the new machine, and make it a global catalog. Move the licensing to the new server as well (in AD Sites and Services, right-click "License Server" in the right pane, choose Properties).
Change the zone type of your DNS zones to AD integrated.
How To View and Transfer FSMO Roles in Windows Server 2003
http://support.microsoft.c
How to promote a domain controller to a global catalog server
http://support.microsoft.c
Start dcdiag to make sure everything is still running okay.
Finally, dcpromo down the virtual machine, and shut it off.
The former PDC can just be shut down and the object deleted in AD as soon as you don't need it anymore.
And some other links that might be useful:
Tools and Documentation for Upgrading to Windows Server 2003
http://www.microsoft.com/w
Background Information for Upgrading to Windows Server 2003 Active Directory
http://www.microsoft.com/r
Migrating Windows NT Server 4.0 Domains to Windows Server 2003 Active Directory
http://www.microsoft.com/w
Main Topics
Browse All Topics





by: TS_BenBPosted on 2009-11-06 at 04:07:49ID: 25758381
I should also mention that Exchange isn't used.