VMware

Stage Manager 1.0 Release Notes

VMware Stage Manager 1.0 | Build 1561

The release notes contain these topics:

Upgrading Stage Manager to Release Build 1561

You can upgrade Stage Manager from Beta 1 (build 11) to the release build (build 1561) or from Beta 2 (build 1471) to the release build (build 1561).

To upgrade Stage Manager from Beta 1 (build 11)

  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 this sample command or your own backup method:
    OSQL -S localhost\vsm -E -Q "backup database stagemanager TO DISK='c:\sm_backup.bak'"
    This sample command creates the sm_backup.bak file on the C:\.
  2. Uninstall only the program files of the Beta 1 version of Stage Manager (build 11). See "Uninstalling Stage Manager" in Chapter 3 of the VMware Stage Manager Installation Guide.
  3. Install Microsoft .NET Framework 2.0 Service Pack 1 or higher. (Beta 1 did not require the service pack.)
  4. Install the release version of Stage Manager (build 1561). See "Installing the Stage Manager Server Software" in Chapter 3 of the VMware Stage Manager Installation Guide.
  5. 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.
  6. Log in to the Stage Manager Web console.
  7. In the left pane, click Resources.
  8. Click the Hosts tab.
  9. 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.

To upgrade Stage Manager from Beta 2 (build 1471)

  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 this sample command or your own backup method:
    OSQL -S localhost\vsm -E -Q "backup database stagemanager TO DISK='c:\sm_backup.bak'"
    This sample command creates the sm_backup.bak file on the C:\.
  2. Uninstall only the program files of the Beta 2 version of Stage Manager (build 1471). See "Uninstalling Stage Manager" in Chapter 3 of the VMware Stage Manager Installation Guide.
  3. Install the release version of Stage Manager (build 1561). 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.

Key Features

Stage Manager 1.0 provides these features:

  • Service Lifecycle Visualization
    • Provides a simple user interface.
    • Organizes multimachine configurations by the IT service they support.
    • Breaks services down into stages of the service lifecycle.
    • Moves service configurations across the lifecycle (to and from production).
    • Associates resource pools from VirtualCenter with services and stages.
    • Adds and removes stages and associates resources dynamically.
    • Creates services quickly from a global service template.
    • Adjusts stage resources to emulate business conditions (for example, high load, constrained resources, and failed load balancers).
  • Resource Management
    • Integrates with VirtualCenter to allow for the full benefits of VMware Infrastructure 3.
    • Selects storage formats dynamically for performance or cost savings. Stage Manager supports standard and linked clones.
    • Sets expiration dates for unused configurations to be removed from storage or hidden from users.
    • Automates the issuing and tracking of IP addresses from a central repository.
  • Multimachine Configurations
    • Creates service configurations in seconds using virtual machine templates. You can use an unlimited number of virtual machines without having to perform manual adjustments.
    • Imports existing virtual machines in VirtualCenter to different service stages.
    • Displays all virtual machine consoles side-by-side in a configuration.
    • Acts on virtual machines in a configuration as a unit. You can suspend, multi-snapshot, revert to, shut down, turn on, turn off, reset, deploy, undeploy, clone, archive, and access properties of virtual machines.
    • Shares a library of virtual machine templates across all services while keeping services isolated from each other.
    • Transfers configurations between services.
    • Deploys a whole configuration or portions of a configuration.
    • Provides an annotated history of actions on a configuration.
    • Sets up virtual machines in a configuration to boot in a controlled sequence.
  • Service Archive
    • Quickly archives service configurations for regulatory and IT process compliance.
    • Quickly restores or replicates archived configurations to respond to requests for information or regulation.
    • Exports and imports configurations for third-tier archival storage.
  • Deployment
    • Provides browser-initiated deployment.
    • Automates load balancing of virtual machines deployed on ESX Server hosts.
    • Provides "fenced" networking for side-by-side execution of cloned configurations.
    • Sets lease times to automatically undeploy expired configurations.
    • Leverages VMware DRS for optimum virtual machine placement across resource clusters.
  • Templates for Virtual Machines
    • Offers cloning and modification of existing templates to create new templates.
    • Imports pre-existing virtual machines from disk or VirtualCenter for use as templates.
    • Leverages VMware Converter to bring physical systems into the service lifecycle.
    • Quickly creates virtual machines from templates with a utility that customizes the IP address, machine name, security identifier (SID), and more.
    • Automatically assigns MAC and IP addresses.
  • Media Library
    • Tags media with descriptive attributes.
    • Makes media files available to virtual machines.
    • Serves as a central repository for application and operating system installation media.
  • Monitoring Stage Manager
    • Provides a comprehensive event and job log viewer.
    • Displays CPU and memory resource consumption.
    • Displays resources consumed on a per-service and per-stage basis.
  • Administration and Security
    • Grants user permissions on a per-service and per-stage basis.
    • Provides out-of-the-box support for LDAP.
    • Allows for administrative role assignment to multiple users.
    • Allows for self-managed user preferences.
  • Installation
    • Provides a standard Windows setup.exe installer for all components.
    • Attaches to VirtualCenter for deployment and computing resources.
    • Prepares ESX Server hosts for use by Stage Manager.
    • Automates the expansion of the resource pool by preparing additional hosts.

Requirements

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

ESX 3.5 Update 1 and VirtualCenter 2.5 Update 1 patches are required for using maintenance mode in VirtualCenter. If you do not use the Update 1 patches, you must unprepare an ESX Server host to put it in maintenance mode. For information about unpreparing hosts, see the VMware Stage Manager User's Guide.

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

  • Pre-Installation
    • Two servers from the ESX Server 3.5 HCL.
    • A VirtualCenter Server system.
    • Shared storage (NFS, iSCSI, or Fiber Channel).
  • Post-Installation
    • A Stage Manager Server system. This system can run in a physical or virtual machine.
    • A VirtualCenter Server system. This can be an existing VirtualCenter Server system that Stage Manager connects to, or a new VirtualCenter Server system managing only the hosts used by Stage Manager.
    • Two or more ESX Server hosts.
    • Shared storage.

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. VMware recommends the use of NTP on all systems.

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

Review the known issues for this release.

  • 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.
  • Multiple Stage Manager Server Systems Cannot Access the Same VirtualCenter Datacenter
    You cannot have two Stage Manager Server systems access the same VirtualCenter datacenter.
  • Sample Template Does Not Work After Upgrading from Beta 1 or Beta 2 to the Release Build
    When you upgrade to the release build (Build 1561), you cannot publish the sample template in Stage Manager under these conditions:
    • A user unpublishes the sample template at the time of the upgrade.
    • A user unpublishes the sample template after the upgrade.
    • A user clones the sample template after the upgrade.
    These conditions generate a message that the template does not have the required version of VMware Tools. Even if you deploy the template, you cannot install VMware Tools and use the guest customization feature of Stage Manager.
  • To address this message
    1. In the left pane, click Settings.
    2. In the Guest Customization tab, deselect the Only Allow Publishing of Templates With a Version of VMware Tools That Supports Guest Customization check box.
    3. Publish the template and click OK on the warning message.
    4. Navigate back to the Guest Customization tab and select the Only Allow Publishing of Templates With a Version of VMware Tools That Supports Guest Customization check box.

Review these knowledge base articles:

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.