Monday, April 4, 2016

Migrating from Exchange 2010 to Exchange 2016 Part-3

In the first part,  i have covered process to migration any of the legacy to latest Exchange version, which is mandatory for any process orientated company.

in Second part i have covered basic pre-requisite for introducing Exchange Server 2016, such as server sizing, Naming space planning, end users Outlook updates & whether we will go for physical or virtual environment.

In this part i will focus on my existing Exchange 2010 environment, which should be up to date  or ready for introducing Exchange 2016 server.

As i mentioned on part on we have to do assessment of Exchange 2010 environment before moving forward, there are some basic steps are here:

Exchange 2010 Architecture Report

First of all i will suggest you get the current your Exchange environment architecture details. some time we do have old architecture documents but in between there are lot of the changes happen on environment so best practice to the latest Exchange 2010 environment Architecture report, you can use following PowerShell script which will give you details Architecture details.
Exchange 2010 Architecture Report

Generate Exchange Environment Reports

Generating Exchange environment report one of the best steps to upgrading/migrating your existing Exchange environment.
There are multiple way to generate your Exchange environment report but i will suggest user Steve Goodman's Power Shell which will give you a good overview of your environment. This script generates a HTML report and can be scheduled and emailed.
Although with tools like Visio and Word you can make such a document, it’s hard to keep these documents up to date or use previous versions to track and check changes.
Exchange Environment Reports

Exchange 2010 Servers Mailboxes States

There are multiple way to get the Mailboxes States which include the size of the mailboxes in current environment, i will suggest get the at least last 6 months report which will help you to future forecast of the mailboxes size quota & storage calculation.

you can use following Powershell script for getting Mailboxes States:

Exchange 2010 Mailbox Size Report
Generate Mailbox Size and Information Reports

Email Traffic Report

We need to factor the storage & transport capacity for future Exchange environment. The simplest way to deal with that would be to ignore this fact and oversize transport, which will provide additional capacity for unexpected peaks in message traffic. An alternative way to determine daily message flow would be to evaluate performance counters within your existing messaging system. 
In order to figure out the messages per day that you expect to run through the system, you can look at the user count and messaging profile. Simply multiplying these together will give you a total daily mail volume. You can use following PowerShell script to get the Email Traffic report:
Email Traffic and Daily Email Traffic

Exchange Best Practices Analyzer

The Exchange Best Practices Analyzer programmatically collects settings and values from data repositories such as Active Directory, registry, metabase and performance monitor. Once collected, a set of comprehensive ‘best practice’ rules are applied to the topology. The Microsoft Exchange Best Practices Analyzer is designed for administrators who want to determine the overall health of their Exchange servers and topology. The tool scans Exchange servers and identifies items that do not conform to Microsoft best practices. You can download from here: Exchange Best Practices Analyzer

You can use other tools, scripts to discover your Exchange environment before moving to Exchange 2010.

Updating Exchange Server 2010 

The minimum supported patch level for Exchange Servers 2010 is Service Pack 3 with Update Rollup 11 for introducing Exchange Server 2016.

You can download Exchange Server 2010 Service pack 3
Also you can download Exchange Server SP3 update Rollup 11 or you can download latest Rollup

As you can see my Exchange Server 2010 environment is updated and ready for getting Exchange 2016.

My Servers are with Update Rollup 12 for Exchange Server 2010 SP3 (KB3096066)

Update Outlook for end user

One of the very critical step is to update the Outlook client , in past experience this part is very critical and show stopper, once you introduce the Exchange 2016 in your environment, your end user can access there email without any issues.

Exchange Server 2016 supports Outlook 2010 and above for Windows client and on Mac Outlook 2011 and higher. Outlook 2007 is no more supported.
All versions of Outlook 2016 and Outlook 2013 are supported. Outlook 2010 is supported 

In this part 3 i have focused on Preparation of existing Exchange Server 2010 up to date for introducing Exchange Server 2016 such as assessment, Exchange Server 2010 Service pack & End users Outlook updates etc.

In next part 4 i will start installing Exchange Server 2016 in existing Exchange Server 2010 environment.

Hope this part will help you prepare your existing environment for up-gradation or migration.


For Part-2                                                           For Part-4

No comments:

Post a Comment