7.41 HP Agents lose certificate and trust when SIM Repliactes Agent Settings

[Kevin Kelling]

Lately been noticing that our population of untrusted servers has been increasing. This could be easily fixed by updating the certificate which appears to have become corrupted.

Problem is that the corrupted certificate returns in a few days. After further review it seems that when our Replicate Agent Settings task runs, it works fine on all our servers -- except for those running Windows 2003 with version 7.41.00 agents.

For some reason, the agents running this specific version will have their certificate become corrupted when this task runs. Less than 5% of our servers are at version 7.41 and this appears to be the only population affected.

Don't recall seeing any advisories on this. Can anyone else confirm this behavior?

Thanks!

[Craig Boeker]

There is a problem with replicating trusted server certificates with System Management Homepage version 2.1.4

The specific problem is with copying over an existing trusted management server certificate. This fails, resulting in the existing trusted server cert being deleted and possibly other parts of the replicated settings not being changed. Because of the failure the SMH does not reload the certificates from disk. So the UI will show the server as being trusted but the certificate is no longer present on the disk and trusted operations from that server will fail.

An advisory is in the approval/release process but not yet available on HP.com.

The fix for this problem is in the pipeline for the next version of SMH slated for release in SmartStart 7.5

Unfortunately the only way to avoid the problem is not to run RAS tasks containing trusted server certificates against servers running SMH 2.1.4

[Kevin Kelling]

Excellent info! Thanks!

What I can do is modify the RAS task so that systems with SMH 2.1.4 are excluded.

The only problem with this is that any rules or collections that I build have to be re-created when the SIM (5.0 SP3) server is rebooted.

for some reason any rule that contains hardware/software version becomes "blanked-out" following a reboot.