Initial Support Pack Install - MxFailedAuthentication

[Pat Wilson]

Whenever I try to Deploy->Initial Proliant Support Pack Install, the job fails with the following STDERR:

EXCEPTION CLASS: com.hp.mx.exceptions.MxFailedAuthenticationException
EXCEPTION: Authentication failed.

I am logged in to the CMS with the install account(which has domain admin privileges). I supply the same account name, and password during the task setup. My destination server (receiving the support pack - version 6.30) is a Proliant 2500 with Windows NT4 SP6a, which was setup using Smart Start 5.00, and therefore does not have the VC agent, and I can't configure the client to trust by certificate. (Since I am prompted for a domain account, I don't think it is a certificate problem anyway - right?) If the VC Agent was present, then I could just use the Deploy->Install Software and Firmware.

I noticed an older post dealing with this same error, but the poster indicated that using the install account worked for him. Am I missing something? I know I could just manually install/update the agents, but with a distributed network, this is not an attractive solution.

Thanks for any help,
Pat Wilson

[David Claypool · Accepted solution]

The interface that hpSIM uses to call a command line on its own server is through OpenSSH. The error refers to the application not being able to validate against SSH, before the command line with the credentials you supplied is even invoked.

Have you followed the instructions in the readme and gone through the extra steps to configure OpenSSH?

[Pat Wilson]

Yes I had done this, and it still did not work until I read another post from today to add the group info as per your answer to Adam Nickells:
mkgroup -d >> "c:\program files\openssh\etc\group"

I was just coming back to the forum to inform everyone that my problem was resolved.

Thanks for the assistance !!

By the way, maybe a better path to use for the output destination for the mkpasswd command would be: >> "..\etc\passwd" , and for the mkgroup command would be: >> "..\etc\group" - assuming the commands are run directly from the bin directory. There seem to a few posts about a file named 'program' showing up in the C:\ directory. Tha advantage to the paths specified here is they will work with or without the quote marks.

:)