Migrating A Small Organization From Exchange 2010 To Exchange 2016 (Part 3) - TechGenix PDF

2/5/2018 Migrating a small organization from Exchange 2010 to Exchange 2016 (Part 3) - TechGenix
SECTIONS  TECH NEWS  TUTORIALS REVIEWS NEWSLETTERS VIDEOS ABOUT  

Migrating a small organization from Exchange 2010 to Exchange 2016 (Part 3)
 3 COMMENTS  SHARE
Migrating a small organization FEATURED PRODUCT
from Exchange 2010 to

Exchange 2016 (Part 3)
Steve Goodman 1  9 Views  3
POSTED ON JANUARY 26, 2016

YOU ARE READING
 SHARE ON FACEBOOK  TWEET IT   

Get expert tech
reports and guides
for FREE!
Join 900,000 fellow IT Pros...
and be among the rst to learn

about new security threats, system
optimization tricks, and the hottest
technologies in the industry.
Email address
CO U N T M E I N !
LATEST PODCAST
If you would like to read the other parts in this article series please go to: TechGenix Xtreme
Blockchain expl… Share
Migrating a small organization from Exchange 2010 to Exchange 2016

(Part 1)
Cookie policy
(Part 2)
(Part 4)
FEATURED FREEWARE
(Part 5)
http://techgenix.com/migrating-small-organization-exchange-2010-exchange-2016-part3/ 1/14
Migrating a small
SECTIONS
organization TUTORIALS
TECH NEWS 
from ExchangeREVIEWS
2010 to Exchange 2016
NEWSLETTERS VIDEOS ABOUT  
(Part 6)
Post-Installation Con guration

Changes Get a free copy of
the new
SolarWinds
Checking Exchange After Permissions

Analyzer!
Installation
After installation completes we will ensure that the new Exchange Server is
available. RECOMMENDED
Choose Start and launch the Exchange Administrative Center from the menu,
Load
or navigate using Internet Explorer to https://servername/ecp/? balancing
Exchange
ClientVersion=15: Server 2016
(Part 2)
Exchange 2016
upgrade tips
and tricks
from the eld
(Part 2)
Load
balancing
Exchange
Figure 1: Launching the EAC Server 2016
(Part 1)
When launching via a localhost URL and because we haven’t installed the
real SSL certificate we will see a certificate warning, as shown below. Click
Continue to this website to access the EAC login form:
FOLLOW US
 
Figure 2: First login to the EAC
You should see the Exchange Admin Center login form. Login using an
organization admin credentials:

Figure 3: Login as an Admin to the EAC
After you successfully login, take a moment to navigate around each section
of the EAC to familiarise yourself with the new interface.
Figure 4: Exploring the Exchange 2016 EAC
You’ll notice that the EAC is very different in layout to Exchange Server
2010’s Exchange Management Console. In Exchange 2010 and 2007, the
focus was based on the organization, servers and recipients with distinct
sections for each. Exchange 2013 and 2016 move to a more task-oriented
view. For example, Send and Receive connectors are both managed from the
Mail Flow section rather than hidden within respective Organization and
Server sections.
However even with those changes, very similar commands are used within
the Exchange Management Shell and you will be able to re-purpose any
Exchange 2010 PowerShell skills learnt.
Like what you're reading? Get the latest updates and tech guides in
your inbox.
Enter your email address...
G E T E X C L U S I V E U P D AT E S
SECTIONS TECH NEWS  TUTORIALS REVIEWS NEWSLETTERS VIDEOS ABOUT 

Updating
Migrating athe
small Service
organization Connection
 
from Exchange 2010 to Exchange 2016 (Part 3)
Point for Autodiscover

After successfully installing Exchange Server 2016, a change worth making

is to update the Service Connection Point (SCP).
The SCP is registered in Active Directory and used, alongside the Exchange
2010 SCP, as a location Domain-Joined clients can utilize to find their
mailbox on the Exchange Server.
By default, the SCP will be in the form https://ServerFQDN

/Autodiscover/Autodiscover.xml; for example
https://EX1601.goodmanindustries.com/Autodiscover/Autodiscover.xml.
The name above however won't be suitable for two reasons - firstly, no
trusted SSL certificate is currently installed on the new Exchange 2016
server, and the SSL certificate we'll replace it with in the next section won't
have the actual full name of the server.
This can cause certificate errors on domain-joined clients, most commonly

with Outlook showing the end user a certificate warning shortly after you
install a new Exchange Server.
Therefore, we will update the Service Connection Point to use the same name
as the Exchange 2010 uses for its Service Connection Point. This is also the
same name we’ll move across to Exchange 2016 later on.
To accomplish this, launch the Exchange Management Shell from the Start
Menu on the Exchange 2016 server:
Figure 5: Launch the EMS
To update the Service Connection Point, we'll use the Set-

ClientAccessService cmdlet from the Exchange Server 2016 Management
Shell, using the AutodiscoverServiceInternalURI parameter to update the
actual SCP within Active Directory:
Set-ClientAccessService -Identity EX1601 -AutodiscoverServiceInternalURI

Migrating a small organization from Exchange 2010 to
https://autodiscover.goodmanindustries.com/Autodiscover/Autodiscover.xm Exchange 2016 (Part 3)
Figure 6: Updating the SCP
After making this change, any clients attempting to use the Exchange 2016
Service Connection Point before we implement co-existence will be directed
to use Exchange 2010.
Exporting the certi cate as PFX

format from Exchange 2010
Because we will migrate the HTTPS name from Exchange 2010 to Exchange
2016 we can re-use the same SSL certificate by exporting it from the existing
Exchange server.
To perform this step, log in to the Exchange 2010 server and launch the
Exchange Admin Console. Navigate to Server Configuration in the Exchange
Management Console, select the valid SSL certificate with the correct name,
then select Export Exchange Certificate from the Actions pane on the right
hand side.
Figure 7: Exporting the Exchange 2010 SSL cert
The Export Exchange Certificate wizard should open. Select a location to

save the Personal Information Exchange (PFX) file and an appropriate strong
password, then choose Export:

Figure 8: Specifying an export directory and password
Make a note of this location, as we’ll use it in the next step.
Importing the Certi cate PFX File

Back over on the Exchange 2016 server, open the Exchange Admin Center
and navigate to Servers>Certificates. Within the more (…) menu choose
Import Exchange Certificate:
Figure 9: Importing the SSL certificate to Exchange 2016
In the Import Exchange Certificate wizard we’ll now need to enter a full
UNC path to the location of the exported PFX file, along with the correct
password used when exporting the certificate from Exchange 2010:

Figure 10: Specifying the path to the Exchange 2010 server
After entering the location and password, we’ll then choose Add (+) to select
our Exchange 2016 server, EX1601, as the server to apply this certificate to.
We’ll then choose Finish to import the certificate:
Figure 11: Selecting appropriate servers to import the certificate to
Assigning the SSL certi cate to

services
Although we now have the SAN SSL certificate installed on the Exchange
2016 server it is not automatically used by services such as IIS, SMTP,
POP/IMAP or Unified Messaging. We’ll need to specify which services we
want to allow it to be used with.
To perform this step, within Certificates select the certificate and then choose
Edit:

Figure 12: Assigning SSL certificates for use
Next, choose the Services tab in the Exchange Certificate window and select
the same services chosen for Exchange 2010. In this example, we’re only
enabling the SSL certificate for IIS (Internet Information Services):
Figure 13: Selecting services to assign the SSL cert to
After the certificate is assigned, ensure it is applied to IIS by running the

following command:
iisreset /noforce
Con guring Exchange URLs using

the Exchange Management Shell
The Exchange Management Shell also provides the functionality to change
the Exchange URLs for each virtual directory, however unless you know the
syntax it can be a little intimidating - and even if you do know the relevant
syntax, typing each URL can be a little time consuming too.
We can use a PowerShell script to make this process simpler.
The first two lines of the script are used to specify the name of the Exchange
2016 server, in the $Server variable, and the HTTPS name used across all
services in the $HTTPS_FQDN variable.
The subsequent lines use this information to correctly set the Internal and
External URLs for each virtual directory:
$Server = "ServerName"
$HTTPS_FQDN = "mail.domain.com"
Get-OWAVirtualDirectory -Server $Server | Set-

OWAVirtualDirectory -InternalURL
"https://$($HTTPS_FQDN)/owa" -ExternalURL
"https://$($HTTPS_FQDN)/owa"
Get-ECPVirtualDirectory -Server $Server | Set-ECPVirtualDirectory

-InternalURL "https://$($HTTPS_FQDN)/ecp" -ExternalURL
"https://$($HTTPS_FQDN)/ecp"
Get-OABVirtualDirectory -Server $Server | Set-

OABVirtualDirectory -InternalURL
"https://$($HTTPS_FQDN)/oab" -ExternalURL
"https://$($HTTPS_FQDN)/oab"
Get-ActiveSyncVirtualDirectory -Server $Server | Set-

ActiveSyncVirtualDirectory -InternalURL
"https://$($HTTPS_FQDN)/Microsoft-Server-ActiveSync" -
ExternalURL "https://$($HTTPS_FQDN)/Microsoft-Server-
ActiveSync"
Get-WebServicesVirtualDirectory -Server $Server | Set-

WebServicesVirtualDirectory -InternalURL
"https://$($HTTPS_FQDN)/EWS/Exchange.asmx" -ExternalURL
"https://$($HTTPS_FQDN)/EWS/Exchange.asmx"
Get-MapiVirtualDirectory -Server $Server | Set-

MapiVirtualDirectory -InternalURL
"https://$($HTTPS_FQDN)/mapi" -ExternalURL
https://$($HTTPS_FQDN)/mapi
In the example below, we've specified both our server name EX1601 and
HTTPS name mail.goodmanindustries.com and then updated each Virtual
Directory accordingly:

Figure 14: Updating URL values
Con guring Outlook Anywhere

After updating the Virtual Directories for Exchange, we'll also update the
HTTPS name and authentication method specified for Outlook Anywhere.
As Outlook Anywhere is the protocol Outlook clients will use by default to

communicate with Exchange Server 2016, replacing MAPI/RPC within the
LAN, it's important that these settings are correct - even if you are not
publishing Outlook Anywhere externally.
During co-existence it's also important to ensure that the default

Authentication Method, Negotiate, is updated to NTLM to ensure client
compatibility when Exchange 2016 proxies Outlook Anywhere connections
to the Exchange 2010 server.
To update these values, navigate to Servers and then choose Edit against the
Exchange 2016 server:
Figure 15: Locating Outlook Anywhere settings
InSECTIONS
the Exchange
 Server properties
TECH NEWS  window choose
TUTORIALS the OutlookNEWSLETTERS
REVIEWS Anywhere tab. VIDEOS ABOUT  
Update the External Host Name, Internal Host Name and Authentication
Method as shown below:
Figure 16: Updating Outlook Anywhere configuration
Naturally you can also accomplish this with PowerShell, however it's just as
quick to use the Exchange Admin Center for a single server.
With these settings configured, along with iisreset /noforce to ensure

configured is re-loaded into IIS we could in theory move client access across
from Exchange 2010 to Exchange 2016. Before we do that we will first make
some additional configuration changes.
Summary
In part three of this series, we’ve performed the first basic configuration
required for our Exchange 2016 server post-installation. In part four we will
complete the post-installation configuration and begin preparation for
migration.
If you would like to read the other parts in this article series please go to:

(Part 1)
(Part 2)
Migrating a small
SECTIONS
organization TUTORIALS
TECH NEWS 
from ExchangeREVIEWS
2010 to Exchange 2016
NEWSLETTERS VIDEOS ABOUT  
(Part 4)
Migrating a small organization from Exchange 2010 to Exchange 2016  3 COMMENTS  SHARE
(Part 5)
(Part 6)
Featured Links
READ NEXT
Migrating a small Migrating a small Migrating a small

organization from organization from organization from
Exchange 2010 to Exchange 2010 to Exchange 2010 to
Exchange 2016 Exchange 2016 Exchange 2016
(Part 5) (Part 4) (Part 1)
Migrating a small Migrating a small How to migrate

organization from organization from from Microsoft
Exchange 2010 to Exchange 2010 to Exchange 2010 to
Exchange 2016 Exchange 2016 Exchange 2016
(Part 2) (Part 6)
TECHGENIX » MS EXCHANGE SERVER » DEPLOYMENT & MIGRATION » MIGRATING A SMALL

ORGANIZATION FROM EXCHANGE 2010 TO EXCHANGE 2016 (PART 3)
AUTHOR
Steve Goodman
Steve is a 5 times recipient of the MVP (Microsoft’s Most

Valuable Professional) award from Microsoft, is a
regular international conference speaker, podcast host,
regular blogger, plus he is the author of a number of
popular Exchange books. Steve is Head of Messaging
and UC at top Of ce 365 partner Content and Code,
responsible for their Exchange and Skype for Business
offerings. Steve has worked on a vast number of
Exchange and Of ce 365 projects across customers
large and small, often with complex requirements and

Migrating a small
loves organization
to share his expertise. from Exchange 2010 to Exchange 2016 (Part 3)
3 COMMENTS
Selai April 19, 2017 at 11:48 am R E P L Y
I am using oulook 2016 while trying to configure mailbox

during the migration on new exchange 2016 with windows
logon credential, outlook searching for mailbox and asking
me for credential?
May i know what authentication need to be checked?
Thank You
Justin June 1, 2017 at 9:34 am R E P L Y
In this example, we’re only enabling the SSL certificate for

IIS (Internet Information Services):
Any reason to not enable the other services at this time?

Should they be done at a different stage?
Tom November 7, 2017 at 6:01 am R E P L Y
I’m anxious to know the answers to two questions above.
Your email address will not be published. Required fields are marked
*
Name* Email* Website
POST COMMENT
SECTIONS
N O T I FY M E TECH NEWS
OF FO U P C OTUTORIALS
L L O W - M M E N T S B Y E MREVIEWS
AIL. NEWSLETTERS VIDEOS ABOUT  
NOTIFY ME OF NEW POSTS BY EMAIL.  3 COMMENTS  SHARE
TECHGENIX RECENT POSTS
Under the hood:

Hyper-V
shutdown registry settings
6 can’t-miss tips
to improve
TechGenix reaches millions of IT
Windows 10 performance
Professionals every month, and has
set the standard for providing free Skygofree
technical content through its malware poses
growing family of websites, serious danger to Android
empowering them with the answers users
and tools that are needed to set up,
configure, maintain and enhance
their networks.
 
Copyright © 2018 TechGenix Ltd. | Privacy Policy | Terms & Conditions | Advertise  

Migrating A Small Organization From Exchange 2010 To Exchange 2016 (Part 3) - TechGenix PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Migrating A Small Organization From Exchange 2010 To Exchange 2016 (Part 3) - TechGenix PDF

Uploaded by

Copyright:

Available Formats

2/5/2018 Migrating a small organization from Exchange 2010 to Exchange 2016 (Part 3) - TechGenix

SECTIONS  TECH NEWS  TUTORIALS REVIEWS NEWSLETTERS VIDEOS ABOUT  

Migrating a small organization FEATURED PRODUCT

from Exchange 2010 to

POSTED ON JANUARY 26, 2016

 SHARE ON FACEBOOK  TWEET IT   

Join 900,000 fellow IT Pros...

and be among the rst to learn