VMware vCenter Orchestrator 4.0.3 Release Notes
vCenter Orchestrator 4.0.3 | 5 May 2011 | Build 4705
vCenter Server 4.0.3 | 5 May 2011 | Build 387869
Check frequently for additions and updates to these release notes.
What's in the Release Notes
The release notes cover the following topics:
Downloading and Installing VMware vCenter Orchestrator
If you have downloaded and installed VMware vCenter Server, Orchestrator is already installed on your system and only needs configuration.
Read the VMware vCenter Orchestrator Installation and Configuration Guide for step-by-step guidance on configuring vCenter Orchestrator.
Upgrading or Migrating to vCenter Orchestrator 4.0.3
You can migrate an existing Orchestrator 4.0 installation to Orchestrator 4.0.3 by following the instructions in the VMware vCenter Orchestrator Installation and Configuration Guide.
The vCenter Server 4.0 plug-in is fully supported for use with vCenter Server 4.0. However, you cannot use the vCenter Server 4.0 plug-in with VirtualCenter Server 2.5. To use Orchestrator 4.0 with VirtualCenter Server 2.5, you must install the VMware Infrastructure 3.5 plug-in.
Orchestrator provides the VMware Infrastructure 3.5 plug-in in the following locations after installation:
- If you have installed Orchestrator by using the standalone installer:
- If you have installed Orchestrator together with vCenter Server:
Internationalization (I18N) Support
vCenter Orchestrator 4.0.3 complies with I18N Level 1. Although Orchestrator is not localized, it can run on non-English operating systems and handle non-English text.
How to Provide Feedback
Your active feedback is appreciated. Provide your feedback through:
- Support Requests (SRs)
- Orchestrator Discussion Forum
File all issues that you find as Support Requests (SRs), even if you report them to VMware by other means.
VMware Support's commitment to SRs filed by customers and instructions on how to file an SR can be found at http://www.vmware.com/support/services/.
Experienced SR users can file support requests at http://www.vmware.com/support/sr/sr_login.jsp.
Use your registered VMware store account to log in.
Include log files in your SRs. To gather log files from Orchestrator:
- Go to the Orchestrator configuration interface at
- Log in with your username and password.
- Click Logs.
- Click Generate log report.
- Save the generated ZIP file.
- Upload the saved ZIP file to VMware Support.
For Orchestrator configuration issues, include an exported configuration file in your SRs. To export your configuration from the Orchestrator configuration interface:
- Go to the Orchestrator configuration interface at
- Log in with your username and password.
- Click General.
- Click the Export Configuration tab.
- Type your password and press Enter.
- Save the
- Upload the saved files to VMware Support.
Orchestrator Discussion Forum
View the Orchestrator forum at http://communities.vmware.com/community/vmtn/mgmt/orchestrator. Use your registered VMware store account to log in.
Prior Releases of vCenter Orchestrator
Features and issues from earlier releases of vCenter Orchestrator are described in the release notes for each release. To review release notes for earlier releases of vCenter Orchestrator, click one of the following links:
The following issues have been resolved in the Orchestrator 4.0.3 release:
- Security vulnerabilities in the Apache Struts version embedded in Orchestrator
Earlier versions of Orchestrator versions embed Apache Struts 2.0.11 or earlier, which contain vulnerabilities described at the following URLs:
The vulnerabilities are classified as Important, according to the VMware Security Response Policy.
This issue is fixed in this release.
The known issues in this Orchestrator release are grouped as follows:
- Restarting vCO server service after reinstalling plug-ins adds Java exceptions to the logs
In the Troubleshooting tab of the Orchestrator configuration interface, if you reinstall plug-ins by clicking Reset current version and then restart the Orchestrator server, several Java exceptions are written to the Orchestrator server logs.
- Problems handling non-ASCII characters in certain contexts
Using non-ASCII characters in input parameters results in incorrect behavior in the following contexts:
- If you run the SCP put or SCP get workflows on a file with a name that contains non-ASCII characters, the workflow runs, but name of the resulting file on the destination machine is garbled.
- If you try to insert non-ASCII characters into attribute names, the characters do not appear. The issue occurs for Web view attributes, workflow attributes and action attributes.
- Client-only upgrade shows incorrect version number in the configuration interface
If you have an existing Orchestrator installation of both the client and the server on the same machine, and you use the standalone Orchestrator installer to upgrade the client by selecting Client-Only, after the upgrade the Orchestrator configuration interface shows the version number of the new client installation. This is incorrect. The server has not been upgraded.
- SSL certificate is lost during upgrade from 4.0 to 4.0.1
If you upgrade an existing Orchestrator 4.0 installation to 4.0.1, and import the configuration of the previous installation in the 4.0.1 installation, the SSL certificate from the old installation is not loaded. The Server Certificate tab shows red in the configuration interface.
Workaround: You must import the certificate manually.
- Orchestrator does not work with forest and external trusts in Active Directory
Multiple domains that have a two-way trust, but are not in the same tree, are not supported and do not work with Orchestrator. The only configuration supported for multi-domain Active Directory is domain tree. Forest and external trusts are unsupported.
- Support for TNSNames missing when you connect to an Oracle database
You cannot use TNSNames to connect to an Oracle database. You can connect to an Oracle database using an IP address or a DNS name.
Add support for RAC and TNS configuration for Oracle 11g Database instances to vCenter Orchestrator (KB 1022828).
- Restricted access to vCenter Server inventory can cause errors if Session per user is set
If you select the Session per user option in the vCenter Server tab of the configuration interface, accessing the vCenter Server inventory can result in some errors if the connected user has restricted access to inventory objects.
- No error message is displayed on the Network tab of the Orchestrator configuration interface when a network port is already in use
The Network configuration is saved successfully without errors even when the port numbers that you enter are already taken on your host.
Workaround: Make sure the port numbers you enter on the Network tab are free.
- Possible loss of logs when using vmo.bat file to restart the Orchestrator server
If you start the Orchestrator server as a service and you try to restart it by running the
vmo.bat file directly, you can experience a potential loss of logs. The loss of logs is due to the Orchestrator server potentially running with different permissions.
Workaround: Do not restart the server by using the
vmo.bat file. Start the Orchestrator server as a service as follows:
- Right-click My Computer and select Manage > Services and Applications > Services
- Right-click VMware vCenter Orchestrator Server and select Start
- Importing packages using the Orchestrator client might fails
Occasionally, importing a package by using the Orchestrator client results in the error
Unable to import a certificate, reason : Unable to save keystore.
Workaround: Close the error message and attempt the import again.
- The Revert option for the parameters table on the Scripting tab of the Edit Actions view does not revert to the last saved state
When you add a parameter to an action script, you cannot remove it using the Revert option.
Workaround: Right-click the parameter and click Delete Selected.
- Characters are accepted as the input value for workflow attributes of number type
Format validation has been disabled on workflow attributes that are of the number type. Invalid input values are accepted without any warning, and workflows are saved successfully, which can lead to unpredictable results.
- The Find orphaned virtual machines workflow might detect VMDK files that are used by linked clones
Some VMDK files that are associated with linked clones in the Orchestrator inventory might be listed as unused by the Find orphaned virtual machines workflow. If you remove these VMDK files, the linked clones become unusable.
- Changes to input parameter descriptions are not propagated to the presentation
If you change the description of an input parameter for a workflow, the change is not propagated to the description in the presentation.
Workaround: Copy the description to the presentation manually.
- You cannot export policies as templates
The Export as policy template function is disabled in the Orchestrator client and cannot be used.
- The Convert disks to thin provisioning workflow does not handle virtual machines with snapshots correctly and does not convert the thick-provisioned disks
On completion, the Convert disks to thin provisioning workflow reports that the thick-provisioned disks of virtual machines with snapshots are successfully converted to thin-provisioned, when they are actually not.
Workaround: Do not include virtual machines with snapshots in the workflow.