Monday, January 18, 2016

Exchange 2010 to Exchange 2013 Mailbox Move Bug

Over the past few months I have been working to get our organization upgraded from Exchange 2010 to Exchange 2013. During one of more recent mailbox moves for some of our test users, we stumbled across an interesting issue with Exchange 2013 and Outlook once the mailbox migration was completed.


Scenario
- Exchange 2010 Server SP3 RU 11
- Exchange 2013 Server CU10
- Users Mailbox on Exchange 2010 has not only a mailbox but also an Exchange archive mailbox.
- An online mailbox move of both the mailbox and archive is initiated to move the mailbox to Exchange 2013

Issue
As the mailbox move is completing, the user get the obligatory "The Microsoft Exchange administrator has made a change that requires you to quit and restart Outlook” . After the user restarts Outlook, everything looks fine until they try to access there archive mailbox. upon trying to access there archive they get an error "Cannot expand the folder. The set of folders cannot be opened. Microsoft Exchange is not available. Either there are network problems or the Exchange server is down for maintenance." This was puzzling as user could access there archive via Outlook Web App with out issue. now one of the odd things I noticed was that users were getting the notice to restart outlook prior to Exchange showing it was 100% done with the mailbox/archive move.

Fix
So after some troubleshooting mainly on the client side, I opened a Premier Support Ticket with Microsoft. After describing my issue to the support specialist he suggested I move another user and reproduce the issue and then recycle the Autodiscover Application Pool. Much to my surprise, I was able to reproduce the issue again and upon recycling the Autodiscover Application pool, the user got yet another prompt to restart outlook. After that the user was able successfully access both there mailbox and archive mailbox.

Premier support indicated to me that this is currently an active bug within Exchange 2013.

to workaround this issue, I have created a little PowerShell script to recycle the Autodiscover ApplicationPool on all my Exchange 2013 servers.





Hope this helps.