VMware

VMware vCenter UNIX/ESX/vSphere Deployment Utility Release Notes

VMware vCenter UNIX/ESX/vSphere Deployment Utility 1.3.0.56 | 9 SEPTEMBER 2010 | Build 56

Last Document Update: 28 SEPTEMBER 2010

Check frequently for additions and updates to these release notes.

What's in the Release Notes

The release notes cover the following topics:

What's New

Welcome to VMware vCenter UNIX/ESX/vSphere Deployment Utility for VMware vCenter Configuration Manager (VCM) 5.3. The following information provides highlights of some of the enhancements available in this release of the UNIX/ESX/vSphere Deployment Utility.

Features

The VMware vCenter UNIX/ESX/vSphere Deployment Utility includes the following new features.

  • ESX 4.1 support.

  • SUSE 11 support.

  • Mac OS X agent support.

  • Discovery import file supported for importing list of machines to the Deployment Utility.

  • SFTP/SCP transfer protocol options enabled for copying files to UNIX, Linux, and ESX machines.

  • Agent files location option to support deployment to multiple UNIX/Linux platform types. The Deployment Utility will find the appropriate Agent files to deploy to the machine without requiring users to specify the Agent package for each machine.

  • Ability to support multi-threaded deployment to multiple machines, and the ability to specify the maximum number of threads to use at one time.

  • Support for copying, cutting, and pasting into data grid rows.

  • VMware vCenter Branding: The EMC Ionix Deployment Utility is now renamed and branded as VMware vCenter UNIX/ESX/vSphere Deployment Utility for VMware vCenter Configuration Manager (VCM) 5.3.

  • Platform Support for vCenter UNIX/ESX/vSphere Deployment Utility: Supported platforms for vCenter UNIX/ESX/vSphere Deployment Utility are listed in the vCenter Configuration Manager Hardware and Software Requirements Guide.

Installation

The vCenter UNIX/ESX/vSphere Deployment Utility ships with a Readme that explains the server and agent prerequisites for installation and how to install the Deployment Utility.

Prior Releases of vCenter UNIX/ESX/vSphere Deployment Utility

Features and known issues from prior releases of vCenter UNIX/ESX/vSphere Deployment Utility (EMC Ionix Deployment Utility 1.2) are described in the release notes for each release. The current Release Notes are posted to the VMware download Web site and the Configuresoft Customer Download page.

Product, Feature, and Platform Support Notices

Frozen Platforms: The platforms now considered to be frozen include VMware ESX 2.5. 3.0, 3.5, ESXi 3.5; and Microsoft Windows 2000, Windows XP SP2 or earlier. Note that "freezing" means these platforms will not support the additional features in VCM 5.3. For more information about frozen platforms, see the VCM 5.3 Release Notes.

Resolved Issues

The following items are software fixes included in the VMware vCenter UNIX/ESX/vSphere Deployment Utility 1.3 release.

  • Popup displayed when switching tabs
    When going from ESX Configuration tab to UNIX/Linux Agent Deployment tab a Save data popup is displayed. The popup should not be displayed.

  • Applying the same User Names and Passwords
    Inconsistency between ESX and UNIX\Linux tools when "Apply the same User Names and Passwords..." is selected.

  • Key and script files setup information should be retained
    When any ellipsis button for Key and Script Files for Setup, from the ESX Configuration Deployment tab, is selected and then is canceled in the popup window, the information is removed. When canceled, the information should be retained.

  • UNIX/Linux Agent Deployment information should be retained
    When any ellipsis button for Agent Package and Files Locations, from the UNIX/Linux Agent Deployment tab, is selected and then is canceled in the popup window, the information is removed. When canceled, the information should be retained.

  • Not all information cleared with selecting Clear All User Info
    When clicking the Clear All User Info button, all added data should be cleared.

  • User for Web Services does not update rows previously entered
    For ESX config if "Use the same User Name and Password for both SSH and Web Services collections" is checked after some data is entered, the User for Web Services does not update the rows previously entered, only the new rows entered.

  • Enhancement to read "Add Machines" import file from vCenter VCM
    Enhancement: Have the ability to read "Add Machines" import file from vCenter VCM to populate the grid for ESX and UNIX/Linux.

  • Agent and configuration tool deployment limitation
    UNIX/Linux agent deployment and ESX configuration tool only works on 32-bit Windows systems.

  • Invalid XML DOCUMENT error
    When loading a saved ESX Configuration xml file under the UNIX/Linux Agent Deployment tab, an Invalid XML DOCUMENT error occurs.

  • vSphere Client required when using the Deployment Utility on 64-bit collectors
    Document that the vSphere Client (previously VI Client) has to be installed when using the Deployment Utility on 64-bit collectors.

  • "Super User" column in data grid out of place
    "Super User" column in the grid should be immediately after the "User for Setup" column in both Agent Deployment and ESX Utility.

  • Initial installation and upgrade of UNIX Agent fails with SCP
    When installing the UNIX Agent using the SCP transfer protocol, the initial installation and Upgrade Existing Agents both fail.

  • Existing directory on Agent causes initial installation to fail
    Initial installation fails if /opt/CMAgent exists on the target UNIX Agent Machine.

  • Incompatible Version of WODs dll
    When upgrading UNIX Agents, an error may occur: Incompatible Version of WODs dll are already present on the system. Please unregister existing dll manually before running the utility!

Known Issues

The following items are known issues in the VMware vCenter UNIX/ESX/vSphere Deployment Utility 1.3 release.

  • Default location for certificate
    On the UNIX\Linux Agent Deployment tab, the Location for Certificate should default to the location of the vCenter VCM installation.

  • Default location for Collector key
    On the UNIX\Linux Agent Deployment tab, the Location for Collector Key should default to the location of the vCenter VCM installation.