What happens when you try to access EAC after introducing Exchange 2013 into an existing 2010 organization?
The first thing admins try after having 2013 and 2010 servers co-existing is to hit the EAC url – to see what works and what doesn’t ;)
If you access EAC using the https://mail.domain.com/ecp or https://localhost/ecp on the local server, you may be a bit surprised to see the familiar 2010 ECP after logging in!
It is not a bug & Exchange is doing the right thing. The reason for the 2010 ECP is that the account that you have logged on with (mostly administrator) has its mailbox hosted on a 2010 database. There are two ways to fix the issue.
- You can move the admin mailbox to a 2013 database.
- If you don’t want to move the mailbox, but still want to access the EAC, add ?ExchClientVer=15 at the end of the ECP url, like https://mail.domain.com/ecp?ExchClientVer=15 or https://localhost/ecp?ExchClientVer=15 if you run it against the local 2013 server.