vCO Appliance Powershell Plugin

Similar Questions

• esxcli of vCO using PowerShell plugin

  Hello

  I tried to come up with a workflow to run esxicli on an ESXi host commands, I am aware of the different solutions out there including one that uses the vMA as an SSH server, but I would like to give it a try with the plugin from PowerShell. So far, I can connect the vCenter, get the crowd and not even the subject of esxcli by using different examples already on the PowerShell plugin library.

  But my problem is that after I get the object esxcli is on the PowerShellRemotePSObject format and I don't know how to work with it.

  var sess;
  try {
    sess = host.openSession()
    sess.addCommandFromString("Add-PSSnapin VMware.VimAutomation.Core -ErrorAction  SilentlyContinue");
    var invResult = sess.invokePipeline();
    //Show result
    System.log( invResult.getHostOutput() );
    sess.addCommandFromString('Connect-VIServer '+vcenter+' -User user@domain -Password "passw0rd" -Force');
    var invResult = sess.invokePipeline();
    //Show result
    System.log( invResult.getHostOutput() );
    // Get PowerShellRemotePSObject
    sess.addCommandFromString('Get-VMHost -Name '+esxi+' -Server '+vcenter);
    var invResult = sess.invokePipeline();
    //Show result
    System.log( invResult.getHostOutput() );
    var psObject = invResult.getResults();
    if (invResult.invocationState  == 'Failed'){
    System.error(invResult.getErrors());
    }
    else {
    var cmd = sess.addCommandFromString('Get-EsxCli')
    cmd.addParameter('Server', vcenter);
    cmd.addParameter('VMHost', psObject);
    var sessionId = sess.getSessionId();
    var esxcli = System.getModule("com.vmware.library.powershell").invokeCommand(host,sessionId);
    System.log(esxcli);
    }
  
  
  } catch ( ex ) {
    System.log (ex);
  } finally {
    if (sess) {
    host.closeSession( sess.getSessionId());
    }
  }
  
  
  

  The esxcli object is accessible as $esxcli.software.vib.list () in PowerShell I don't know how to use the PowerShellPSObject to access information or execute methods on it.

  Any help is appreciated.

  Thank you

  Juan.

  Hi Juan,

  I'm not sure you can call methods from PowerShellPsObjects returned by VCO.  In the meantime, they were serialzed in XML format from the PowerShell script then resérialisé in VCO.  I'm sure that you lose all methods when this happens.

  What I've done for similar purposes, use the WF model who calls a PowerShell script externally.  I put all my my logical calls and method in the external PoSH script and at the end pass back the final results to the VCO.  I'm much better with PoSH as VCO, so I put as much intelligence in the PoSH as possible.

• vCO + host Powershell - little doubt

  Good evening everyone,

  I work in my company with automation. We use the vCO to automate tasks.

  Today, we can remotely running scripts and command-line inside the machine virtual linux.

  When a machine virtual linux is supplied at a distance, I can execute a command for puppets or run the bash script, for example.

  I want to run remote commands as on windows server.

  According to my research, it is possible using PowerShell. Right? Is there another way?

  As an example, I want to run the command as follows:

  -install puppets (msiexec /qn /i puppet.msi PUPPET_MASTER_SERVER = 192.168.0.10/l * v log_install.txt)

  -run any bat script;

  Resume my doubts:

  -L' PowerShell host is the same target Windows virtual machine created recently? or it is another virtual machine between the vCO and target VM?

  See you soon!

  Well, technically you can use the Powershell plugin and dynamically configure each virtual newly deployed as the target host computer (temporarily).

  However, if you just need to call a few commands, which seems to be a bit of an overdose.

  Alternatives:

  -Use the powershell plugin, to a "midwife" powershell static host, which then calls the new virtual machines via psexec or remote powershell

  -Use the SSH plugin (in which case you can have a SSH server in the windows model)

  -Use the operations of comments (if you only need vmware tools installed on the Windows machine). Check the package to "get comfortable": comments script package manager

  See you soon,.

  Joerg

