HP Systems Insight Manager 5.0 HOTFIX50_001 for Microsoft Windows

[NJK-Work]

Just saw this on HPs site:

http://h18004.www1.hp.com/support/files/server/us/download/23910.html

Fixes

Updated to correct the following:
SIM trust with managed systems to prevent breaking or inability to establish even though it is properly configured.
Task Wizard to not delete newly created tasks selected as Run Now but that are also scheduled to run in the future.
Advanced Search for specific versions of iLO firmware.

If the currently running HP Systems Insight Manager is version 5.0, then applying this hotfix updates the functionality of HP Systems Insight Manager to Service Pack 2.

Nelson

[NJK-Work]

Well - the link DID work, but now appears to be broken.

Nelson

[Ed Welch_1]

Right now (11/19) it is at: http://h18005.www1.hp.com/support/files/server/us/download/23910.html
SoftPaq ID is SP31535, in case it moves again.

[Renato Richina]

A few questions about this patch:

When I understand the installation instructions corrects, the *.jar file has to be copied to the "patch" directory and the SIM service to be restarted. I assume the patch should then be installed automatically.

However is it "normal" that the version still shows C05.00.00.00 within SIM?

The second part of the installation instructions is not clear for me:

Empty the CIM_SoftwareIdentity table by executing the following SQL script command against the SIM5 database:

delete
from CIM_SoftwareIdentity

From where I have to run this commands?

[Joel Rubenstein · Accepted solution]

That is correct. When you copy the new .jar file to the patch directory the SIM version is not updated. The .jar file contains multiple .class files (you can open the .jar with winzip to look at them). When SIM starts up it will look in the patch directory and automatically replace the corresponding .class files with the patched versions.

If you are not experiencing the problem of missing entries in a collection of ILO FW versions you do not need to clear the database table. Otherwise it can be done using the SQL query analyzer tool that is a part of SQL 2000. If you do not have access to the query analyzer then it can also be done using the osql command line utility.

[NJK-Work]

This was just an observation posting, not really a question.