EXCHANGE 2010 TO EXCHANGE 2016 MIGRATION – PART 2

Exchange 2010 to Exchange 2016 Migration

Introduction

In Part 1 of this blog series, we talked about planning of Exchange 2010 server upgrade to Exchange 2016 Server. In this blog series, we are going to deploy Exchange 2016 Server in coexistence with Exchange 2010 Server in same active directory site. As we do not need a legacy namespace for Exchange 2016 Server by design, I am going to use the same namespace that we are using on Exchange Server 2010 i.e. mail.msexperttalk.com. Exchange 2010 to Exchange 2016 migration – part 2 blog post is focused on completing the pre-requisites for Exchange 2016 server and deploying your first Exchange 2016 production Server in coexistence with Exchange 2010 Server.

I highly recommend to use Microsoft Exchange sizing calculator to calculate the hardware requirements of Exchange 2016 Server. Latest version of Exchange sizing calculator can be downloaded from TechNet Gallery.

Preparing for Exchange 2016 Server Installation

Exchange 2016 server installation can be done using GUI or command line. In this blog article, we will install Exchange 2016 server using a command line interface. For step by step instructions of installing and configuring Exchange 2016, you can download ebook from TechNet Gallery. To install the Exchange 2016 server pre-requisites, run the following powershell cmdlet on windows server 2012 R2 machine where you’re planning to install Exchange server 2016.

Install-WindowsFeature RSAT-ADDS

EXCHANGE 2010 TO EXCHANGE 2016 MIGRATION – PART 2

Once the RSAT-ADDS feature is installed, run the following cmdlet to install other required pre-requisites for Exchange server 2016. This process requires a system reboot.

Install-WindowsFeature AS-HTTP-Activation, Server-Media-Foundation, 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, RSAT-ADDS

EXCHANGE 2010 TO EXCHANGE 2016 MIGRATION – PART 2

Once the server is rebooted, Install .Net Framework 4.5.2 and Microsoft Unified Communications Managed API Core Runtime, version 4.0. If you have all the latest updates installed on windows server 2012 R2, you will get a message that .Net framework 4.5.2 or higher version is already installed. Proceed with the installation on Microsoft Unified Communications Managed API Core runtime version 4.0.

EXCHANGE 2010 TO EXCHANGE 2016 MIGRATION – PART 2 EXCHANGE 2010 TO EXCHANGE 2016 MIGRATION – PART 2 EXCHANGE 2010 TO EXCHANGE 2016 MIGRATION – PART 2

Next step is to prepare your active directory forest for Exchange server 2016 installation. Active Directory preparation requires to extend the AD schema for Exchange 2016 server and prepare AD domain where you would like to deploy Exchange 2016 server. Once you extend the AD with Exchange 2016 Server attributes, you cannot install Exchange 2013 server in your messaging organization. If you plan to install Exchange 2013 Server later on, then first extend the AD with Exchange 2013 server and then extend the for Exchange 2016 server.

The process of extending the AD schema is irreversible and it’s highly recommended to perform a full backup of active directory before extending the schema.

To extend the AD schema for Exchange Server 2016, perform the following steps.

  • Login to Exchange server 2016 server with an admin account that is a member of Enterprise Admin and Schema Admin group.
  • Launch the command prompt with elevated rights and change the directory to Exchange server 2016 where you have extracted the setup files.
  • Run the following cmdlet to extend the AD schema

.\Setup /PrepareSchema /IAcceptExchangeServerLicenseTerms

EXCHANGE 2010 TO EXCHANGE 2016 MIGRATION – PART 2

  • Once the Active Directory schema is extended for Exchange Server 2016, next step is to prepare the domain in active directory forest where you need to install your Exchange Server 2016. To prepare the AD domain, run the following cmdlet

.\Setup /PrepareAD /IAcceptExchangeServerLicenseTerms

EXCHANGE 2010 TO EXCHANGE 2016 MIGRATION – PART 2

  • After preparing the AD, the last step for exchange pre-requisites is to prepare the domain for Exchange 2016 installation. To prepare a domain, run the following cmdlet

.\Setup /PrepareDomain /IAcceptExchangeServerLicenseTerms

EXCHANGE 2010 TO EXCHANGE 2016 MIGRATION – PART 2

We are now ready to install the first exchange server 2016 server in our exchange organization.

Installing Exchange Server 2016

After preparing the pre-requisites for Exchange Server 2016, next step is to install the exchange server 2016. To install Exchange server 2016 using powershell, run the following cmdlet in elevated window.

.\setup /Mode:Install /Roles:Mailbox /IAcceptExchangeServerLicenseTerms

After the successful installation of Exchange 2016 server. Reboot the server.

Conclusion

In Part 2 of this blog series, we have successfully completed the pre-requisites installation for Exchange Server 2016. We have also installed our first Exchange server 2016 in Exchange server 2010 organization. In Part 3 of this series, we will perform the post installation tasks.

If you would like to read the other parts of this blog article series please go to: