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.
Open Exchange 2007 management shell and run the following commands.
Set-OwaVirtualDirectory -Identity "e12-01\OWA (Default Web Site)" -ExternalUrl https://legacy.contoso.com/owa
Set-OabVirtualDirectory -Identity "e12-01\OAB (Default Web Site)" -InternalUrl https://legacy.contoso.com/oab -ExternalUrl https://legacy.contoso.com/oab
Set-ActiveSyncVirtualDirectory –Identity “e12-01\Microsoft-Server-ActiveSync (Default Web Site)” –ExternalUrl $Null –InternalUrl https://legacy.contoso.com/Microsoft-Server-ActiveSync
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
Set-UMVirtualDirectory -Identity "UnifiedMessaging (Default Web Site)" –InternalUrl https://legacy.contoso.com/UnifiedMessaging/services.asmx –ExternalUrl https://legacy.contoso.com/UnifiedMessaging/services.asmx
Set-OutlookAnywhere -Identity "E12-01\Rpc (Default WebSite)" -IISAuthenticationMethods Basic,Ntlm
Create/update your TMG publish rules
For Exchange 2007 update your publish rules to accept connections for Legacy name space:
Follow the steps in this link to publish Exchange 2013.
Update your DNS records as follows
Point to Exchange 2013 server
New record points to Exchange 2007 Server
Point to TMG Listener
New record Point to TMG Listener
Apply all your test scenarios for both internal and External client types; once again you can use Microsoft Remote Connectivity Analyzer
Once you complete your tests successfully, its time to start moving mailboxes. you can do this using EAC or Shell.
New-MoveRequest -Identity 'email@example.com' -TargetDatabase "DB01"
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).
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.
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,
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...
As I was migrating from Exchange 2007 to Exchange 213, I got an error, "Set-OwaVirtualDirectory: Object is read only because it was created by a future version of Exchange: 0.10 (184.108.40.206). Current version supported is 0.1 (8.0.535.0)", from Exchange
2007 management shell when i run the command "Set-OwaVirtualDirectory -Identity "e12-01\OWA (Default Web Site)" -ExternalUrl
Please help. Thanks.
this is a nice Article.