Making progress, but OpenSSH still won't work.

[Jason Balinski]

Nope. I have a second account, call it admin2, that is set up and works fine with mxagentconfig. However as soon as I disable the account that's actually named administrator, I can no longer run scripts or initial deployment of PSPs from the CMS.

If anyone has an idea on this I'd certainly appreciate it.

Thanks.

[Joel Rubenstein]

The latest version of the white paper "Secure Shell (SSH) in HP Systems Insight Manager" which is avalable at

http://www.hp.com/go/hpsim --> Information Library --> White Papers

describes the procedure to modify the tool definitions to run using an account other than "administrator"

[Jason Balinski]

Joel = Lifesaver. :)

Will the workaround on page 11 work for the initial support pack install?

Thanks!

[Joel Rubenstein]

Yes, InstallPSP is defined in the proliant-msa-tools.xml file which should be modified in step 2e. on page 11

[Jason Balinski]

Hopefully this is the last question. On page 7 of that document it states that if no user is specified, the tool will run as whoever is logged in to the CMS. I have servers accross three domains that I'd like to manage from one CMS, and creating identical log in id's on each would be impossible. I could however create the id's necessary on the CMS and then have a matching one on each other box.

So what I guess I'm asking is can I completely delete the entry for ? Will SIM then default to the user that logged into the console?

[Joel Rubenstein]

If you were to delete the then yes the command would attempt to run as the logged on user. However this would require that OpenSSH be configured for every SIM user and I don't think that is what you want to do. The InstallPSP task uses openSSH to login to the CMS to initiate the installation process. It does not login to any of the remote servers using openSSH during this process.