VMware

Stage Manager 1.0.1 Release Notes

VMware Stage Manager 1.0.1 | 21 APR 2009 | Build 1970

Last Document Update: 21 APR 2009

The release notes contain these topics:

What's New in This Release?

Stage Manager 1.0.1 adds usability and performance enhancements and bug fixes:
  • New: Stage Manager 1.0.1 supports ESX Server 3.5 Update 4 and VirtualCenter Update 4.
  • Adds support for ESX Server 3.5 Update 3 and VirtualCenter 2.5 Update 3.
  • Allows undeploying of stages. Stage Manager administrators and service administrators can free up non-production resources easily by undeploying all configurations on selected stages simultaneously.
  • Improves performance for large-scale deployments of Stage Manager.
  • Allows importing of LDAP users. Stage Manager administrators can import users from Active Directory.
  • Removes server license from Stage Manager.
  • Adds support for VMFS media store.
  • Allows discarding of saved state. You can discard the saved state of a virtual machine that is in undeployed saved state.
  • Expands the comments feature.
    You can add change summaries for more operations on configurations, as well as add a note to a configuration.
  • Expands browser support. Stage Manager supports FireFox 3.0.
  • Adds support for more guest operating systems. For a complete list of supported guest operating systems, see the VMware Stage Manager User's Guide.

Requirements

Stage Manager requires the following software components:

  • VMware Infrastructure 3 Standard or VMware Infrastructure 3 Enterprise.
  • ESX Server 3.5 and above and VirtualCenter 2.5 and above.
  • For using the maintenance mode in VirtualCenter, install ESX 3.5 Update 1, Update 2, Update 3, or Update 4, and VirtualCenter 2.5 Update 1, Update 2, Update 3, or Update 4 patches. If you do not use the Update patches, you must unprepare an ESX host to put it in maintenance mode. For information about unpreparing hosts, see the VMware Stage Manager User's Guide.

Stage Manager does not work with VMware Infrastructure 3 Foundation or VMware ESXi 3.5. For information about all requirements and procedures to set up Stage Manager, see the VMware Stage Manager Installation Guide.

Stage Manager requires the following hardware:

  • One server from the ESX Server 3.5 HCL
  • A VirtualCenter Server system
  • Shared storage (NFS, iSCSI, or Fiber Channel)
  • A physical or virtual machine running Stage Manager Server

Make sure to review the ESX hardware compatibility guides. See http://www.vmware.com/support/pubs/vi_pages/vi_pubs_35.html.

Do not install Stage Manager Server software in compressed or encrypted folders. For guidelines on working with VirtualCenter and Stage Manager in the same environment, see the VMware Stage Manager Installation Guide.

Note: Time synchronization between the ESX Server hosts, VirtualCenter Server system, and Stage Manager Server system is important and noted in the VMware Stage Manager Installation Guide. Use NTP on all systems.

Upgrading Stage Manager 1.0 to 1.0.1

You can only upgrade Stage Manager from 1.0 release (build 1561) to 1.0.1 release (build 1970).

To upgrade Stage Manager from GA (build 1561)
  1. Back up the Stage Manager database as a precaution before upgrading Stage Manager.
    From the command prompt on the Stage Manager Server system, run the following command:
    OSQL -S localhost\vsm -E -Q "backup database stagemanager TO DISK='c:\sm_backup.bak'"
    This command creates the sm_backup.bak file on the C:\ drive.
  2. Uninstall only the program files of Stage Manager (build 1561). See Uninstalling Stage Manager in Chapter 3 of the VMware Stage Manager Installation Guide.
  3. Install the release version of Stage Manager (build 1970). See "Installing the Stage Manager Server Software" in Chapter 3 of the VMware Stage Manager Installation Guide.
  4. Clear the browser cache to ensure the Stage Manager Web console appears with the proper icons and layout:
      In Internet Explorer, choose Internet Options in the Tools menu and delete the temporary internet files.
      In Firefox, choose Clear Private Data in the Tools menu and clear only the browser cache.
  5. Log in to the Stage Manager Web console.
  6. In the left pane, click Resources.
  7. Click the Hosts tab.
  8. For each host with a red X in the Ready column, move the pointer over the host name and choose Upgrade Agent from the menu.

