I’m a little late to the game, but finally got around to installing PowerCLI 5.0.1. Upon connecting to my lab vCenter, I learned of the behavior change that will appear in future releases of PowerCLI. In short, you won’t be able to connect.
By default, it’s unset: 
To change that, set the Invalid Certificate Action to Ignore: 
You simply type this:
|
1 |
set-PowerCLIConfiguration -invalidCertificateAction "ignore" -confirm:$false |
It could potentially break all your scripts if you upgrade to whatever’s after 5.0.1.
Or better yet, how about they FIX VCENTER so that you don’t need a PHd to replace the default certificates with ones that actually match up to your infrastructure.
I agree! At VMworld 2012, the showed a tool that was in Alpha which would change certs on their products. However, that was the first & last time I heard anything about it.