Windows Integrity Enterprise Edition Release Notes

Release Notes
Troubleshooting common issues
HP Integrity Servers with Microsoft® Windows® Server 2003, Enterprise Edition
37
3. HP Integrity Gigabit Ethernet Dual-Port NIC Driver
4. OpenSSH Services for HP Systems Insight Manager
5. HP WMI Utilization Provider
6. HP WMI Integrity Virtual Machines Provider
7. HP StorageWorks Fibre Channel Adapter Kit for the QLAxxxx STORPort
Driver for Windows Server 2003 on Itanium Based Systems
8. HP StorageWorks FC-:HBA Configuration Utilities by QLogic for Windows
Server 2003 Itanium Based Systems.
Workaround There is no workaround at this time.
all Integrity
servers
Version Control Repository Manager (VCRM) does not start after System Management
Homepage (SMH) reinstallation
Issue VCRM fails to start if SMH is uninstalled, the system rebooted, and then SMH is
reinstalled. This problem occurs only when the system is rebooted between the
SMH install and reinstall.
Workaround Reinstall VCRM after reinstalling SMH.
all Integrity
servers
Version Control Repository Manager (VCRM) does not upload the Japanese Support
Pack from Japanese OS
Issue VCRM uploads the English Support Pack instead of the Japanese Support Pack
when used on a Japanese OS.
Workaround Before uploading the Support Pack on a Japanese OS, change the browser's
language setting to “en” or “en-us”, upload the Japanese Support Pack, and then
switch the browser's language setting back to Japanese.
HPVM
Guest
Windows device messages shows a VGA adapter when “display hidden devices” is
enabled.
Issue Version Control displays the VGA driver installed version and latest version on
HPVM Guest, even though VGA is not supported.There is no VGA on HPVM
guests, however, the driver shows up in version control. The driver is loaded when
Windows incorrectly detects VGA and installs the driver. The foundation agent
passes the information to version control, and version control displays the driver
installed version, support pack version and latest version.
Workaround Ignore the message, there is no negative impact from the video driver. There is
presently no work around.
Virtual Machine Install
all Integrity
servers
After finishing the HPVM Windows install do not install EBSU.
Issue Since the EBSU install adds some firmware and EFI based hardware tools to the
install, it was recommended. Most of the EBSU installs do not benefit the HPVM
system at all, and will fail to install since they are not usable with the HPVM
system.
Workaround Install the SSM Components directly. This provides the agents and HPVM/VSE
providers important to HPVM users.
all Integrity
servers
Telnetd errors appear in the Windows MP Services syslog.