Initial ProLiant Support Pack Install Problem

[Victor Caraballo_1]

I receive the following error message when trying to deploy an Initial PSP to a clean Windows 2003 Server in standalone mode (not a domain member). It is a clean ProLiant ML350, with absolutely no HP management software istalled.

---------------------------------------------

Initializing...

Unable to connect to the target computer. All available connection methods were
attempted with no success.

A possible reason is that the operating system of the target computer is not sup
ported. An unknown error occurred that prevented connection to the target compu
ter.

Unknown Initialization Error!
---------------------------------------------
My CMS is also Windows 2003, running all the Management Sofware and tools. It is also standalone.

I am using the remote Windows Administrator username and password to attempt to install the PSP. Am I missing something?

[David Claypool]

The good news is that you are already past the problem that most users run into which is OpenSSH configuration on the HP SIM server. It's working and firing off the task to the command line, so you're in good shape.

The "Initial PSP Install" is a fancy way to use the command-line deployment utility to connect with a remote server. On the HP SIM server open a command prompt and navigate to the directory where the repository is located. Issue the command

setupc /use-latest /t:TARGETCOMPUTERNAME /user:DOMAIN\USERNAME /passwd:PASSWORD

...and see what happens. If you receive the same error message, repeat the command with the switch /override-existing-connection. It may be that a connection has been made previously using a different user context which is a Windows no-no. For example, connecting to the same system using different user contexts will give an error in Windows, such as if you try:

net use j: \\SERVERNAME\SHARENAME /user:DOMAIN\USER1

and then:

net use j: \\SERVERNAME\SHARENAME /user:DOMAIN\USER2

Windows will complain with "Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed. Disconnect all
previous connections to the server or shared resource and try again."

[Victor Caraballo_1]

It was a password syntax issue. I did not realize that special characters or some special characters (in my case, the ^ character) are not supported in the password when using a command-line tool. After changing it to a password without any special characters, it worked.

[Victor Caraballo_1]

You cannot use some (the ^ character) or any special characters in the password when using the Remote Deployment Console.