CMS doesn't recognize VCRM as configured

[Steven Laux]

I am having a problem when I try to deploy software/firmware through the Deploy menu on the CMS.

I have 12 VCRMs. One at each satellite office. When trying to deploy software/firmware, it asks to select a repository and shows a column that says "Trusted?". Half of my repositories say "NO" in this column. I have imported the CMS certificate on these servers and they show up as trusted in the "All Servers" view on the CMS. They are giving me the proper Software Status within the All Servers view. Also, I can browse to the SMH on these servers from the CMS without inputting my credentials, so it appears that the trust works.

When I was in the "Select a Repository" menu and saw some of the servers listed as untrusted, I clicked the "Configure" link, which took me to the "Trust by Certificate" configuration page on the VCRM. I went through the process of saving that configuration. They are still showing as untrusted VCRMs.

Any ideas? Anyone else see this before?
Thanks in advance.
Steve

[Rich Purvis · Accepted solution]

Hey Steve,
I went ahead and tried this out on my network. This is how I did it, it may not be the best way but it worked for me. I went through the same steps you described and saw the same behavior. I then went and deleted/removed the system with the VCRM from the HPSIM list. I then went and ran a manual discovery on the system with the VCRM, it was again added back into the database, this time it showed up as a trusted VCRM. Again, there may be a better way to do it but that is how I got it to show up as a trusted VCRM.

-Rich

[Steven Laux]

Thanks, Rich. Removing and rediscovering the VCRMs worked.

This appears to be some kind of bug. I'm glad you were able to reproduce the issue. The work around is not the most pleasnt but it works. Thanks again for your help.

Steve