Install of Initial Proliant support pack fails

[sudesh_5]

Hi ,
I am running HP SIM 5.0 on win xp . The Installation of Initial proliant support pack fails .

Regards
Sudesh

[TechGuru]

Installation of Initial proliant support pack is supported on server edition's of windows only(win 2k, 2k3), In Windows XP you can only install SMH from proliant support pack (you can also install VCRM from Management CD in xp system).

[rcseattle]

I have the same issue.

Just tryed it today for the first time. Going from our SIM server (Win2k3) to a Windows 2000 Server node. Both servers are in the same domain yet everytime I get:

"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 supported. Either the username is unknown, or a bad password was provided."

I've tried domain admin credentials. Local Admin credentials on the destination box.

It simply does not work.

[rcseattle]

By searching I also found this:
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=975365

It looks like we're not the only ones with this issue and I see no good answer.

[Rob Buxton]

For the W2000 /W2003 Server, run the Setup.exe from within the PSP itself.

From the resulting GUI you can first configure the Agents if they're not already configured, e.g.Trust details etc.

Then you can use this utility to deploy the PSP.
Once done you can then use HPSIM to deploy later versions of the PSP via the VCA/VCRM mechanism.

[rcseattle]

Documentation of the "Initial ProLiant Support Pack Install" says this:

"The Initial ProLiant Support Pack Install process enables you to install a ProLiant Support Pack to a Windows system because you do not have any HP Insight Management Agents, especially HP Version Control Agent, installed. This process also configures the systems to use the trust certificate from the HP Systems Insight Manager and the setting to use the desired HP Version Control Repository Manager."

I am trying to run it from a Win2k3 server with a Insight Manager and a repository installed:

Operating system: Windows 2003
Version: Systems Insight Manager 5.0 - Windows
Build version: C.05.00.00.00

to a Windows 2000 server in the same domain.

I go thru "Deploy" "Deploy Drivers Firmware and Agents" "Initial ProLiant Support Pack Install"

I supply domain admin credentials and it still fails.

Same error as the other thread I referenced.

Running setup on well over 100 servers with limited downtime period won't work.

I'm working around it by creating scheduled tasks to use setupc. But that's still a pain.

The pretty interface just doesn't work.

[sudesh_5]

Hi ,

Has anyone tried monitoring the Proliant Server through SIM .

When SIM is used for monitoring Proliant server running Win server 2000/ win server 2003, do we get the same error .

Doc says , SIM can manage , Proliant , Integrity, and HP 9000 . I am wondering , how SIM manages the Integrity / HP 9000 . Be cause , for Proliant server , the installation of the proliant pack will install the management agent , but for the Integrity server/Hp 9000 , how the management agent gets installed ? . Doc doesnt talk about any support pack for integrity/HP 9000.

Looks like , more Insight is needed on System Insight Manager .


regards
Sudesh

[Rich Purvis]

In regards to the questions about managing Integrity and other systems - HPSIM does manage those systems. They have management agents or CIMOM providers that can be installed to provide the same type information that the Proliant Insight agents provide. The management software for those systems are not delivered in the PSP because the PSP is the Proliant Support Pack - those systems are not Proliants.

-Rich

[Rich Purvis]

As an FYI if you go to this link:

http://h18013.www1.hp.com/products/servers/management/hpsim/download.html

There are links to different HPSIM OS downloads. Pick the OS you want management for and it will take you to a page that as not only links for downloading HPSIM for that OS but the supporting management agents and WBEM providers. You don't have to download the HPSIM for that OS to get to the other management software. Perhaps that will help.

-Rich

[Rich Purvis]

R Caughie,
I see as your work around you are using setupc as a scheduled task. Are you using the same credentials for setupc that you used when you tried the Initial PSP Deploy? Because they should behave the same.

-Rich

[rcseattle]

Rich,

I scheduled the jobs using AT commands, but must have done something wrong. They failed.

I was actually using lower credentials with the AT jobs. created a svc account on the SIM server with rights to the share and used switches to pass userid and pass to connect to the share.

Since it failed we had to log into the servers and run the batch files manually. (Batch files with the setupc command line and switches.)

I assumed since the AT jobs run under "System" that that should have rights to update the software on the server. Not sure why the AT jobs failed, but I don't use AT much and probably just did something simple wrong.

Last week was dev, this week is production and will be hitting about 300 servers. I will probably have to log into every one of them this week and set up scheduled tasks thru the GUI using domain admin credentials. That should work. Just a pain to set up.

[Systems Administrator_4]

Could the issue be somehow related to the new security features of Windows 2003 SP1? I am trying to deploy to 2 servers with the same configuration and both fail.

My understanding is the ONLY thing needed by the remote box is LOCAL admin rights. If that is the case, something is very wrong with SIM 5.0.

I know in my circumstances, I can just use the setup.exe to load the PSP on these 2 servers, but that defeats the whole purpose of remote deploy. I'm glad I don't have hundreds of servers to deploy to...

Anyone from HP listening out there?

[Systems Administrator_4]

Shortly after I posted my comments yesterday, I was finally able to deploy the PSP to the 2 servers. I don't know exactly what happened, but I'm guessing a few changes and time were the culprits.

The main things I changed were the SNMP settings on both the SIM server and the clients. Make sure you have the right community strings set on both. I'm guessing it's the READ CREATE string that must be set properly.

Check the GLOBAL PROTOCOL SETTINGS on the SIM server to make sure the WRITE string matches the clients.

I installed as a Domain Admin and it ended up working.