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 1: Step-by-Step Exchange 2007 to 2013 Migration

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

  • Comments 17
  • Likes

In this article series we will explain and go through all the steps to migrate from Exchange 2007 to Exchange 2013.

The series consists of four Parts:

Before You Begin

Exchange is always considered as a mission critical service; accordingly and to assure a smooth upgrade process without any interruption to mail services, you have to spend some time on planning your deployment and upgrade. A good start can be through the below links:

Exchange 2013 TechEd Sessions and Labs  which includes session about Exchange 2013 high availability, virtualization,  managed availability, retention, site mailboxes, modern public folders, transport, unified messaging, Outlook Web App, EWS, and the most important one in case you will be doing a migration is Exchange Server 2013 On-Premises Upgrade and Coexistence

Sizing Exchange 2013 Deployments by the Exchange Team Blog

Exchange Server 2013 Deployment Assistant

IntroductionDrawing1_thumb17

In my Lab I have Exchange 2007 server holding CAS/HUB/MBX roles with a few users on it, published to the internet using TMG (with no pre-authentication), TMG acting as my SMTP GW as well, our goal in these series of posts to deploy a single Exchange 2013 server with all server roles on it, migrate all users and services to the new server, and finally decommission our legacy server.

 

 

 

 

 

 

 

Checklist

  1. Exchange 2013 Deployment
  2. Digital Certificates Configurations
  3. Configure Exchange-related virtual directories
  4. Configure offline address book (OAB)
  5. Move Internet mail flow from Exchange 2007 to Exchange 2013
  6. Move Client Access from Exchange 2007 to Exchange 2013
  7. Move mailboxes from Exchange 2007 to Exchange 2013
  8. Move public folder data from Exchange 2013 to Exchange 2013
  9. Decommissioning Exchange 2007

1.Exchange 2013 Deployment

AD Preparation

From a domain joined machine in the same AD domain, & Site of your Schema master (in my case I have single forest single domain and single AD site); with Microsoft .NET Framework 4.5 and Windows Management Framework 3.0 installed, open PowerShell and run the following commands:

Install-WindowsFeature RSAT-ADDS

Capture0_thumb2

.\setup /PrepareAD /OrganizationName: contoso /IAcceptExchangeServerLicenseTerms

Capture5_thumb4

To Validate your AD preparation open your Schema partition using ADSI and make sure that ms-Exch-Schema-Version-Pt is showing the correct value as shown below:

Capture6_thumb2

Open you Active Directory Users and Computers console, you should be able to see the below groups created:

Capture6.1_thumb2

For more validation steps, and information about AD preparation requirements visit this link.

Force AD replication and make sure its successful, then let us move to the next steps.

Exchange 2013 Installation

OS prerequisites Installation:

To Install OS prerequisites on Windows Server 2012 open PowerShell and run the following command:

Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience, NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Clustering-CmdInterface, RSAT-Clustering-Mgmt, RSAT-Clustering-PowerShell, Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45, Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext45, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI, Windows-Identity-Foundation

Capture2_thumb3

After restart install the below components in the same order:

  1. Microsoft Unified Communications Managed API 4.0, Core Runtime 64-bit
  2. Microsoft Office 2010 Filter Pack 64 bit
  3. Microsoft Office 2010 Filter Pack SP1 64 bit

In case you have a different scenario (such as separate MBX & CAS roles) follow the steps in this link.

MBX/CAS Server Installation:

To install MBX/CAS server (in my case I will change the first DB name and directory; this is optional) open PowerShell and run the following command:

.\setup /m:Install /Roles:ca,mb,mt /IAcceptExchangeServerLicenseTerms /InstallWindowsComponents /DBFilePath:"C:\DB01\DB01.edb" /LogFolderPath:"C:\DB01\Logs" /MdbName:"DB01"

Capture7_thumb3

You can follow the steps in the below links for different scenarios, or in case you prefer to use the Exchange Setup Wizard:

Install Exchange 2013 Using Unattended Mode

Install Exchange 2013 Using the Setup Wizard

After you complete installation successful let us move to the next steps through part 2 of this series.

Comments
  • Hi Mohammad, congrats, quite simply!

  • Shouldn't you note the potential for a full OAB download here and the optional configurations that could prevent said download from happening?  

    Might also be a good idea to cover the automatic things that will happen once the first Exchange 2013 server is installed such as the effect on Autodiscover, etc.

  • Very Nice,  Thank You!

  • Fantastic post.  After trying multiple such documents online, this was the first one that I was able to get to work.  Thank you VERY much.

    Oddly enough, I don't see "Mobile Devices" under "Phone and Voice Features" in my Exchange Admin Center when I click on a mailbox.  I do see this on my Office365 mailboxes when I login to exchange online.  Any thoughts?

    alan at jefric.com

  • Follow up to my 28 Sep post - the "Mobile Devices" magically appeared in the EAC 24 hours after the final mailbox migrations.

    Again, thanks VERY much Mohammad!

  • Quick question i setup exchange 2013 on Windows 2012 server, and seem to have issues telnet to smart host address.  example would be telnet smtp.mandrillapp.com 587.  Have any of you experienced such an issue? No firewalls are enabled on anything, and dont seem to experience this on WIndows 2008

  • Hi,

    This is for on-premises upgrade, right? What if I set-up an exchange 2013 on a remote server and then need to migrate mail boxes from a 2007 server? How do I migrate mail boxes?

  • @Cyril please clarify what to you mean by remote ?

  • @Jedi please refer back to the below link for how to test exchange 2013 using telnet

    technet.microsoft.com/.../bb123686(v=exchg.150).aspx

  • Does "/OrganizationName" still have to be used during the AD preparation, eventhough Exchange2013 is to be installed into the existing Exchange2007 Organisation.

    Wouldn't the AD preparation process just updates the present Exchange-Schema if the flag is not used.

    I beleive I do not have to create a new Organisation just for Exch2013.

  • repair the this step

    .\setup /PrepareAD /OrganizationName: contoso /IAcceptExchangeServerLicenseTerms

    if you are installing exchange to organisation with existing exchange configuration you should use

    .\setup /PrepareAD  /IAcceptExchangeServerLicenseTerms

  • You fail to mention this is for Server 2012. For example, this won't work on earlier versions: Install-WindowsFeature

  • you mention "published to the internet using TMG". What is TMG?

  • @bonoslav thanks for the comment I updated the command accordingly

  • Can I move a 2007 mailbox to a 2013 mailbox with the users still logged into their mailbox?

    Thanks

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