Office 365 Hybrid Deployment with Multiple Active Directory Forests

This article explains how you can deploy a hybrid Office 365 and Exchange on-premises environment with multiple Active Directory Forest. An organisation that utilizes an account forest and a resource forest to separate Active Directory accounts and Exchange servers in a single forest, aren’t considered as multiple AD Forest. Let’s say Company A (DomainA.com) bought Company B (DomainB.com). Company A has an Office 365 tenant with default domain domainA.onmicrosoft.com. Now Company A wishes to migrate Company B mailboxes into the Office 365 tenant but maintains the hybrid environment.

Here is the infrastructure you should consider.

AD Forest 1 AD Forest 2
On-prem Forest Corp.DomainA.com Corp.DomainB.com
Email Domain or Externally Routable NameSpace DomainA.com DomainB.com
Externally Routable Autodiscover CNAME Autodiscover.DomainA.com Autodiscover.DomainB.com
Default Domain in Office 365 Tenant domainA.onmicrosoft.com domainA.onmicrosoft.com
On-Prem Exchange Server Version Exchange 2013 SP1 or later Exchange 2013 SP1 or later
On-prem Certificate Issued by Public CA

CN= mail.DomainA.com

SAN=Autodiscover.DomainA.com

Issued by Public CA

CN= mail.DomainB.com

SAN=Autodiscover.DomainB.com

To configure a hybrid environment for a multi-forest organization, you’ll need to complete the basic steps below:

  1. Create Two-Way Trust Relationship between on-premises Corp.DomainA.com and On-premises Corp.DomainB.com if Trust relationship is not already established.
  2. Make sure you have correct public certificates for both Exchange Organisation.
  3. Build AAD Connect Server in Corp.DomainA.com Domain. AD Synchronisation occurs Corp.DomainA.com domain. you do not need to add another AAD Connect server in domainB.com domain. Run custom AAD Connect wizard and use domain filter and select both domains to sync to Azure AD.
  4. Build ADFS Farm in Corp.DomainA.com Domain. You use either AD FS or password sync to allow for a seamless user authentication experience for both domains.
  5. Add domain and verify both domains in Office 365 tenant. Setup both domain in Office tenant as an Internal Relay Domain
  6. Run Hybrid Configuration wizard in both Forest. Select both domains whilst running HCW.  For Centralized MailFlow Configuration of both domains, you must retain your existing MX record. Add EOP in your SPF record for the both domains. If you do not wish to configure Centralized MailFlow then point MX record to the EOP record of Exchange Online.

AAD Connect Recommendations:

  • Separate Topology – This topology might be the situation after a merger/acquisition or in an organization where each business unit operates independently. These forests are in the same organization in Azure AD and appear with a unified GAL.

In AAD Connect Wizard Select “Users are only once across all forests” and Mail Attribute.

  • Full Mesh- A full mesh topology allows users and resources to be located in any forest. Commonly, there are two-way trusts between the forests.

In AAD Connect Wizard Select “Users identities exist across multiple forests” and Mail Attribute.

Hybrid with Multiple Forest  Recomendations:

  • Having a single tenant in Azure AD for an organization
  • Having a single ADD connect server for an organisation
  • Having a unique Active Directory object for an organisation. Each unique object is synced into the Azure AD for once only.
  • Having a single on-prem namespace (UPN: domainA.com, domainB.com) to match the registered domain in Azure AD.
  • Having a single namespace associated with an user or an object
  • Having all email domains registered in a single tenant
  • Having a single AAD Connect and ADFS Farm in a same forest if “Federation with ADFS” is selected in AAD Connect custom installation Wizard

Relevant Article:

Office 365 Hybrid Deployment with Exchange 2016 Step by Step

Exchange 2010/2013 to Exchange 2016 Migration Step by Step

  • 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:

Task Permissions required
Install the Mailbox server role

(first server installed)

Local Administrator

Enterprise Administrator

Schema Administrator

Install additional Mailbox servers Organization Management
Install the Edge Transport server role Local Administrator

Exchange Server 2016 Deployment Datasheet

Description Example value in checklist
Active Directory forest domain.com
Internal Exchange 2016 Mailbox EXCH2016
Internal Exchange 2016 Edge Transport EXCH2016EDGE
Internal Exchange 2013 Mailbox and CAS EXCH2013
Internal Exchange 2013 Edge Transport EXCH2013EDGE
Internal Exchange 2010 Mailbox and CAS EXCH2010
Internal Exchange 2010 Edge Transport EXCH2010EDGE
External and Internal Exchange 2016 FQDN for the following services:

  • Outlook Anywhere
  • Offline Address Book
  • Remote Windows PowerShell
  • Exchange Web Services (EWS)
  • Exchange ActiveSync
  • Outlook on the web
  • ECP (Exchange admin center)
