Exchange 2013 windows server 2016

• Deployment Location: On-premises
• Target Environment: Exchange Server 2016 CU4
• Current Environment: Exchange Server 2010 or Exchange Server 2013 or mixed
• Public Folder Location: Exchange Server 2013

Understanding of Exchange Server 2016: Exchange Server 2016 wraps up in two Exchange roles to simplify hassle of many roles evolution in previous versions of Exchange Servers:

• Mailbox- The Mailbox server includes the Client Access protocols, the Transport service, the Mailbox databases, and Unified Messaging. The Mailbox server handles all activity for the active mailboxes on that server.
• Edge Transport- The Edge Transport server role is deployed in your organization’s perimeter network and outside your internal Active Directory forest. Designed to minimize the attack surface, the Edge Transport server handles all Internet-facing mail flow and provides SMTP relay and smart host services, anti-spam features, message protection, and transport security for the Exchange organization.

Extend AD DS Schema and Prepare AD DS: To make sure Active Directory Forest is ready to run Exchange 2016 Setup. Open a Windows Command Prompt window and go to where you downloaded the Exchange 2016 installation files. Run the following command to extend the schema.

set-executionpolicy unrestricted

Setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms

Setup.exe /PrepareAD /OrganizationName:”<organization name>” /IAcceptExchangeServerLicenseTermsSetup.exe /PrepareAllDomains /IAcceptExchangeServerLicenseTerms

(Optional Steps, Only required if you have multiple Domains in a single forest)

Certificates: When deploying Exchange 2016, Microsoft strongly recommend that you obtain a public certificate issued by a third either party CA or use current certificate from existing environment. Export current certificate from Exchange Server 2013 and save the PFX format certificate into new Windows Server 2016 where Exchange Server 2016 will be installed. Add Common Name mail.domain.com and SAN autodiscover.domain.com or use *.domain.com

Supported Client: Exchange 2016 and Exchange Online support the following versions of Outlook:

• Outlook 2016
• Outlook 2013
• Outlook 2010
• Outlook for Mac for Office 365
• Outlook for Mac 2011

Hybrid Deployment Consideration with office 365: The hybrid deployment can serve as an intermediate step to moving completely to an Exchange Online organization. To configure a hybrid deployment after initial Exchange 2016 installation or migration is complete, select Hybrid Configuration Wizard from EAC and configure desired mailflow architecture to suit your needs.

Exchange Server 2016 Systems Requirements:

• Update Rollup 11 Exchange 2010 SP3 or later on all Exchange 2010 servers in the organization, including Edge Transport servers.
• Exchange 2013 Cumulative Update 10 or later on all Exchange 2013 servers in the organization, including Edge Transport servers.
• Windows Server 2008 domain functional level
• Windows Server 2016 with desktop experience or Windows Server 2012 R2
• 2vCPU, 8GB RAM, 30GB free space and space for mailboxes
• .NET Framework 4.6.2
• Unified Communications Managed API (UCMA) 5.0

Permission and RBAC:

Exchange Server 2016 Deployment Datasheet

Note:

• Edge Transport- If you have existing Edge Transport servers or if you plan to install Edge Transport servers, or both.
• Co-existence Scenario- Applicable only if your existing organization has Exchange 2010/2013 servers.
• Availability- Add multiple servers for availability and site resiliency

Configure default offline address book:

Configure offline address book if OAB has not been already configured in the current environment.

Get-MailboxDatabase | Format-Table Name, Server, OfflineAddressBook -AutoGet-MailboxDatabase | Set-MailboxDatabase -OfflineAddressBook “Default Offline Address Book”

Servers Build:

• Build Windows Server 2016 and assign IPv4 to the network interface of to be Exchange Servers.
• Rename all other Windows Server 2016 prepared for Exchange 2016 and Join them to domain
• Rename Computer and create DNS prefix for Exchange 2016 Edge Server

1. Log on to the computer where you want to install the Edge Transport role as a user that’s a member of the local Administrators group.
2. Open the Control Panel, and then double-click System.
3. In the Computer name, domain, and workgroup settings section, click Change settings.
4. In the System Properties window, make sure the Computer Name tab is selected, and then click Change.
5. In Computer Name/Domain Changes, click More .
6. In Primary DNS suffix of this computer, enter the DNS domain name for the Edge Transport server. For example, domain.com.
7. Click OK to close each window.
8. Restart the computer.

• Windows Server 2016 Roles and Features Prerequisites for Mailbox Role:

Open Windows PowerShell. Run the following command to install the required Windows components.

Install-WindowsFeature 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

After you have installed the operating system roles and features, reboot computer. Install the following software in the order shown:

1. Microsoft Knowledge Base article KB3206632
2. Microsoft Unified Communications Managed API 4.0, Core Runtime 64-bit

Windows Server 2016 Roles and Features Prerequisites for Edge Transport Role:

Open Windows PowerShell. Run the following command to install the required Windows components.

Install-WindowsFeature ADLDS

Installation of Exchange Server 2016:

1. Download latest release of Exchange 2016 to an accessible network location.
2. Log on to the computer where you want to install Exchange and navigate to the network location of the Exchange 2016 installation files.
3. Start Exchange 2016 Setup by double-clicking Setup.exe. You must right-click Setup.exe, and then select Run as administrator.
4. On the Check for Updates page, choose whether you want Setup to connect to the Internet and download product and security updates for Exchange 2016. If you select Connect to the Internet and check for updates, Setup will download updates and apply them before continuing. If you select Don’t check for updates right now, you can download and manually install updates later. We recommend that you download and install updates now. Click Next to continue.
5. The Introduction page begins the process of installing Exchange into your organization. It will guide you through the installation. Several links to helpful deployment content are listed. We recommend that you visit these links before continuing setup. Click Next to continue.
6. On the License Agreement page, review the software license terms. If you agree to the terms, select I accept the terms in the license agreement, and then click Next.
7. On the Recommended settings page, select whether you want to use the recommended settings. If you select Use recommended settings, Exchange will automatically send Microsoft your error reports and information about your computer hardware and how you use Exchange. If you select Don’t use recommended settings, these settings remain disabled, but you can enable them at any time after Setup completes.
8. On the Server Role Selection page, select Mailbox role. The management tools are installed automatically if you install any server role.
9. Select Automatically install Windows Server roles and features that are required to install Exchange Server to have the Setup wizard install required Windows prerequisites. You may need to reboot the computer to complete the installation of some Windows features. If you don’t select this option, you must manually install the Windows features.
10. Click Next to continue.
11. On the Installation Space and Location page, either accept the default installation location or click Browse to choose a new location. Make sure that you have enough disk space available in the location where you want to install Exchange. Click Next to continue.
12. On the Malware Protection Settings page, choose whether you want to enable malware scanning. If you disable malware scanning, it can be enabled in the future. Unless you have a specific reason to disable malware scanning, we recommend that you keep it enabled. Click Next to continue.
13. On the Readiness Checks page, view the status to determine if the organization and server role prerequisite checks completed successfully. If they haven’t completed successfully, you must resolve any reported errors before you can install Exchange 2016. You don’t need to exit Setup when resolving some of the prerequisite errors. After resolving a reported error, click Back, and then click Next to run the prerequisite check again. Be sure to also review any warnings that are reported. If all readiness checks have completed successfully, click Install to install Exchange 2016.
14. On the Completion page, click Finish.
15. Restart the computer after Exchange 2016 installation is complete. Repeat the steps for all other Exchange Server 2016 Mailbox Role.

Installation of Edge Server 2016

1. After you download Exchange 2016, log on to the computer where you want to install it.
2. Go to the network location of the Exchange 2016 installation files.
3. Start Exchange 2016 Setup by double-clicking Setup.exe as an administrator.
4. On the Check for Updates page, choose whether you want Setup to connect to the Internet and download product and security updates for Exchange 2016. If you select Connect to the Internet and check for updates, Setup will download updates and apply them before continuing. If you select Don’t check for updates right now, you can download and manually install updates later. We recommend that you download and install updates now. Click Next to continue.
5. The Introduction page begins the process of installing Exchange into your organization. It will guide you through the installation. Several links to helpful deployment content are listed. We recommend that you visit these links before continuing setup. Click Next to continue.
6. On the License Agreement page, review the software license terms. If you agree to the terms, select I accept the terms in the license agreement, and then click Next.
7. On the Recommended settings page, select whether you want to use the recommended settings. If you select Use recommended settings, Exchange will automatically send Microsoft your error reports and information about your computer hardware and how you use Exchange. If you select Don’t use recommended settings, these settings remain disabled, but you can enable them at any time after Setup completes. For more information about these settings and how information sent to Microsoft is used, click ?.
8. On the Server Role Selection page, select Edge Transport. Remember that you can’t add the Mailbox server role to a computer that has the Edge Transport role installed. The management tools are installed automatically if you install either server role.
9. Select Automatically install Windows Server roles and features that are required to install Exchange Server to have the Setup wizard install required Windows prerequisites. You may need to reboot the computer to complete the installation of some Windows features. If you don’t select this option, you need to install the Windows features manually.
10. Click Next to continue.
11. On the Installation Space and Location page, either accept the default installation location or click Browse to choose a new location. Make sure that you have enough disk space available in the location where you want to install Exchange. Click Next to continue.
12. On the Readiness Checks page, view the status to determine if the organization and server role prerequisite checks completed successfully. If they haven’t completed successfully, you need to resolve any reported errors before you can install Exchange 2016. You don’t need to exit Setup when resolving some of the prerequisite errors. After resolving a reported error, click back, and then click Next to run the prerequisite check again. Be sure to also review any warnings that are reported. If all readiness checks have completed successfully, click Next to install Exchange 2016.
13. On the Completion page, click Finish
14. Restart the computer after Exchange 2016 installation is complete.

