A quick overview of migrating from Exchange 2007 to Exchange 2016

Migrating from Exchange 2007 to Exchange 2016 is a laborious and time consuming process because it cannot be done correctly. It involves upgrading from Exchange 2007 to 2010/2013, and then to Exchange 2016. Doing the migration natively requires a large amount of technical knowledge and can be costly as it involves setting up an intermediate Exchange environment.

One other method is to deploy an Exchange migration solution like LepideMigrator for Exchange. This solution makes it possible to upgrade directly from Exchange 2007 to 2016, without the need for double hopping.

Upgrading from Exchange 2007 to Exchange 2016 using Exchange 2013

Upgrading from Exchange 2007 to Exchange 2016 through 2013 involves two major stages:

I. Upgrading from Exchange 2007 to Exchange 2013
For detailed steps, please refer to: http://mstechtalk.com/step-by-step-guide-to-migrate-from-exchange-server-2007-to-exchange-server-2013/

II. Upgrading from Exchange 2013 to Exchange 2016
For detailed steps, please refer to: https://www.lepide.com/blog/step-by-step-guide-for-migrating-exchange-server-2013-to-2016-part-1/

Upgrade from Exchange 2007 to Exchange 2016 using Exchange 2010

Upgrading from Exchange 2007 to Exchange 2016 through 2010 involves two major stages:

I. Upgrading from Exchange 2007 to Exchange 2010
It’s is easy to upgrade from Exchange 2007 to Exchange 2010 as they are immediate versions of Exchange. The steps are given here briefly:

  1. Ensure that you have the system requirements
    For smooth installation of Exchange 2010, and upgradation from 2007, ensure that you have the minimum system requirements:

    For Exchange 2010
    Processor- 64 bit supported (computer with x64 bit architecture)
    Disk space – 1.2 GB (for installation) + 200 MB free space
    OS –  Windows Server 2008 (SP2)/2008 R2 – Standard/Enterprise editions (64bit)
    For management tools –  Windows 7/Vista (64bit)
    Additional – NTFS (for disk partitions), .NET Framework 3.5 SP1, IIS,
    Windows PowerShell V2.0, Windows Remote Management V2.0

    In Exchange 2007
    Exchange 2007 Service Pack 3 (for each server)

  2. Configure disjoint namespace
    If you want to run a disjoint namespace in Exchange 2010, do the following:

    a) Configure the DNS suffix search list using GPMC
    In this step, set a DNS suffix search list using a GPO.

    b) Create a list of allowed DNS suffixes.
    For this, modify the relevant attribute (msDS-AllowedDNSSuffixes) value of the domain object container (using ADSI edit).Also, verify these settings (by pinging from other servers).

  3. Install the Client Access Role

    Client Access Role is the first server role to be installed on a server. This role facilitates the functioning of Exchange email clients.

    You can install this role from Exchange 2010 DVD by running the setup exe (if not installed previously, initiate .NET Framework 3.5 SP1 and Windows PowerShell v2 installation from here). For Exchange 2010 installation, accept the license agreement, and follow the instructions on the dialogue box. Here is a what you will do while going through different pages of the installation wizard:

    • Enable error reporting feature if required
    • Opt for ‘Custom Exchange Server installation’
    • Change Exchange installation path if necessary
    • Select Client Access Role on the Server Role Selection page
      cas-role-instllation

      Figure 1: Installation of Client Access Role

       

    • Configure an external FQDN (for connection with email clients)
    • Fix errors, if any are reported by the wizardFinally install Exchange and verity it using Get-ExchangeServer cmdlets (in Exchange Management Shell). After the installation, add digital certificates, and configure Outlook Anywhere and virtual directories.

      NOTE: It is possible to have separate servers for each role; but you can deploy multiple roles on servers as per the requirement.

  4. Install the Hub Transport Role

    Hub Transport Role facilitates internal mail flow in the organization. It can be installed on a separate server, or on the same server on which the CAS role was installed.

    To install the Hub Transport Role (on a separate server), follow the same steps as those for the installation of the CAS role. But on the Server Role Selection page, select Hub Transport Role. And verify the installation using Get-ExchangeServer cmdlets (in Exchange Management Shell).

    hubtransport-installation

    Figure 2: Installation of Hub Transport Role

    To ensure co-existence between the Exchange 2007 and Exchange 2010 environments, configure a legacy DNS and associate it with Exchange 2007 Server (while the current one will be associated with Exchange 2010 CAS). The steps are not given here as they may vary according to the firewall configuration and internet provider.

  5. Install the Unified Messaging Role

    The Unified Message Role facilitates voice mail and fax in Exchange mailboxes. For installation and verification of this role on a dedicated server, follow the steps for the earlier roles, but select Unified Messaging Role on the Server Role Selection page.

    The next step after the installation of UM role is to configure and enable unified messaging. If you already have UM in Exchange 2007, transition it to Exchange 2010 using Exchange Management Console or Exchange Management Shell. If you do not have one in Exchange 2007, create and configure a dial plan, gateways, and mailbox policies for UM, and then add the UM server to a dial plan. Finally, enable users for UM so that they can start using the UM features.

  6. Install the Mailbox Role

    Mailbox Role is important as it hosts databases—both the mailbox database and public folder database. Its installation and verification procedure—except for the selection of Mailbox Role on the Server Role Selection page— are the same as for described earlier.

    As the next step, you can move the offline address book generation to Exchange 2010. Use the Move Offline Address Book wizard (of Exchange Management Console) to do this.

    NOTE: How to install a server role along with an already installed one?
    After the installation of the Client Access Role, it is possible to install Hub Transport, Unified Messaging, and
    Mailbox Roles on the same server. However, the procedure for this is slightly different from that for installing
    them on a separate server. Here is how you can do this:
    1. Select Microsoft Exchange Server 2010 from the list in Control Panel > Programs and Features, and select Change.
    2. Click Next in the setup wizard.
    3. Select the required role on the Server Role Selection page.
    4. Proceed as with the installation procedure and complete the process.
    5. Restart the computer.

  7. Install the Edge Transport Role

    The Edge Transport Role is different from the all other server roles—it cannot exist with any other server role as the other roles do. Its responsibility being antivirus and anti-spam filtering, it is deployed outside the AD forest (in the perimeter network) for security reasons. On the installation and verification side, the procedure is similar, but it is mandatory to deploy this role on a dedicated server.

    At this stage, you can subscribe the Edge Transport server—either subscribe to the new Exchange 2010 Edge server or transition the Edge subscription from Exchange 2007 to Exchange 2010. These actions can be done using the Exchange Management Shell (on Exchange 2010 Edge Transport server). And the subscription can be verified using Get-EdgeSubscription cmdlets.

  8. Migrate mailboxes/public folders to exchange 2010.

    Finally, move mailboxes and public folder data from Exchange 2007 to Exchange 2010.

    To migrate mailboxes from Exchange 2007 to Exchange 2010 by create local move requests in Exchange Management Console (Recipient Configuration > Mailbox). While creating a move request, you can select mailboxes for migration and can browse for the database to which they are to be migrated. After successful completion of the move, use Get-Mailbox cmdlets to the mailboxes on the Exchange 2010 database to get the list of mailboxes over there.

    To migrate public folders from Exchange 2007 to Exchange 2010 by replicate them using the Exchange Management Console (Toolbox > Public Folder Management Console). The public folder migration can be verified by using Get-PublicFolder cmdlets in the Exchange Management Shell.

  9. Perform the final tasks
    Again use Get-ExchangeServer cmdlets to verify the Exchange installation. You can license the product now. And finally, proceed to configure accepted domains, internal mail flow, Outlook Anywhere, internal SMTP server list, and safe list aggregation.

Exchange 2010 to Exchange 2016 migration
The second part of the migration involves upgrading from Exchange 2010 to Exchange 2016. For Exchange 2010 to Exchange 2016 migration, refer to our article “A quick guide for upgrading from Exchange 2010 to 2016”.

Another informative article to move mailboxes from Exchange 2010 to Exchange 2016 using Exchange Admin Center: http://mstechtalk.com/migrating-to-exchange-2016-using-the-exchange-admin-center/

Exchange 2007 to 2016 migration using LepideMigrator for Exchange
LepideMigrator for Exchange helps you migrate directly from Exchange 2007 to Exchange 2016 (supports cross-forest migration only). The solution allows you to perform pre-migration analysis, synchronize Global Address List, migrate mailboxes and public folders, migrate limits and permissions, migrate Outlook rules & permissions and update Outlook profiles.

Pre-migration analysis
Before starting the migration, you can create and run a pre-migration analysis (for mailboxes and public folders) to get an idea of the approximate time required. To do this you have to provide the login credentials, network speed, no.  of agents used and the list of mailboxes/public folders to be migrated. After the analysis, the software displays the expected migration time.