• vCO with Powershell and causing VMware.VimAutomation.Extensions to workflows to hang

  Environment:

  vSphere Version: 5.5

  vCO Version: 5.5.0 build 1281930

  PowerShell Plugin: PowerShell 1.0.3.304

  
  

  I have successfully instantiated several Powershell commands in by vCO in the past, including commands PowerCLI. However, when I use the

  "import-module VMware.VimAutomation.Extensions.

  command, the workflow seems to stop. I need this module in order to obtain information of vSAN.

  
  

  I know that the module is supposed to be implicitly imported without the need of the declaration when running in a PowerShell command prompt, but I've also had instances where I know that the line is necessary, especially when a Powershell script requires that the module is called from the command line.

  
  

  It seems to be the case here because removing the line causes an error "unknown cmdlet", when it tries to parse the command "Get-VsanDiskGroup".

  
  

  
  

  
  

  Any help would be greatly appreciated! Thank you.

  Solution:

  Add: ' Get-childitem | unlock file "before:"

  import-module VMware.VimAutomation.Extensions

• Typos in Powershell-Plugin objects!

  Hello!

  While testing the new powershell plugin for vCO, I found a misspelled object: PowerShellAutorizationMode should be... AutHorizationMode!

  and in GROUP Action, there is one more in the logging chain: successfully should be successfully at the end...

  Not to be pedantic, but especially misspelling the names of objects causes difficulties to find in the box search and other inconveniences while developing.

  See you soon,.

  Joerg

  

  I pushed this issue within VMware - and I heard that VMware is working on a fix that will be accompanied by an update. I can't share the details, however. Stay tuned.

• PowerShell Plugin only supports version 2.0 of Powershell?

  I'm looking, and it seems that the PowerShell Plugin only supports version 2.0 of Powershell.   Microsoft is currently at version 5.0.  What is the problem?  VMware has renounced this Plugin?  I'm wrong and it really supports a newer version of Powershell?

  See here: Technical preview of VMware vCenter Powershell plugin 1.0.x version

  We supported until PowerShell 4.0 since the 1.0.4 version of the plug-in

• PowerShell Plugin and HTTPS domain credentials

  Someone been able to make this work?

  I have configured WinRM on my powershell host and it seems to work fine.  I can connect via negotiate and kerberos very well via HTTPS w / domain credentials.  However, I can't see the powershell plugin to authenticate with a domain service account, it will only connect w / basic authentication enabled by using the local credentials to the host of powershell.

  I tried the following syntax for the username:

  User domain\username

  username@domain

  I happened to notice that I can't connect to the host PowerShell forcing basic authentication using the enter-pssession cmdlet either which brings me to the conclusion that basic authentication cannot make the domain credentials.

  Any ideas would be appreciated.

  > basic authentication cannot field identification information.

  Yes. The first version of the plugin supports basic authentication only and not with the credentials of domain.

  The good news is that in about 2 weeks, an update of the plugin version would be released that would provide support for kerberos.

  Thank you.

