HP Xw460c HP Insight Control Environment User Guide - Page 150

Other tools report that a Windows system is patched

Get HP Xw460c - ProLiant - Blade Workstation PDF manuals and user guides View all HP Xw460c manuals
Add to My Manuals
Save this manual to your list of manuals

Page 150 highlights

Other tools report that a Windows system is patched, but Vulnerability and Patch Management reports patches needed Many other tools read the registry to determine if a patch is installed. In many cases, when a patch installation fails, the registry is updated while the files remain unchanged. Vulnerability and Patch Management verifies that both the files and registry keys have been updated. Patch source for vendor patches is Microsoft or Red Hat To determine patch applicability, Vulnerability and Patch Management might enhance patch detection criteria to be more precise than vendor information. These patches appear with an asterisk in the Patch Source column. Multiple events listed in HP SIM for patch deployments Patch deployments create multiple events in HP SIM. There is a start event, a completion event, and a patch current status event. The patch current status event evaluates the status of the patches after the reboot has been completed. STAT Scanner update error listed in the HP SIM event log If STAT Scanner cannot access certain necessary files during a patch acquisition scanner update, a 3010 error appears in the HP SIM event log. The file update will be completed the next time a reboot is performed. Radia internal error listed in the HP SIM event log A generic Radia internal error appears in the HP SIM event log if the patch repository is viewed before a patch acquisition had been performed. "Abuse of Service" error occurs when attempting to acquire Red Hat patches The Red Hat network might be disabled if the network determines that patches have been acquired too frequently. To resolve this issue, delete the registered system from the Red Hat network web interface at https://rhn.redhat.com. Recreate the Red Hat credentials on the Red Hat server, and then copy to the VPM server. Validate Installed Patches event does not complete Certain VPM events cannot complete successfully until after a system has been scanned and patched at least one time. Be sure a system has been scanned and patched before attempting to validate installed patches. HP SIM integration The HP SIM tool menus might not appear after a VPM installation for any of the following reasons: • The HP SIM user does not have appropriate privileges to access the menus. If a new HP SIM user cannot view the VPM menus, be sure that the user is authorized for All Tools or VPM Tools in Options→Security→Users and Authentication. • A successful installation of Vulnerability and Patch Management requires the user to have CMS administrative privileges because changes are made to the HP SIM core and the tool menus. • When installing Vulnerability and Patch Management, you must use the credentials previously used when installing HP SIM. Failure to do so results in an incorrect installation. Also, the user name will not have appropriate privileges. Be sure the CMS user has privileges (toolbox and authorizations) to use Vulnerability and Patch Management. If the authorization is not correct, the menus do not appear. To correct this issue, uninstall Vulnerability and Patch Management and reinstall using the correct credentials. Be sure that the CMS user that will be using Vulnerability and Patch Management has appropriate privileges. Privileges can include having authorization for a toolbox containing the Vulnerability and Patch Management tools. • The Vulnerability and Patch Management installation failed. Installation errors appear during installation and in the log files. 150 Troubleshooting

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
Other tools report that a Windows system is patched, but Vulnerability and Patch Management
reports patches needed
Many other tools read the registry to determine if a patch is installed. In many cases, when a patch installation
fails, the registry is updated while the files remain unchanged. Vulnerability and Patch Management verifies
that both the files and registry keys have been updated.
Patch source for vendor patches is Microsoft or Red Hat
To determine patch applicability, Vulnerability and Patch Management might enhance patch detection criteria
to be more precise than vendor information. These patches appear with an asterisk in the Patch Source
column.
Multiple events listed in HP SIM for patch deployments
Patch deployments create multiple events in HP SIM. There is a start event, a completion event, and a patch
current status event. The patch current status event evaluates the status of the patches after the reboot has
been completed.
STAT Scanner update error listed in the HP SIM event log
If STAT Scanner cannot access certain necessary files during a patch acquisition scanner update, a 3010
error appears in the HP SIM event log. The file update will be completed the next time a reboot is performed.
Radia internal error listed in the HP SIM event log
A generic Radia internal error appears in the HP SIM event log if the patch repository is viewed before a
patch acquisition had been performed.
“Abuse of Service” error occurs when attempting to acquire Red Hat patches
The Red Hat network might be disabled if the network determines that patches have been acquired too
frequently. To resolve this issue, delete the registered system from the Red Hat network web interface at
ht
tps://r
hn
.r
edhat
.com
. Recreate the Red Hat credentials on the Red Hat server, and then copy to the VPM
server.
Validate Installed Patches event does not complete
Certain VPM events cannot complete successfully until after a system has been scanned and patched at least
one time. Be sure a system has been scanned and patched before attempting to validate installed patches.
HP SIM integration
The HP SIM tool menus might not appear after a VPM installation for any of the following reasons:
•
The HP SIM user does not have appropriate privileges to access the menus. If a new HP SIM user cannot
view the VPM menus, be sure that the user is authorized for All Tools or VPM Tools in
Options
→
Security
→
Users and Authentication
.
•
A successful installation of Vulnerability and Patch Management requires the user to have CMS
administrative privileges because changes are made to the HP SIM core and the tool menus.
•
When installing Vulnerability and Patch Management, you must use the credentials previously used
when installing HP SIM. Failure to do so results in an incorrect installation. Also, the user name will not
have appropriate privileges. Be sure the CMS user has privileges (toolbox and authorizations) to use
Vulnerability and Patch Management. If the authorization is not correct, the menus do not appear. To
correct this issue, uninstall Vulnerability and Patch Management and reinstall using the correct credentials.
Be sure that the CMS user that will be using Vulnerability and Patch Management has appropriate
privileges. Privileges can include having authorization for a toolbox containing the Vulnerability and
Patch Management tools.
•
The Vulnerability and Patch Management installation failed. Installation errors appear during installation
and in the log files.
150
Troubleshooting