BlueBear and the windows certificate issue
Well I finally overcame the Windows certificate issue that occurs with Adobe Air and BlueBear Kodiak. I thought I should reshare this seeing as everyone wants to have a play with this new ESX management tool.
Step 1
Ensure your ESX server has a valid hostname on it’s certificate by connecting to it through a web browser and viewing the certificate. Certificates are usually not a problem with ESX 3.0 or ESX 3.5. ESX 3.5i on the other hand is a completely different story. See my blog post on how to sort this problem out Regenerating SSL Certificates in ESX 3.5i
Step 2
Follow Bluebear’s updated instructions on how to install the certifcate and workaround the trust issue. http://www.bluebear.org/wiki/display/pub/Windows+trust+work-around
Step 3
When logging on to Bluebear Kodiak, don’t make the same mistake I did. Log on with the FQDN name of the ESX host, I was using the shortname which works fine for most things but obviously does not match the certificate that’s been installed. Once you’ve done all that you should have no issues using this great program on a windows machine.
