Systems Insight Manager 6.1 Release Notes

2 Important notes
SQL Server vulnerability
A vulnerability in Microsoft SQL Server could allow remote code execution. To fix this defect, you must install
the patch provided at: http://www.microsoft.com/technet/security/Bulletin/MS09-004.mspx. Download
the patch corresponding to you version of Microsoft SQL Server and install on the database server.
Data Collection
After discovering MSA2000 systems, Data Collection might fail resulting in minimal information appearing
on the System page and only Discovery/Identification data appearing in Data Collection report. To resolve
this issue, run Data Collection again.
Database credentials
During Systems Insight Manager installation, the database credentials must have SQL administrator access
with dbowner rights. After installation, these rights can be reduced.
ESXi Hosts
If an ESXi 4.x host is managed by HP Virtual Connect 4.x in a lockdown mode, then these hosts cannot be
monitored and managed by Insight Control components by providing the root credentials.
A user with name <remmgr> needs to be created on each of the ESXi 4.x hosts that need to be managed
by vCenter 4.x in lockdown enabled mode. The username <remmgr> should have root equivalent privileges.
This user credentials (remmgr and its password) should be used as to discover and identify the host in Systems
Insight Manager.
Data migration
The Japanese, Korean, Simplified Chinese, and Traditional Chinese HP Systems Insight Manager Installation
and Configuration Guides include incorrect information for Data Migration.
The CLI command for exporting data from a CMS must be:
mxexport [–f<filename.zip>] [-p password]
The CLI command for importing data from a CMS must be:
mximport [–f<filename.zip>] [-p password]
Scenarios not supported by Data Migration
The target system should not be one of the managed systems of the source CMS, and instead must be a new
system. Deleting the target system from the source CMS will not work if the target system was ever licensed
for any product. Licensing what will be the target CMS on the source CMS (even if it is then deleted before
running DMT) might allow for multiple licenses for the same product.
Central Management Server
Use careful planning if you want to deploy new drivers, firmware agents, or other software to the local CMS
because you might receive unexpected results, such as a mandatory reboot of the CMS.
Installing the CMS on Windows uses the user desktop locale to determine the CMS locale. For example, if
you install the CMS on a German Windows system and the user desktop locale happens to be English, then
the CMS installed becomes an English CMS.
The language of mxlog.txt (a log file) currently depends on the CMS locale. If the installer user desktop
locale is German, mxlog.txt is logged in German, even though the CMS is installed on an English Windows
system and the browser locale is also English.
This happens because the Log On As property of the Systems Insight Manager service is configured as the
install user name, instead of Local System, which specifies system environment. Running the service with the
SQL Server vulnerability 9