Auditing task for migrating Windows Server 2003 32-bit to Windows Server 2008 R2 64-bit

975 pts.
Data Center management
Domain Controller
Microsoft Windows Server 2003
Windows Server 2008 R2
We're moving from a 32-bit platform to 64-bit and we need to audit our tasks. We have four DCs located in one data center. One domain controller holds all FSMO roles, server runs DNS, WINS. The other holds the terminal servers licenses and runs DNS, WINS, and holds trust for an external domain (I believe Windows Server 2003 domain) to allow users to log into our hosted Sharepiont site with their own IDs and passwords. 1 DC located in Europe 2 DCs located in Pacific Rim When should I run the following commands since I need to demote and wipe out each of the DCs? adprep/ forestprep adprep/ domainprep Since we’re close to the DCs located in the [strong class="keyhilite">data[/strong] [strong class="keyhilite">center[/strong], I thought we’d start with them. First, I’d select the DC with no roles and just the terminal services licenses and trusts. I’d make sure to have all the licensing information to be able to contact Microsoft and have them reload it for us (is there anyway else around this?) I’d demote the server Turn server off Ensure replication has been completed with other servers Check with NTUTILS to ensure the server name was been removed. Install the Windows 2008 r2 disk, delete the disk partition and install the 64B OS Join to domain Promote Install DNS Install WIN install licensing Re-establish the trusts Repeat with the other domains.

Answer Wiki

Thanks. We'll let you know when a new response is added.

Hi TeachMeIT and everyone,

In my opinion, your approach is not too bad.
For me, the best, safest and simplest path to do what you’re planning to do is:

– Start by adding a W2k8 Domain controller to your existing domain. (if you do not have a spare physical server you can use for this step, I suggest you to create one in a virtual machine like VMWare Server). This will provide to your existing domain, the schema for the w2k8 domain/forest.
– Run this commands to prepare the actual W2k3 Domain so it will accept the new W2k8 DC:

<pre> 1) adprep /forestprep;
2) adprep /domainprep
3) adprep /gpprep</pre>

(The existing domain will not allow you to add a W2K8 machine to the domain if you jump this step)

These commands are are done with the W2K8 DVD in one of your Windows 2003 DC – ADPREP is in the SOURCES folder on the DVD.

After this, go ahead and install W2K8 in a new box/VM.

Don’t forget to assign an IP address and subnet mask to this new server and make sure that the DNS (in W2K8) is pointing to the existing DNS Server.
After this, join the new 2008 machine to the existing domain as a member server.

From the command line promote the new machine to a domain controller with the DCPROMO command.
From the command line Select “Additional Domain Controller in an existing Domain”

Once Active Directory is installed then to make the new machine a global catalog server (GC). Go to Administrative Tools->Active Directory Sites and Services->Expand, Sites->Default First Site and Servers. Right click on the new server and select Properties and tick the ”Global Catalog” checkbox. (Global Catalog is essential for all logon processes as it needs to be queried to establish Universal Group Membership)

If necessary install DNS on the new server. Assuming that you were using Active Directory Integrated DNS on the first Domain Controller, DNS will automatically replicate to the new domain controller along with Active Directory.

To transfer the FSMO roles to the 2008 machine (needed if you’re retiring all W2K3 DC’s) then follow the process outlined at

Netometer has a nice video –


Discuss This Question:  

There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.


Share this item with your network: