• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 461
  • Last Modified:

How can i Migration of Windows 2003 Server 32Bit Enterprise Edition to Windows2008 server 64bit Enter prise Edition

Dear all,

We have separately  2 Servers Physically .

1. For Windows2003 Server 32Bit Enterprise Edition Service pack 2. ( Presently it's working fine like
 ( ADS, DNS ,GPO,OU , Exchanger server 2003)

2.For Windows 2008 server 64Bit Enterprise Edition  ( Newly installed )

How can i Move   Windows 2003 server 32Bit Enterprise Edition to Windows 2008 server 64Bit Enterprise edition ? without loosing anything like ADS, DNS, OU, Exchange server .



1 Solution
Unfortunately you cannot upgrade from 32bit to 64bit architecture.

You have to install the 2008 64bit as additional Domain controller in the
existing domain, which is no problem. Also Exchange 64bit version can coexist
with 32bit 2003.

For the upgrade to windows server 2008 AD and change to Exchange 2007 in
the same domain i suggest to do it in 2 steps, 1st AD and then going on with
Exchange 2007.

For exchange i will creaete a second posting to make it more easy to read.

For AD upgrade see this step by step:


- On the old server open DNS management console and check that you are running
Active directory integrated zone (easier for replication, if you have more
then one DNS server)

- run replmon from the run line or repadmin /showrepl(only if more then one
DC exist), dcdiag and netdiag from the command prompt on the old machine
to check for errors, if you have some post the complete output from the command
here or solve them first. For this tools you have to install the support\tools\suptools.msi
from the 2003 installation disk.

- run adprep /forestprep and adprep /domainprep and adprep /rodcprep from
the 2008 installation disk against the 2003 schema master(forestprep) / infrastructure
master(domainprep/rodcprep), with an account that is member of the Schema/Enterprise/Domain
admins, to upgrade the schema to the new version (44) or 2008 R2 (47)

- you can check the schema version with "schupgr" or "dsquery * cn=schema,cn=configuration,dc=domainname,dc=local
-scope base -attr objectVersion" without the quotes in a command prompt

- Install the new machine as a member server in your existing domain

- configure a fixed ip and set the preferred DNS server to the old DNS server
only, think about disabling IPv6 if you are not using it, some known problems
exist with it. Follow to disable it

- run dcpromo and follow the wizard to add the 2008 server to an existing
domain, make it also Global catalog and DNS server.

- for DNS give the server time for replication, at least 15 minutes. Because
you use Active directory integrated zones it will automatically replicate
the zones to the new server. Open DNS management console to check that they

- if the new machine is domain controller and DNS server run again replmon,
dcdiag and netdiag (copy the netdiag from the 2003 to 2008, will work) on
both domain controllers

- Transfer, NOT seize the 5 FSMO roles to the new Domain controller (http://support.microsoft.com/kb/324801
applies also for 2008), FSMO should always be on the newest OS DC

- you can see in the event viewer (Directory service) that the roles are
transferred, also give it some time

- reconfigure the DNS configuration on your NIC of the 2008 server, preferred
DNS itself, secondary the old one

- if you use DHCP do not forget to reconfigure the scope settings to point
to the new installed DNS server

- if needed export and import of DHCP database for 2008 choose "netshell
dhcp backup" and "netshell dhcp restore" command (http://technet.microsoft.com/en-us/l.../cc772372.aspx)

Demoting the old DC (keep in mind it is also best practise to have at least
2 DC/DNS/GC per domain, failover and redundancy)

- reconfigure your clients/servers that they not longer point to the old
DC/DNS server on the NIC

- to be sure that everything runs fine, disconnect the old DC from the network
and check with clients and servers the connectivity, logon and also with
one client a restart to see that everything is ok

- then run dcpromo to demote the old DC, if it works fine the machine will
move from the DC's OU to the computers container, where you can delete it
by hand. Can be that you got an error during demoting at the beginning, then
uncheck the Global catalog on that DC and try again

- check the DNS management console, that all entries from the machine are
disappeared or delete them by hand if the machine is off the network for ever

- also you have to start AD sites and services and delete the old servername
under the site, this will not be done during demotion

Hope it helps!
Best Regards
Co0L_DBAAuthor Commented:
I got it many answer from this topic
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now