I have run into an issue where some users after migrating their accounts from Exchange 2007 to Exchange 2013 (sp1), their devices which were configured and working with an activesync device association fails to connect (the device says "the connection to the server failed"). I tried doing the testexchangeconnectivity.com test, and it fails for these affected users with an HTTP 500 (
Exchange ActiveSync returned an HTTP 500 response (Internal Server Error).HTTP Response Headers:
MS-ASProtocolCommands: Sync,SendMail,SmartForward,SmartReply,GetAttachment,GetHierarchy,CreateCollection,DeleteCollection,MoveCollection,FolderSync,FolderCreate,FolderDelete,FolderUpdate,MoveItems,GetItemEstimate,MeetingResponse,Search,Settings,Ping,ItemOperations,Provision,ResolveRecipients,ValidateCert
MS-ASProtocolVersions: 2.0,2.1,2.5,12.0,12.1,14.0,14.1
MS-Server-ActiveSync: 15.0
request-id: 6aa60282-2cb6-4d81-b106-c344018f1653
X-BEServer: EXCHANGE-MB2
X-CalculatedBETarget: EXCHANGE-mb2.MYDOMAIN.LOCAL
X-DiagInfo: EXCHANGE-MB2
X-FEServer: EXCHANGE-CAS1
X-MS-BackOffDuration: L/-230
It is a very small percentage of users who are having this issue. Just to test, I tried to provision my personal account which is also on Exchange 2013 on the affected users phones, and it works just fine. No issues. So I am convinced it is something wrong with their individual account.
Nothing shows up in get-mobiledevicestatistics for these users, I expected their previously provisioned devices to migrate over, but it appears this is not the case. And trying to provision new devices does not work. You can run the activesync setup on the phone, and it appears to work, but when you check messages, it gives the error.
Any ideas?