VMware vRealize CloudClient 4.2 Release Notes

vRealize CloudClient 4.2 | 23 AUG 2016 | Build 4287344

Check for additions and updates to these release notes.

What's in the Release Notes

The release notes cover the following topics:

What's New

  • The vra login commands now take an optional port number as part of the --server parameter. To connect to a vRealize Automation, IaaS, vRealize Orchestrator, or Site Recovery Manager server that is listening on a non-default port, specify the server in hostname:port format. For example, --server vra.example.com:8443.
  • Keyfile-based authentication is supported for IaaS login.
  • A new vco logout command has been introduced to close active vRealize Orchestrator sessions.
  • Two new options have been added to the cloudclient.config file.
    • In cases where CloudClient is primarily used for scripting rather than in interactive mode, set auto.completion.enable=false for better performance. Auto-completion is enabled by default.
    • To bypass certificate checking in CloudClient the first time CloudClient communicates with a server, set trust.certs.on.first.use=true. By default, CloudClient prompts the user to review and accept certificates that are not present in the CloudClient truststore.
  • New vra icon commands are available to manage the catalog icons. System administrators can use these commands to update the default system icons.
  • The new vra service update command enables updating an existing service with CloudClient.
  • Disaster recovery scenarios with Site Recovery Manager for machines provisioned through XaaS are supported through CloudClient.


To run CloudClient, run the cloudclient.sh (Unix) or cloudclient.bat (Windows) command.

On Windows, CloudClient requires Java version 1.7U80 or later. On Unix, any Java 7 or later is supported.

When running CloudClient in script mode, use single quotes (') instead of double quotes (") in command arguments.

Use the following guidelines for the best Windows experience when running CloudClient:

  • Ensure that your Command Prompt or PowerShell uses the same value for Window Buffer Width and Window Width. If your prompt's Window Buffer Width is larger than your Window Width, commands do not wrap properly.
  • Only the [Home] and [End] keyboard shortcut keys are supported when running CloudClient.

For full product documentation, open docs/index.html in your browser.

Resolved Issues

  • Network- and storage-related properties are no longer deleted on reprovisioning
    In previous releases, custom properties related to networking and storage were deleted after submitting a reprovision request.

  • Error accepting untrusted certificates
    In release 4.1, CloudClient would sometimes return an error when attempting to add a certificate to the truststore.

  • CloudClient now relies on server-side pagination
    In previous releases, CloudClient would fetch the full list of machines, deployments, and requests from the server even when pagination was configured.

  • Imported machines now appear in the Deployments and Machines lists
    The vra machines unmanaged register command now takes three additional parameters: --deploymentName (the name of new deployment under which the new machine should appear), --blueprintId (the ID of the blueprint to associate with the machine), and --componentId (the name of the component within blueprint that represents the machine).

  • The organization field is now populated when creating vCloud endpoints
    In previous releases, when adding a vCloud endpoint with organization administrator credentials, the organization was not saved even when the --organization parameter was specified, which caused data collection to fail.

  • CloudClient successfully logs in into environments with no IaaS server
    In CloudClient 4.1, logging in required trusting the IaaS certificate, which failed if there was no IaaS server. CloudClient now proceeds after trusting the VA certificate only if there is no IaaS server.

Known Issues

  • The vco workflow list command does not support paging
    The response for the vco workflow list command is always displayed as a single list regardless of paging configuration.