• vCO PowerShell plugin access is denied

  Hello

  Can someone please help with a problem I'm having with vCO and the PowerShell plug-in?  I have correctly installed the plugin for the vCO PowerShell and added/checked one PS via WinRM/HTTPS/Kerberos host, configured with "Session by the user.  (I also tried "Shared Session").

  I can run scripts of PS based on this host in a workflow of vCO, as "Write-Output"... «, 'Get-ChildItem...' ", etc., and it returns the results in the workflow log.  However, if I try to run whatever it is more advanced as PowerCLI or external commands such as 'dnscmd' to create a host A record, it gives the error "failed command: ERROR_ACCESS_DENIED 5 0x5.  I ran 'whoami' leave in a script called by the PS plugin vCO and it shows the good user who has permission to run the commands.

  I ran the command locally on the host of PS using the same user account, and it completes successfully.

  Thank you, Richard

  I was able to get it this way.

  We use the vCO 5.1 device, so I have a host of windows power shell and winrm service has been activated. I configure kerberos authentication. Try to run the powershell script that is running dnscmd. So this script was running fine when we run manually, but of vCO fail with access denied.

  I made a few changes in my powershell script that helped me get through this.

  ~ CredSSP activated in the powershell hosts winrm service

  ~ In my script powershell creates a new session on the local host, even

  $session = New-PSSession-Credential $credential - authentication Credssp - ComputerName localhost

  Invoke-Command - Session $session - ScriptBlock {#Your dnscmd automation}

  ~ Its vCO as a powershell script to call in my powershell host and in the script I am session to the same machine creation and execution of my orders of dnscmd.

  ~ With this I have not any access denied exceptions. Was able to add/delete DNS records.

  Probably, there could be different ways of doing this. But it helped me.

• PowerShell plugin question - dynamically create an instance of PowerShellHost in a workflow

  Hi people,

  Whoever did this for a host who has never been in the inventory of PowerShell vCO? More specifically, how Kerberos in the face of a host name which could have been created since the last time tried to Kerberos for authentication of access for?

  See you soon

  I just wanted to let anyone interested know

  I got this works in the following way in a script

  var hostConfig = new PowerShellHostConfig()

  hostConfig.name = "example";

  .

  .

  .

  .

  Download the plugin to create an instance of the host of this configuration by using the update call

  var host = PowerShellHostManager.update (hostConfig);

  If the configuration is correct, you get an instance of the valid host that you can now call commands on. Looking at the Java code for the plugin, the update method does the following

  Check the config for a host ID.

  If ID is found

  then search for this instance and return it

  on the other

  create and validate a new instance of the host for this config and returning

  There are a few side effects / traps to consider here though

  Gotcha 1.     PowerShellHostConfig has no Member for a host ID attribute if you always create a new instance using this method. New instances will appear in your inventory as of the configs duplicate with different instance ID

  Gotcha 2.     During the validation of the hostConfig during the creation of the host, a the connection test is performed using the specified configuration. In other words, you will see that recorded in the log file of the server so it will look like two connections were established in quick succession if you then an invoke on the new host

  Gotcha 3.     Because of the 1 witch hunt, you should probably do PowerShellHostManager.remove (host) at the end of your script

  Gotcha 4.     If you use 3 to clean up inventory know that if your script/workflow terminates with an error/exception then remove it might not happen. Thus, use the error handling, or finally clause in order to ensure that it is executed. Of course if the deletion up a mistake then all bets are off

  Anyway, just thought I'd share

• PowerShell plugin 1.0.6 - How to move a SecureString vRO to host Powershell?

  I need to pass a variable value SecureString to a vRO input parameter to the Powershell host.

  I imported a powershell script using "generate script PS action". One of the variables is a securestring used for an authentication mechanism on the remote host of the PS. The value is inserted by the user when it starts the workflow in vRO (SecureString type).

  It looks like this:

  -L' user highlights a string safe in the presentation

  -the workflow is executed, and the value of the variable is used during the execution of script on the host PS

  -It must be used as System.Data.SqlClient.SqlCredential

  Edit:

  a few details. Part of the hat to check if the SQL user credentials supplied by the user can be used to connect to a database of MS SQL script:

  $SqlConnection = new-Object System.Data.SqlClient.SqlConnection

  $SqlConnection.ConnectionString = "Server = $strServer; Basis of data = $dbname; »

  $SqlCredential = new-Object System.Data.SqlClient.SqlCredential($loginAccount,$securePassword)

  $SqlConnection.Credential = $SqlCredential

  $SqlConnection.Open)

  $securePassword should be passed through vRO.

  How could I achieve this? I unserstand the SecureString of vCO must be decrypted - key which could I use? How to convert from vRO SecureString of entry so that the host PS recognizes it as such?

  Thank you!

  Hello

  Well, if the account with which you have added the host of powerShell in vRO is different then the account credentials that you are using for the SQL connection, then you need credSSP.  Is it?

  Best regards

  Kaloferov spas

