SCOM 2012 exception error when trying to run Lync 2013 synthetic transactions

Error: An exception occurred during discovery script, Exception: Could not connect to SQL server. Discovery did not succeed. Monitoring may fail if discovery data's initial state was not available. Please check alert context for details.

To resolve ensure your synthetic transaction watcher node is a member of the RTCUniversalReadOnlyAdmins group. Then try fully restarting SCOM and the synthetic node. This typically will fix the issue.

Lync constantly prompts users for username and password

Lync constantly prompts users for username and password even though they check the box  to save password.

I typically see this issue when a customer’s SMTP address is different than their SIP address and there is no domain for the SMTP address. This can occur because Lync expects NTLM to be the provided authentication. You can force IIS to use NTLM, which should resolve the authentication prompts.