Clock skew between servers is causing cryptographic verification failures. In the past %1 minutes, the server received %2 requests that could not be verified because there is a significant clock skew between the originating server and the local server. The last affected request was from server [%3]. Cause: Cryptographic verification of certain requests is failing because the time set on the originating server differs from that of the local server by more than one hour. Resolution: Ensure that the computer clock of the local server is properly synchronized to a public time source.
Click Update to update ProductName from your computer. Click Back to review or change any of your installation settings. ...
Client certificate authentication (UseCertificateForClientToProxyAuth) has been disabled. Certain soft phones and scenarios ...
Client connection was disconnected by Web Conferencing Server Over the past %1 minutes Lync Server has disconnected client(s) ...
Client connection was disconnected due to throttling Over the past %1 minutes Lync Server has disconnected client(s) %2 times ...
Clock skew between servers is causing cryptographic verification failures. In the past %1 minutes, the server received %2 ...
Close these applications and click Retry to continue the installation. Selecting Ignore will result in a reboot at the end ...
Cluster {0} and its associated store roles does not have enough fault domain. The total number of machines in this cluster ...
Cluster {0} and its associated store roles does not have enough upgrade domain. The total number of machines in this cluster ...
Cmdlet cannot read from a path because it is running remotely. You can provide input by using byte stream. For example: Get-Content ...