This transition has been done may times by our organization for independent companies, and it's time for us to share our secrets to success.

Transcription

1 This transition has been done may times by our organization for independent companies, and it's time for us to share our secrets to success. Let me first explain the example environment 1) 2003 Standard/Enterprise Domain Controller 1) Exchange 2003 Enterprise Server 1) Exchange 2010 Server This blog will walk you through the basics on how to migrate the physical data of exchange 2003 to 2010 with as little pain as possible. Things to be aware of up front: when you migrate your mailbox from exchange 2003 it takes it offline until it's migrated, and since it will be migrated over Gigabit Ethernet, the smaller the mailbox, the better, anything over 5GB may even fail, so it's important to clean out any old mail before you start the process, it will make your life much easier! *** MAKE A BACKUP OF ACTIVE DIRECTORY, and EXCHANGE IN CASE SOMETHING GOES WRONG! ******** Let's talk about the Outside Outlook Anywhere/RPC, OWA aspect of this first, because we will be having to make an Exchange Topology Change. Normally DNS (such as mail.domain.com) is pointed to a firewall at your location, that then forwards to the exchange server.

2 from there we are going to transition to a period of time called "coexistence" when both exchange servers are running, sending/receiving s while the migration occurs, this requires adding a few Outside DNS Records on a Separate WAN IP. You will be adding "autodiscover" and Legacy, Legacy will be port forwarded to your 2003 Exchange Server, and Autodisocver, and Mail will then point to the 2010 server. DO NOT CHANGE THIS YET, i'm simply explaining what will occur when we get to the necessary point to make these changes. From there we will decommission exchange 2003, and be left with only yay! out exchange outside DNS records have been changed, thanks to our awesome DNS Host zwiegnet.com. So as of right now, mail.mydomain.com and legacy.mydomain.com is pointing to exchange 2003, and only autodiscover.mydomain.com is pointing to the 2010 exchange server. Let's Get Started.First Make sure that your exchange 2003 server is running service pack 2, if not apply it before you begin, as well as your 2003 servers themselves need to

3 be running service pack 2 you also have to be sure that you are running domain Forrest Functional level of 2003 or higher, if not, raise to 2003 before you continue

4 From here we will put our exchange server 2003 in "native mode" change to native mode by right clicking on the first organization, going to properties, and following the above screenshot. As you can see, the mode changed

5 now we have to make one change in the registry on our exchange 2003 server to make sure that it's good to go so go to

6 HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\RESvc\Parameters > Right Click > New DWORD > Call it SuppressStateChanges. > Set its value to 1 >Then either reboot or restart the Simple Mail Transfer Protocol (SMTP) service again, set the value to 1

7 form there, download the Exchange Pre-Deployent analyzer from the following link: make sure all tests passed, if not review the above steps. On the Freshly installed 2008R2 Machine where we will be installing Exchange 2010, go to the server manager, and add the necessary roles

8 select "Web Server (IIS)" From there select static content, default document, directory browsing, and HTTP Errors

9 Also select all options under performance, and IIS6 from there, Next --> Install after that there is one more role that needs to be added, ad LDS services install (reboot if asked)

10 Once installed, go into windows features, and select add new features. add http activation (make sure.net Framework is checked

11 also make sure RPC over HTTP is checked (you may be required to reboot in-between). From here, open services Make sure the.nettcp service is set to automatic and is started

12 From here it's time to open the 2010R2 Installation media, open the setup file to start

13 install languages from the DVD (unless you have a reason to do it otherwise) Select "install Microsoft Exchange" and follow the next few steps

14 From here do the typical installation, be aware that down below you can specify what hard drive you would like to install exchange on if you would like to change

15 Here put in the auto discover if you would like to have access to the outside on your mobile Phone, ipad, other computer, or other Exchange Servers Select your 2003 exchange server that way mail flow can be configured to work between the two servers and that they can coexist. 1) Hit Browse 2) Select exchange server 3) Hit ok

16 4) Hit next It will do some prerequisite checks. Hit install afterwards, and then take a break (this part takes forever)

17 hit finish, then from there reboot.

18 As you can see, there is another exchange server detected in the console.

19 Now let s start the data migration go to organization configuration, and then Mailbox Here we want to move the store by selecting move database path so it s on the new exchange server 2010

20 Now check to make sure your old OWA, exchange is working just to be sure before proceeding further Ok, were good. Go to the 2003 management console, your 2003 public folder, and then select view system folders

21

22 Expand FREE+BUSY Schedule, and go to the properties of the First Administrative Group Select add it will know what your new public folder store will be

23 Go ahead and hit OK from there change the replication to Urgent and always run Go through all the public folders and repeat the process, add the replication partner, and go from there. Set to always run and urgent. This should take about 24 hours for everything to replicate, it just takes forever because public folders are prioritized very low for exchange. Now s the time to start setting up exchange 2010 with the Send/Receive Connectors Go into the Server configuration, and then Hub Transport and go to the properties of the Default Connector We want to go to permission groups, and allow anonymous users to send to us (this enables receiving )