Product Compatibility

For information about VMware product compatibility with Stage Manager, see the VMware knowledge base and article links in the Known Issues section of the release notes.

Known Issues

The following issues are known to occur in this release.

  • Fenced Configurations Display Error Messages After Upgrading From Stage Manager 1.0 to Stage Manager 1.0.1
    After upgrading from Stage Manager 1.0 (build 1.0.0.1561) to Stage Manager 1.0.1 GA build (build 1.0.1.1970), fenced configurations display error messages similar to the following in the Messages column of the configuration list page:

    Virtual router which was POWERED ON has changed its state from VirtualCenter.
    8/20/2008 1:47:27 PM
    Virtual Machine: VirtualRouter_C9F4_DontModify
    Virtual router 26 is not POWERED ON.

    The configurations work properly and, contrary to the error message, the virtual router is powered on. The error condition does not result in loss of functionality.

    Workaround: To clear a message, click on it, and in the System Messages dialog box that appears, click Clear All.
  • Host Configuration in VirtualCenter Requires Prior Host Unpreparation in Stage Manager
    Any change of host configuration in VirtualCenter must be preceded by host unpreparation in Stage Manager. This includes, but is not limited to, lockdown mode, distributed power management standby mode, and any change of compute resource association (for example, the movement of a host from one cluster to another).
    See the VMware Stage Manager User's Guide for instructions on unpreparing a host.

Review the following knowledge base articles:

Installation of VMware MKS Plug-in on Firefox 3.0 Fails (KB 1006950)
Stage Manager Installation Fails on Compressed or Encrypted Folders (KB 1005703)
Stage Manager Datastores Tab Does Not Display Current Capacity After Creating Virtual Machines (KB 1005704)
Product Compatibility Between VMware Stage Manager and VMware Site Recovery Manager (KB 1005686)
Product Compatibility Between VMware Stage Manager and VMware Update Manager (KB 1005687)
Product Compatibility Between VMware Stage Manager and VMware Lifecycle Manager (KB 1005677)
Product Compatibility Between VMware Stage Manager and VMware Lab Manager (KB 1005688)
Product Compatibility Between VMware Stage Manager and VMware Consolidated Backup (KB 1005690)
Antivirus Software Blocks SMTP Email Alerts From Stage Manager (KB 1005700)
Incorrect Context View for Virtual Machine Datastore Usage Appears When Using Internet Explorer Enhanced Security Configuration (KB 1005702)

You can also search for all Stage Manager KB articles. To narrow down the search process, choose VMware Stage Manager in the Product menu.

Resolved Issues

The following issues are resolved in this release.

  • Multiple Stage Manager Server Systems Cannot Access the Same VirtualCenter Datacenter
    With this release, multiple Stage Manager Server systems can access the same VirtualCenter datacenter as long as they don't access the same cluster.
  • Configurations Are Not Distributed Evenly Among ESX Hosts Within a DRS Enabled Cluster
    When configurations are deployed on a DRS enabled cluster, virtual machines tend to be deployed on the ESX hosts where they were originally registered. This might result in a large number of deployments on a single ESX host. This issue is fixed in this release.
  • Stage Manager Does Not Support SMB Shares That Include the $ Symbol in the UNC Path
    Stage Manager now supports SMB shares that include the $ symbol in the Universal Naming Convention (UNC) path.
  • Stage Manager Might Not Delete all Data From a Datastore
    Even after deleting all data on a datastore, some directory entries might remain, as these entries might be referenced by virtual machines as revert points. This issue is fixed in this release by enabling users to delete revert points.