HP Virtual Server Environment Management for Integrity Version 4.0 Release Notes

• The vseassist command checks that use the Win32 API are not logging API and exit code
details to the logfile.
The status (PASS, FAIL, or WARN) of these checks is still logged. And if the check fails,
vseassist logs the Issue and Resolution messages for the failure. However, vseassist
does not log the details of the APIs that were called and their results.
• When running vseassist Managed Node Configuration checks for a 64-bit Windows
managed system, the following message will be displayed in stderr:
'chcp' is not recognized as an internal or external command, operable program or batch file.
This is an issue with the remote command execution facility (DTF) of SIM, and the message
can be ignored.
VSE Agent Software Installation
Minor Issues
• When installing agents to a Windows managed system, the WMI Mapper item is checked
by default on the software selection screen. This is correct for Integrity Windows managed
systems, but not for Proliant Windows managed systems. If you leave the WMI Mapper item
checked for a Proliant managed system, an attempt will be made to install it, but the attempt
will fail (which is correct).
Workaround To avoid the unnecessary install attempt, uncheck the WMI Mapper item
when installing to a Proliant Windows managed system.
• If an agent fails to install to a managed system, the HP SIM task results show a status of
“Complete” instead of “Failed”. You must review the stdout and stderr of the HP SIM
tasks to verify whether an agent was successfully installed or not. This applies to both the
HP-UX and Windows CMS.
• For this release, there is no reinstall option in the “Install Integrity Linux VSE Agents” tool.
If you need to reinstall an agent on a Linux managed system, you must remove the agent
manually from the managed system and then install it through the “Install Integrity Linux
VSE Agents” tool.
• If you log into a CMS as a non-Administrator/non-root user and install agents, you will see
task results for the main install task, but not the install subtask results. In order to see the
install sub-task results, you will have to log into the CMS as Administrator/root.
• If you select a group of systems that are running different operating systems and you try to
install agents to them, the install task results are confusing. The agents will only be installed
on systems with the correct OS, but the task results are missing the information that points
you to the install subtask results.
• If you try to install the gWLM agent and JRE 1.5 at the same time to an HP-UX managed
system, and the JRE 1.5 has not previously been installed, then the gWLM agent install will
fail. Once the JRE 1.5 has been successfully installed to the managed system, then you can
install the gWLM agent as well.
• When installing VSE agents to a 64-bit Windows managed system, the following message
will be displayed in the stderr of the install sub-task:
'chcp' is not recognized as an internal or external command, operable program or batch file.
This is an issue with the remote command execution facility (DTF) of SIM, and the message
can be ignored.
Utilization Provider
Minor Issues
• Utilization Provider 1.7 will always report 1 thread on multi-thread Integrity systems running
Windows 2003.
VSE Agent Software Installation 55