Alert: Alert generated by Send Queue % Used Threshold

Cause
As it turned out, this server ran many monitored objects, services and applications. As a matter of fact, too many. Normally the queue for a SCOM Agent is set to 15 megabytes (15360 KB).

Solution
The maximum queue size is set to 75 megabytes (76800 KB). Afterwards the Agent is restarted and all is well again. The maximum queue size is 256 megabytes (262144).
The register key you need to update is to be found here: HKLM\SYSTEM\CurrentControlSet\services\HealthService\Parameters\Management Groups\<MG NAME>\MaximumQueueSizeKb.

We need to increase the size of the following registry key:

 Then you need to reboot the server to activate the new MaximumQueueSizeKb value

Error message while opening the WSUS console after installing WSUS 3.0 SP2 .Cannot connect to 'WSUS-Jimmy' (WSUS) Server. The server may be using another port or different Secure Sockets Layer setting.

Symptom
===========

Error message while opening the WSUS console after installing WSUS 3.0 SP2 .Cannot connect to 'WSUS-Jimmy' (WSUS) Server. The server may be using another port or different Secure Sockets Layer setting.

Cause
======

IIS  not allowing any connections for the WSUS administration site.

Resolution
==========

Changed the setting for WSUS administration site to allow connections to it in IIS

WSUS 3.0 - The server may be using another port or different Secure Sockets Layer setting.

Problem
========

The server may be using another port or different Secure Sockets Layer setting.

Cause

=======

This issue can occur if the Enable-32bit mode is set to true for WSUS Application Pool.

Solution

==========
To resolve this issue, follow these steps:

1.) Open IIS Manager

2.) Expand Server Name -> Application Pools

3.) Select the WSUS Application Pool (WsusPool) and click Advanced Settings under the Actions pane.

4.) Change the value for Enable 32-Bit Applications to False.

5.) Run IISRESET /noforce