Team blog of MCS @ Middle East and Africa

This blog is created by Microsoft MEA HQ near shoring team, and it aims to share knowledge with the IT community.With its infrastructure and development sides,It brings to you the proven best practices and real world experiences from Subject Matter Experts
Follow Us On Twitter! Subscribe To Our Blog! Contact Us

Part 3: Step-by-Step Exchange 2007 to 2013 Migration

Part 3: Step-by-Step Exchange 2007 to 2013 Migration

  • Comments 7
  • Likes

In part 1 we covered the deployments steps for Exchange 2013, in Part 2 of this series we covered Exchange 2013 configurations and testing, in this part we will start our migration. Make sure to start these configuration outside business hours, also plan a proper downtime to complete these steps and test them.

6.Move Client Access from Exchange 2007 to Exchange 2013

Virtual Directories

Open Exchange 2007 management shell and run the following commands.

OWA:

Set-OwaVirtualDirectory -Identity "e12-01\OWA (Default Web Site)" -ExternalUrl https://legacy.contoso.com/owa

Capture1

OAB:

Set-OabVirtualDirectory -Identity "e12-01\OAB (Default Web Site)" -InternalUrl https://legacy.contoso.com/oab -ExternalUrl https://legacy.contoso.com/oab

Capture2

ActiveSync

Set-ActiveSyncVirtualDirectory –Identity “e12-01\Microsoft-Server-ActiveSync (Default Web Site)” –ExternalUrl $Null –InternalUrl https://legacy.contoso.com/Microsoft-Server-ActiveSync

Capture3

Web Services:

Set-WebServicesVirtualDirectory –Identity “e12-01\EWS (Default Web Site)” -InternalUrl https://legacy.contoso.com/ews/exchange.asmx –ExternalUrl https://legacy.contoso.com/EWS/Exchange.asmx

Capture4

Unified Messaging:

Set-UMVirtualDirectory -Identity "UnifiedMessaging (Default Web Site)" –InternalUrl https://legacy.contoso.com/UnifiedMessaging/services.asmx –ExternalUrl https://legacy.contoso.com/UnifiedMessaging/services.asmx
Capture5

Outlook Anywhere:

Set-OutlookAnywhere -Identity "E12-01\Rpc (Default WebSite)" -IISAuthenticationMethods Basic,Ntlm

Capture6

TMG Rules:

Create/update your TMG publish rules

For Exchange 2007 update your publish rules to accept connections for Legacy name space:

CaptureCapture1

Follow the steps in this link to publish Exchange 2013.

DNS Configurations:

Update your DNS records as follows

Internal DNS

Record/Type

Comment

mail.contoso.com

Point to Exchange 2013 server

autodiscover.contoso.com

Point to Exchange 2013 server

Legacy.contoso.com

New record points to Exchange 2007 Server

Public DNS

Record

Comment

mail.contoso.com

Point to TMG Listener

autodiscover.contoso.com

Point to TMG Listener

Legacy.contoso.com

New record Point to TMG Listener

Testing

Apply all your test scenarios for both internal and External client types; once again you can use Microsoft Remote Connectivity Analyzer

7.Move Mailboxes:

Once you complete your tests successfully, its time to start moving mailboxes. you can do this using EAC or Shell.

New-MoveRequest -Identity 'mohsaeed@contoso.com' -TargetDatabase "DB01"

Capture1

You can create Batch moves as described in this link. Once you complete your mailboxes migration let us move to the final steps in this migration process (PF Migration and Exchange 2007 Decommissioning).

Comments
  • As per my Experience, you just need legacy for owa and EWS.

  • Great write up. I am already migrating users however the move request only does 2 mailboxes at a time. Do you have any ideas of how to increase this?

  • For Greg. There is a setting to adjust on target CAS server to increase moves. http://madoxr.blogspot.com/2010/01/increasing-number-of-simultaneous.html

  • Hi, great articles ! But what about receive connectors after decomissionning Exchange 2007 ? If you don"t recreate receive connectors from Exchange 2007, what's happening ?

  • HI, I tried to move the mailboxes across using the PowerShell and EMC and both ways I tried the move is just sitting on queued, I left it for a day and the same thing.. Queued with 0% progress.
    Any suggestions?

  • Hey, GZ, I was sitting here watching my attempt at moving a mailbox sit here on zero percent and then I saw this. Did you find out what was causing this, or find a resolution?
    Thanks in advance,
    Sam

  • Never mind. . . I just did a get-moveRequestStatistics command and it says percent complete is up to 32. So maybe the command just isn't refreshing and one must run this get-moveRequestStatistics command every so often to check the progress? Oh well. Good luck... to me and you and everyone in this boat...

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment