PowerCli 11.2.0 and Microsoft System Center Orchestrator CU 5 problem


We have some workflows work on  Microsoft System Center Orchestrator CU 5. We face some trouble  when we upgrade Vitrual Center to 6.7 U1 While we try to access from powershell to Virtual Center there is no problem to log in but when we try to log in from orchestrator workflow with same code; we cant log in to vitrual center. We face above the error message:

The term 'Connect-VIServer' 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.

Also we relized that issue related to ssl and tls usage when we add tls registery key into the registry; Wmware integration pack started to work but some workflows still does not work which are use powershell scipts.


0 Kudos
1 Reply

In a regular PowerShell session, and provided you are using PS v4 or above, the module autload feature and the content of $env:PSMOdulePath variable, will make sure that the PowerCLI cmdlets are found.

I have no experience with that Orchestrator, but can you check what the content of $env:PSModulePath is when you run a script through that Orchestrator?

You might also try loading the PowerCLI modules explicitly at the start of a script.

Import-Module -Name VMware*

Blog: lucd.info  Twitter: @LucD22  Co-author PowerCLI Reference

0 Kudos