This is an issue we are having with some but not all of our users..
It appears to be impacting about 60% of the accounts we have tested..
For some users the move is Successfull.. Outlook asks to restart, it does and they are good to go.
For others Outlook fails. They get the promot to restart outlook after the mailbox move is complete..
They restart and outlook stops with a Outlook cannot log on error.
THe profile looks correct with the Exchangeguid and email address.
They can log on VIA OWA without issue but not Outlook 2010.
I have run the Connectivity Analzser with on of the failed users credentials and it shows Autoconfigure passses
but it fails on Outlookanywhere.
If I gave a successfull 2013 user full control over a failed users mailbox and they can open the mailbox without any issues.
The issue also follows the user from PC to PC or thin clients. Successfull users work logged into a failed users PC. Failed users don't work logged into a successfull user's PC.
We thought it may be a Kerberos ticket size issue so we increased the HTTP parameters MaxFieldLength and MaxRequestBytes to 65534 on all the CAS servers.
THis did not help.
I ran Netmon while I had a user try to open outlook and noted for following
Network capture on CAS during attempts show
Http: Response, HTTP/1.1, Status: Unauthorized, URL: Using Multiple Authetication Methods, see frame details
StatusCode: 401, Unauthorized
And
Http: Response, HTTP/1.1, Status: Bad request, URL:
StatusCode: 400, Bad request
Outlook and the sever are current on all patching.
Certs on CAS are issued from our Enterprise CA.