Migrating A Small Organization From Exchange 2010 To Exchange 2016 (Part 4)

2/5/2018 Migrating a small organization from Exchange 2010 to Exchange 2016 (Part 4) - TechGenix
 14 COMMENTS  SHARE
SECTIONS  TECH NEWS  TUTORIALS REVIEWS NEWSLETTERS VIDEOS ABOUT  
Migrating a small organization FEATURED PRODUCT
from Exchange 2010 to

Exchange 2016 (Part 4)
Steve Goodman 2  9 Views  14
POSTED ON FEBRUARY 28, 2016
 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 3)
FEATURED FREEWARE
(Part 5)
Migrating a small organization from Exchange 2010 to Exchange 2016 (Part 4)

http://techgenix.com/migrating-small-organization-exchange-2010-exchange-2016-part4/ 1/20
Migrating a small organization from Exchange 2010 to Exchange 2016  14 COMMENTS  SHARE
(Part 6)

Completing Post Installation Get a free copy of
the new
Con guration SolarWinds
Permissions
Analyzer!
Con guring Receive Connectors
We’ll need to ensure that the same settings are applied to Receive Connectors
on Exchange 2016 as per Exchange 2010. Default and Client connectors are
already created and do not typically need to be altered. The defaults for RECOMMENDED
Exchange Server 2016 allow email from the internet or spam filter to be
Best and worst
delivered without adding an additional permission. practices for
Microsoft
Many organizations do allow users to relay mail through Exchange from Exchange TLS
and SSL
application servers, so we will use this as an example to illustrate how the
Exchange 2016
process is slightly different when compared to Exchange 2010. upgrade tips
and tricks
RECOMMENDED from the eld
(Part 1)
Migrating Public Folders to Exchange 2013 (Part
1) Deploying
Exchange
Server 2016
(Part 1)
To begin, launch the Exchange Admin Center and navigate to Mail
Flow>Receive Connectors and after selecting the Exchange 2016 server from
the list, then choose Add (+) to create a new Receive Connector:
FOLLOW US
 
Figure 1: Creating a new Receive Connector

On the first page of the wizard, enter the name for the receive connector. For  14 COMMENTS  SHARE
consistency we’ve specified the server name after entering Anonymous Relay.
Select Frontend Transport as the role and choose Custom as the type: 
SECTIONS  TECH NEWS  TUTORIALS REVIEWS NEWSLETTERS VIDEOS ABOUT 
Figure 2: Naming the connector and specifying core options
On the next page, we'll be provided with the opportunity to specify Network
Adapter Bindings - the IP address and TCP/IP port that the receive connector
will listen on. Our example receive connector will listen on the standard port
for SMTP, port 25:
Figure 3: Leaving TCP/IP listener settings as default
On the final page of the wizard, we'll choose which IP addresses that the
receive connector will accept mail for.
This allows multiple receive connectors to listen on the same TCP/IP port
and IP address and perform an action depending on the remote IP address of
a client.
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
As an example, if our anonymous connector on Exchange 2010 only allowed

mail relay from the IP addresses 192.168.15.1-20, we'll specify that range
here:
Figure 4: Specifying IP addresses that can use this connector
After completing the wizard, we will then open the new Receive Connector’s
properties page by selecting it from the list, then choosing Edit, as shown
below:
Figure 5: Editing connector settings after creation
In the Exchange Receive Connector window, select the Security tab. Then
within the Authentication section select Externally secured to indicate our
anonymous relay is from secure IPs; then under Permission Groups, choose
Exchange Servers and Anonymous users:
Figure 6: Allowing anonymous relay
Moving Default Mailbox Databases

We will move the initial database created by Exchange Server 2016 setup and
make it our first Mailbox Database.
To perform this action, we will perform a two-step process using the

Exchange Management Shell.
First, launch the Exchange Management Shell and use the following
command to rename the database to DB01:
Get-MailboxDatabase -Server <Server> | Set-MailboxDatabase -Name DB01
Figure 7: Renaming the default database
In the example above you'll see that by executing the Get-MailboxDatabase

cmdlet before making the change we see its default name – “Mailbox
Database” with a random suffix. After making the change, the name is
changed to something more appropriate.

With the database name changed, it still remains in the same location. Move  14 COMMENTS  SHARE
both the Database file and the associated log files to their respective final
destinations using the Move-DatabasePath cmdlet with the -EdbFilePath and
-LogFolderPath
SECTIONS  parameters:
TECH NEWS  TUTORIALS REVIEWS NEWSLETTERS VIDEOS ABOUT  
Move-DatabasePath -Identity DB01 -EdbFilePath

