This article was developed to complement the use of the WsusClientDiagnostic tool.
Read this article all the way through as it has useful information about the results in the tool but also steps on how to troubleshoot/resolve issues the tool highlights.
OS Information
This section provides basic information about the system in question.
Windows Update Agent (WUA) Client Information
This section will provide information about the Windows update client.
WUA Registry Settings
This section will provide information on the Windows update policy registry key settings. These settings are best described in Microsoft’s documentation on the topic Configure Automatic Updates using Registry Editor.
This information may be used to help validate the configuration on the client machine against what is configured in Service Center.
Windows Server Update Services (WSUS) Connectivity
This section will provide results for basic connectivity tests to the Onsite Managers patch service, or your Service Center Patch service in the case of a Device Manager. DNS lookups are also performed which can be useful in identifying DNS resolution issues.
Group Policy Conflicts
This section will report any potential group policies applied to the device which may conflict with Patch Management through Barracuda RMM.
If any group policies are detected they should be reviewed and any Windows Update-specific settings contained within them should be set to “Not Configure” as documented in the latest version of the Domain Configuration Guide.
Dual Scan
Additionally, Dual Scan can be an issue with Windows 10 Kernel-based systems. Please see this Knowledge Base article on that behavior.
Windows Service Configurations
This section displays the status of the Windows Update (wuauserv) and Background Intelligent Transfer (bits) services.
Reboot Status
This section checks if there is a pending reboot for previous windows update operations.
BITS Queue
This section will check the Background Intelligent Transfer Service job queue which is used by windows update to download updates.
Update History
The console output will report the number of installed updates collected via the Windows Update API. The details of each individual updates are logged in the WsusClientDiagnostic.txt log file in the utilities folder when executed.
Check Updates
This section will perform a check for updates using the default source of updates on the system. If a policy is applied through Barracuda RMM, then the device will check for updates through an Onsite Manager or Barracuda RMM Update Service. The number of installed and needed updates will be reported, along with a number of warnings, if any, as well as the result code for the check for updates.
The details of each individual updates are logged in the WsusClientDiagnostic.txt log file in the utilities folder when executed.
Microsoft Update
This section will perform a check for updates using Microsoft Update. This can be used to verify that the Windows update agent does function and detect updates however, this cannot be used as a 1:1 comparison due to variations in update availability between Microsoft update and WSUS that Barracuda RMM depends on for patch metadata. The results may sometimes provide hints to review Products and Categories synchronized in Service Center, as well as verifying that patches that are expected to be installed, are in fact approved. The number of installed and needed updates will be reported, along with a number of warnings, if any, as well as the result code for the check for updates.
The details of each individual updates are logged in the WsusClientDiagnostic.txt log file in the utilities folder when executed.