- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm getting ready to dive back into getting our vPro world working and we've discovered that we suffer from the Self-Signed Certificate Issue on 3.x systems that have been updated to 3.2.1 before being provisioned. I wonder if there are any 'new' ways of handling this issue short of using WS_MAN Translater and the VBScript fix?
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Sandy,
A new version of the firmware was released (3.2.2).
With this release, the Self Signed Certificate Issue was addressed.
I'm not sure which system you have, but here is the link to the HP release of 3.2.2:
http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&prodTypeId=12454&prodSeriesId=3459241&prodNameId=3459245&swEnvOID=2096&swLang=13&mode=2&taskId=135&swItem=vc-66385-1 http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&prodTypeId=12454&prodSeriesId=3459241&prodNameId=3459245&swEnvOID=2096&swLang=13&mode=2&taskId=135&swItem=vc-66385-1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks Josh. I was just at the HP driver / firmware page and noticed the same thing. You must be psychic! Thanks for the heads up.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page