mail.domain.com
Internal and External Autodiscover FQDN autodiscover.domain.com
Primary SMTP namespace domain.com
User principal name domain @domain.com

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:

Virtual directory External URL value
Autodiscover No external URL displayed
ECP https://mail.domain.com/ecp
EWS https://mail.domain.com/EWS/Exchange.asmx
Mapi https://mail.domain.com/mapi
Microsoft-Server-ActiveSync https://mail.domain.com/Microsoft-Server-ActiveSync
OAB https://mail.domain.com/OAB
OWA https://mail.domain.com/owa
PowerShell http://mail.domain.com/PowerShell

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:
Virtual directory Internal URL value
Autodiscover No internal URL displayed
ECP https://mail.domain.com/ecp
EWS https://mail.domain.com/EWS/Exchange.asmx
Mapi https://mail.domain.com/mapi
Microsoft-Server-ActiveSync https://mail.domain.com/Microsoft-Server-ActiveSync
OAB https://mail.domain.com/OAB
OWA https://mail.domain.com/owa
PowerShell http://mail.domain.com/PowerShell

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.

External DNS Record
FQDN Record type Value TTL
domain.com MX mail.domain.com 10 minutes
mail.domain.com A Public IP Address i.e. 203.17.x.x 10 minutes
autodiscover.domain.com A Public IP Address i.e. 203.17.x.x 10 minutes

Internal DNS Record
FQDN Record type Value TTL
mail.domain.com CNAME EXCH2016.domain.com 10 Minutes
autodiscover.domain.com A Internal IP Address i.e. 10.142.x.x 10 Minutes

 

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

Configuring Retention Policies in Office 365

Retention policies are used to manage email lifecycle. Retention policies are applied by creating retention tags, adding them to a retention policy, and applying the policies to mailboxes.

To Create various retention policies in Office 365 using simple PowerShell. Connect Office 365 PowerShell module and run the below cmdlets. Tweak the cmdlets as desired.

7 Years (2,556 days) Retention Policy
New-RetentionPolicyTag -Name “7 Years Retention” -Type All -AgeLimitForRetention 2556 -RetentionAction DeleteAndAllowRecovery

2 Years (730 days) Retention Policy

New-RetentionPolicyTag -Name “2 years retention” -Type All -AgeLimitForRetention 730 -RetentionAction MoveToArchive

Delete voice mail messages after 30 days.

New-RetentionPolicyTag -Name “Delete Voicemail After 30 Days” -Type All -MessageClass Voicemail -AgeLimitForRetention 30 -RetentionAction DeleteAndAllowRecovery

Permanently delete messages in the Junk EMail folder after 30 days.

New-RetentionPolicyTag -Name “Delete Junk Email After 30 Days” -Type JunkEmail -AgeLimitForRetention 30 -RetentionAction PermanentlyDelete

Apply Retention Policy to a single mailbox
Set-Mailbox “John Doe” -RetentionPolicy “RP-Finance”

Apply Retention Policy to All Mailboxes
Get-Mailbox -ResultSize unlimited | Set-Mailbox -RetentionPolicy “Delete Junk Email After 30 Days”

Placing a mailbox on retention hold suspends the processing of a retention policy or managed folder mailbox policy for that mailbox. Retention hold is designed for situations such as a user being on vacation or away temporarily.

Enable Retention Hold on a Single Mailbox
Set-Mailbox “John Doe” -RetentionHoldEnabled $true

To extract retention holds for all mailboxes, issue the following cmdlets.
Get-Mailbox -ResultSize unlimited | Where-Object {$_.RetentionHoldEnabled -eq $true} | Format-Table Name,RetentionPolicy,RetentionHoldEnabled -Auto

Office 365: Configuring catch-all mailbox during migration

Step1: Create Catch-All Mailbox

1. Sign in to portal.office.com>Active Users

2. Create a new user named “Catch-All-Mailbox” and assign licenses either E1 or E3.

Step2: Create exception Security Group (Optional Step)

1. Log onto Office 365 admin portal

2. Go to Admin>Exchange>Recipients>Groups

3. Create a new Security Group named Catch-All-Exception

4. Add members to this group

Step3: Create a Transport Rule

5. Log onto Office 365 admin portal

6. Go to Admin>Exchange>Click “Mail Flow” icon, Click “Rules”

7. Click the “+” icon, then “Create a new rule”

8. As soon as the new rule box appears, click “More Options…” link towards the bottom of the page

9. Give rule a name, CatchAll-Mailbox Migration

10. Change the “apply this rule if…” to “The Sender is…”–>”Internal/External”–>”Outside this Organisation”

11. Change the “do the following…” to “Redirect the message to…”–>”These recipients”–> then select “Catch-All-Mailbox”

12. *OPTIONAL*  Click “Add Action” and then “Modify the message properties”–>”Set a message header”, then set the header to “X-Catchall-Migration-Rule” and value to “Yes”

13. Under “Except if”, Click “Add action” and then “If Recipient…”–>”Is this person”–>and select the “all” Group which contains all exclusions (this should be the “All” group which contains all users/groups INCLUDING the Catchall mailbox/group that you don’t want diverted)

14. Save

15. Once Migration is complete, delete the rule.

 

Branding and Customizing the ADFS Sign-in Pages

Branding and promoting Company name and logos are common business practices. You would like to see your own brand whilst signing into to Microsoft Office 365. ADFS provides opportunity for businesses to customize sign in page and promote own brand. Here are the simple steps and procedure to brand ADFS sign in page.

Remote into ADFS Server and implement below steps to customize ADFS Portal.

Change company name

Import-Module ADFS

Set-AdfsGlobalWebContent –CompanyName “Domain Corp”

Change company logo

Create a logo with 260×35 pixels @ 96 dpi with a file size of no greater than 10 KB and save the file into a path e.g. C:\Domain\logo.png. Then execute the PowerShell.

Set-AdfsWebTheme -TargetName default -Logo @{path=”c:\Domain\logo.png”}

Change Illustration

Create an illustration photo to be displayed on the left hand side of the sign in page. Photoshop illustration.png file to be 1420×1080 pixels @ 96 DPI with a file size of no greater than 200 KB.

Set-AdfsWebTheme -TargetName default -Illustration @{path=”c:\Domain\illustration.png”}

Add sign-in page description

Set-AdfsGlobalWebContent -SignInPageDescriptionText “<p>Sign-in to Domain Corp requires you comply with corporate information uses policy. Click <A href=’http://www.Domain.com/policies/’>here</A&gt; for more information.</p>”

Add Help Desk Link

Set-AdfsGlobalWebContent -HelpDeskLink https://www.Domain.com/help/ -HelpDeskLinkText Help

Add Home Link

Set-AdfsGlobalWebContent -HomeLink https://www.Domain.com/home/ -HomeLinkText Home

Add Privacy Link

Set-AdfsGlobalWebContent -PrivacyLink https://www.Domain.com/privacy/ -PrivacyLinkText Privacy

Customize the Update Password page description

Set-AdfsGlobalWebContent -UpdatePasswordPageDescriptionText “This is the Domain Corp Update Password page.”

Customise error page

Set-AdfsGlobalWebContent -ErrorPageGenericErrorMessage “This is a generic error message.  Contact Domain Corp IT Support on 123466 for assistance.”

Build Custom theme

Export current theme using below Cmdlets.

Export-AdfsWebTheme -Name default -DirectoryPath c:\Domain\Theme\Custom

Replace existing theme with Custom Theme.

New-AdfsWebTheme -Name Custom -SourceName default

Open the script file you downloaded from “C:\Domain\Theme\Custom\script\onload.js” in Notepad

Add this line at the bottom of the script to change the placeholder text in the username input box

document.forms[‘loginForm’].UserName.placeholder = ‘username@domain.com’;

Add these blue lines at the bottom of the script to add a text above the login form, this is an example from Microsoft that you can find further down

// Sample code to update the username format test “someone@example.com”.

var userNameInput = document.getElementById(Login.userNameInput);
if (userNameInput) {
// userNameInput element is present, modify its properties.
userNameInput.setAttribute(‘placeholder’, ‘Corp UserName OR EmailAddress’);
}

// Sample code to change “Sign in with organizational account” string.

// Check whether the loginMessage element is present on this page.
var loginMessage = document.getElementById(‘loginMessage’);
if (loginMessage)
{
// loginMessage element is present, modify its properties.
loginMessage.innerHTML = ‘Sign in with your company email address OR Corp UserName and password’;
}

var AppendUPN = function () {
var userName = document.getElementById(Login.userNameInput);

if ((/^\d+$/.test(userName.value)) && userName.value.length == 6)
{
userName.value = ‘Corp\\’ + userName.value;
}
return true;
}

document.getElementById(‘submitButton’).onclick = new Function(“AppendUPN();return Login.submitLoginRequest();”);
document.getElementById(‘loginForm’).onkeypress = function(event){ if(event && event.keyCode == 13) {AppendUPN();Login.submitLoginRequest()}};