Post Installation Tasks:

Check or Add Exchange Organisation Management Role

1. In the EAC https://EXCH2016/ecp?ExchClientVer=15, go to Permissions > Admin Roles. On the Admin Roles page, select Organization Management.
2. In the details pane, view the Members list. If the Exchange 2016 mailbox has been successfully added as a member of the Organization Management role group, the mailbox will be listed here.

Create a test mailbox

1. Open the EAC https://EXCH2016/ecp?ExchClientVer=15 by browsing to the URL of your Exchange 2016 Mailbox server.
2. Enter the user name and password of the account you used to install Exchange 2016 in Domain\user name and Password, and then click Sign in.
3. Go to Recipients > Mailboxes. On the Mailboxes page, click Add , and then select User mailbox.
4. Provide the information required for the new user, and then click Save.
5. Go to Permissions > Admin Roles. On the Admin Roles page, select Organization Management, and then click Edit .
6. Under Members, click Add .
7. Select the Exchange 2016 mailbox you just created, click Add , then click OK. Then click Save.

Install Exchange Server 2016 Product key

1. Open the EAC by browsing to https://Exch2016/ecp.
2. Enter your user name and password in Domain\user name and Password, and then click Sign in.
3. Go to Servers > Servers. Select the server you want to license, and then click Edit .
4. (Optional) If you want to upgrade the server from a Standard Edition license to an Enterprise Edition license, on the General page, select Change product key. You’ll only see this option if the server is already licensed.
5. On the General page, enter your product key in the Enter a valid product key text boxes.
6. Click Save.
7. If you licensed an Exchange server running the Mailbox server role, do the following to restart the Microsoft Exchange Information Store service:
   1. Open Control Panel, go to Administrative Tools, and then open Services.
   2. Right-click on Microsoft Exchange Information Store and click Restart.

Simply use the below PowerShell Cmdlets to install product key.

Set-ExchangeServer ExCH2016Server01 -ProductKey XXXXX-XXXXX-XXXXX-XXXXX-XXXXX

Configure Exchange Server 2016 External URL:

There are several settings that you need to configure on the Exchange 2016 virtual directories, which include Outlook Anywhere, Exchange ActiveSync, Exchange Web Services, Offline Address Book (OAB), Outlook on the web, the Exchange admin center, and the availability service.

1. Open the EAC by browsing to the URL of your Exchange 2016 Mailbox server. For example, https://EXCH2016/ECP or https://EXCH2016/ecp?ExchClientVer=15 .
2. Enter your user name and password in Domain\user name and Password, and then click Sign in.
3. Go to Servers > Servers, select the name of the Internet-facing Exchange 2016 Mailbox server, and then click Edit.
4. Click Outlook Anywhere.
5. In the Specify the external hostname field, specify the externally accessible FQDN of the Mailbox server. For example, mail.domain.com.
6. While you’re here, let’s also set the internally accessible FQDN of the Mailbox server. In the Specify the internal hostname field, enter the FQDN you used in the previous step. For example, mail.domain.com.
7. Click Save.
8. Go to Servers > Virtual directories.
9. In the Select server field, select the Internet-facing Exchange 2016 Mailbox server.
10. Select the virtual directory you want to change, and then click Edit.
11. In External URL, replace the host name between https:// and the first forward slash (/ ) with the new FQDN you want to use. For example, if you want to change the EWS virtual directory FQDN from EXCH2016.domain.com to mail.domain.com, change the external URL from https://EXCH2016.domain.com/ews/exchange.asmx to https://mail.domain.com/ews/exchange.asmx.
12. Click Save.
13. Repeat steps 9, 10 and 11 for each virtual directory you want to change.

To verify that you successfully configured the external URL on the Internet-facing Exchange 2016 Mailbox server virtual directories, do the following:

1. In the EAC, go to Servers > Virtual directories.
2. In the Select server field, select the Internet-facing Exchange 2016 Mailbox server.
3. Select a virtual directory and then, in the virtual directory details pane, verify that the External URL field is populated with the correct FQDN and service as shown below:

Configure internal and external URLs to be the same:

Note: I personally prefer to have same URL for internal and external web access. The same URL eliminates confusion when using OWA internally and externally. Microsoft also recommends that you use the same URL for both internal and external URLs. Using the same URL makes it easier for users to access your Exchange servers because they only have to remember one address. Regardless of the choice you make, you need to make sure you configure a private DNS zone for the address space you configure.

1. Open the Exchange Management Shell on your Exchange 2016 Mailbox server.
2. Store the host name of your Exchange 2016 Mailbox server in a variable that will be used in the next step. For example, EXCH2016.

$HostName = “EXCH2016”

1. Run each of the following commands in the Shell to configure each internal URL to match the virtual directory’s external URL.

Set-EcpVirtualDirectory “$HostName\ECP (Default Web Site)” -InternalUrl ((Get-EcpVirtualDirectory “$HostName\ECP (Default Web Site)”).ExternalUrl)7.

Set-WebServicesVirtualDirectory “$HostName\EWS (Default Web Site)” -InternalUrl ((Get-WebServicesVirtualDirectory “$HostName\EWS (Default Web Site)”).ExternalUrl)

Set-MapiVirtualDirectory “$HostName\mapi (Default Web Site)” -InternalUrl ((Get-MapiVirtualDirectory “$HostName\mapi (Default Web Site)”).ExternalUrl)

Set-ActiveSyncVirtualDirectory “$HostName\Microsoft-Server-ActiveSync (Default Web Site)” -InternalUrl ((Get-ActiveSyncVirtualDirectory “$HostName\Microsoft-Server-ActiveSync (Default Web Site)”).ExternalUrl)

Set-OabVirtualDirectory “$HostName\OAB (Default Web Site)” -InternalUrl ((Get-OabVirtualDirectory “$HostName\OAB (Default Web Site)”).ExternalUrl)

Set-OwaVirtualDirectory “$HostName\OWA (Default Web Site)” -InternalUrl ((Get-OwaVirtualDirectory “$HostName\OWA (Default Web Site)”).ExternalUrl)

Set-PowerShellVirtualDirectory “$HostName\PowerShell (Default Web Site)” -InternalUrl ((Get-PowerShellVirtualDirectory “$HostName\PowerShell (Default Web Site)”).ExternalUrl)

While you are in the Shell, let’s also configure the Offline Address Book (OAB) to allow Autodiscover to select the right virtual directory for distributing the OAB. Run the following command to do this.

Get-OfflineAddressBook | Where {$_.ExchangeVersion.ExchangeBuild.Major -Eq 15} | Set-OfflineAddressBook -GlobalWebDistributionEnabled $True -VirtualDirectories $Null

To verify that you successfully configured the internal URL on the Exchange 2016 Mailbox server virtual directories, do the following:

1. In the EAC, go to Servers > Virtual directories.
2. In the Select server field, select the Internet-facing Exchange 2016 Mailbox server.
3. Select a virtual directory, and then click Edit.
4. Verify that the Internal URL field is populated with the correct FQDN and service as shown below:

Configure Exchange 2016 certificates

Outlook Anywhere and Exchange ActiveSync, require certificates to be configured on your Exchange 2016 server. You can choose whether you want to re-use the SSL certificate installed from an existing Exchange server or purchase a new SSL certificate from a third-party certificate authority (CA). If you decide to re-use a certificate, the host names you have configured on the Exchange 2016 virtual directories must match the host names configured on the SSL certificate.

1. Open the EAC by browsing to the URL of your Mailbox server. For example, https://EXCH2016/ECP.
2. Enter your user name and password in Domain\user name and Password, and then click Sign in.
3. Go to Servers > Certificates. On the Certificates page, make sure your Mailbox server is selected in the Select server field, and then click New.
4. In the New Exchange certificate wizard, select Create a request for a certificate from a certification authority, and then click Next.
5. Specify a name for this certificate, and then click Next.
6. If you want to request a wildcard certificate, select Request a wild-card certificate, and then specify the root domain of all subdomains in the Root domain If you don’t want to request a wildcard certificate and instead want to specify each domain with SAN like mail.domain.com, edge.domain.com and sts.domain.com (for future hybrid configuration with ADFS)you want to add to the certificate, leave this page blank. Click Next.
7. Click Browse, and specify an Exchange server to store the certificate on. The server you select should be the Internet-facing Mailbox server. Click Next.
8. For each service in the following list, verify that the external or internal server names that users will use to connect to the Exchange server are correct. For example:
   • If you configured your internal and external URLs to be the same, Outlook Web App (when accessed from the Internet) and Outlook Web App (when accessed from the Intranet) should show mail.domain.com. OAB (when accessed from the Internet) and OAB (when accessed from the Intranet) should show mail.domain.com, edge.domain.com and sts.domain.com (for future hybrid configuration with ADFS)
9. These domains will be used to create the SSL certificate request. Click Next.
10. Add any additional domains you want included on the SSL certificate.
11. Select the domain that you want to be the common name (for example, domain.com) for the certificate and click Set as common name. Click Next.
12. Provide information about your organization. This information will be included with the SSL certificate. Click Next.
13. Specify the network location where you want this certificate request to be saved. Click Finish.

After you’ve saved the certificate request, submit the request to your CA. After you receive the certificate from the CA, complete the following steps:

1. On the Server > Certificates page in the EAC, select the certificate request you created in the previous steps.
2. In the certificate request details pane, under Status, click Complete.
3. On the Complete pending request page, specify the path to the SSL certificate file, and then click OK.
4. Select the new certificate you just added, and then click Edit.
5. On the certificate page, click Services.
6. Select the services you want to assign to this certificate. At minimum, you should select IIS, but you can also select IMAP, POP, and UM call router if you use these services. If you want to use secure transport, you can also select SMTP to make this certificate available to Exchange 2016 transport. Click Save.
7. click Yes.

To re-use certificate you need to export your certificate from your pre-exiting Exchange server with the certificate’s private key using the following steps:

1. Log on directly to a pre-existing Exchange Client Access server with an administrator user account.
2. Open an empty Microsoft Management Console (MMC).
3. Click File, then Add/Remove Snap-in.
4. In the Add or Remove Snap-ins window, select Certificates, and then click Add >.
5. In the Certificates snap-in window that appears, select Computer account, and then click Next.
6. Select Local computer and click Finish. Then click OK.
7. Under Console Root, expand Certificates (Local Computer), Personal, and then Certificates.
8. Select the third-party certificate that’s used by Exchange that matches the host names you’ve configured on the Exchange 2016 server. This must be a third-party certificate and not a self-signed certificate.
9. Right-click the certificate, select All Tasks, and then click Export.
10. In the Certificate Export Wizard, click Next.
11. Select Yes, export the private key, and then click Next.
12. Make sure Personal Information Exchange – PKCS #12 (.PFX) and Include all certificates in the certification path if possible are selected. Make sure no other options are selected. Click Next.
13. Select Password and enter a password to help secure your certificate. Click Next.
14. Specify a file name for the new certificate. Use the file extension .pfx. Click Next and then click Finish.
15. You’ll receive a confirmation prompt if the certificate export was successful. Click OK to close it.
16. Copy the .pfx file you created to your Internet-facing Exchange 2016 Mailbox server.

After you’ve exported the certificate from your pre-existing Exchange server, you need to import the certificate on your Exchange 2016 server using the following steps:

1. Log on to your Internet-facing Exchange 2016 Mailbox server with an administrator user account.
2. Open an empty MMC.
3. Click File, then Add/Remove Snap-in.
4. In the Add or Remove Snap-ins window, select Certificates, and then click Add >.
5. In the Certificates snap-in window that appears, select Computer account, and then click Next.
6. Select Local computer and click Finish. Then click OK.
7. Under Console Root, expand Certificates (Local Computer), and then Personal.
8. Right-click Personal, select All Tasks, and then click Import.
9. In the Certificate Import Wizard, click Next.
10. Click Browse, and select the .pfx file you copied to your Exchange 2016 Mailbox server. Click Open and then click Next.
11. In the Password field, enter the password you used to help secure the certificate when you exported it on the pre-existing Exchange server.
12. Verify that Include all extended properties is selected, and then click Next.
13. Verify that Place all certificates in the following store is selected and Personal is shown in Certificate store. Click Next and then Finish.
14. You’ll receive a confirmation prompt if the certificate import was successful. Click OK to close it.

Now that the new certificate has been imported on your Exchange 2016 Mailbox server, you need to assign it to your Exchange services using the following steps:

1. Open the EAC by browsing to the URL of your Exchange 2016 Mailbox server. For example, https://EXCH2016/ECP.
2. Enter your user name and password in Domain\user name and Password, and then click Sign in.
3. On the Server > Certificates page in the EAC, select the new certificate you just added, and then click Edit.
4. On the certificate page, click Services.
5. Select the services you want to assign to this certificate. At minimum, you should select IIS, but you can also select IMAP, POP, and UM call router if you use these services. If you want to use secure transport, you can also select SMTP to make this certificate available to Exchange 2016 transport. Click Save.
6. click Yes.

Configure Outlook Anywhere

• The Outlook Anywhere external URL is set to the external host name of the Exchange 2016 server.
• Client authentication, which is used to allow clients like Outlook 2016 to authenticate with Exchange, is set to Basic.
• Internet Information Services (IIS) authentication, which is used to allow Exchange servers to communicate, set to NTLM and Basic.

Perform the following steps to enable and configure Outlook Anywhere on your Exchange 2010 servers. The following command will change the configuration of Outlook Anywhere on any Exchange 2010 server in your organization on which it’s already enabled.

1. Open the Exchange Management Shell on your Exchange 2010 Client Access server.
2. Store the external host name of your Internet-facing Exchange 2016 Mailbox server in a variable that will be used in the next steps. For example, mail.domain.com.

$Exchange2016HostName = “mail.domain.com”

1. Run the following command to configure Exchange 2010 servers that already have Outlook Anywhere enabled to accept connections from Exchange 2016 servers.

Get-ExchangeServer | Where {($_.AdminDisplayVersion -Like “Version 14*”) -And ($_.ServerRole -Like “*ClientAccess*”)} | Get-ClientAccessServer | Where {$_.OutlookAnywhereEnabled -Eq $True} | ForEach {Set-OutlookAnywhere “$_\RPC (Default Web Site)” -ClientAuthenticationMethod Basic -SSLOffloading $False -ExternalHostName $Exchange2016HostName -IISAuthenticationMethods NTLM, Basic}

1. Run the following command to enable Outlook Anywhere and configure Exchange 2010 to accept connections from Exchange 2016 servers.

Get-ExchangeServer | Where {($_.AdminDisplayVersion -Like “Version 14*”) -And ($_.ServerRole -Like “*ClientAccess*”)} | Get-ClientAccessServer | Where {$_.OutlookAnywhereEnabled -Eq $False} | Enable-OutlookAnywhere -ClientAuthenticationMethod Basic -SSLOffloading $False -ExternalHostName $Exchange2016HostName -IISAuthenticationMethods NTLM, Basic

To verify that you successfully configured Outlook Anywhere on your Exchange 2010 servers to accept connections redirected from Exchange 2016, do the following:

1. Open the Exchange Management Shell on your Exchange 2010 Client Access server.
2. Run the following command to view the Outlook Anywhere configuration on your Exchange 2010 servers.

Get-ExchangeServer | Where {($_.AdminDisplayVersion -Like “Version 14*”) -And ($_.ServerRole -Like “*ClientAccess*”)} | Get-OutlookAnywhere | Format-Table Server, ClientAuthenticationMethod, IISAuthenticationMethods, SSLOffloading, ExternalHostname -Auto

Configure Edge Transport server

To make the best use of an Edge Transport server, you need to configure an Edge Subscription between the Edge Transport server and an Exchange 2016 Mailbox server in an Active Directory site. Edge Subscriptions automatically create Send connectors on the Edge Transport server based on the configuration of the Mailbox server it’s subscribed to. They also replicate recipient and other information to the Edge Transport server to improve anti-spam functionality.

Perform the following steps to configure your Edge Transport server 2016.

1. Run the following command on the Edge Transport server.

New-EdgeSubscription -FileName “C:\Edge2016.xml”

1. Copy the Edge2016.xml to your Mailbox server. Open the Exchange Management Shell on the Mailbox server that you want to subscribe to the Edge Transport server. This Mailbox server should be in the Active Directory site to which you want to subscribe the Edge Transport server.
2. On the Mailbox server, run the following command. Specify the path to the location where you copied the Edge2016.xml file, and the Active Directory site where your Mailbox server is located.

New-EdgeSubscription -FileData ([byte[]]$(Get-Content -Path “C:\Edge2016.xml” -Encoding Byte -ReadCount 0)) -Site “Default-First-Site-Name” -CreateInternetSendConnector $true -CreateInboundSendConnector $true

1. On the Mailbox server, run the following command.

Start-EdgeSynchronization

1. On the Mailbox server, run the Test-EdgeSynchronization This cmdlet gives you detailed information about whether the subscribed Edge Transport servers have current and accurate synchronization status.

Test-EdgeSynchronization

Remove legacy Edge Subscriptions

Now that you’ve installed an Exchange 2016 Edge Transport server in your perimeter network, we need to remove the Edge Subscription between your legacy Edge Transport and Hub Transport servers. This needs to be done so that mail will flow through your new Exchange 2016 Edge Transport server. Make sure your firewall rules are changed and pointed to new Edge Servers.

Perform the following steps to remove the Edge Subscription between your legacy Edge Transport and Hub Transport servers.

1. Log on to your legacy Edge Transport server.
2. Run the following command to find the name of the Edge Subscription on the server.

Get-EdgeSubscription

1. Remove the Edge Subscription using the following command and the name of the subscription found in the previous step.

Remove-EdgeSubscription EXCH2013EDGE

1. Log on to your legacy Hub Transport server.
2. Run the following command to find the name of the Edge Subscription on the server.

Get-EdgeSubscription

1. Remove the Edge Subscription using the following command and the name of the subscription found in the previous step.

Remove-EdgeSubscription EXCH2013

On the Edge Transport and Hub Transport servers server, run the Get-EdgeSubscription cmdlet. No Edge Subscriptions should be listed.

Get-EdgeSubscription

Configure service connection point

1. Open the Exchange Management Shell on your Exchange 2010 Client Access server.
2. Store the Autodiscover host name of your Internet-facing Exchange 2016 Mailbox server in a variable that will be used in the next step. For example, autodiscover.domain.com.

$AutodiscoverHostName = “autodiscover.domain.com”

1. Run the following command to set the SCP object on every Exchange 2010 server to the Autodiscover URL of the new Exchange 2016 server.

Get-ExchangeServer | Where {($_.AdminDisplayVersion -Like “Version 14*”) -And ($_.ServerRole -Like “*ClientAccess*”)} | Set-ClientAccessServer -AutoDiscoverServiceInternalUri https://$AutodiscoverHostName/Autodiscover/Autodiscover.xml

Perform the following steps to configure the SCP object on your Exchange 2013 servers.

1. Open the Exchange Management Shell on your Exchange 2013 Client Access server.
2. Store the Autodiscover host name of your Internet-facing Exchange 2016 Mailbox server in a variable that will be used in the next step. For example, autodiscover.domain.com.

$AutodiscoverHostName = “autodiscover.domain.com”

1. Run the following command to set the SCP object on every Exchange 2013 server to the Autodiscover URL of the new Exchange 2016 server.

Get-ExchangeServer | Where {($_.AdminDisplayVersion -Like “Version 15.0*”) -And ($_.ServerRole -Like “*ClientAccess*”)} | Set-ClientAccessServer -AutoDiscoverServiceInternalUri https://$AutodiscoverHostName/Autodiscover/Autodiscover.xml

Perform the following steps to configure the SCP object on your Exchange 2016 servers.

1. Open the Exchange Management Shell on your Exchange 2016 Mailbox server.
2. Store the Autodiscover host name of your Exchange 2016 Mailbox server in a variable that will be used in the next step. For example, autodiscover.domain.com.

$AutodiscoverHostName = “autodiscover.domain.com”

1. Run the following command to set the SCP object on every Exchange 2016 server to the Autodiscover URL of the new Exchange 2016 server.

Get-ExchangeServer | Where {($_.AdminDisplayVersion -Like “Version 15.1*”) -And ($_.ServerRole -Like “*Mailbox*”)} | Set-ClientAccessService -AutoDiscoverServiceInternalUri https://$AutodiscoverHostName/Autodiscover/Autodiscover.xml

To verify that you successfully configured the AutoDiscoverServiceInternalUrl property on your Exchange 2010 servers with the value of the Exchange 2016 Autodiscover URL, do the following:

1. Open the Exchange Management Shell on your Exchange 2010/2013 Client Access server.
2. Run the following command to view the SCP object configuration on Exchange 2010 servers.

Get-ExchangeServer | Where {($_.AdminDisplayVersion -Like “Version 14*”) -And ($_.ServerRole -Like “*ClientAccess*”)} | Get-ClientAccessServer | Format-Table Name, AutoDiscoverServiceInternalUri –Auto Get-ExchangeServer | Where {($_.AdminDisplayVersion -Like “Version 15*”) -And ($_.ServerRole -Like “*ClientAccess*”)} | Get-ClientAccessServer | Format-Table Name, AutoDiscoverServiceInternalUri -Auto

To verify that you successfully configured the AutoDiscoverServiceInternalUrl property on your Exchange 2010 servers with the value of the Exchange 2016 Autodiscover URL, do the following:

Configure DNS records

It’s time to change your DNS records to direct connections to your new Exchange 2016 servers. You’ll move the host names (for example, mail.domain.com) users have been using to connect to Outlook Web Access (now known as Outlook on the web in Exchange 2016), Autodiscover, and so on, from existing Exchange servers to new Exchange 2016 server.

Other option is without changing the DNS records to point your public DNS records to a new external IP address for Exchange 2016 Edge server, you can reconfigure your firewall to route connections for the original IP address to the Exchange 2016 server instead of the Exchange 2010/2013 server. The existing Exchange Client Access server no longer needs to be accessible from the Internet because all connections will be proxied by the Exchange 2016 server. If you choose to reconfigure your firewall, you don’t need to change your public DNS records. TTL 10 minutes to minimize impact. If you dc change DNS records, it should be like the below DNS records.

Migrating Mailboxes from Exchange 2010/2013 to Exchange 2016:

Move arbitration mailbox

1. In the EAC, go to Recipients > Migration.
2. Click New , and then click Move to a different database.
3. On the New local mailbox move page, click Select the users that you want to move, and then click Add .
4. On the Select Mailbox page, add the mailboxes that have the following aliases:
   • SystemMailbox{1f05a927-7bd0-47e5-9b6a-0b5ec3f44403}
   • FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042
   • DiscoverySearchMailbox{D919BA05-46A6-415f-80AD-7E09334BB852}
   • SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9}
   • SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}
   • Migration.8f3e7716-2011-43e4-96b1-aba62d229136
5. Click OK, and then click Next.
6. On the Move configuration page, type the name of the migration batch, and then click Browse next to the Target database box.
7. On the Select Mailbox Database page, add the mailbox database to move the system mailbox to. Verify that the version of the mailbox database that you select is Version 15.1, which indicates that the database is located on an Exchange 2016 server.
8. Click OK, and then click Next.
9. On the Start the batch page, select the options to automatically start and complete the migration request, and then click New.

Move mailboxes to Exchange 2016

Since you have built a co-existence environment, you can move mailboxes to your Exchange 2016 Mailbox server. To move mailboxes to your Exchange 2016 Mailbox server, you’ll need to use the

1. Open the EAC by browsing to the URL of your Mailbox server. For example, https://EXCH2016/ECP.
2. Enter your user name and password in Domain\user name and Password, and then click Sign in.
3. Go to Recipients > Migration, click Add , and then select Move to a different database.
4. Under Select the users that you want to move, click Add .
5. In the Select Mailbox window, select the mailboxes you want to move, and then click Add and then OK.
6. Verify that the mailboxes you want to move are listed, and then click Next.
7. Specify a name for the new mailbox move, and verify that Move the primary mailbox and the archive mailbox, if one exists, is selected.
8. Under Target database, click Browse.
9. In the Select Mailbox Database window, select a mailbox database on the Exchange 2016 server that you want to move the mailboxes to, click Add and then OK.
10. Verify that the mailbox database displayed in Target database is correct, and then click Next.
11. Decide which user should receive the mailbox move report once the move is complete. By default, the current user will receive the move report. If you want to change which user receives the report, click Browse, and then select a different user.
12. Verify Automatically start the batch is selected.
13. Decide whether you want to have mailbox moves complete automatically. During the finalization phase, the mailbox is unavailable for a short time. If you choose to manually complete the mailbox move, you can decide when the move is finalized. For example, you might want to finalize the move during off-work hours. Select or clear Automatically complete the migration batch.
14. Click New.

Migrate public folders from Exchange 2013 to Exchange 2016

To migrate your Exchange 2013 public folders to Exchange 2016, you need to move all of your Exchange 2013 public folder mailboxes to an Exchange 2016 server. Before you move your public folder mailboxes, here are some things you should think about:

• Exchange 2016 capacity Make sure the Exchange 2016 servers where you’ll move your public folder mailboxes have enough storage capacity.
• Time to move It might take a while for your public folder mailboxes to be moved to Exchange 2016. Things that could impact how long it’ll take include public folder mailbox size, the number of public folder mailboxes, available network capacity, and other factors.

