Current Patch Information Is Not Displayed In Scan Reports; Patches And Configuration Fixes; Vpm Patch Agent Installation Fails; A Patch Acquisition Was Started, But No Patches Are Seen - HP Xw460c - ProLiant - Blade Workstation User Manual

When scheduling vulnerability scans and patches, be sure the two processes do not overlap. Allow adequate
time for a vulnerability scan to complete before starting a patch. If a patch deployment runs during a
vulnerability scan, the scan results might be inaccurate or the target systems might reboot during the scan.

Current patch information is not displayed in scan reports

Scan definition updates are available a few days after the release of patches. You might have a patch in
your patch repository that does not appear in your scan results. You can apply the patch without a scan.
The VPM Patch Agent will not apply patches that are not appropriate. With the new patch reports, you can
also use the Validate VPM Patch Agent operation to determine where patches are needed. This operation
applies to patches only. The VPM Patch Agent does not report on non patch security vulnerabilities.

Patches and configuration fixes

VPM Patch Agent installation fails

The VPM Patch Agent is automatically deployed when systems are licensed to allow patches to be applied
to the systems. If a server type is identified as Unknown or Unmanaged with no identified operating system
in the HP SIM console, Vulnerability and Patch Management automatically attempts to deploy the VPM Patch
Agent for Windows systems. The VPM Patch Agent deployment fails on Linux systems, and event details
display an error.
To deploy the VPM Patch Agent to target systems, see the "Deploying the VPM Patch Agent" section. Be sure
that the Red Hat library, compat libstdc++, is installed on Red Hat target systems.
The VPM Patch Agent installation can also fail because the WBEM credentials are not configured properly
to allow Vulnerability and Patch Management to access target systems. For information about configuring
WBEM credentials, see the HP Insight Software Installation and Configuration Guide .

A patch acquisition was started, but no patches are seen

A patch acquisition can take quite a bit of time the first time it is run. It is not unusual for the acquisition to
take more than four hours, depending on how many operating systems are selected for download and the
speed of the Internet connection.
Progress of the acquisition can be monitored at:
<VPM_installation_folder>\Radia\IntegrationServer\logs\patch-acquire.log.
If the log file indicates that no patches are being acquired and there is a proxy server in the environment,
be sure you have properly configured Vulnerability and Patch Management to access the proxy server by
148 Troubleshooting