When you are done and save changes. Upload the changes to the newly created theme

Set-AdfsWebTheme -TargetName Custom -AdditionalFileResource @{Uri=’/adfs/portal/script/onload.js’; path=”c:\Domain\Theme\Custom\script\onload.js”}

Now apply the changes with this command

Set-AdfsWebConfig -ActiveThemeName Custom

Use these commands to verify your settings

Get-AdfsWebConfig

Get-AdfsGlobalWebContent

Data Loss Prevention (DLP) in Exchange 2013

Data Loss Prevention (DLP) is a mechanism introduced in Exchange 2013 to prevent accidental or malicious disclosure of information via email message. Built-in DLP solution in Exchange 2013 scan message header, message body and attachment based on DLP rule by the transport agent. There are certain conditions applied in Exchange 2013 DLP.

Notify Only Policy

The following conditions can be used:

  • The recipient is
  • The recipient is located
  • The sender is
  • The sender is a member of
  • The sender is located

The following actions can’t be used:

  • Reject the message and include an explanation
  • Reject the message with the enhanced status code of
  • Delete the message without notifying anyone

Block Message Policy

  • Block the message, but allow the sender to override and send
  • Block the message.

To add a notify only DLP policy:

  1. Go to Exchange Administration Center, Go to Compliance management > Data loss prevention
  2. Then go to Policies, Select Edit
  3. On the Edit DLP policy page, select Rules.
  • To add Policy Tips to an existing rule, highlight the rule and select Edit.
  • To add a new blank rule that you can fully customize, select Add or plus sign and then select Create a new rule .
  1. Select plus sign, select the sensitive information types, select Add, select OK, and then select OK.
  2. In the Do the following box, select Notify the sender with a Policy Tip, and select an option in the Choose whether the message is blocked or can be sent drop-down list, and then select OK.
  3. If you want to add additional conditions or actions, at the bottom of the window, select More options.
  4. In the Choose a mode for this rule list, select whether you want the rule to be enforced. We recommend testing the rule first.
  5. Select Save to finish.

To add a block message DLP policy:

  1. In the Exchange Administration Center, go to Compliance management > Data loss prevention.
  2. Select desired policy> Click Edit .
  3. On the Edit DLP policy page, select Rules.
  • To add Policy Tips to an existing rule, highlight the rule and select Edit .
  • To add a new blank rule that you can fully customize, select Add .
  • To add an action that will reveal a Policy Tip, select More options and then select the Add action
  1. From the drop down list, select Notify the sender with a Policy Tip and then select Block the message.
  2. Select OK, then select Save to finish modifying the rule and save your changes.

Supported Systems for Exchange 2013

Supported Domain Controller

  • Windows Server 2012 R2 Standard or Datacenter 1
  • Windows Server 2012 Standard or Datacenter
  • Windows Server 2008 R2 Standard or Enterprise SP1 or later
  • Windows Server 2008 R2 Datacenter RTM or later
  • Windows Server 2008 Standard or Enterprise SP1 or later (32-bit or 64-bit)
  • Windows Server 2008 Datacenter RTM or later
  • Windows Server 2003 Standard Edition with Service Pack 2 (SP2) or later (32-bit or 64-bit)
  • Windows Server 2003 Enterprise Edition with SP2 or later (32-bit or 64-bit)

Supported Forest

Windows Server 2003 forest functionality mode or higher 2

  1. Windows Server 2012 R2 is supported only with Exchange 2013 SP1 or later.
  2. Windows Server 2012 R2 forest functionality mode is supported only with Exchange 2013 SP1 or later.

DNS Name Space

  • Contiguous
  • Noncontiguous
  • Single label domains
  • Disjoint

Mailbox, Client Access, and Management Tools

  • Windows Server 2012 R2 Standard or Datacenter
  • Windows Server 2012 Standard or Datacenter
  • Windows Server 2008 R2 Standard with Service Pack 1 (SP1)
  • Windows Server 2008 R2 Enterprise with Service Pack 1 (SP1)
  • Windows Server 2008 R2 Datacenter RTM or later

Supported Client

  • Outlook 2013
  • Outlook 2010
  • Outlook 2007
  • Entourage 2008 for Mac, Web Services Edition
  • Outlook for Mac 2011

Supported Coexistence

  • Exchange 2007 SP3 Update Rollup 10
  • Exchange 2010 SP3 Update Rollup 6

Supported Hybrid Deployment

  • Latest version of Office 365

Relevant Articles

Exchange 2013 Upgrade Guide

Exchange 2013 Deployment

Unified Messaging in Exchange 2013

Publish Exchange 2013