Not Real University makes use of a broad range of Exchange features, including:

An Exchange 2013 CU13 Edge Transport server for inbound/outbound mail flow.An Exchange 2013 CU13 multi-role server, hosting one database for 33 mailboxes.An Exchange 2010 SP3 UR14 multi-role server, hosting one database for 78 mailboxes, and a public folder database.Running the script reveals the following information about Not Real University. Steve Goodman’s environment report script is a good tool for this purpose. To begin with, let’s perform a review of the existing environment to gather information that can be used for planning the migration project. That scenario provides the opportunity to demonstrate many of the technical requirements for migrating to Exchange 2016 from both Exchange 2010 and Exchange 2013. With the release of Exchange 2016, Not Real University has decided to stop the Exchange 2013 project and upgrade the entire environment to Exchange 2016 instead. They were in the process of upgrading to Exchange 2013 but were delayed by some technical issues. The customer, Not Real University, is currently running a mixed Exchange 20 environment. To demonstrate the Exchange 2016 migration process I’ll be using the following scenario. This article is the first part in a series on migrating to Exchange Server 2016.

Exchange server 2010 to 2016