One of the first things I’ve noticed when I finished installing Exchange Server 2013 in coexistence with Exchange Server 2010, is that when we navigate to the EAC URL at https://CAS_SERVER_NAME/ecp/
Then login, we automatically get redirected to Exchange Server 2010 ECP instead.
At first this made a lot of sense simply because my Administrator mailbox is still residing on the Exchange Server 2010. However this is going to be a common scenario for everyone when doing these types of coexistence deployments. So how do we get around that?
I searched on TechNet and came across article about Exchange Admin Center in Exchange 2013 that mentions something interesting that fixes this issue. Here’s the quoted text from this article describing a workaround:
If you’re in a coexistence scenario, where you’re running Exchange 2010 and Exchange 2013 in the same organization, and your mailbox is still housed on the Exchange 2010 Mailbox server, the browser will default to the Exchange 2010 ECP. You can access the EAC by adding the Exchange version to the URL. For example, to access the EAC whose virtual directory is hosted on the Client Access server CAS15-NA, use the following URL:
https://CAS15-NA/ecp?ExchClientVer=15. Conversely, if you want to access the Exchange 2010 ECP and your mailbox resides on an Exchange 2013 Mailbox server, use the following URL:
So the key element to this post is the ?exchclientver=15. By adding this line to the original ECP link, we would then be able to access the Exchange Admin Center. For example:
It would be nice to have this fixed, after all, this should be automatic, if we want to get to the EAC we should just simply type the correct link and connect and vise versa. Hopefully this issue will be addressed soon.