VC Agent returing the incorrect username/password

[Gary Connolly_1]

Hi.

In HP SIM I've used the deploy-> drivers firmware etc to install a PSP (7.10a).After the installation (and it does work fine) the VC Agent on the server has reverted back to an incorrect Login account and password. I have checked the VCRM but I couldn't find anywhere to change this. I must have set it when configuring my VCRM. Any ideas ?

thanks,
Gary

[Rob Buxton · Accepted solution]

Go to the VCRM Page, Select Catalog and then the Configure a Component.
Select the Insight Manager Agents and then get the screen that has the details for the password, Trust etc.
Set these as appropriate, check that it will overwrite the settings.
Next time this is deployed the settings within the agent will be as expected.
You need to reconfigure them whenever a new softpaq or the agent component is brought into the repository.

[Gary Connolly_1]

Hi Rob,

I have tried this but it has not fixed my problem. After another deploy I went back into the VCA and it has the incorrect details. The details look like the http server details I entered when first configuring the vcrm through HP SIM. Does this help ?
First when I configure the login details I set the VCA to Administrator, after the deployment the login details are my domain_name\username.

I have also noticed that some of my servers have hung when I selected "reboot after installation" this has happend both for a PSP and a controller driver update I was deploying.

thanks

[Gary Connolly_1]

Sorry,

Thanks Rob, I configured the PSP but forgot to configure the VCA.

If you have any hints on the "NON-Reboot" of my servers I would apreciate it.

thanks again

[Rob Buxton]

Gary, You can select for the VCA and other items to Not overwrite settings. I typically do this except for the Agents. I then just control it from that.

I usually roll out the entire softpaq as the agents are not often released standalone so I usually need to schedule a reboot.
That plus the MS Patch updates usually require a fairly frequent reboot cycle.
The VCA itself always seems to require a reboot. Not too sure why.