Perform the following steps to move your public folder mailboxes from Exchange 2013 to Exchange 2016.

1. Open the Exchange Management Shell on your Exchange 2016 Mailbox server.
2. Run the following command to get a list of Exchange 2016 mailbox databases you can move your public folder mailboxes to. You can use this information to check how much drive space is available for each Exchange 2016 mailbox database.

Get-ExchangeServer | Where {($_.AdminDisplayVersion -Like “Version 15.1*”) -And ($_.ServerRole -Like “*Mailbox*”)} | Get-MailboxDatabase | Format-Table Name, EdbFilePath, Server

1. Run the following command to get a list of Exchange 2013 public folder mailboxes. The list this command creates includes the public folder mailbox name, its size, and what Exchange 2013 server it’s on.

Get-ExchangeServer | Where {($_.AdminDisplayVersion -Like “Version 15.0*”) -And ($_.ServerRole -Like “*Mailbox*”)} | Get-Mailbox -PublicFolder | Get-MailboxStatistics | Format-Table DisplayName, TotalItemSize, ServerName

1. You can use the information from the previous command to decide which Exchange 2016 server to move some or all of your public folder mailboxes to. For example, you might not want to move three large public folder mailboxes to a server with low available drive space. Replace the Exchange server, database, and public folder mailbox names with your own.
2. Move all Exchange 2013 public folder mailboxes at once.

Get-ExchangeServer | Where {($_.AdminDisplayVersion -Like “Version 15.0*”) -And ($_.ServerRole -Like “*Mailbox*”)} | Get-Mailbox -PublicFolder | New-MoveRequest -TargetDatabase EXCH2016MbxDatabase

1. Move all public folder mailboxes on a specific Exchange 2013 server at once.

Get-Mailbox -PublicFolder -Server EXCH2013Mbx | New-MoveRequest -TargetDatabase EXCH2016MbxDatabase

1. Move a specific Exchange 2013 public folder mailbox.

New-MoveRequest “Sales Public Folder Mailbox” -TargetDatabase EXCH2016MbxDatabase

1. Use the following command to see the status of the move requests you created. Depending on the size of the public folder mailboxes you’re moving and your available network capacity, it could take several hours or days for the moves to complete.

Get-MoveRequest

Do the following to check the status of your move requests:

1. Open the Exchange Management Shell on your Exchange 2016 Mailbox server.
2. Run the following command to see the status of the move requests you created.

Get-MoveRequest

The command above will return each move request you created along with one of the following statuses:

• Completed The public folder mailbox was successfully moved to the target Exchange 2016 mailbox database.
• CompletedWithWarning The public folder mailbox was moved to the target Exchange 2016 mailbox database, but one or more issues were encountered during the move.
• CompletionInProgress The public folder mailbox’s move to the target Exchange 2016 mailbox database is in its final stages. Public folders hosted in this mailbox may be unavailable for a brief period of time while the move is finalized.
• InProgress The public folder mailbox’s move to the target Exchange 2016 mailbox database is underway. Public folders hosted in this mailbox are available during this portion of the move.
• Failed The public folder mailbox’s move failed for one or more reasons. You can find more information by viewing the move report that was delivered to the Administrator mailbox.
• Queued The public folder mailbox’s move has been submitted but the move hasn’t started yet.
• AutoSuspended The public folder mailbox’s move is ready to enter its final stages but won’t proceed further until you manually resume the move. To resume the move when you’re ready, use the Resume-MoveRequest
• Suspended The public folder mailbox’s move has been suspended by Suspend-MoveRequest cmdlet and won’t proceed further until you manually resume the move. To resume the move when you’re ready, use the Resume-MoveRequest

Do the following to view the location of your public folder mailboxes after their move request has completed:

1. Open the Exchange Management Shell on your Exchange 2016 Mailbox server.
2. Run the following command to see the location of your public folder mailboxes.

Get-Mailbox -PublicFolder | Get-MailboxStatistics | Format-Table DisplayName, TotalItemSize, ServerName

In the list public folder mailboxes that are returned, verify that they’ve each been moved to an Exchange 2016 mailbox server.

Post Cutover Tasks

Remove Legacy Exchange Servers Removing Exchange 2010 after Coexistence with Exchange 2010/2013

If you’re removing Exchange 2010 after being in coexistence mode with Microsoft Exchange Server 2013, make sure you have completed the following checklist before you uninstall Exchange 2010 from your organization:

• All Client Access server FQDNs are pointing to Exchange 2013.
• All mail flow connectors are pointing to Exchange 2013.
• All user and arbitration mailboxes have been moved to Exchange 2013.
• If you were using public folders, make sure the public folders databases have been migrated to Exchange 2013.
• Any Exchange 2010 CAS arrays you have configured must be removed.
• Make a list of applications that may be using Exchange 2010 and then make sure to configure these applications to start using Exchange 2013 if necessary.

Mount Exchange 2010/2013 ISO. You can either run Exchange 2010/2013 Setup.exe or navigate to Control Panel to modify or remove Exchange 2010/2013 (either server roles or an entire installation).

1. The Maintenance Mode page of the Exchange Server 2010/2013 Setup wizard begins the process of changing or removing your Exchange installation. Click Next to continue.
2. On the Server Role Selection page, select the Exchange server roles that you want to add (if you’re changing an installation) or remove (if you’re removing one or more server roles or an entire installation). Click Next to continue.
3. On the Readiness Checks page, view the status to determine if the organization and server role prerequisite checks completed successfully. If the prerequisites check doesn’t complete successfully, review the Summary page to help troubleshoot and fix any issues that are preventing Setup from completing. If the checks have completed successfully, click Install if you want to add a server role or Uninstall to remove the specified server role(s) or the entire installation of Exchange 2010.
4. On the Completion page, click Finish.
5. De-join computer from domain and shutdown the computer.

Similar Articles:

Exchange 2010 to exchange 2013 migration

Exchange 2013 Upgrade, Migration and Co-existence

Account we are logged in needs following group rights:

Domain Admins – Enterprise Admins – Schema Admins

1. Installing Windows feature

1.1. For Exchange 2013 + Windows 2012

Run the commands below on a PowerShell prompt as Administrator.

Import-Module ServerManager

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

Картинка с сайта: collaborationyard.wordpress.com

1.2. Exchange 2016 + Win 2012 R2

Basically we need to install IIS, .NET Framework 4.5 and RSAT Tools. For that run Windows PowerShell as Administrator and run the following:

Import-Module ServerManager

Install-WindowsFeature 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

1.3. For Exchange 2016 + Windows 2016

For Exchange 2016 on Windows 2016 server use the command below on PowerShell.

Install-WindowsFeature 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 -Restart

2. Installing Pre-Requisites – Windows Server 2012 R2 and Windows Server 2016

2.1. You want to make sure you have the correct .NET framework. You can check which one is required for your Windows version and MS Exchange CU here. Then cross-check what you have using a .NET check utility like this one here .NET Check

Картинка с сайта: collaborationyard.wordpress.com

2.2. Now download and install Unified Communications Managed API 4.0 Runtime – UcmaRunTimeSetup.exe

3. Preparing Active Directory

You must run commands from a server in same AD domain as Schema Master. Or simply run these commands on the Schema Master AD server.

To Prepare AD Schema you need the commend below. It will add groups, permissions etc, extending AD for Exchange. Run it from the installation or Exchange CD installation. Start DOS prompt started as Administrator

Setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms

Картинка с сайта: collaborationyard.wordpress.com

Replicated extended Schema to other Active Directory Servers if necessary

Now the command below is how you how you prepare your new organization. Note you may want make sure you understand what is the point of no return first

Setup.exe /PrepareAD /OrganizationName:”MyOrg” /IAcceptExchangeServerLicenseTerms

Now to prepare the domain run the following

Setup.exe /PrepareDomain /IAcceptExchangeServerLicenseTerms

if you have more than one domain, run the following for the specific domain

Setup.exe /PrepareDomain:mydomain.com /IAcceptExchangeServerLicenseTerms

Great, now you can proceed to install MS Exchange 2013 or 2016.

Here are are a few other documents on preparing Servers for Exchange installation

Installing Exchange Server 2016 Pre-Requisites on Windows Server 2012 R2 and Windows Server 2016

Lesson 1: Preparing the Infrastructure for Exchange Installation

Our company offer IT consulting and support services. If you like this article and want to get a quote relate to our services contact us on https://www.sepetra.com/contact-us

Microsoft Exchange Server 2013 reached its end of life on April 11, 2023, meaning that Microsoft no longer provides security updates, technical support, or bug fixes for this version. If your organization is still using Exchange 2013, upgrading to a newer version like Exchange Server 2016 or 2019 should be a top priority to maintain continued security and support. Delaying the upgrade exposes your organization to significant risks, including data breaches and security threats due to unpatched vulnerabilities. It is essential to migrate to a supported version to keep your email system secure and operational.