• Build packages of vCO with the Plugin o11n-package

  I began using the maven-011n-package-plugin, found in the Maven Repo to edge of the vCO device or such that got by the vCO Client of-> package-> Expand to folder feature.  First of all, it is a very useful tool, however, the docs are very minimal.  And I have two questions

  (1) is REQUIRED when I build a package (from the native XML) I digitally sign it?

  (2) is there a version of the functionality built into this Maven plugin library?  Where can I get the source?  I was wondering if I can do this without involving the maven; We use gradle.

  I think that the signature is required and package build fails if you don't specify a password and the location of the keystore.

  As for your second question - there is no library, but there is a command line tool that package exim. It can be found in the Maven repo, / com/vmware/o11n/tool/vco-cli-Java /.

  Here is the list of commands it supports + examples.

  On Maven vs Gradle - currently, our tooling is concentrated around Maven. I'll see if we can also provide a Gradle plugin.

  -----------------------------

  vCO Package Exim command line tool

  Description:

  Tool command line that offers the package vCO basic import and export transactions. As source or target, it may have the .package file directory.

  Use:

  Java - jar PackageToolCli.jar

  Controls:

  Here are the basic commands indicating the tool the operation to perform.

  fi - importing files

  Imports the package to vCO .package file.

  Fe - exporting files

  Exports the package vCO .package file.

  di - import directory

  The package is important to vCO of directory tree.

  Ed - directory export

  Exports the vCO to the directory tree package.

  FD - file in the directory

  Create the directory tree .package file.

  Parameters of the command:

  The direct parameters that relate to the specific command. Source or destination files or directories.

  FI

  -Name of the .package file to import.

  fe []

  -Name of the package to export.

  -Directory to export. If this isn't a directory specified, current is assumed.

  di

  -Directory from which to import.

  de []

  -Name of the package to export.

  -Directory to export. If this isn't a directory specified, current is assumed.

  FD

  -Directory to build the .package file.

  Java settings:

  Additional settings that may be needed by the system, in order to execute specific commands.

  -DserverUrl =

  URL and connection of the vCO server against which will be take place imports or exports.

  -DallowedMask =

  Attributes of the package.

  v components can be found

  e editable elements

  f elements can be transferred in other packaging

  -DkeystoreFileLocation =

  Path to the .vmokeystore file that contains the certificate of development

  -DkeystorePassword =

  Password of the .vmokeystore file

  -DexportVersionHistory =

  Export version history

  -Dincludes =

  ';' - separate the list of models showing what are the items to include.

  -Dexcludes =

  ';' - separate the list of models showing the items to be excluded.

  Examples:

  Export com.vmware.test.TestPackage package as a package in the current folder file.

  -DserverUrl=username:password@myserver:8281 java-jar PackageToolCli.jar fe com.vmware.test.TestPackage

  Export the package com.vmware.test.TestPackage as a directory of the current folder structure.

  -DserverUrl=username:password@myserver:8281 java-jar com.vmware.test.TestPackage PackageToolCli.jar

  Import com.vmware.test.TestPackage.package file package vCO server.

  -DserverUrl=username:password@myserver:8281 java-jar PackageToolCli.jar fi com.vmware.test.TestImpex.package

  (Note: the next two commands require a development certificate in order to accomplish)

  Build the .package file in directory structure.

  Java-DserverUrl=username:password@myserver:8281-DkeystoreFileLocation=/path/to/my_cerificate.vmokeystore

  -DkeystorePassword = mypassword-jar PackageToolCli.jar fd com.vmware.test.TestPackage

  Import the directory structure com.vmware.test.TestPackage package to the server vCO.

  Java-DserverUrl=username:password@myserver:8281-DkeystoreFileLocation=/path/to/my_cerificate.vmokeystore

  -DkeystorePassword = mypassword-jar PackageToolCli.jar di com.vmware.test.TestPackage

  The last two commands is also in charge of the allowedMask, the exportVersionHistory and includes / excludes java settings, which offer more control to content and access attributes of the package.

  -DallowedMask = vf

  Creates a package that cannot be edited.

  -DexportVersionHistory = true

  Keeps a history of local versions of objects vCO developed between exports and imports.

  -Dincludes = "" * / Test Package/**/*.element_info.xml;**/Test Samples/**/*.element_info.xml;**/testPackage/**/*.element_info.xml ""

  Includes only the objects that have '. '. element_info.xml"descriptor (which is specific for parcels exported as trees of directories), the folders in the library of tests and samples (for workflows) or testPackage (for actions).

• vCloud Director 5.1 with vco 5.5 plugin configuration

  I installed the plugin for vCloud director 5.1 in vCenter Orchestrator 5.5, the plug-in installed very well with the certificate that I imported from the url. However, configure the plug-in is another story, when I go to set up the plug-in of the customer or in the page web configuration, I get "failed to connect with the user name. My authorization of vco is configured with LDAP, so is my vCloud Director. In the client workflow 'Add link' vco for vCloud director, my selections are the url to vCloud, port 443, active, max 600 connections, the connection times out 20000 ms, session mode by user, the use and organization system SAML authentication Session. I followed the instructions of the Plugin VMware vCenter Orchestrator Documentation Centre . I tried to configure the plug-in as a shared user and I get the same error. I tried to configure the plugin in the web configuration page and it excludes the host that is the url to vCloud, but I do not see an inventory after that restart services vco and vco customer return logging. My vCloud infrastructure is set up with 2 cells and her sitting behind a vShield load balancing.  If I try to configure the plugin to go directly to one of my cells the workflow times out. I have a request of service opened with vmware, but I hope someone else has experienced this problem or might have a few suggestions that will point me in the right direction.

  Thank you

  J

  Changing the IP of my vco did the trick. When I set up the server of vco, I put it on the same subnet as my vcd cells. While my load balancer was on a separate subnet. Assigning the vco server an ip address on a different subnet allowed transmitted traffic of the vco through the load balancer, solve my problem of time-out.