24 That s it for that, yay, that was easy

25 Now Let s go to Organization Configuration and Hub Transport to create a send connector

26 Insert a name; I like SMTP To Outside that usually works well for me. Since we are sending out to the internet, select Internet. Add an address space, and then put a * in the address, that way if the exchange server s IP ever changes it will still be able to send mail, this may be different if you have multiple IP s on the same server.

27 From here I m relying on DNS to send properly (if you have postini, or some other smart host, this may be slightly different)

28 Next

29 Next it will ask what server you want to send with, since we only have one, we will use the default of itself Hit next, and then new.

30 It should complete successfully Hit finish. Let s log into our new OWA to make sure everything s working correctly, go to

31 As you can see here is our new OWA, so it s time to witch out our DNS Autodiscover points to the same place Legacy points to the same place Mail.mydomain.com switches to the new server 2010 From here go to Recipient Configuration, and then mailbox configuration

32 Below you can see that there are a few mailboxes for this example TestUser1 and TestUser2 *** Disclaimer, once you proceed with this next step, the mailbox will be taken offline to migrate to exchange 2010! **** do in off business hours

33 Right click on the mailbox, and then select local move request Select browse, and select the new target mailbox database Let s go

34 Ahead and select the name of our new exchange server, and hit OK This is where having a smaller mailbox comes in handy, if there are any corrupted messages they will be caught here. For this example we are going to hit skip the mailbox but if you have a large mailbox, hit skip corrupted messages and set the number to something ridiculous like 500, the reason that is because if you get ¾ of the way done with the process and you reach your threshold, you have to spend hours

35 retrying agin.

36 Hit next. You will see the next screen As soon as you hit new the migration process begins, when ready, hit NEW

37 It should look as so when done As you can see this user has been moved to the new exchange server. Test with outlook web access if you are able to send/receive s, if so: Do this for groups of users at a time, you can select multiple and proceed. After that entire process is done, go back to organization configuration, mailbox, and Offline Address Book

38 This is still on our old server, so we need to move it Right click, and go to move, and select the new 2010 server, and move it. Once completed Verify that it s 2010 that now holds the address book. Let s setup our address policy by going to the exchange management shell

39 Run the following command: Get- AddressPolicy where {$_.RecipientFilterType eq Legacy } Set- AddressPolicy IncludedRecipients AllRecipients Hit a to confirm Yes to All From here there are a few more things we need to update, type the following commands: Set-AddressList All Users IncludedRecipients MailboxUsers Set-AddressList All Groups IncludedRecipients Mailgroups Set-AddressList All Contacts IncludedRecipients MailContacts Set-AddressList "Public Folders" -RecipientFilter { RecipientType -eq 'PublicFolder' } Set-GlobalAddressList "Default Global Address List" -RecipientFilter {(Alias -ne $null - and (ObjectClass -eq 'user' -or ObjectClass -eq 'contact' -or ObjectClass -eq 'msexchsystemmailbox' -or ObjectClass -eq 'msexchdynamicdistributionlist' -or ObjectClass -eq 'group' -or ObjectClass -eq 'publicfolder'))} Sweet, now that all those are done, things are looking a little brighter.

40 Go through each one, and go to the repliacation tab and make sure that they say in Sync From there, right click the folder, and go to the properties again, one by one and remove the 2003 from the mix. Remove the SMTP Connectors from exchange 2003 and for Make sure you leave your send connector for exchange 2010 however, just remove the one with 2 envelopes

41 on it. From there go to recipients and recipient update services Even though exchange 2010 doesen t use this, you still have to tell exchange where to go with it to decommission Change these to your 2010 server. With Exchange 2010 (post SP1) This May Not Work! So that you can gracefully remove Exchange 2003, The Recipient Update Services needs to be removed first. If you cannot gracefully remove it (as above). Then you will need to Manually Remove it from Active Directory. To do this run ADSIEdit.msc (On Server 2003 you will need the support tools installing first). Then navigate to; Configuration > CN=Configuration,CN={domain} > CN=Services > CN=Microsoft Exchange > CN={Exchange organization name} > CN=Address Lists Container > CN=Recipient Update Services

42 Make sure EVERYTHING Is out of your exchange databases, and dismount the store. When you are certain all is good to go, browse to your Mailbox store in exchange management of 2003, and right click, and hit dismount

43 It will ask are you sure? Go ahead and hit yes. Stop all Microsoft Exchange Related Services From here, we can go ahead and Un-install Exchange 2003

44 Hit next Set all to remove

45 Hit next Next Again

46 The Un-installation should look like the above diagram.

47 Finished. From here, I would change around some things, such as install Antivirus on Exchange 2010, and Get 2010 Backed Up. Please make a donation to sales@zwiegnet.com on PayPal if you found this helpful!