Issue deploying Proliant Support pack

[Vincent Roodenburg]

When I want to deploy a Proliant Support Pack to a newly discovered server I configure a task to perform this action. When I've submitted the task, the target system I've configured seems to disappear and the CMS point somehow automatically to the CMS server itself, and fails to deploy the support pack for the original system I've pointed to.
How can this be avoided ?

[David Claypool]

Is this "Initial ProLiant Support Pack Install" ? If so, the assumption is that there is nothing at the other end except for an operating system, so there is nothing to receive a task from HP SIM except the OS.

The "Initial PSP Install" 'shells out' locally through SSH, copies a PSP from the repository to a temporary directory and invokes the command line utility to remotely install:

setupc /t:TARGET /user:USERNAME /passwd:PASSWORD BPxxxxxx.xml

[Vincent Roodenburg]

Yes, it's the initial install of the PSP. I don't quite understand what you exactly mean in your reply to my question.

Do I have to install the PSP locally on the server to workaround this issue ?

[Mike Strako]

No, the PSP has to be in your version conrol repositoy manager directory on the CMS server Ex: c:\repository (if that's where you placed the repository.)

Mike.