Manual migration methods, such as using the Exchange Admin Center (EAC) or PowerShell scripts, are often complex and time-consuming. These methods require deep technical knowledge as administrators must manually export mailboxes, configure databases, and manage migration batches. Moreover, manual migrations are prone to risks such as data loss, extended downtime, and incomplete migrations, especially in large-scale or hybrid environments.

Картинка с сайта: www.edbmails.com

To make this transition smoother and more reliable, EdbMails Exchange Migration Software offers an ideal solution. It simplifies the entire migration process, allowing for seamless migration from Exchange 2013 to newer versions such as Exchange 2016, 2019, or Office 365. With EdbMails, you can be assured that the migration will be secure, fast, and free from data loss or downtime. The software ensures full-fidelity migration, preserving all mailbox data, including emails, contacts, calendars, tasks, public folders, archive mailboxes and their associated metadata and folder structures, guaranteeing a smooth, worry-free migration.

1. What’s new in Exchange server 2016?

   Exchange server 2016 introduced several new features and improvements over Exchange server 2013:

   1. Improved search and indexing: Exchange server 2016 comes with a new search and indexing engine that offers faster and more accurate searches of mailbox content. EdbMails Exchange migration ensures that all mailbox data, including emails and attachments, is transferred accurately, allowing users to take advantage of this improved search functionality immediately after migration. The software maintains the original folder structure and metadata, enhancing the user experience.
   2. Enhanced data protection: With enhanced data loss prevention (DLP) capabilities, Exchange server 2016 assists organizations in safeguarding sensitive information from unintentional sharing. EdbMails supports the secure migration of sensitive data, providing peace of mind regarding data protection.
   3. Improved email archiving: Exchange server 2016 features a new archiving system that enhances the efficiency of storing and retrieving archived email messages. EdbMails facilitates the migration of archived emails and other mailbox items, ensuring all archived content is correctly transferred to the new system, allowing users to benefit from improved archiving without losing historical data.
   4. Enhanced collaboration: Exchange server 2016 introduces collaboration tools, including support for Office 365 Groups and the ability to schedule Skype for Business meetings directly from Outlook. EdbMails focuses on migrating mailbox data, including emails, calendars, contacts, and tasks, enabling users to leverage the new features and functionalities of Exchange Server 2016 after the migration.
   5. Improved performance: Exchange Server 2016 introduces several performance improvements, ensuring faster mailbox access and more efficient resource utilization. EdbMails is designed for high-speed migration, enabling a seamless transition with zero downtime and no user disruptions. This allows organizations to take full advantage of Exchange Server 2016’s enhanced performance without affecting daily operations.
   6. Improved security: With upgraded security measures such as multi-factor authentication and enhanced data encryption, Exchange Server 2016 ensures a secure environment. EdbMails supports secure data transfer protocols during migration to maintain the integrity of the mailbox data being migrated.

      It’s important to note that some features from Exchange Server 2013 have been phased out in 2016. EdbMails helps organizations navigate these changes by providing detailed migration reports and support, ensuring users are aware of any deprecated features. Additionally, extended support for Exchange Server 2016 will end on October 14, 2025. EdbMails provides ongoing support and resources to help organizations plan for future migrations or upgrades, ensuring they stay current with the latest technology.

2. What is the best way to migrate Exchange 2013 to 2016?

   EdbMails is an effective solution for Exchange 2013 to 2016 migration, ensuring a smooth and secure transfer of mailbox data. The software simplifies the migration of mailboxes, public folders, shared mailboxes, and archive mailboxes, guaranteeing that all crucial email data—including user folders, contacts, calendars, permissions, mail headers, tasks, journals, and notes—is migrated with complete data integrity.

   EdbMails provides several advanced features to streamline the migration process. Its incremental migration feature ensures that only new or modified items are transferred during subsequent migrations, preventing data duplication. The concurrent migration functionality allows multiple mailboxes to be migrated simultaneously, speeding up the overall process. Automatic mailbox mapping simplifies setup by automatically matching source and target mailboxes, and advanced filter options provide users with the flexibility to apply specific criteria during migration.

   With these features, EdbMails ensures a secure and comprehensive migration while maintaining the integrity of your email data. It’s an ideal choice for organizations looking to upgrade Exchange 2013 to Exchange 2016.

3. Exchange 2013 and 2016 Coexistence scenario

   Exchange Server 2013 and Exchange Server 2016 can coexist within the same Active Directory (AD) environment. However, a direct upgrade from Exchange 2013 to 2016 is not currently supported. For successful coexistence, Exchange 2013 must be updated to Cumulative Update 10 or later on all Exchange 2013 servers in the organization, including Edge Transport servers.

   With the EdbMails Exchange Migration Tool, you can directly migrate from Exchange 2013 to Exchange 2016, eliminating the need for complex coexistence setups. The software ensures a smooth and secure migration, preserving all your mailbox data, folder structures, and permissions.

   Here is a general overview of the steps you can follow to migrate Exchange 2013 to 2016 in the same AD environment:

   1. Install Exchange Server 2016 in a new organization

      If you are planning to introduce Exchange Server 2016 into an existing Exchange Server 2013 organization, it is recommended to create a new Exchange organization and install Exchange Server 2016 into it. This will allow you to gradually transition to Exchange Server 2016 while keeping Exchange Server 2013 in place.

   2. Upgrade the AD schema

      Before installing Exchange Server 2016, you will need to upgrade the AD schema to include the new attributes and objects introduced in Exchange Server 2016. To do this, you will need to run the following command on a domain controller

      Command: Copy & Paste

      setup.exe /PrepareSchema

   3. Prepare the AD domains

      After upgrading the schema, prepare the AD domains in which you plan to install Exchange Server 2016. To do this, you will need to run the following command on a domain controller:

      Command: Copy & Paste

      setup.exe /PrepareAD /OrganizationName:<Contoso ABC>

   4. Install Exchange Server 2016

      After preparing the AD domains, you can proceed with the installation of Exchange Server 2016. Run the Exchange Server 2016 setup program and follow the prompts to install the software.

   5. Configure the mail flow

      After installing Exchange Server 2016, configure the mail flow between the two Exchange servers. You can do this by creating a send connector in Exchange Server 2016 that routes mail to Exchange Server 2013.

   6. Migrate from Exchange 2013 to 2016

      Set up EdbMails software for Exchange migration and directly migrate all of your mailbox data from the source to the target. Test and verify the migration and add MX records for proper mail flow.

   In the following sections, we describe in detailed steps to configure Exchange 2016, the pre migration tasks, Exchange 2013 to 2016 migration steps and post migration activities.

4. Exchange 2013 to 2016 migration checklist

   Here is a checklist of steps that you should consider when you migrate Exchange 2013 to 2016:

   1. Prepare your users for the migration: When you transfer your email data to a new system, it is important to train all your users for the change so that they are familiar with the new features and working flow. Also communicate the changes to your stakeholders.
   2. Plan the migration: Determine the scope of the migration, migration type, including which mailboxes and other Exchange objects will be migrated and the timeline for the migration.
   3. Prepare the target environment: Make sure that the Exchange 2016 server is installed and configured properly, and that all necessary prerequisites are met.
   4. Migrate the mailbox data: Migrate all your emails, mailboxes and folders from Exchange 2013 server to the Exchange 2016 server.
   5. Migrate other Exchange objects: Migrate other Exchange objects, such as room and equipment mailboxes, public folders, distribution lists, and contacts, from the Exchange 2013 server to the Exchange 2016 server.
   6. Configure Outlook: Configure Outlook on the client computers to connect to the Exchange 2016 server.
   7. Test the migration: Test the migration to ensure that everything has been migrated properly and that users can access their mailbox data on the Exchange 2016 server.
   8. Decommission the Exchange 2013 server: After the migration is complete and has been tested, decommission the Exchange 2013 server and remove it from the network.

