Tutorials

In this situation, we already have installed Windows Server 2016 and we migrated FSMO roles from the SBS 2011 to the new server. We have been following this migration tutorial How to migrate from SBS 2011 to Windows Server 2016 (Essentials) and we have ‘Enable folder redirection on the Windows Server 2016 Essentials and clean up old SBS 2011 group policies’. 

If you have Windows Server 2016/2019 standard without the Essentials role you have to follow How to migrate SBS 2011 to Windows Server 2016 Standard or Datacenter or How to migrate SBS 2011 to Windows Server 2019 Standard, Datacenter or Essentials. You can start the migration of your Exchange Server also before you introduce the new Domain Controller. It is up to you!

Every step in this tutorial has a screenshot and if any Powershell is involved we have made it easy for you to copy it to your own situation. This tutorial will guide you from the start until all Exchange mail has been migrated to the new server. The tutorial includes Powershell commands to migrate public folders in one batch to the new Exchange Server 2016. We will also explain what DNS changes are needed.

This tutorial will help most companies to migrate from Exchange Server 2010 to a new server with a new Exchange Server 2016. You should read the procedure before you start and if there is anything not clear please use our special forum for subscribers to ask your questions.

When the Exchange Server 2016 is installed and properly configured it can act as a downstream proxy for the Exchange Server 2010. The other way around is not possible because Exchange Server 2010 cannot act as an upstream proxy. This way both Exchange Servers will coexist in the network. You can migrate mailboxes in batches. An Outlook client will connect to the highest version Exchange Server in our network, in our case the Exchange Server 2016, and if the mailbox for that user has not been migrated to the new server it will proxy the request.