C:\ExchangeDatabases\DB01\DB01.EDB -LogFolderPath
C:\ExchangeDatabases\DB01_Log
Figure 8: Moving the default database path
When moving the database, it will be dismounted. The files will then be
moved to the new location and the database and log locations updated in
Active Directory. Finally the database will be re-mounted.
Creating Additional Mailbox

Databases
Next, create additional Mailbox Databases to match our design specifications.
We can create the mailbox databases using either the Exchange Admin
Center or the Exchange Management Shell.
In this example we will use the Exchange Management Shell, which for a
larger number of databases will be faster and more accurate.
The cmdlets used are New-MailboxDatabase, Restart-Service, Get-

MailboxDatabase and Mount-Database.
In the example shown below we will use the first cmdlet to create the
databases, restart the Information Store to ensure it allocates the correct
amount of RAM, then after retrieving a list of all databases we will ensure
they are mounted:

New-MailboxDatabase -Name DB02 -Server <Server> -EdbFilePath

C:\ExchangeDatabases\DB02_Log 
SECTIONS
 TECH NEWS  TUTORIALS REVIEWS NEWSLETTERS VIDEOS ABOUT 


Restart-Service MSExchangeIS
Get-MailboxDatabase -Server <Server>| Mount-Database
Figure 9: Creating additional databases
Con guring Mailbox Database

Settings
After we have moved our first Mailbox Database and created our additional  14 COMMENTS  SHARE
mailbox databases, we will now need to configure each database with the
correct limits.
The limits chosen for our example environment are shown below, along with
retention settings for mailboxes:
Warning Limit
Prohibit Send Limit
Prohibit Send/Receive Limit
Keep Deleted Items for (days)
Keep Deleted Mailboxes for (days)
4.8GB
4.9GB

5GB
14
30
It’s possible to configure this using the Exchange Admin Center, but for
multiple databases, use Exchange Management Shell to ensure consistency.
Using a combination of the Get-MailboxDatabase cmdlet and Set-
MailboxDatabase cmdlet make the changes, using the values from the table
above:
Get-MailboxDatabase -Server <Server> | Set-MailboxDatabase -

IssueWarningQuota 4.8GB -ProhibitSendQuota 4.9GB -
ProhibitSendReceiveQuota 5GB -DeletedItemRetention "14:00:00" -
MailboxRetention "30:00:00"
Figure 10: Updating mailbox database settings
Preparing for Exchange 2016

Migration
Testing base functionality

Before we can move namespaces and mailboxes across to Exchange Server  14 COMMENTS  SHARE
2016 we need to test that the new server is fully functional.
We'll start by creating a test mailbox to use on Exchange 2016. To do this, 

navigate to the Exchange Admin Center and within Recipients choose Add,
then User Mailbox:
Figure 11: Creating a test mailbox
There is no prescriptive name for a basic test account, so enter suitable

unique and identifiable details:
Figure 12: Specifying test mailbox settings
After creating our test mailbox we’ll now need to test that they are functional
from a client perspective.
Navigate to OWA via the server’s name. As a minimum test mail flow works
correctly between our new Exchange 2016 test user and existing Exchange
2010 users.

Figure 13: Testing OWA and other services
Updating Exchange 2010 Virtual

Directory URLs
Exchange 2016 supports acting as a proxy for Exchange 2010 services. This
means that it is easy to allow Exchange 2010 and Exchange 2016 to co-exist
using the same URLs.
We decided earlier in this guide that we would use the same names for both
Exchange 2016 and 2010.
It is now time to move the autodiscover.goodmanindustries.com and

mail.goodmanindustries.com names across from Exchange 2010 to Exchange
2016.
This, along with the respective DNS / firewall changes, will result in HTTPS
client traffic for Exchange 2010 going via the Exchange 2016 server.
We will update our core URLs for Exchange 2010 to remove the
ExternalURL value. We'll also enable Outlook Anywhere, configuring it with
the HTTPS name that will move to Exchange 2016.
To do this we will login to the Exchange 2010 server and launch the
Exchange Management Shell. Enter the following PowerShell commands,
substituting the $Server and $HTTPS_FQDN variables for appropriate
values.
$Server = "EX1401"

$HTTPS_FQDN = "mail.goodmanindustries.com"
Get-OWAVirtualDirectory -Server $Server | Set-OWAVirtualDirectory -

