could not connect securely to server %2 because the certificate presented by the server did not match the expected hostname ...

%1 could not connect securely to server %2 because the certificate presented by the server did not match the expected hostname (%2).

Resolution:
If you are using manual configuration with an IP address or a NetBIOS shortened server name, a fully-qualified server name will be required.  If you are using automatic configuration, the network administrator will need to make sure that the published server name in DNS is supported by the server certificate.

Context not supported: this conversation includes context which requires a Microsoft (!IDS_PRODUCTNAME_SHORT) plug-in. Please ... Conversations, you have %1!s! missed conversations. There are Exchange connectivity issues. Your conversation history cannot ... Could not automatically save your instant message conversation. To save manually, click Save As on the File menu of the conversation ... could not be added because your Contacts list contains the maximum number of groups or contacts.Delete one or more contacts ... could not connect securely to server %2 because the certificate presented by the server did not match the expected hostname ... could not connect securely to server %2 because the certificate presented by the server was invalid. The certificate was ... could not connect securely to server %2 because the certificate presented by the server was not trusted due to validation ... Could not connect to Microsoft Lync {0}, please ensure that this web page is in your list of trusted sites in Microsoft Internet ... couldn't be converted for presentation because Visual Basic for Applications (VBA) is not installed on this computer. Please ...