5. Exchange 2013 to 2016 migration prerequisites

   • Step 1: Check that your system meets the Exchange 2016 setup requirements.

     Before you migrate your mailbox data to Exchange 2019, ensure that your current environment and hardware is compatible for the transfer. The following links will help you to know about the network, hardware,.NET framework and operating system requirements for installing Exchange server 2016.

     1. Network and directory requirement for Exchange 2016
     2. Hardware Requirements for Exchange 2016
     3. Supported operating systems for Exchange 2016
     4. Supported .NET Framework in Exchange 2016
     5. Supported Outlook clients in Exchange 2016

     Note: Exchange 2016 requires Active Directory forest functional level of Windows Server 2008 R2 or higher and a .NET Framework 4.8 on a Cumulative Update (CU) of 15. The Mailbox and Edge Transport servers require Windows Server 2012 Standard or Datacenter and higher. See the Exchange 2016 server supportability matrix for more information.

   • Step 2: Prepare your system with the following prerequisites for Exchange 2016

     Ensure that you meet the following prerequisites for Active Directory, Windows 2016 Mailbox server and Windows 2016 Edge Transport servers for installing Exchange 2016.

     1. Prerequisites for preparing Active Directory (AD)
     2. Windows Server prerequisites for Exchange 2016
   • Step 3: Decide on the approach for Exchange 2013 migration to 2016

     Consider if you want to migrate all your mailboxes at once or migrate it in phases. EdbMails can help you with a complete Exchange 2013 to 2016 migration without affecting your users. The advantage with it is that you can keep using your mailboxes even during the migration without disconnecting your Exchange server.

     Current environment and requirement	Ideal migration approach	Migration flow
     You want to move all mailboxes from Exchange 2013 to 2016 in a single event and within a limited time frame.	Full Exchange 2013 to 2016 Migration	Set up the Exchange 2016 server and migrate all mailboxes in a single session. Suitable for large mailbox migrations.
     You have limited time and want to migrate mailboxes from Exchange 2013 to 2016 in phases or over weekends.	Staged Exchange migration	Migrate mailboxes and data in stages, starting with the most recent data, followed by the rest.
     You want to migrate from Exchange 2013 to a Hybrid Exchange 2016 and Office 365 environment.	Migrate from Hybrid Exchange to Office 365	Migrate from the source server to a Hybrid Exchange and Office 365 environment. See the prerequisites for a Hybrid deployment.

     Note: The specific migration method depends on the number of mailboxes, size of the data and your organizational requirements.

   • Step 4: Set up the target Exchange Server 2016 for migration

     Given below is a list of key points for installing and preparing the Exchange 2016 server for migration.

     1. Prepare the AD and domains
        1. Before installing Exchange Server 2016, you need prepare your Active Directory forest and its domains for the new version of Exchange.
        2. If you have a separate team to manage the Active Directory schema, you must extend the active directory schema, else proceed to the next step to prepare the Active Directory.
        3. If you have multiple domains you need to additionally prepare the Active Directory domains.
     2. Install Exchange server 2016

        Before installing the Exchange server 2016, ensure that you meet the server system requirements and prerequisites as outlined above. Next, follow the link to install Exchange 2016 mailbox server and edge transport server using the setup wizard.

     3. Prepare a clean Exchange 2016 target environment
        1. Install and upgrade Exchange to the latest cumulative update to keep your server up to date.
        2. Create and configure a Send connector to send mail outside the Exchange organization.
        3. By default, Exchange automatically creates receive connectors for inbound mail flow when the mailbox server is installed. However, if you want to configure custom receive connectors for certain mail flow scenarios, follow the steps in the link.
        4. Add accepted domains to allow recipients to send and receive email from another domain.
        5. Configure the default email address policy to add the accepted domain to every recipient in the organization.
        6. Configure external URLs (domains) on the virtual directories in the Client Access (frontend) services on the Mailbox server to allow clients to connect to your server from the internet (outside the organization’s network).
        7. Configure internal URLs on the virtual directories in the Client Access (frontend) services on the Mailbox server to allow clients to connect to your server from the internal network.
        8. Configure SSL certificates from a third-party certificate authority for services such as Outlook Anywhere and Exchange ActiveSync.
        9. Verify the Exchange server installation by running the command Get-ExchangeServer on the Exchange Management Shell (EMS)
     4. Create mailboxes and Public folder on the target 2016 Exchange server

        Ensure to create mailboxes on the target server and assign suitable licenses to them. You can choose EdbMails to automatically create mailboxes on the target Exchange server. However, if you want to create mailboxes manually follow the link below:

         Steps to create mailboxes in Exchange 2013 server.

        If you are planning to migrate to public folders, create mail-enabled Public folders on your target server and assign the admin permissions.

         Steps to create Public folder in Exchange 2013 server and assign admin permissions.

     5. Install cumulative updates (CU) on Exchange server 2013

        For migrating Exchange server 2013 to Exchange 2016, it is required that you have installed the latest cumulative updates (CU) on the source server (2013).

     6. Create trust relationship between forests (Optional)

        A forest trust is an authentication between two domains within the same Active Directory forest which creates a trust between two root domains for exchanging information. By creating a trust in advance, it is possible to address the trust issues during the cross-forest authentication. See steps for cross forest migration from Exchange 2013 to 2016.

        Note: Creating a forest trust relationship applies to Windows Server 2008, Windows Server 2008 R2 and Windows Server 2012. It is not required for SBS based environments.

     7. Assign management roles to the admin account

        Ensure that you have set the following permissions to the admin account on the source (2013) and target server (2016)

        1. On the source
           1. ApplicationImpersonation
           2. View-Only Configuration — Run the cmdlet New-ManagementRoleAssignment using the Exchange Management Shell to assign the View-Only Configuration role to the admin.
           3. Organization Management role group. It is an elevated permission that is required to migrate Public folders.
        2. On the target
           1. ApplicationImpersonation
           2. View-Only Recipients
           3. View-Only Configuration
     8. Verify the mailbox of the admin account

        Check to see if the admin account that has been assigned management roles has a valid and non-hidden mailbox on the Exchange 2013 server. See how to configure user mailbox properties for the users from the Exchange admin center (EAC).

     9. Configure the throttling and message-size limits

        You can manually change the EWS throttling and message size limits on the target Exchange 2016 server by following the steps outlined in the links below.

        1. Custom EWS throttling policies on Exchange 2016 server.
        2. Message size limits on target Exchange 2016 server.

6. Exchange 2013 to 2016 migration using EdbMails Software

   • Step 1: Download and install the EdbMails software

     • Download and install the EdbMails application on your computer running on Windows OS.
       

       Картинка с сайта: www.edbmails.com

         System requirements for Exchange 2013 to 2016 migration.

     • Launch the EdbMails software.
     • Log in with your email address and password, or select ‘Start Your Free Trial’ if you haven’t created an account yet.
       

       Картинка с сайта: www.edbmails.com

     • Select ‘Live Exchange Migration’ option.
       

       Картинка с сайта: www.edbmails.com

     • Select ‘Live Exchange to Live Exchange Migration’ option.
       

       Картинка с сайта: www.edbmails.com

     • Keep the default job name or click ‘New Job’ to change it, then click ‘Next’.
       

       Картинка с сайта: www.edbmails.com

   • Step 2: Connect to source Exchange 2013 server

     • Click the ‘Add New Connection’ button to establish a new connection to the source Exchange server. To use a previous connection, select it from the connection list and click the ‘Connect to Existing’ button to proceed.
       

       Картинка с сайта: www.edbmails.com

        EdbMails allows you to migrate mailboxes, public folders, and archive mailboxes from the source Exchange to the target server.

     • Select the required connection options and click the ‘Next’ button.

         Different options to connect to Exchange server in EdbMails.

       

       Картинка с сайта: www.edbmails.com

     • Enter the source Exchange 2013 server details and click the ‘Login’ button.
       

       Картинка с сайта: www.edbmails.com

     • Choose the option to load mailboxes. EdbMails will automatically load your mailboxes from your source Exchange 2013 server, or you can load them manually using a CSV file.
       

       Картинка с сайта: www.edbmails.com

   • Step 3: Select Exchange server 2013 mailboxes to migrate to Exchange 2016

     • Choose the Exchange 2013 mailboxes you wish to migrate.
     • Click the ‘Next’ button.
       

       Картинка с сайта: www.edbmails.com

   • Step 4: Connect to target Exchange 2016 server

     • To connect to the target Exchange Server 2019, click the ‘Add New Connection’ button to establish a fresh connection. If you wish to use a previously saved connection, simply select it from the list and click ‘Connect to Existing’ to continue.
       

       Картинка с сайта: www.edbmails.com

     • Select the required connection options and click the ‘Next’ button.

        check Different options to connect to Exchange server in EdbMails

       

       Картинка с сайта: www.edbmails.com

     • Enter the target Exchange server 2016 details and click the ‘Login’ button to continue.
       

       Картинка с сайта: www.edbmails.com

     • Once you’ve successfully logged in, select the required option for loading the target Exchange 2016 server mailboxes.
       

       Картинка с сайта: www.edbmails.com

   • Step 5: Exchange 2013 to 2016 mailboxes mapping

     • Select the required mapping option
       

       Картинка с сайта: www.edbmails.com

       .

     • If you’ve installed EdbMails on your target Exchange 2016 server, you can opt to let EdbMails automatically create the necessary mailboxes for you—streamlining the setup and reducing manual work.

         Learn more about automatic mailbox creation.

       EdbMails also handles automatic mapping between source and target mailboxes. This is particularly useful when migrating a large number of mailboxes.

       

       Картинка с сайта: www.edbmails.com

   • Step 6: Start Exchange 2013 to Exchange 2016 migration

     • After completing the mailbox mapping, click the ‘Start Migration’ button to initiate the migration process.
       

       Картинка с сайта: www.edbmails.com

     • While the migration is running, you can monitor its real-time progress through the progress bar. When the migration finishes, a confirmation message will be displayed. To review the details of the operation, simply click the ‘View Logs’ button to access the complete migration report.
       

       Картинка с сайта: www.edbmails.com

