Managing a new Exchange Server 2016 EAC having your mailbox on a previous version

Share this:

During the transition between Exchange Server 2010/2013 to Exchange Server 2016, before moving the mailboxes any administrator that tries to access the EAC will be redirected to the legacy system.

Solution

In order to be able to manage it, the solution is simple, we just need to work on the URL, using the following example:

https://<server>/ECP/?ExchClientVer=15.1

The result is shown in the image below.

Written by Anderson Patricio

Anderson Patricio

Anderson Patricio is a Canadian MVP in Cloud and Datacenter Management, and Office Server and Services, besides the Microsoft Award he also holds a Solutions Master (MCSM) in Exchange and several other certifications. Anderson has been contributing to the Microsoft Community with articles, tutorials, blog posts, twitter, forums and book reviews. He is a regular contributor here at ITPROCentral.com, MSExchange.org, Techgenix.com and Anderson Patricio.org (Portuguese).

Related Post

How to deploy Exchange Server 2016 using command-l... Exchange Server 2016 can be deployed using the graphical user-interface or a setup deployment wizard, in this Tutorial we are going to cover the requi...
How to… access EAC after installing the first Exch... As soon as you introduce your first Exchange Server 2013 in your organization you first action may be trying to logon on ECP/EAC to get access however...
New version of Azure Backup Server introduces Mode... WOW! What a day for me! Microsoft Azure just announces new and improved features on the new version Azure Backup Server. Let’s start! They announce...
Exchange Server 2016 is here! Hello folks, Exchange Team has just released Exchange Server 2016 bits. To download a copy of the final version, use the following link: availab...