Hi all,

I have been battling an issue following the migration of mailboxes from Exchange Server 2010 to Exchange Server 2013.

When I created test accounts for migration on 2010 they connect to the 2013 server fine after migration using Outlook 2013.

I am running Exchange 2013 Enterprise CU6.

I then chose several users for a secondary migration test for live accounts. All of these users are running Outlook 2013 with the Latest updates.

Following the migration the users are asked to restart as normal.

Once they restart their clients they are prompted again to restart, "The Microsoft Administrator has made a change that requires you to quit and restart outlook".

Outlook continues to load and show as "connected". However, the users cannot send or receive.

They are presented with error: "Task "emailaccount@domain.com" - Sending reported error (0x80040115): We can't complete this because we can't contact the server right now.

Please try again."

If I do a "repair" of the mail account, everything passes successfully, however, they still cannot send or receive. If I then remove the mail profile and attempt to add it again, I receive the error: "The connection to Microsoft Exchange is unavailable. Outlook must be online or connected complete this action."

If I select okay, I am presented with the correct Microsoft Exchange server and Mailbox details of the user, (GUID of the mailbox@domain and =SMTP:emailaccount@domain.com). I can check name, and it fails with The name cannot be resolved. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action.

If I log onto a different machine on the same network as the same user who has been migrated, the mailbox will load successfully without issue. The autodiscover .xml is returning all of the correct addresses.

There is no ACL on the network.

Has anyone had any similar issue with Exchange 2010 to 2013 migration?

The select users I have migrated are now using OWA as a workaround.

Any assistance would be appreciated. 

Thanks.

Please try below tips for better prospects;

1. Unmount the DB and mount where these users' mailboxes resides.

2. move users into a sample test db and confirm the validity of DB

Rizmi

Based on your mentioned error, I would suggest you to have a look on this informative technet blog that cover this part in depth to sort-out the issue quickly : http://blogs.technet.com/b/vytas/archive/2014/11/12/your-administrator-has-made-a-change-and-requires-you-to-restart-outlook.aspx

Moreover, while need to move users mailbox from old server to newly created one, you may also consider on this automated solution(http://www.exchangemigrationtool.com/) that provides a hassle-free environment to get this job done in an easier way.

Hi Adam,

I have already ensured that this update has been applied, as I stated in my post all users are running the latest updates as I control them via WSUS.

Thanks

Curious about your namespaces.

What autodiscover URLs are in play.

Also what are the namespaces for OA and for the CASArray.

Hi Rhoderick,

I am using Direct Access for clients externally, and for anyone else without a DA enabled device I am publishing EWS, OWA, AS and Autodiscover via a netscaler. 

The issues I am experiencing are happening internally but would most likely be evident if I tested them externally in the same manner. 

The internal autodiscover url is as follows on both the 2010 and 2013 exchange servers: https://autodiscover.domain/Autodiscover/Autodiscover.xml

Hi everyone,

I have found the answer to my problem, it appears one our sys admins had applied a GPO to disable outlook anywhere on an OU. I have since removed the GPO and executed a gpupdate on the machines in question. The accounts are now working as normal.

Thank you for everyone's contributions

• Marked as answer by itupgrader 7 hours 5 minutes ago