Enthusiast
Enthusiast

Can't Import Certificate running Add Powershell Host Workflow

Running VRO 7.2.

I get this error when running Add Powershell Host Workflow:

[I] Manage SSL certificate called for URL->https://hostname:5986/wsman/

I don't understand why because I can punch that url into my browser and view the certificate under developer settings.

Everything is setup on the powershell host for winrm, the cert is even valid. I just don't understand why this is happening.

2017-06-23 16:19:45.583+0000 [WorkflowExecutorPool-Thread-1] DEBUG {:Add a PowerShell host:EF8180808080808080808080808080803D80808001270557368849c62c352aa82:token=ff8080815cd5b977015cd5c0739a0009} [WinRmPowerShellClient] handleStream STDERR buffer broker_serialize : The term "broker_serialize" is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. At line:1 char:1 + broker_serialize "$host" + ~~~~~~~~~~~~~~~~ + CategoryInfo : ObjectNotFound: (broker_serialize:String) [], Co mmandNotFoundException + FullyQualifiedErrorId : CommandNotFoundException

So is this something I'm doing wrong? It doesn't seem like it. Did Microsoft push something in a patch? If so, please update your powershell plugin!

0 Kudos
2 Replies
VMware Employee
VMware Employee

Hi,

Is this PowerShell version 5.1? We are aware of the incompatibility issue of current vRO PowerShell plug-in with version 5.1 of PowerShell, and we are working on a fix. Hopefully, an updated plug-in build will be released soon.

BTW, we have some customers reporting that this issue is not reproducible with the latest Windows versions (Windows 10/Windows Server 2016); only Windows 8/Windows Server 2012 and older versions are affected.

0 Kudos
VMware Employee
VMware Employee

This error  is caused when trying to add PS host running PowerShell 5.1. (on Windows Server 2012 R2)

We have just published technical preview version of the plugin that should resolve the issue hereTechnical preview version of VMware vCenter Powershell Plug-in 1.0.x

0 Kudos