README - HP Systems Insight Manager 5.3
-------------------------------------------------------------
On an HP-UX system, when an administrative rights user edits a task, changes the owner to an operator
rights user, and then views the task, the original owner is still shown as the owner. If you open another
browser and view the task, the correct owner is displayed. This error is sporadic.
-------------------------------------------------------------
To successfully execute the Initial ProLiant Support Pack Install task, reboot the system after Installing HP SIM.
Otherwise, you will receive an error, stating Installpsp.bat is not an internal or external
command operable program or batch file.
-------------------------------------------------------------
To successfully execute the Install OpenSSH task, reboot the system after installing HP SIM. Otherwise, you
will receive an error, stating Installssh.bat is not an internal or external command
operable program or batch file.
-------------------------------------------------------------
After setting up a trust relationship to a target system using the Configure link, the Trusted? column still
displays No. This error occurs in the Install Software and Firmware, Initial ProLiant Support Pack Install, and
Replicate Agent Settings tasks. This error also occurs on the Version Control Repository setting panel.
To resolve this issue, click the Last Update link above the table to update the selected row. The currently
selected row is updated for performance reasons only.
If the Last Update does does not refresh the trust status, start a new browser session, and the trust status is
updated.
-------------------------------------------------------------
The message, The task cannot be edited because the repository used when creating
the task is not found in HP SIM or has been deleted and rediscovered. You must
delete this task and recreate it using a different repository system, can appear
when editing a task for which the HP Version Control Repository system is no longer in the HP SIM database.
In this case, you must recreate the task using a different HP Version Control Repository system. This message
can also be displayed if the HP Version Control Repository system has been deleted and subsequently
rediscovered. In this case, sign out of HP SIM, and sign back in to eliminate the error.
-------------------------------------------------------------
When executing a task, the message Unknown OS appears. To correct this issue:
1. If the system that you are trying to execute a task against is a Windows system, verify that it was rebooted
after installation of SSH. A reboot is required to complete the installation.
2. Enable Desktop Management Interface (DMI), WBEM, or SNMP on the system so the type of operating
system can be determined, and then run data collection to update the HP SIM database.
3. Verify that the commands to determine the operating system are working.
On Windows: ver
On HP-UX and Linux: uname
-------------------------------------------------------------
If you cancel a running task, by clicking Stop or Delete, and immediately try to start another task of the
same type, the second task does not run until the previously canceled task fully completes the cancellation.
Systems in the cancelled task that are currently being processed are allowed to run to completion. For some
long-running tasks like data collection or software deployment, it can take some time to actually allow the
systems in progress to reach completion and finally cancel the task.
If, for example, a data collection runs for an unusually long time you might want to stop or delete the task,
and wait 5 to 10 minutes after the cancellation has completed before running another data collection task.
If there is more than one task, such as data collection, pending then cancel these tasks first before stopping
or deleting the active task. If the data collection task is allowed to run to full completion without canceling,
another data collection task cannot be run for at least 15 minutes or the task will fail because it is actually
skipped (this would be shown in the STDOUT of the task instance if this is the case).
-------------------------------------------------------------
Task 39