VMware Cloud Community
MQVMW
Contributor
Contributor

AddPowerShellHost workflow hangs for remote machine with PSv4.0

Hi All,

vCO PowerShell plugin version : 1.0.1.204

Remote machine : Windows Server 2012 Standard ( By default comes with PS v3.0, due to requirement upgraded to PS v4.0 )

                            WinRM configured on this machine.

Remote machine with PS v3.0 AddPowerShellHost workflow completed successfully.

Remote machine with PS v4.0 AddPowerShellHost workflow hangs.

Any input will be helpfull.

Server.log :

2013-12-06 09:53:57.296-0600 [http-bio-10.0.4.81-8281-exec-1552] INFO  {} [Execution] Executing workflow 'Add a PowerShell host'

2013-12-06 09:53:57.312-0600 [org.springframework.jms.listener.DefaultMessageListenerContainer#0-1] INFO  {} [Execution] Invoking workflow handler.8a8084d142bf08570142c89d8b300497

2013-12-06 09:53:57.374-0600 [WorkflowExecutorPool-Thread-84] INFO  {username:Add a PowerShell host:EF8180808080808080808080808080803D80808001270557368849c62c352aa82:8a8084d142bf08570142c89d8b300497} [OverthereWinRMPowerShell] Connecting to cifs:WINRM_HTTP://username@domainname.com@machinename.domainname.com:5985

Regards,

MQ

9 Replies
igaydajiev
VMware Employee
VMware Employee

PowerShell 4.0 got released couple of months ago and the plugin currently does not support it.

MQVMW
Contributor
Contributor

Thanks igaydajiev for reply.

Will you pls provide me some VMware reference/links. It will be helpful.


Reply
0 Kudos
igaydajiev
VMware Employee
VMware Employee

Reply
0 Kudos
MQVMW
Contributor
Contributor

Hi

   Thanks for your reply. However I already have this information. I was more looking for a document or reference where it says that power shell 4.0 is not supported by the power shell plug-in. I would like to know when can we expect the support for power shell 4.0 in power shell plug-in.

The other thing I would like to know is about the root cause of the failure to add power shell host in version 4.0. When we try to add the power shell host with version 4.0 the call never completes. It just hangs there, no failure reported. If you could throw some light for this failure it would really help

Reply
0 Kudos
igaydajiev
VMware Employee
VMware Employee

PowerShell  plugin for vCener Orchestrator 1.0.3 is about to be released till the end of the week. This version of the plugin will support PowerShell 3.0.

Yet there are no concrete plans for adding support for PowerShell 4.0.

Regards, Ivo

Burke-
VMware Employee
VMware Employee

Since the PowerShell plug-in does not currently support version 4.0, a potential work-around would be to attempt using the Guest Operations workflows to run the PowerShell commands inside the Guest OS of the machine hosting these scripts... just a thought..

If my answer resolved or helped you, please mark it as Correct or Helpful to award points. Thank you! Visit http://www.vcoteam.info & http://blogs.vmware.com/orchestrator for vRealize Orchestrator tips and tutorials - @TechnicalValues on Twitter
Reply
0 Kudos
serverguy55
Contributor
Contributor

Unfortunately for us all our post provisioning workflows for both physical and virtual servers use the PowerShell plugin. re-writing using guest operations workflows will take a lot of effort plus it doesn't help us when we're forced to provision Windows on physical servers. I'm hoping VMware prioritizes adding PowerShell 4.0 functionality.

Reply
0 Kudos
d-fens
Enthusiast
Enthusiast

Have you tried the following: If you need to run a PowerShell 4.0 session: you could have vCO to connect to a ,,standard'' 3.0 session (by changing the version in the PSSessionConfiguration of it) and from there connect to a 4.0 session with a different session configuration. This some penalties in form of performance and some additional configuration but might do the trick until VMware decides to support 4.0. Regards, Ronald

Ronald Rink d-fens GmbH
Reply
0 Kudos
igaydajiev
VMware Employee
VMware Employee

Plugin update is availabe with added support for PowerShell  v4.0

VMware vCenter Orchestrator Plug-In for Microsoft Windows PowerShell Release Notes

Reply
0 Kudos