I was recently asked to look in to a Skype for Business 2015 infrastructure due to reported 2013 mobility client issues. The infrastructure consisted of a standard edition front end, edge server and KEMP load master reverse proxy. The issue was that mobility clients could not search for contacts and could not see certain status messages. All other features were working and users could chat/make calls.
Fresh deployment of Exchange 2013. As you try to connect to the management console https://localhost/ecp/ with a valid administrator account, it redirects to OWA and responds with “:-( Something Went Wrong, A problem occurred when trying to use your mailbox.”
This seems to be related to left over Exchange attributes in Active Directory. I tried everything from a multitude of TechNet articles including the following:
Installing a new Exchange 2013 deployment on an existing domain with questionable history. The existing domain had untold number of previous Exchange deployments with remnants scattered throughout Active Directory. After using ADSI edit to manually remove all instances of the old Exchange servers, running a schema prep runs in to an error about an existing Active Directory Connector. Microsoft suggests (TechNet) disabling the ADC service on the running computer, then uninstalling the service using the exchange server installation CD. In this situation of course the detected ADC was probably on a computer that was long ago trashed or removed.