Vsphere Orchestrator ( vco ) - problem to add a Powershell Host

Hi everyone,

I'm currently configuring a VSphere Orchestrator server and I have some trouble to add a new host via WinRM with the Add a PowerShell host template.

I followed this tutorial:

http://blogs.technet.com/b/meamcs/archive/2012/02/25/how-to-force-winrm-to-listen-interfaces-over-https.aspx

I can connect with Powershell from a second server with HTTPS but not with vco..

This is my configuration:

PS WSMan:\localhost\Client> winrm get winrm/config
Config    MaxEnvelopeSizekb = 500    MaxTimeoutms = 60000    MaxBatchItems = 32000    MaxProviderRequests = 4294967295    Client        NetworkDelayms = 5000        URLPrefix = wsman        AllowUnencrypted = true        Auth            Basic = true            Digest = true            Kerberos = true            Negotiate = true            Certificate = true            CredSSP = false        DefaultPorts            HTTP = 5985            HTTPS = 5986        TrustedHosts    Service        RootSDDL = O:NSG:BAD:P(A;;GA;;;BA)(A;;GR;;;IU)S:P(AU;FA;GA;;;WD)(AU;SA;GXGW;;;WD)        MaxConcurrentOperations = 4294967295        MaxConcurrentOperationsPerUser = 1500        EnumerationTimeoutms = 240000        MaxConnections = 300        MaxPacketRetrievalTimeSeconds = 120        AllowUnencrypted = true        Auth            Basic = true            Kerberos = true            Negotiate = true            Certificate = false            CredSSP = false            CbtHardeningLevel = Relaxed        DefaultPorts            HTTP = 5985            HTTPS = 5986        IPv4Filter = *        IPv6Filter = *        EnableCompatibilityHttpListener = false        EnableCompatibilityHttpsListener = false        CertificateThumbprint        AllowRemoteAccess = true    Winrs        AllowRemoteShellAccess = true        IdleTimeout = 7200000        MaxConcurrentUsers = 10        MaxShellRunTime = 2147483647        MaxProcessesPerShell = 25        MaxMemoryPerShellMB = 1024        MaxShellsPerUser = 30

PS WSMan:\localhost\Client> winrm enumerate winrm/config/listener
Listener    Address = *    Transport = HTTP    Port = 5985    Hostname    Enabled = true    URLPrefix = wsman    CertificateThumbprint    ListeningOn = 127.0.0.1, 169.254.152.175, 192.168.1.139, ::1, 2001:0:5ef5:79fb:2087:3306:fde2:7302, fe80::5efe:192.168.1.139%14, fe80::2087:3306:fde2:7302%15, fe80::c19d:d401:ff68:98af%13, fe80::c407:cc5e:43dc:6909%18
Listener    Address = *    Transport = HTTPS    Port = 5986    Hostname = host-vsphere.urbanvirtu.local    Enabled = true    URLPrefix = wsman    CertificateThumbprint = 4f00d909810f619876bf5712a22e0fb21382d628    ListeningOn = 127.0.0.1, 169.254.152.175, 192.168.1.139, ::1, 2001:0:5ef5:79fb:2087:3306:fde2:7302, fe80::5efe:192.168.1.139%14, fe80::2087:3306:fde2:7302%15, fe80::c19d:d401:ff68:98af%13, fe80::c407:cc5e:43dc:6909%18

If I try to connect from a second server via Kerberos with HTTPS it's working:

PS C:\Users\Administrator> winrm identify -r:https://host-vsphere.urbanvirtu.local:5986 -a:Kerberos -u:administrator -p:password
IdentifyResponse    ProtocolVersion = http://schemas.dmtf.org/wbem/wsman/1/wsman.xsd    ProductVendor = Microsoft Corporation    ProductVersion = OS: 6.3.9600 SP: 0.0 Stack: 3.0    SecurityProfiles        SecurityProfileName = http://schemas.dmtf.org/wbem/wsman/1/wsman/secprofile/http/basic, http://schemas.dmtf.org/
wbem/wsman/1/wsman/secprofile/https/basic, http://schemas.dmtf.org/wbem/wsman/1/wsman/secprofile/http/spnego-kerberos, h
ttp://schemas.dmtf.org/wbem/wsman/1/wsman/secprofile/https/spnego-kerberos

But with vco I have:

Name: test

Host/IP: host-vsphere.urbanvirtu.local

Port:5986

PowerShell remote type: WinRM

Transport protocol: HTTPS

Authentication: Kerberos

Session Mode: Shared Session

User name: administrator

Password: password

Does someone had this problem before? What did i do wrongly?

Thank you in advance for your help.

Best regards,

Jean