ExternalURL $null
Get-ECPVirtualDirectory -Server $Server | Set-ECPVirtualDirectory -

ExternalURL $null
Get-OABVirtualDirectory -Server $Server | Set-OABVirtualDirectory -

ExternalURL $null
Get-ActiveSyncVirtualDirectory -Server $Server | Set-

ActiveSyncVirtualDirectory -ExternalURL $null
Get-WebServicesVirtualDirectory -Server $Server | Set-

WebServicesVirtualDirectory -ExternalURL $null
Enable-OutlookAnywhere -Server $Server -ClientAuthenticationMethod

Basic -SSLOffloading $False -ExternalHostName $HTTPS_FQDN -
IISAuthenticationMethods NTLM, Basic
Figure 14: Updating a

Migrating Exchange 2010 URL and Outlook
small organization Anywhere 2010 to Exchange 2016 (Part 4)
from Exchange
configuration  14 COMMENTS  SHARE
From a client perspective this should not have any immediate effect. The
Exchange 2016 server will provide External URL values via Autodiscover,
but in the meantime client traffic will still be directed at the Exchange 2010
staging server.
Updating Internal DNS records

and switching external HTTPS
connectivity
To direct traffic internally at the Exchange 2016 server we need to change
internal DNS records so that both the Autodiscover name and HTTPS
namespace (in our case, mail.goodmanindustries.com) are configured with
the IP address of the new Exchange 2016 server.
On a server with access to DNS Manager, such as an Active Directory

domain controller, update both records from the IP address of the Exchange
2010 server to the Exchange 2016 server:
Figure 15: Updating internal DNS entries
Clients will not be immediately redirected to use the Exchange 2016 server as
the proxy for client access, and instead will do so once their cached records
expire. As soon as clients can access the server retry login and client access
to ensure no issues exist.
If internal access works without issue, update the external HTTPS publishing
- which in our example organization is a NAT rule configured via the router.
Summary
In part four of this series, we’ve completed the post-install configuration and
SECTIONS TECH NEWS TUTORIALS REVIEWS NEWSLETTERS VIDEOS ABOUT 
began preparation

for the migration.
 Base functionality has been tested and 
we have updated records to direct client access to the server. In the next part
of this series we’ll begin by updating mail flow.
If you would like to read the other parts in this article series please go to:

(Part 1)
(Part 2)
(Part 3)
(Part 5)
(Part 6)
Featured Links
READ NEXT
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 5) (Part 6)
Load balancing Load balancing Exchange 2016

Exchange Server Exchange Server upgrade tips and
2016 (Part 1) 2016 (Part 2) tricks from the
eld (Part 2)

TECHGENIX » MS EXCHANGE SERVER » DEPLOYMENT & MIGRATION » MIGRATING A SMALL

ORGANIZATION FROM EXCHANGE 2010 TO EXCHANGE 2016 (PART 4)
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
loves to share his expertise.
14 COMMENTS
Jorden April 19, 2017 at 3:12 pm R E P L Y
On Part 4, updating the Exchange 2010 Virtual Directory

URLs, When running the last command, Enable-
OutlookAnywhere -Server $Server -
ClientAuthenticationMethod Basic -SSLOffloading $False -
ExternalHostName $HTTPS_FQDN -
I get the following error:
The virtual directory ‘Rpc’ already exists under
‘FNSSERVER.feedns.local/Default Web Site’.
Parameter name: VirtualDirectoryName
+ CategoryInfo : InvalidArgument: (FNSSERVER\Rpc
(Default Web Site):ADObjectId) [Enable-
OutlookAnywhere],
ArgumentException
+ FullyQualifiedErrorId :
78452C6B,Microsoft.Exchange.Management.SystemConfig
urationTasks.EnableRpcHttp
Evan August 11, 2017 at 5:31 pm R E P L Y
I’m getting the same error as Jorden

Michael April 20, 2017 at 2:24 am R E P L Y
Every guide for creating a receive connector has had the

same “use defaults” listed and it has never worked for me. It 
breaks the transport service because multiple connectors are

attempting to listen on the same port apparently. If I change
it from 25 to 2526 as an example and restart Transport role
mail starts flowing normally again. Still not sure why this is
but it has always been like this for me.
Shawn May 3, 2017 at 11:06 am R E P L Y
Receiving the same error as Jorden.
Justin June 2, 2017 at 9:04 am R E P L Y
Enable-OutlookAnywhere -Server $Server -

ClientAuthenticationMethod Basic -SSLOffloading $False -
Gives an error. A positional parameter cannot be found that

