VMware Cloud Community
wwstreet
Enthusiast
Enthusiast

Trying to add a PowerShell Host via the vRO 7 workflow

When I run this workflow I enter the server name, the FQDN in the host field and press next.

I leave the PowerShell remote host type as WinRM, the Transport protocol as HTTP and Authentication as Basic. Press next

I enter localadmin@localservername and then the password.  When I click submit I get this mess below.

I have tried Kerberos as well as other combinations of the username/password combo.  Any thoughts?

[2016-06-13 16:06:27.328] [E] Workfow execution stack:

***

item: 'Add a PowerShell host/item8', state: 'failed', business state: 'null', exception: 'Unauthorized Access. Authentication mechanism requested by the client may not be supported by the server. (Dynamic Script Module name : addPowerShellHost#12)'

workflow: 'Add a PowerShell host' (EF8180808080808080808080808080803D80808001270557368849c62c352aa82)

|  'attribute': name=errorCode type=string value=Unauthorized Access. Authentication mechanism requested by the client may not be supported by the server. (Dynamic Script Module name : addPowerShellHost#12)

|  'attribute': name=sslUrl type=string value=

|  'input': name=name type=string value=XXXXXXX

|  'input': name=type type=string value=WinRM

|  'input': name=transportProtocol type=string value=HTTP

|  'input': name=port type=string value=

|  'input': name=hostName type=string value=XXXXXXX

|  'input': name=username type=string value=admin@XXXXXXX

|  'input': name=password type=SecureString value=__NULL__

|  'input': name=sessionMode type=string value=Shared Session

|  'input': name=authentication type=string value=Basic

|  'input': name=acceptAllCertificates type=boolean value=false

|  'output': name=host type=PowerShell:PowerShellHost value=null

*** End of execution stack.

Reply
0 Kudos
4 Replies
john23
Commander
Commander

Just opened the script: Workflow is passing the sslUrl in below format sslUrl = "https://" + host + ((port) ? ":" + port : ":5986") + "/wsman/"; Can you try above combination in Url and  check /

Thanks -A Read my blogs: www.openwriteup.com
Reply
0 Kudos
tschoergez
Leadership
Leadership

Reply
0 Kudos
koushik_vmware
Enthusiast
Enthusiast

Please refer the below link. It was helped me a lot.

http://www.valcolabs.com/2015/09/30/adding-a-vro-powershell-host-kerberos-configuration/

Thanks,

Koushik

Reply
0 Kudos
SpasKaloferov
VMware Employee
VMware Employee

you problem is that you have specified BASIC Auth , but you are trying to use KERBERO Auth (username@domainname). Make up you mind , match them and try again. Either use BASIC with Username/Password or KERBEROS with doamin@username/Password. For Kerberos you may try this:

Using CredSSP with the vCO PowerShell Plugin (SKKB1002) | Spas Kaloferov's Blog

BR,

Spas Kaloferov
(www.kaloferov.com/blog)

Reply
0 Kudos