EAC Access While Co-Existing Exchange 2013 With 2010

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.
  1. hi there,
    i have just installed new Exchange 2013 , my previous exchange 2010 is primary to receive and send email inbound and outbound.

    I have to decommission my 2010 once all users mailboxes are transferred to 2013 until then i want 2010 to be used for all email routing incoming /outgoing for itself and users on 2013 (who will be transferred).

    the problem is that users on 2013 database are unable to send emails inbound and outbound although they are recieving emails from 2010 and outside so i cant start this transfer

    Please help me with this issue.

  2. if we moved Admin mailbox from 2007/2010 to 2013 can we make configuration on 2007/2010 any more ?
    or we will lost our configuration rights on 2007/2010 exchange ?

    • Hi Sajid,

      You can edit both sides, but will have to use the appropriate tools. Moving mailbox wont be an issue.
      You can always create a new 2013 admin account if you want.


Leave a Comment