• problem of Plugin vCO-Powershell by running a command (for members of a local administrator on a server group)

  Hello

  Tearing my hair out and looking for a little help :-)

  I have a powershell script for the verification of the members of the Local administrators on a server, and it works very well in a powershell window. (running on the server that hosts my VCO in powershell and under the registered with vCO user/account name...)  However, when I call it from a workflow of vCO it fails.

  Track down, I've isolated the code criminalized in this section:

  I provide $servername as the server to run the script against.

  
  $group = [ADSI] "" WinNT: / / $servername/administrators ' "

  $members = @($group.psbase.Invoke ("membres"))

  $results = $members | foreach {$_.} GetType(). InvokeMember("Name",'GetProperty',$null,$_,$null)}

  and the highlighted line is the specific code that fails.

  the specific error is:

  System.Management.Automation.MethodInvocationException: Exception calling "invoke" with "2" arguments: "the network path was not found.

  I noticed that if I replace with $servername in the 1st line with '. '. (it is run on the local server) It works very well. However, if I use the var $servername, or incorporate just a specific server name, it fails with the above error.

  Any help appreciated,

  Thanks in advance,

  John.

  (any error in the vCO journal is):

  2014-09-11 12:59:16.717] [I] PowerShellInvocationError: errors found during execution of script
  System.Management.Automation.MethodInvocationException: Exception calling "invoke" with "2" arguments: "the network path was not found.
  "---> System.Runtime.InteropServices.COMException: the network path was not found."

  at System.DirectoryServices.DirectoryEntry.Bind (Boolean throwIfFail)
  at System.DirectoryServices.DirectoryEntry.Bind)
  at System.DirectoryServices.DirectoryEntry.get_NativeObject)
  at System.DirectoryServices.DirectoryEntry.Invoke (String methodName, Object [] args)
  at System.Management.Automation.DotNetAdapter.AuxiliaryMethodInvoke (arguments Object [], Object target, Object [] originalArguments, MethodInformation methodInformation)
  -End of the exception stack trace internal-
  to System.Management.Automation.ExceptionHandlingOps.CheckActionPreference (FunctionContext funcContext, Exception exception)
  to System.Management.Automation.Interpreter.ActionCallInstruction'2.Run (InterpretedFrame frame)
  at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run (InterpretedFrame frame)
  at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run (InterpretedFrame frame)
  at System.Management.Automation.Interpreter.Interpreter.Run (InterpretedFrame frame)
  to System.Management.Automation.Interpreter.LightLambda.RunVoid1 [T0](T0 arg0)
  at System.Management.Automation.ScriptBlock.InvokeWithPipeImpl (ScriptBlockClauseToInvoke clauseToInvoke, createLocalScope Boolean functionsToDefine dictionary 2 list 1 variablesToDefine, ErrorHandlingBehavior errorHandlingBehavior, Object dollarUnder, entry object, object scriptThis, Pipe outputPipe, InvocationInfo invocationInfo, Object [] args)
  to System.Management.Automation.ScriptBlock. <>c__DisplayClassa. < InvokeWithPipe > b__8()
  System.Management.Automation.Runspaces.RunspaceBase.RunActionIfNoRunningPipelinesWithThreadCheck (use)
  at System.Management.Automation.ScriptBlock.InvokeWithPipe (Boolean useLocalScope, functionsToDefine dictionary 2, list 1 variablesToDefine, ErrorHandlingBehavior errorHandlingBehavior, Object dollarUnder, entry object, object scriptThis, Pipe outputPipe, InvocationInfo invocationInfo, Object [] args)
  to System.Management.Automation.ScriptBlock.InvokeUsingCmdlet (Cmdlet contextCmdlet, Boolean useLocalScope, ErrorHandlingBehavior errorHandlingBehavior, Object dollarUnder, entry of the object scriptThis, Object [] args)
  at Microsoft.PowerShell.Commands.InvokeExpressionCommand.ProcessRecord)
  at System.Management.Automation.CommandProcessor.ProcessRecord)
  (Name of the dynamic Script Module: invokeScript #14)

  
  

  There are some security restrictions applied when the power shell scripts remotely (what vCO made using the Microsoft WinRM service).

  To simulate a runtime environment similar outside the vCO, you can use "winrs" tool microsoft to call remote power shell script and check if the similar error will exist also outside the vCO.

  Bolg very extensive on the subject can be found here http://kaloferov.com/blog/using-credssp-with-the-vco-powershell-plugin/

  See the section for access to the network and access to mapped network drives through vCO.

• VSphere Orchestrator (vco) - problem to add a Powershell host

  Hello world

  I am currently set up a VSphere Orchestrator server and I have a few problems to add a new host via WinRM with Add a PowerShell host model.

  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 to a second server HTTPS but not with the vco...

  This is my setup:

  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 works:

  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 the vco I:

  Name: test

  The Host/IP: Home - vsphere.urbanvirtu.local

  Port: 5986

  Type remote PowerShell: WinRM

  Transport protocol: HTTPS

  Authentication: Kerberos

  Session mode: A shared Session

  User name: administrator

  Password: password

  

  

  Someone has had this problem before? What I did wrong?

  Thanks in advance for your help.

  Best regards

  Jean

  Based on the log, I see that "Connection refused:" error was connected to the kdc parameter in the krb5.conf file and you have already defeated it.

  Now, if I understand 'Add a PowerShell host' the workflow remains in working condition and does not end.

  This behavior I observed in the case of PowerShell plugin 1.0.3 is trying to connect to PowerShell host running PowerShell 4.0.

  Would you please provide version of

  the PowerShell vCO plugin version

  PowerShell host - Windows Version

  PowerShell host - PowerShell version

• vCO-plugins: documentation of type object &amp; source

  Hi guys,.

  I'm new to vCO and were it testing the past few days. Powerful tool, really I have to say.

  However, there are two things I have really miss me and could not find so far:

  -Construction in the API browser is nice to find custom objects provided by the vCO Plugins, but the description of the object often doesn't have any information about the types of objects and parameters (to be precise: all possible parameters and their brands to parameter order, required / optional, parameter object types) and return types. Is there some kind of documentation showing that the available information? I use the browser API the wrong way? It is almost impossible to develop without it.

  -This brings me to my next question: are the provided plugins open source? That would make it possible to extend some of the classes as well as of course it would make possible to verify what really happens behind the scenes. I found that for some plugins, like the vCAC plugin for example, it seems to be a package open source the plugin (for example https://my.vmware.com/group/vmware/details?downloadGroup=VCO_VCAC_PLUGIN_520 & productId = 344 ). However, during the inspection of the package I couldn't find the source files for the libraries open source used by the plugin, not the plugin sources themselves.

  My question is simple: is it possible the GET the plugins source provided?

  Thanks in advance

  Robert

  Right, I remembered supply open the powershell plugin has been discussed but did not know if this was published as the newer version does not have the included sources.