Return to site

Skype For Business Certificate Error Clock Settings Mac

broken image


(This certificate must have a subject name or subject alternative name that identifies the user and must be issued by a Root CA that is trusted by servers running Skype for Business Server, be within the certificate's validity period, and not have been revoked.) To be authenticated, users only need to type in a personal identification number (PIN).

  • Your certificate first before proceeding ahead. Same for any non-domain machine, if you are facing such type of issue you first need to check if the certificate to the Office Online Server (OOS) is correctly installed in your machine or not. Or you need to make sure you do have correct certificate. To validate it, you can do it as of above methods.
  • Certificate creation and requirements for Skype for Business / Lync integrations. Pexip Infinity supports the use of Base64-encoded X.509 SSL/TLS certificates. Such certificates are used when integrating Pexip Infinity with Microsoft Skype for Business and Lync., either as part of an on-prem deployment or when deploying Pexip in a public DMZ for enabling direct federation with remote SfB/Lync.
  • They can't login to Skype For Business because of this error: 'There was a problem acquiring a personal certificate required to sign in. If the problem continues, please contact your support team.' They have Office 365 Business Premium license assigned to them which includes Skype For Business Plan 2.
Scenario
Skype for business certificate error

Skype For Business Certificate Error Clock Settings Mac Desktop

User cannot sign-in to Skype for Business via client and has error:

'Cannot sign in to Skype for Business because your computer clock is not set correctly. To check your computer clock settings, open Date and Time in the Control Panel.'
Solution
Per KB2581291 Microsoft suggests to make sure that the computer's clock and time zone settings are set correctly. And it's correct article except the fact that the registry key 'ClockSkew' is located under another registry path:

Skype For Business Configuration Settings


HKEY_CURRENT_USERSoftwareMicrosoftMSOIdentityCRL
instead of documented:

Skype For Business View Settings

HKEY_USERS.DEFAULTSoftwareMicrosoftMSOIdentityCRL

In my particular case users messed with time and had unchecked 'Daylight Saving Time' setting.

Setting Up Skype For Business


The Time Zone, the 'Daylight Saving Time' settings were corrected, time synchronization were completed, registry key 'ClockSkew' was deleted and Skype for Business client could sign-in.

Skype For Business Server Certificate Error

References




broken image