I don’t have any screenshots of the problem because I was too busy trying to resolve it, so will do my best to explain. It turns out that when performing the failover, Skype for Business leaves the CMS active on both Servers! However, this is not immediately apparent or clear and I wanted to detail my experience in identifying that this is the case and what I had to do to resolve this issue. At this point I would like to thank Chris Hayward ( for warning me of a potential issue during failover that screws up your CMS. Once I was happy with the configuration I wanted to perform a controlled failover from the primary to the backup pool including users and CMS to prove the failover process worked as expected. I successfully paired the two Skype for Business Standard Edition servers together, both the backup and replication services were happily synchronising data.Ī few prudent powershell commands to prove correct replication returned all values as expected. The deployment and migration of services, users and data from the legacy Lync installation went absolutely fine and without issues. Response Text: Domain is not hosted by this service.I have been setting up a Standard Edition pool pair for disaster recovery for a customer and wanted to share my experiences around failover. Error: Error Message: The endpoint was unable to register. Tell me more about this issue and how to resolve it Additional DetailsĬouldn't sign in. See details below for specific failure reasons. Specified remote connectivity test(s) to Microsoft Lync server failed.

Additional Details Test Steps Testing remote connectivity for user to the Microsoft Lync server. The certificate passed all validation requirements. Additional Details Testing the SSL certificate to make sure it's valid. Additional Details Testing TCP port 443 on host to ensure it's listening and open. Test Steps Attempting to resolve the host name in DNS. Testing remote connectivity for user to the Microsoft Lync server.

Skype for business login fails