Can I migrate/upgrade Windows Server 2008 32-bit to 64-bit?

[Chris Kiekens]

Is there a way to migrate/upgrade Windows Server 2008 32-bit to 64-bit?

Can it be done directly or do I have to use ADMT 3.1 or some other tool?

Apparently there is no more support for 32-bit (no Exchange, SQL Server), so
we have to go to 64-bit.

[Meinolf Weber]

For the OS itself is no way without reinstalling. If you like to install
a total new domain and migrate the complete environment you can use ADMTv3.1

Thanks for the update. I was already suspecting that there was no direct
upgrade possible.

[David Shen [MSFT]]

Thank you for posting in newsgroup. And thanks to Meinolf for the
contribution.

Based on the research, I agree with what Meinolf said.

I'm wondering if the information has helped or if you have any further
questions. Please feel free to respond to the newsgroups if I can assist
further.

[phemmywales]

Please im in a similar situation. A client has a Windows Server 2003 SP2 32bit AD DOmain and Exchange 2003 SP2 32bit. They just got a new Server machine which is x64. I need to implement Windows Server 2008 x64 on this new server, make it a DC and install Exchange 2007 x64 on it. Can i upgrade Exchange 2003 32bit using coexistence to Exchange 2007 x64. Please advice.

Thank for the step by step, I know th rule concerning having exchnage on a DC but that what my client can afford now. but just to clarify, can i do the x64 on the new server and still be able to make it a DC of the 32bit 2003 system. ( can i use a x64 2008 Server CD to prep the schema of a 32bit 2003 Server OS.

[Meinolf Weber [MVP-DS]]

It is not recommended to run Exchange, doesn't matter which verison, on a DC:
http://technet.microsoft.com/en-us/l.../aa997407.aspx

So for Exchange i strongly recommend to use an additional member server.
It will work on a DC but you should really prevent this.

In-place upgrade form 32bit to 64bit architecture is not possible.

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:

!!!NEVER START BEFORE HAVING CREATED AND TESTED A BACKUP OF YOUR DATA/MACHINE!!!

- 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
appear

- 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

[phemmywales]

Exchange 2003 to 2007 transition:
http://support.microsoft.com/kb/555854

http://technet.microsoft.com/en-us/l.../bb125224.aspx

http://www.msexchange.org/tutorials/...007-Part1.html

http://www.msexchange.org/tutorials/...007-Part2.html

http://www.msexchange.org/tutorials/...007-Part3.html

http://technet.microsoft.com/en-us/l.../bb124008.aspx

Known/solved problems:
http://msexchangeteam.com/archive/20...26/448511.aspx

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

If you like to work only with .pst files and install the Exchange organization
complete new:
http://msexchangeteam.com/archive/20...13/437745.aspx

Is the Exchange Edge Transport role important since the client already has ISA Server 2006 SP1 runing on the network. or can the Edge Tranport role be installed on a ISA Server box

[Meinolf Weber [MVP-DS]]

As said in my previous answer, they will work together without any problem.
OS architecture has nothing to do with AD itself. But you have to use a 32bit
2008 adprep version, not the 64bit version.

For 32bit adprep download the 2008 trial version:
http://www.microsoft.com/downloads/d...displaylang=en

[phemmywales]

I started my migration process by installing Win2k8 Ent x64 on the new machine extended the domain and forest with the adprep utility. I was able to make the machine additional DC for the domain.

I then proceed to run exchange 2010 setup with the /pl switch. it was successful. a little while later i tried to transfer the fsmo role but couldnt see the new DC in the list of DC when i tried to change domain controller in the AD user and computer snapin.

I got curious and found out that the AD DS Service, File replication service, is stopped on the new DC, i tried to retstart them but didnt start. I checked th event log, saw messages about the new server not been able to setup a session with the old DC. the Old DC is still runing fine with the exchange on it.
what can i do pleas.

Meanwhile ididnt use exchange 2007 again because i got a error messsage that exchange 2007 is not supported on windows server 2008 SP1 x64. is this right?

[Meinolf Weber [MVP-DS]]

Your reply to the subject doesn't really fit, 2008 32bit to 2008 64bit inplace
upgrade is not possible.

Exchange on a DC is not recommended for none Exchange version.
http://technet.microsoft.com/en-us/l.../aa997407.aspx

Also using Exchange 2010 which is not RTM until in a production environment
is a not recommended setup.

According to the not running services on the 2008 DC, please describe your
complete domain setup, amount of DCs and how they are located, which functional
levels do you run and which SP/patch level is installed on all DCs. Are all
DCs Global catalog server?

Which server is your DNS server and are all DCs listed with there A record
under the forward lookup zone and if they are DNS server also with there
Nameserver record? Do you use AD integrated zones in DNS? Can you ping between
the DCs with ip address, computername and FQDN?

[phemmywales]

First, its not an inplace upgrade of 32bit 2008 to x64. Its a brand new 2008 x64 trying to join a window 2003 domain.

Its a single domain single forest. Forest and domain funtional level is window 2003.

The Primary Dc(first DC) is a windows Server 2003 SP2 holding all the 4 fsmo roles and also a GC, Its the Primary DNS Server while another member servers thats not a DC act as the Secondary DNS.

The New window 2008 and current windows 2003 machine can ping each other by IP and by name, All DNS Zones are AD integrated.

[phemmywales]

Hi Meinolf

I have run through the migration processes you recomended to install the new Windows 2008 server and make it a DC. what is suprising now is that each time i tried to run exchange /prepareAd command the AD DS halts.

I am not able to access AD user and Computer or any other AD Snap-in. I had to reboot the machine or restart the netlogon and AD DS service manually before its been able to gain access to the snapin.

If i initiate the Exchane 2007 SP1 install wizard. it brings error that it couldnt contact the domain and this point the AD DS services halt. There are currently two Domain controllers on the network.One is Windows server 2003 and the other windows server 2008. What do you think could be responsible. Please help