Microsoft Exchange 2010 to Exchange 2013 Transition (part 4)
April 29, 2013
Microsoft Exchange 2010 to Exchange 2013 Transition Part 1
Microsoft Exchange 2010 to Exchange 2013 Transition Part 2
Microsoft Exchange 2010 to Exchange 2013 Transition Part 3
I want to take a second to explain that this series of posts on how to migrate to Exchange 2013 didn’t come without it’s share of difficulties.
Upon the installation of Exchange 2013 I was able to connect to the Exchange Admin Console without issue. I documented all of the procedures from the first three posts. However after I restarted my Exchange Server I was unable to login anymore. I would continually get a blank page which I’ve seen others having the same issues.
I was unable to fix this issue using any of the methods described and built a new Exchange 2013 server thinking I did something wrong. After the second Exchange Server did the exact same thing, I’ve decided that Microsoft needs to add a patch for whatever problem is happening. Maybe it’s a bug with IIS, Server 2012 or Exchange 2013 but I have not made any modifications to the IIS virtual server directories so I’m concluding that it’s a Microsoft bug.
If anyone has suggestions for other users, please post them below so that we can get this solved. I’ll update this post if I ever find a solid solution to this puzzle.
I believe the reason for the issue where you could not connect following reboot after a fresh install is due to where the admin mailbox resides. If it’s still on the 2010 server the EAC will put you onto that server rather than the 2013 server.
The easiest way to get around this is to add the exch client version number to the URL used to access the 2013 EAC:
“https://exchange2013servername/ecp?ExchClientVer=15” – using this will always log you onto the 2013 EAC.
The other option is to move or create a new admin mailbox on the 2013 server before rebooting – note that you need to ensure the account has correct admin rights to exchange.
how about transition with RPC over https connexions