Windows Vista Tips

Windows Vista Tips > Newsgroups > Windows Server > Server Migration > Migrating old 2003 server with Exchange to new 2003 64-bit serverwith Exchange 2008

Reply
Thread Tools Display Modes

Migrating old 2003 server with Exchange to new 2003 64-bit serverwith Exchange 2008

 
 
Willo van der Merwe
Guest
Posts: n/a

 
      10-22-2009
Hi,

We were running Windows Server 2008 64-bit with Exchange 2008. The
hardware was unstable and eventually disaster struck and we lost the
entire machine. we quickly commandeered a standby machine, installed
Windows Server 2003 (32-bit) and Exchange 2003 on it, recreated the
mailboxes, had all the desktop/laptops in the company rejoin the domain.
It was not pretty. Mail was lost, profiles corrupted - generally nasty.

This was 3 weeks ago.

Now we have a replacement machine. The guys supplying the machine is now
scared of Windows Server 2008, so decided to downgrade to the more
stable (longer in the field) 2003 server - but because our backups of
mail was in 64 bit Exchange 2008, it could not be restored without
considerable effort on their part. Therefore they decided to go to
Exchange 2008, 64-bit.

They want to do the same as last time - recreate the mailboxes, have all
the desktop/laptops in the company rejoin the domain. Understandably we
are not very enamored with this idea. A bit of research revealed that we
do not have to go this route.

From my research it seems we should:
1. Introduce the new server, without Exchange (or Exchange disabled) as
a member server.
2. Make it a DC.
3. Wait till the AD has propagated.
4. Demote PDC.
5. Promote new server.
Now the new server should be acting as the new PDC and users should be
authenticating from it.

The part where I get stuck is how do I migrate the existing Exchange
2003 mailboxes to Exchange 2008, and still recover the mailboxes.

Any suggestions welcome.

Willo van der Merwe
 
Reply With Quote
 
 
 
 
Meinolf Weber [MVP-DS]
Guest
Posts: n/a

 
      10-22-2009
Hello Willo van der Merwe,

Just to clarify some parts at the beginning, i think you talk about Exchange
2007, so i will refer to it, because there is no 2008 version from it.

Running Exchange on domain controllers is not recommended, it should be always
installed on member servers:
http://technet.microsoft.com/en-us/l.../aa997407.aspx

You have no need to built a new domain again, everything can be done from
the existing domain.

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 (http://blogs.dirteam.com/blogs/paulb...dows-2008.aspx)
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

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> Hi,
>
> We were running Windows Server 2008 64-bit with Exchange 2008. The
> hardware was unstable and eventually disaster struck and we lost the
> entire machine. we quickly commandeered a standby machine, installed
> Windows Server 2003 (32-bit) and Exchange 2003 on it, recreated the
> mailboxes, had all the desktop/laptops in the company rejoin the
> domain. It was not pretty. Mail was lost, profiles corrupted -
> generally nasty.
>
> This was 3 weeks ago.
>
> Now we have a replacement machine. The guys supplying the machine is
> now scared of Windows Server 2008, so decided to downgrade to the more
> stable (longer in the field) 2003 server - but because our backups of
> mail was in 64 bit Exchange 2008, it could not be restored without
> considerable effort on their part. Therefore they decided to go to
> Exchange 2008, 64-bit.
>
> They want to do the same as last time - recreate the mailboxes, have
> all the desktop/laptops in the company rejoin the domain.
> Understandably we are not very enamored with this idea. A bit of
> research revealed that we do not have to go this route.
>
> From my research it seems we should:
> 1. Introduce the new server, without Exchange (or Exchange disabled)
> as
> a member server.
> 2. Make it a DC.
> 3. Wait till the AD has propagated.
> 4. Demote PDC.
> 5. Promote new server.
> Now the new server should be acting as the new PDC and users should be
> authenticating from it.
> The part where I get stuck is how do I migrate the existing Exchange
> 2003 mailboxes to Exchange 2008, and still recover the mailboxes.
>
> Any suggestions welcome.
>
> Willo van der Merwe
>



 
Reply With Quote
 
Meinolf Weber [MVP-DS]
Guest
Posts: n/a

 
      10-22-2009
Hello Willo van der Merwe,

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


Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> Hi,
>
> We were running Windows Server 2008 64-bit with Exchange 2008. The
> hardware was unstable and eventually disaster struck and we lost the
> entire machine. we quickly commandeered a standby machine, installed
> Windows Server 2003 (32-bit) and Exchange 2003 on it, recreated the
> mailboxes, had all the desktop/laptops in the company rejoin the
> domain. It was not pretty. Mail was lost, profiles corrupted -
> generally nasty.
>
> This was 3 weeks ago.
>
> Now we have a replacement machine. The guys supplying the machine is
> now scared of Windows Server 2008, so decided to downgrade to the more
> stable (longer in the field) 2003 server - but because our backups of
> mail was in 64 bit Exchange 2008, it could not be restored without
> considerable effort on their part. Therefore they decided to go to
> Exchange 2008, 64-bit.
>
> They want to do the same as last time - recreate the mailboxes, have
> all the desktop/laptops in the company rejoin the domain.
> Understandably we are not very enamored with this idea. A bit of
> research revealed that we do not have to go this route.
>
> From my research it seems we should:
> 1. Introduce the new server, without Exchange (or Exchange disabled)
> as
> a member server.
> 2. Make it a DC.
> 3. Wait till the AD has propagated.
> 4. Demote PDC.
> 5. Promote new server.
> Now the new server should be acting as the new PDC and users should be
> authenticating from it.
> The part where I get stuck is how do I migrate the existing Exchange
> 2003 mailboxes to Exchange 2008, and still recover the mailboxes.
>
> Any suggestions welcome.
>
> Willo van der Merwe
>



 
Reply With Quote
 
Ace Fekay [MCT]
Guest
Posts: n/a

 
      10-24-2009

"Meinolf Weber [MVP-DS]" <meiweb@(nospam)gmx.de> wrote in message
news:. com...
> Hello Willo van der Merwe,
>
> 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
>
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and
> confers no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>


There's also one more option to recover the mailboxes from the original
Exchange 2007 database. There's a utility called Ontrack Power Control
Tools. It can read the EDB files and extract all the mailboxes into PSTs.
Once the PSTs are recovered, they can be used to add them to an Outlook
profile, and pump the data back into their mailboxes. For Calendar items,
use the Export/Import function in Outlook.

Exchange Server Recovery, Exchange Data Recovery, Email Recovery ...Exchange
data recovery, exchange server recovery and pst recovery. Ontrack®
PowerControls™ is a powerful software tool for copying, searching, ...
www.ontrackpowercontrols.com/

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Please reply back to the newsgroup or forum for collaboration benefit among
responding engineers, and to help others benefit from your resolution.

Ace Fekay, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA
2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer

For urgent issues, please contact Microsoft PSS directly. Please check
http://support.microsoft.com for regional support phone numbers.



 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
How to Move WSUS Database From Windows Server 2003 to 2008 Charles Update Services 5 12-07-2011 08:42 PM
SBS2003 | Windows Server 2008 - Exchange 2007 Cary Shultz Windows Small Business Server 33 11-04-2009 06:26 AM
Re: 2003 migration to new 2003 server Meinolf Weber [MVP-DS] Server Migration 0 10-22-2009 08:48 AM
Offline files fail to synchronize Bob Windows Vista File Management 19 04-30-2009 05:45 AM
Exchange Server Tools 2003 Ramzus Windows Vista Installation 1 08-06-2007 01:48 PM



1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59