HP SIM 4.2 doesn't work using other than local Administrator

[Joshua Warcop]

I give up.
I have been totally unsucessfull in installing HP SIM 4.2 with a domain account not called Administrator. OpenSSH fails somewhere along the way.
At this point I'm going to have to go to the customer and tell them that this piece of software will not comply with the security policies already set forth.
If someone has been able to make this work. Let me know, I want to know how you did it.

[k_kovacs]

I ran into the same situation as you did. After calling the HP Insight Manager support team, I found out that the SSH component as well as the Proliant Support Pack installation will not work unless the software is installed with the local computer administrator account. (as well as other components)
After the installation, you can add a domain administrator (of any name) account to the SIM console.
Hope this helps.

[Claas Kruhoefer]

what you could do, is to add the domain account you want to use for the installation to the servers`local administrators group, this fixed the installation issues on my side.

[Joel Rubenstein]

When you say OpenSSH fails somewhere along the way exactly what do you mean?

SIM and OpenSSH can be successfully installed using a domain account that is not named administrator. However the OpenSSH component will require some post installation tweaking to complete it's configuration.

[Joshua Warcop]

Well - it seems the difference is between the Typical and Custom installation routines. During a custom installation I'm asked to supply a username and password for OpenSSH installation. During a typical installation, OpenSSH installs using the logged on account. I was using the Custom installation all along to install all components. Believe it or not, if I go back and use the Typical installation, everything installs fine with a domain administrator account other than "Administrator". I however cannot use any of the default tools within SIM because it tries to connect via the Administrator account. Any ideas on how to modify the default tools for 4.2? The OpenSSH PDF document does not apply to 4.2.

[Joel Rubenstein · Accepted solution]

Yes, the openssh white paper has been updated for 4.2 and a copy is available on the 7.2 management CD which is available for download as an ISO image. It has not been posted to the web yet so I will attach a copy to this thread

[Joshua Warcop]

Excellent! I've burned the Management CD 7.2, but didn't realize the white paper was updated on this. Thanks.

[Joshua Warcop]

Yes, the command line to modify the XML files has been updated in is document.

mxtool â m â f toolname.xml â