Scribd
Upload
22 views4 pages

Exchange Upgrade

Uploaded by

Mwebia Raymod
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
22 views4 pages

Exchange Upgrade

Uploaded by

Mwebia Raymod
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

UPGRADE OF EXCHANGE 2010 TO EXCHANGE 2019

1) INTRODUCTION

This proposal document is to clarify and streamline the planning and deployment process for
Knightfrank towards the upgrade of exchange 2010 to Exchange to 2019. The proposal includes
the following:

• Defining the technical decisions through the planning and deployment process
• Describing the decisions made and the commonly available options to consider in making
the decisions.
• Relating the decisions and options to the business in terms of cost, complexity, and other
characteristics
• Framing the decision in terms of additional questions to the business to ensure a
comprehensive understanding of the appropriate business landscape.

The proposal is intended to complement and augment the product documentation. It is assumed
that the reader has a basic understanding of the technologies discussed in this design. It is the intent
of these design to define business requirements, then align those business requirements to product
capabilities, and design the appropriate infrastructure.

KNIGHTFRANK CURRENT INFRASTRACTURE

Knight frank runs MS exchange 2010 which is currently out of support and requires an upgrade to
exchange 2019 to support scanning as all scanned documents are routed to user’s mailbox using the
exchange 2010.
There are three domain controller servers that are maintaining authentication of users and user
synchronization to the cloud.

There is one exchange 2010 server that has mailbox role.

The server roles in Exchange Server 2010 are:

• Mailbox Server – hosts the mailbox and public folder databases.

• Client Access Server – provides connectivity for clients (eg Outlook, Outlook Web App,
ActiveSync) to mailboxes.

• Hub Transport Server – responsible for all mail flow in the organization

• Edge Transport Server – a special transport server intended for installation in DMZ networks
to provide secure inbound/outbound email flow for the organization.

• Unified Messaging Server – provides voice mail and other telephony integration with
Exchange.

So how do these roles match up with Exchange Server 2003?

• The Mailbox server is basically the same as an Exchange 2003 server that hosts databases
(though Exchange 2010 has very different high availability features)

• The Client Access server is similar to an Exchange 2003 front-end server.

• The Hub Transport server is similar to an Exchange 2003 bridgehead server.

• The Edge Transport and Unified Messaging roles are new and don’t closely related to
Exchange 2003
MIGRATION TO EXCHANGE 2019 PROCEDURE

The step-by-step migration from exchange 2010 involves the following.

There is no direct way to migrate Exchange 2010 to 2019. You can manually migrate from 2010 to
2016. After you land in 2016, you can move to 2019.

To migrate Exchange Server 2010 to 2019, you need to go through several steps to perform the
migration from 2010 to 2016. All of the steps should be sequentially executed. Let’s see the process.

1. Meeting Exchange Server Requirements.

By using the 2010 version in the current system, you can find the CPU, RAM, and Disk Space
utilization. Ensures enough RAM and Disk space is available, before migration. Also, managing the
space for the backup.

2. Install Exchange 2016

After setting up the requirements for Exchange 2016, it’s time to install it.

Follow some steps.

• Prepare the Active Directory Schema.

• Update the Active Directory with the Exchange 2016 objects.

• Prepare the Domain.

• Install Exchange on this Server.

• Reboot the server.

3. Configure the Exchange Server

• Export the public SSL to the new Server.

• Export the correct certificate.

• Import public SSL to the new server.

• Log in to the Exchange Admin Centre.

• Enable the Certificate for IIS (Auto Discover)

• Restart IIS to apply for the certificate.

• Run the script.

4. Setting up Co-Existence

• Set up DNS to the new Exchange server.

• Remove the External URL value from the old Exchange server.

5. Migrate the Mailboxes

• Migrate all the mailboxes to Exchange 2016 by logging into the EAC.

• Now, after running all of the steps in a correct manner you moved to the Exchange 2016.
To migrate Exchange 2010 to 2019. Now, you are connecting to the 2016 version. You can migrate
Exchange 2016 to 2019 using the manual steps.

Migrate to 2019 From 2016 Manually

Make sure that both of the servers should be live to perform the migration. Go with these steps.

Note: To migrate mailbox from Exchange 2010 to 2019, you have to first migrate to 2016 versions,
then you need to migrate from 2016 to 2019

PROJECT PLAN

TASK TIMELINE
Envisioning and planning 0.3 hrs
Installation of exchange 2016 and all 4 hrs
prerequisites
Migration of mailboxes to the new 2016 server 2hrs
Installation of exchange 2019 server 4 hrs
Migration of mailboxes from exchange 2016 to 1 hrs
2019
Troubleshoot and remediation 3 hrs

You might also like