Home Free Tools Toolkits Contact Us

 Home > EDB to PST Converter > Free Step by Step guide to migrate Exchange 2013 to 2019

Free Step by Step guide to migrate Author

Exchange 2013 to 2019
 Eric Simson |  Updated on January 30, 2020 |  EDB to PST Converter |  3 Comments |
 6 min read Eric Simson

Eric Simson is an Email

First thing to see when migrating from Exchange 2013 are the requirement, limitations and Platform Consultant and

co-existence. These are the important things to take note when migrating from Exchange is associated with Stellar

2013 to 2019. For this free guide we will assume that only one Exchange Server is installed. Data Recovery from last 6
years. He writes about the

Prerequisites latest technology tips and

provides custom solutions
In this case, if you are migrating from Exchange 2013 you would need the setup to have related to MS Outlook, MS
Cumulative Update 21 (CU21) or later installed and the Active Directory Servers must be Exchange Server, O ce
hosted on Windows 2012 R2 Standard or Datacenter and higher with Windows Server 2012 365, and many other
R2 Active Directory forest functionality or higher. So if you still host Windows 2008 R2 Email Clients & Servers.
domain controllers, you need to make sure that these are decommissioned prior to the
installation and nally the migration.

One important thing to take note is that with Exchange 2019 we don’t have any Uni ed
Messaging (UM) meaning that if you have Lync or Skype for Business Server you will lose the
ability to save voicemail messages in your mailboxes and an alternative needs to be found
like CX-E or Azure Voicemail on O ce 365. Another thing to consider is clients as Outlook
2013 and higher are supported.

So let’s start by having out virtual machine or physical machine installed with speci cally
Windows Server 2019 standard or DataCenter. Microsoft recommends installing Exchange
2019 on Windows Server 2019 Core but the Desktop Experience feature is still supported, so
Search the site
it’s your choice at this stage. You cannot install it on any other operating system. If you will
be installing the Management Tools on other machine you will need to install them on a
Windows 10 64 bit edition. After doing all the updates possible the following are the
Categories
requirements for installation.


Installation of pre-requisites is to have .NET Framework 4.7.2 or later, Visual C++

Redistributable Package for Visual Studio 2012 and 2013; and the Remote Tool Select Category

Adminisration Pack and some other stu . This can be done via PowerShell using the below
command to install all pre-requisites. Related Posts

Install-WindowsFeature NET-Framework-45-Features, RSAT-ADDS, RPC-over-

HTTP-proxy, RSAT-Clustering, RSAT-Clustering-CmdInterface, RSAT- How to use “Search
Clustering-Mgmt, RSAT-Clustering-PowerShell, Web-Mgmt-Console, WAS- Mailbox” & Export to PST
in Exchange Server
Process-Model, Web-Asp-Net45, Web-Basic-Auth, Web-Client-Auth, Web-
Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, May 29, 2018

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- How to Take Exchange
Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, 2016/2013 Mailbox
Backup Using
Web-WMI, Windows-Identity-Foundation PowerShell Cmdlets
November 18, 2016
Before installing anything, let’s start by preparing inserting the Exchange Server 2019 media
and running the below command to prepare the Schema and the AD.
Migrating Exchange
1 Setup.exe /PrepareSchema /IAcceptExchangeServerLiscenceTerms
Server 2010 to 2016 using
2 Setup.exe /PrepareAD /OrganizationName:”Contoso” /IAcceptExchangeServerLicenseTerms
Exchange Admin Center
Here we have prepared the Active Directory to be Exchange 2019 friendly and now we can (EAC)
start the installation. Before we start, make sure that no new updates are available for the July 19, 2016
pre-requisites we installed.

Troubleshooting
Open Setup.exe
Exchange 2013 Mailbox
Database Exceeds Size
Tick the box to Connect to the Internet and check for updates and click Next. After the limit Problem
introduction click Next.
November 23, 2016

On the Server Role Selection page make sure to tick Mailbox Role and Management Tools
and click Next. Choose the location of the installation of the Exchange server and click Next How to Export Exchange
2013/2016 public folder
(Make sure not to install Exchange on the system drive as it’s highly recommended).
to PST

On the Malware protection setting click No for now as this can be enabled in the future but December 31, 2019

for now we don’t need it. After the Readiness screen the installation will start and after
nishing make sure again to see if any updates are available.

Setup the Service Connection Point (SCP)

The next step is to setup the Service Connection Point (SCP) which is an attribute on
Exchange Server that is stored in the AD schema that directs domain-joined client
computers using Outlook to the server using auto discover settings. By default it will change
to the new server and we would need to stop users from connecting to the new server for
now due to issues with certi cates as the default with the installation is a self-signed one.
This can be changed by running the PowerShell cmdlet Set-ClientAccessService –Identity
ExchangeServer2013 –AutoDiscoverServiceInteralUri. This will point the users to the current
server..

Import the Certi cates

Now we need to import the Certi cates to the new server. First we need to identify the
certi cates to move by using the PowerShell cmdlet

1 Get-ExchangeCertificate | fl Thumbprint,NotAfter,Issuer,CertificateDomains,Services.


This will give us a list of certi cates along with the thumbprint and the services they are used
for so we know the certi cates and on what services to assign them to. On the Exchange
2013 server use the PowerShell cmdlet below to export the certi cate for the Exchange 2019
server.

1 $CertPass = ConvertTo-SecureString "LetMeIn" -AsPlainText –Force

2 Export-ExchangeCertificate -Thumbprint C87C1CBA43733D177B2679BC825808C7BECC659B -FileNa

