README - HP Systems Insight Manager 5.3 with Update 1
3. Add the DNS suffix for the CMS to the Exceptions list.
4. Click OK until all dialog boxes are closed.
• The company DNS servers could be having problems. HP recommends that you contact your company's
network support group.
-------------------------------------------------------------
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 HP SIM service is configured as the install user name,
instead of Local System, which specifies system environment. Running the service with the credentials of the
user that installed the application is necessary for the service to have the necessary credentials for database
access and other CMS settings.
If you want the logs to be in a different language (German or English), you have three options:
• Stop HP SIM service. Change the default locale of the user account specified in the Log On As property
of the HP SIM service (the user that performed the install) to the desired language, and restart the
service.
• Stop HP SIM service. Change the Log On As user for the HP SIM service to the local administrator
account, and be sure its locale is set to the desired language. Restart the service.
• If you do not want to change the default locale of either of the previous accounts to the desired language
for the logs, create a new administrator-level account with the desired default locale. Then uninstall HP
SIM and reinstall HP SIM specifying the new administrator-level account.
-------------------------------------------------------------
On a Windows NT 4.0 system running Internet Explorer 6 Service Pack 1, remotely browsing into a CMS
causes a DLL failure after being connected for hours. This issue occurs on a Windows CMS and on an HP-UX
CMS.
Collections
Use English text for naming collections. If you do not use English text, you might see named collections
generated by HP SIM. For example,
collection-<number>
Complex
You cannot delete a complex and all associated systems when you first select either the system or complex
alone and then try to delete. You must select all associated systems from the list for the deletion to work
correctly.
-------------------------------------------------------------
Discovered complex systems might display an inconsistency regarding the number of nPars within the complex.
When viewing the complex through the System Page or Report, the number of nPars represent the total
number of nPars that can potentially be in the complex, regardless of the state of the individual nPars.
Alternatively, when viewing nPars within a complex under a system collection, the number of nPars associated
with a complex is equal to what HP SIM has determined through a WBEM provider. Therefore, the number
of nPars shown in the system collection might be less than or equal to the number displayed in the System
Page or Report.
14 Known Issues and Workarounds