Many security events have been identified by the proxy stack. In the past %1 seconds, %2 security events have been identified by the proxy stack. A large number of security events could indicate that the server is under attack. The last event was: %3 Cause: The server may be under attack, or there might be a configuration problem that is causing errors. Resolution: Launch the Lync Server 2010 Logging Tool. Select the "SIPStack" component, the "Errors" level and the TF_SECURITY flag. Review the events reported to the trace log using the "Analyze Log Files" feature of the logging tool.
Machine {0} from the topology you are publishing was not found in Active Directory and will result in errors during Enable-CsTopology ...
Maintenance task was executed successfully. This task ensures that the back-end performs well over time. It is executed once ...
Maintenance task was executed successfully. This task ensures that the registrar back-end performs well over time. It is ...
Make sure that you drain service "{1}" by executing "Stop-CsWindowsService -Name {1} -Graceful" when draining service "{0}". ...
Many security events have been identified by the proxy stack. In the past %1 seconds, %2 security events have been identified ...
Maximum difference between the OverallAvgNetworkMOS and the maximum possible OverallAvgNetworkMOS for the codec used. High ...
Maximum jitter in the arrival time between RTP packets. High jitter values can be caused by congestion or an overloaded media ...
Maximum RTP packet loss rate for video packets. High values indicate frozen or choppy video and can be caused by network ...
Maximum RTP packet loss rate. High loss values can be caused by congestion, exceeding available bandwidth, wireless congestion/interference, ...