accepts argument ‘=ISSAuthenticationMethods’
Steve Goodman June 2, 2017 at 9:12 am R E P L Y
Justin, this looks like a typo when entering the command –

note that the error says =ISSAuthenticationMethods rather
than -IISAuthenticationMethods
Dexter Wynn June 16, 2017 at 1:45 pm R E P L Y
Your guide is great! I just have one question. You stated you
were setting up 4 databases and a recovery. What were the 4
databases for and how do you set up the VSS and Recovery
drive?
Steve Goodman June 19, 2017 at 7:09 am R E P L Y
Hi,
The four databases are for mailboxes and based on the

output of the Exchange role calculator and to ensure we
make good use of the Exchange Standard edition licence to  14 COMMENTS  SHARE
spread mailboxes across DBs, whilst leaving the potential to

add one more database for maintenance.

The recovery disk is unused until a recovery is required.
The VSS configuration will depend on the backup software
you use and may be automatically managed and configured
by that software.
Cheers,
Steve
Geordie August 14, 2017 at 3:33 pm R E P L Y
Hi Steve,
We currently have Exchange 2010 installed on Windows
Server 2008 R2. This is also our Domain Controller. It is
time for us to upgrade and/or migrate but read somewhere
that once Exchange is installed it is very hard to upgrade
Windows.
So my sort of plan would be to create a new Windows 2016
server and install Exchange 2016 and migrate mailboxes
from Exchange 2010 server.
However, one other complication is that client would like
this new server in the cloud at AWS. The existing servers
are HyperV and for a single domain. So the complication is
do we also move the Domain Controller to AWS or attempt
to split the DC to its own server at AWS which I understand
is best practice.
I wondered if you had any thoughts on this.
Roy August 17, 2017 at 6:25 am R E P L Y
Regarding the error in the first comment; this is because

Outlook Anywhere is still enabled on Exchange 2010 and
the command is telling it to be enabled again. Open the
EMC on 2010, navigate to Server Configuration on the left
then Client Access, and on the right click “Disable Outlook
Anywhere”. Then try running the command again, it should
work this time with the new settings.

Robin November 16, 2017 at 5:32 am R E P L Y

Hi, after step 4 : Updating Exchange 2010 Virtual Directory

URLs : Enable-OutlookAnywhere -Server $Server -
SECTIONS  ClientAuthenticationMethod
TECH NEWS  Basic REVIEWS
TUTORIALS -SSLOffloading $False -
NEWSLETTERS VIDEOS ABOUT  
If first receive an error that the RPC connection allready

exists.
and after updating the DNS records from mail.
I am unable to get the Outlook clients connected to the new

mailserver 2016. it constantly asks for credentials and is
unable to start outlook.
I think this can also be because the first IT provider has

called the exchange 2010 server “mail”.
after changing the A records Mail. the new 2016 server
loses connection with 2010.
any tips? can i rename the old server without any problems?
so i can easily change the A record?
Robin November 20, 2017 at 6:05 am R E P L Y
Any Ideas?
Tom November 28, 2017 at 3:19 am R E P L Y
Same here.
Changed Exchange 2010 Outlook Anywhere external host
mail.domain.com => autodiscover.domain.com. Now
Outlook client works from outside.
Ivan January 23, 2018 at 4:47 am R E P L Y
Hi Steve,
What namespace do you have configured for CAS Array
object for Exchange 2010? If you use one of the two
mentioned (mail.domain.com and
autodiscover.domain.com), what will happen with RPC

connection for Exchange 2010 Outlook Users when you  14 COMMENTS  SHARE
update both DNS records to redirect traffic to Exch2016?

Your email address will not be published. Required fields are marked
*
Name* Email* Website
POST COMMENT
NOTIFY ME OF FOLLOW-UP COMMENTS BY EMAIL .
NOTIFY ME OF NEW POSTS BY EMAIL.
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  14 COMMENTS  SHARE
their networks.
  
Copyright © 2018 TechGenix Ltd. | Privacy Policy | Terms & Conditions | Advertise  

Migrating A Small Organization From Exchange 2010 To Exchange 2016 (Part 4) - 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 4) - TechGenix PDF

Uploaded by

Copyright:

Available Formats

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

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

Migrating a small organization FEATURED PRODUCT

from Exchange 2010 to

POSTED ON FEBRUARY 28, 2016

 SHARE ON FACEBOOK  TWEET IT   

Join 900,000 fellow IT Pros...

and be among the rst to learn