HP Systems Insight Manager - Manual (Page 180)

Therefore, you must provide case sensitive Sign-In credentials during discovery or while running
the Configure or Repair Agents task.
For example: Some Windows managed systems have the username as 'Administrator'. During
discovery the Sign-In credential username is provided as 'administrator', then, Discovery and few
other tasks will work perfectly because Windows does not consider credentials as case sensitive.
However, the Configure or Repair Agents task fails because OpenSSH considers 'Administrator'
and 'administrator' as different users.
To resolve this issue, you can complete one of the following:
•
Update the Sign-In credentials with proper case. (Recommended)
or
•
Do not use Sign-In credentials and provide credentials (with proper case) manually before
running the Configure or Repair Agents task.
-------------------------------------------------------------
When configuring agents from a Linux or HP-UX CMS on a Windows system, you may receive an
STDERR error. The content that is coming on the STDERR console in HP SIM, is captured from the
error stream of the process which is created during the configuration on the target system. The
contents of th standard error stream depends on the operating system of the CMS and the operating
system of the target system. The same content can be seen when you manually run the command
on the CMS for the target system.
If you see the error on the STDERR console in HP SIM, there is nothing wrong going on in the
background. HP SIM displays the content of both the output and error streams.
-------------------------------------------------------------
When you try to do any configuration from a Linux CMS to a Windows 2012 server, ensure the
CMS has a in-built SMB server 3.0. If the CMS has any prior version of SMB server installed, then
internal commands like put etc will fail. As a result, the CMS cannot copy the configuration files
to the windows 2012 server node. Therefore, the Configure or Repair Agents task will fail.
NOTE: Windows server 2012 uses SMB 3.0(or SMB3) on the file server. Windows Server 2012
Hyper-V only supports SMB 3.0 for remote file storage.
-------------------------------------------------------------
The Remote Registry service is not started by default on the workstations like windows7 and
Windows Vista. If this service is not started, then Configure or Repair Agents on these target systems
will fail.
To start the service, follow the steps below:
Procedure 48 Starting Remote Registry service
1. Enter services.msc in run. This displays the list of services.
2. Select the Remote Registry Service and start it and also change the startup type to Automatic.
-------------------------------------------------------------
Configure or Repair Agents cannot be used to install the WBEM Providers to Integrity Windows
systems.
You must manually install the WBEM provider by copying cp010621.exe (can be found in the
smartcomponents directory under the HP SIM install) to the target system and then running it.
-------------------------------------------------------------
HP-UX 11.31 does not ship with smbclient, therefore, any Configure or Repair Agents task from
an HP-UX 11.31 CMS to a Windows target fails until smbclient is installed on the CMS.
Solution: A back up smbclient is located under /opt/mx/bin/smbclient. Copy this to the
opt/samba/bin/smbclient
folder to execute the Configure or Repair Agents task.
-------------------------------------------------------------
How do I push an SSH key using mxagentconfig to a target system running Windows Vista?
Solution: HP recommends turning off the Windows Vista User Account Control.
180 Troubleshooting