7. Exchange 2013 to 2016 post migration tasks

   There are several post-migration tasks that you should perform after completing an Exchange 2013 to Exchange 2016 migration. These tasks can help ensure that your Exchange 2016 deployment is functioning properly and that your users are able to access their email, calendars, and other Exchange services.

   1. Verify that all mailboxes have been successfully migrated to the new Exchange 2016 server.
   2. Test the functionality of all client access protocols (e.g., Outlook Web App, Outlook Anywhere).
   3. Test the functionality of all Exchange services (e.g. Outlook calendar, contacts, tasks).
   4. Test the functionality of any third-party applications that integrate with Exchange (e.g., CRM, archiving).
   5. Update the domain name in the DNS records to point to the new Exchange 2016 server.
      • To receive messages on the Exchange server 2016, update MX records to enable email to work with the new server you have migrated to. In addition, configure the Autodiscover record to allow Outlook to connect to the migrated mailboxes.
   6. Create a new Outlook profile for users in the new domain
      • Ensure you have the latest version of Outlook installed to avoid compatibility issues. Configure the Outlook profile for each user in your domain if Outlook has problems connecting to the new Exchange server.
   7. Monitor the performance of the new Exchange 2016 server to ensure that it is functioning properly.
   8. Decommission and uninstall Exchange server 2013
      1. Remove the Exchange 2013 server from the load balancer, if you have one.
      2. Remove the Exchange 2013 server from the Exchange organization by using the Remove-ExchangeServer cmdlet.
      3. Remove the Exchange 2013 server from Active Directory. This can be done by using the Active Directory Users and Computers console or the Remove-ADObject cmdlet.
      4. If you want to completely remove Exchange 2013 from the server, you can use the Install-WindowsFeature cmdlet to remove the Exchange 2013 server roles.
      5. Once all these steps are complete, you can decommission the Exchange 2013 server and remove it from your network.
      6. Follow the instructions on the Microsoft’s website to decommission Exchange Server 2013

   It’s important to thoroughly test your Exchange 2016 deployment after the migration to ensure that everything is working as expected and that your users are able to access their email and other services. It’s also a good idea to document any issues that you encounter during the testing process so that you can troubleshoot them more effectively.

8. Exchange 2013 to 2016 migration troubleshooting guide

    Refer to the Exchange migration troubleshooting guide for effective solutions to common migration errors.

Exchange Server 2016 has given new heights to the business that were constantly using Exchange Server as a dedicated mail server. It can collaborate with the SharePoint and OneDrive easily, its cloud infrastructure is available on the mobile devices like Smartphones and tablets from both iOS and Android. There is a robust Database Availability Group where the database can overcome any failover, and there are multiple features that are proactive enough to handle all the failure or threats independently.

Exchange Server Migration Guides

Migrate Microsoft Exchange Server 2010 to Exchange 2016
Migrate From MS Exchange 2013 to Exchange Server 2016
Migrate MS Exchange Server 2016 to Exchange 2019

Pre-requisite to Migrate Exchange Server 2013 to 2016

When you have decided to migrate from Exchange Server 2013 to 2016, then before installing the Exchange Server 2016 you need to get the complete requirement of the Server in terms of Hardware, Software, Network etc. The Administrator should also know about the coexistence of current and the previous servers.

• Hardware Requirements

  Processor	Intel Processor supporting 64-bit processor/AMD Processor supporting AMD64 platform.
  Memory size	Mailbox Role: 8 GB Minimum. Edge Transport Role: 4 GB Minimum.
  Paging File Size	Minimum physical RAM plus 10 GB. Maximum Physical RAM 32 GB.
  Disk Space	30 GB of free space on the drive where you are installing the Exchange Server. 200 MB of free space on System Drive. 500 MB of free space for message queue database.
  File Format	NTFS for System partition, Exchange binaries, Exchange Diagnostic logging file, transport database files.
  Drive	DVD-ROM Drive.
  Screen Resolution	1024*768 pixels.

• Software Requirements

  Windows	Windows Server 2012. Windows Server 2012 R2. Windows Server 2016.
  Mailbox and Edge Transport Server Roles	Windows Server 2012 Standard or Datacenter Windows Server 2012 R2 Standard or Datacenter Windows Server 2016 Standard or Datacenter
  Management Tools	Windows Server 2012 Standard or Datacenter Windows Server 2012 R2 Standard or Datacenter Windows Server 2016 Standard or Datacenter Windows 10 with 64-bit Windows 8.1 with 64-bit
  .NET Framework	4.8, 4.7.2, 4.7.1, 4.6.2
  Supported Clients	Microsoft 365 Apps for enterprise, Outlook 2019, Outlook 2016, Outlook 2013, Outlook 2010 SP2, Outlook 2016 for Mac, Outlook for Mac for Office 365.

Install Exchange Server 2016

After checking the prerequisites for the Exchange Server 2016, you can go to Microsoft Download Center and Download Exchange Server 2016. Go to Windows Server on which you want to install it.

Go to the navigation file where the installation files are present. Find the Setup.exe and double-click it. It will open the first page of Exchange Server installation called Check for Updates.

1. There are two options to handle the updates. First one is to connect to the Internet and check for updates and next one is do not check for updates. Choose any one and click Next.
   

   Картинка с сайта: www.datarepairtools.com

2. Read the given Introduction related to the Exchange Server properties and click Next.
   

   Картинка с сайта: www.datarepairtools.com

3. Accept the License agreement terms and click Next.
   

   Картинка с сайта: www.datarepairtools.com

4. On the Recommended Settings page, choose whether you want to use the recommended settings and not. If you choose the recommended settings, then Exchange server will automatically check for online solutions whenever an error occurs and provide the necessary feedback to help the Exchange features. In the Manual configuration, you can enable the settings are the completion of installation.
   

   Картинка с сайта: www.datarepairtools.com

   Click Next.

5. On the Server Role Selection page, choose Mailbox Role. The Management Tools will install automatically after selecting the Mailbox Role. Also, click the checkbox for automatically install Windows Server Roles and features that are required to Install Exchange Server. Then click Next.
   

   Картинка с сайта: www.datarepairtools.com

6. The Malware Protection Settings is an important page where you can choose to enable the malware scanning. It will help recognizing such messages that can contain viruses or spyware. Click Yes, then click Next.
   

   Картинка с сайта: www.datarepairtools.com

7. Setup will check for the setup, its settings and run a through scan. After the completion, click Install.
   

   Картинка с сайта: www.datarepairtools.com

8. The setup is completed successfully and you need to restart the computer to finalize the installation. Click Finish.
   

   Картинка с сайта: www.datarepairtools.com

Now you can go in Exchange Admin Center and create the Administrator and other accounts.

Migrate mailboxes from Exchange Server 2013 to 2016

After the installation of new Exchange Server in the system, there are actually two servers present in a co-existence. So, you can migrate the mailboxes from one database to another easily. Follow the below procedure at the Exchange Admin Center

1. Go to Recipients, then Mailbox list. Choose the mailbox that you want to migrate, then click Move Mailbox. You can also go migration category and click Move to a different database, then choose the mailbox and click Next.
2. Now, provide the name to the migration batch and choose the database as the destination for the mailbox. You can also choose whether you want to migrate primary mailbox, archive mailbox, or both. Click Next.
3. Choose a user account that will receive the migration notification.
4. Choose whether you want to start the migration instantly or schedule the migration for a later time. Click New to start the move request.
5. The status of the migration request will be syncing.
6. After the completion of migration, you can choose to migrate other mailboxes similarly.

Decommission Exchange Server 2013

When you have migrated all the content from Exchange Server 2013, then you can go ahead and uninstall the server completely. Follow the below steps;

1. Remove the hybrid connection using the Remove-HybridConfiguration command at the Exchange Management Shell.
2. Remove the hybrid connectors manually in the connectors category in mail flow.
3. Remove organizational sharing in the sharing category in organization.
4. Remove the mailbox database.
5. Disable the Arbitration Mailbox.
6. Delete the default mailbox database.
7. Uninstall the Exchange Server file from the Control Panel.

For more details, Read decommission Exchange Server 2013 Step by Step Guide

Conclusion

We have presented a complete migration guide from Exchange Server 2013 to 2016 in the simple steps. You can follow the whole guide and complete a migration. But if you want to complete the migration quickly and effectively, then you can use a professional Exchange Migration software and get the job done. The professional software can access the mailboxes from the Exchange Server 2013 mailbox and migrate the directly to Exchange Server 2016 mailbox. You can apply the useful filters and get a report of the migration also.

Download Now