Once done, keep a note of the password. Don’t worry as if you forget it you can always redo
the above and use a new password. Copy the le to the Exchange Server 2019 and run the
below in PowerShell

1 $CertPass = ConvertTo-SecureString "LetMeIn" -AsPlainText –Force

2 Import-ExchangeCertificate -FileName C:\temp\Exchange2013Certificate.pfx -PrivateKeyExp
3 Password $CertPass | Enable-ExchangeCertificate –Services POP,IMAP,IIS,SMTP –DoNotRequi

This will import the certi cate and assign it to the services of POP, IMAP, IIS and SMTP. The
next step is to set the URLs for the internal and external access using Outlook Anywhere. On
the Exchange 2019 run the below command for Outlook Anywhere, OWA, ECP, Web Services,
ActiveSync, O ine Address Book and MAPI

1 Get-OutlookAnywhere -Server srvexc2019 | Set-OutlookAnywhere -InternalHostname ex02.myd

1 Get-EcpVirtualDirectory -Server srvexc2019 | Set-EcpVirtualDirectory -InternalUrl https

1 Get-OwaVirtualDirectory -Server srvexc2019 | Set-OwaVirtualDirectory -InternalUrl https

1 Get-WebServicesVirtualDirectory -Server srvexc2019 | Set-WebServicesVirtualDirectory -I

1 Get-ActiveSyncVirtualDirectory -Server srvexc2019 | Set-ActiveSyncVirtualDirectory -Int

1 Get-OabVirtualDirectory -Server srvexc2019 | Set-OabVirtualDirectory -InternalUrl https

1 Get-MapiVirtualDirectory -Server srvexc2019 | Set-MapiVirtualDirectory -InternalUrl htt

So that these changes are in e ect immediately we would need to recycle the Application
Pool for MSExchangeAutodiscoverAppPool. To do this just open IIS, expand the server and
click on Application Pools. Find the Application pool and click on Recycle.

DNS Records
Now that the URLs are changed it’s now time to point the DNS records to the new Exchange
2019 server by contacting your network team to see that any ports open and forwarded with
NAT to the current Exchange 2013 are replicated to also point to the Exchange 2019. All
open ports to the Exchange 2013 should be opened for the Exchange 2019. Any forwarding
from outside to the inside should be changed to point to the Exchange 2019 server instead.
It’s now the time to point the SCP record we set before to point to the Exchange 2019 rather
than the 2013.

Here the users should be able to work by accessing the Exchange 2019 as their Exchange
server while being redirected to the Exchange 2013 server as the location of their mailbox. 
It’s time to go round and work on the multi-function devices to point to the new Exchange
2019 Server and from the server setup the transport rules to allow the devices to be allowed
to pass through it. You would need to make sure that the URL being used internally is also
changed and propagated. Then it’s up to connecting one Outlook and checking that it’s
connecting to the right Exchange Server by opening the Outlook Connection status.

Mailbox move from one server to another

The next step is to do the mailbox move from one server to another. This is done by creating
a Migration batch job. Open the Exchange Admin and click on Recipients, Click on Migration
and click the + sign and select move to a di erent database

Select the mailboxes to move and click Next

Then you can select to move everything or selective being the mailbox only or the archive
mailbox only. Select the Target database for mail and archive and click next. You can select
multiple mailboxes at once in a job depending on the volume and sizes.

Once all mailboxes have moved, you can go ahead and uninstall Exchange 2013 from the
current server and after that you can decommission the server with it. Your Exchange Server
migration is complete. Now with every migration and practically for any Exchange Setup it is
also recommended to have the right tool like Stellar Converter for EDB for those moments
you have those annoying issues and catastrophes during an installation, migration or day to
day work. With EDB to PST Converter application you will be able to open an online or o ine
EDB le, export to PST, and export to another live Exchange Server or O ce 365. You can
download now and preview your Converted pst le free!!


Best Selling Products

Stellar Data Recovery Stellar Data Recovery

Professional for Windows Professional for Mac
Stellar Data Recovery has the right Stellar Data Recovery for Mac
Windows Recovery tool for all your program performs safe..
data recovery..

Stellar Photo Recovery Stellar Repair for Video

A comprehensive photo recovery Powerful video repair tool for
software to restore photos, music & repairing corrupt or damaged MOV
video les.. and other video les..

View More

Comments(3)

Lucas Armer  February 18, 2020

I agree with Bruno D. I am not a technical person and mostly I have confusion with
commands. So, I always try to nd easy methods to do my work.

Reply

Bruno D  January 30, 2020

Migration by above given solution needs so many assets and lot of expertise. For a
non-technical user, it’s quite di cult to use this solution. I want to go with Stellar
Converter for EDB.

Reply

Eric Simson  February 1, 2020

Thanks for your response. Stellar Converter for EDB also helps in
converting mailboxes from multiple EDB les in a single process.

Reply

Leave a Reply

Your email address will not be published. Required elds are marked *

Name* 

Email*
Website

7  −  6  =  

Submit Comment

REACH US

48 Bridge Street Metuchen, New Jersey 08840, United States

+1-877-778-6087

USEFUL LINKS

About us
Legal Policy

Privacy Policy

Quality Policy

Awards & Reviews

Career
Sitemap

NEWS AND EVENTS

Press Release

Events

PA R T N E R S

Affiliates

Resellers

Distributors

RESOURCES

Support

Knowledge Base

Blog
Articles

Product Videos

Student Discount

Contact us

A L S O AVA I L A B L E AT


Stellar Phoenix & Stellar Data Recovery are Registered Trademarks of Stellar Information Technology Pvt. Ltd.
© Copyright 2020 Stellar Information Technology Pvt. Ltd. All Trademarks Acknowledged.