Exchange 2007 to Exchange 2016 migration using LepideMigrator for Exchange
Exchange 2007 to Exchange 2016 migration project in the solution includes five simple migration jobs. Exchange administrators need to create and run the following jobs:

1.Mailbox configuration
2.GAL synchronization
3.Mailbox / Public folder migration
4.Outlook rule / folder permission migration
5.Profile manager

Creating a job is very easy. The screenshot below shows the first step towards creating a mailbox migration job (this step is similar for all other jobs).

1-mailboxmigrationjob

When creating a job, you can opt to run them immediately or at any desired time. The screenshot below shows the options (under Run Job at) for running a mailbox migration job (the same options are available for all the jobs).

1-runorscheduleajob

Mailbox configuration job
By creating and running a mailbox configuration job, you can migrate the limits and permissions of mailboxes/public folders from Exchange 2007 to Exchange 2016.

2-migratelimitsnpermissions

While migrating you can merge, reassign, replace or skip the permissions on the target Exchange with the permissions on the source Exchange. With Limits, you have the options to Replace and Skip.

GAL Synchronization Job
The GAL synchronization job lets you synchronize the Global Address List between the source and target Exchange Servers.

3-galsynjob

This job provides four options depending on how you want to create a GAL in the target.

  • Full Global Address List –  all addresses from the source
  • Partial Global Address List – selected addresses from the source
  • Full Container – all addresses from the selected source Container(s)
  • Partial Container – selected addresses from the selected source Container(s)

Mailbox / Public folder migration job
Mailbox / Public folder migration job migrates all or selected mailboxes/public folders from Exchange 2007 to Exchange 2016. Once you start creating the job, the wizard will lead you to various steps that can be performed by reading the instructions on the screen. Some important steps of the mailbox/public folder creation job are:

  1. Selection of the mailboxes/Public folders
    You can select mailboxes and public folders as per the requirement.
    4-selectmalboxorpublicfolder1
  2. Filtering
    You can filter the mailboxes and public folders for the required items. It helps to migrate only the selected items.
    5-filteringmailboxespublicfolders
    You can filter mailboxes/public folders by the criteria message classes and date range. The items from a particular date range can be included or excluded. And for mailboxes, an option to include or exclude folders also is available.
  3. Synchronization
    LepideMigrator for Exchange allows you synchronize mailboxes and public folders so that any change on end will be reflected in the other end depending on the selection you have made).
    6-synchronizemailboxespublicfolders
  4. Notifications
    Configuring notifications helps you get notified at different stages of the migration.
    7-notifications
    Note: For this, you need to configure Notification Setting (see the Tools > Notification Settings in the Tool bar) in the beginning.
  5. Setting migration time
    You can set the time period during which migration is to be done. This option helps to pause the migration in office working hours.
    8-setmigrationhours
  6. Outlook rules/folder permission migration jobs
    LepideMigrator for Exchange helps you migrate Outlook rules and folder permissions from Exchange 2007 to Exchange 2016.
    9-outlookfpmigration
  7. Profile Manager job
    After the completion of all other jobs, you can use the Profile Manager to update the Outlook profiles of the migrated mailboxes.
    10-profilemanager

Why LepideMigrator for Exchange is the better option for migrating from Exchange 2007 to 2016
LepideMigrator for Exchange allows you to migrate directly from Exchange 2007 to Exchange 2016. You do not need to use Exchange 2010/2013 as a go-between. The solution allows anyone, regardless of technical ability, to accomplish this migration easily as no in-depth knowledge of Exchange Server architecture is required. The solution’s load sharing feature enables migrations with low server resources. Its Report Console also provides complete details of the migration.

Article Summary
To upgrade from Exchange 2007 to Exchange 2016 is a two staged process—first you need to upgrade from Exchange 2007 to Exchange 2010/2013 and then from Exchange 2010/2013 to Exchange 2016. LepideMigrator for Exchange, however, simplifies the migration of mailboxes and public folders – by allowing you to directly move mailboxes and public folders from Exchange 2007 to Exchange 2016.

The following two tabs change content below.
Ajit Singh

Ajit Singh

Manager – Marketing Operations at Lepide Software Pvt. Ltd
Ajit Singh is a Manager – Marketing Operations with Lepide Software Pvt. Ltd. He is a positive person in every aspect of life and he believes, sharing ones expertise not only helps others in their professional endeavors but it makes the world a better place.

2 Comments

Leave a Reply

Your email address will not be published. Required fields are marked *