I'm working on a Lotus Notes to Office 365 migration and have deployed two Exchange 2013 CU6 CAS/MBX servers, each in a different AD site. These servers will be used for SMTP relays and O365 management, there was no on-premises Exchange environment before these two servers were installed. SITE A contains one CAS/MBX server (SERVER A) and has a mailbox for the user with Org Mgmt rights. SITE B contains one CAS/MBX server (SERVER B) with no mailboxes currently. On both servers, the internal and external URLs are set to the same value (the internal FQDN of the server). These CAS servers are not internet-facing. There are no AD replication issues between sites.
So when the mail administrator logs in to SERVER A and logs intohttps://localhost/ecp with his account, he is able to see the EAC. No problems. However, if he goes to SERVER B and typeshttps://localhost/ecp, we see the address bar update to point to the FQDN for SERVER A, but then an error is thrown similar to the below (servernames changed to protect the innocent).
A problem occured while you were trying to user your mailbox.X-OWA-Error: Microsoft.Exchange.Data.Storage.UserHasNoMailboxException
X-OWA-Version: 15.0.955.28
X-FEServer: SERVER A
X-BEServer: SERVER A
I've never seen something like this. Has anyone else? Any assistance is appreciated. Don