VMware

Lab Manager 2.5.2 Release Notes

Notes on VMware Lab Manager 2.5.2, Build 131

The release notes contain these topics:

For the more information on the product, see the Lab Manager documentation web page and the VMware Knowledge Base (KB). To view Lab Manager KB articles, choose VMware Lab Manager in the Product menu and click Search.

What's New in This Release?

Lab Manager 2.5.2 adds support for ESX Server 3.5. Managed Servers while continuing to support ESX Server 3.0.x Managed Servers. Lab Manager 2.5.2 requires a homogeneous server pool. That is, it supports either ESX Server 3.5 Managed Servers or ESX Server 3.0.x Managed Servers, but not a mix of the two.

There are no incremental bug fixes or new features in this release other than support for ESX Server 3.5, so it is not necessary to upgrade if you do not intend to run ESX 3.5 Server Managed Servers.

NOTE: Lab Manager does not support ESX Server 3i, version 3.5.


Requirements

For details on all requirements and procedures to set up the product, see the Lab Manager 2.5.1 Installation Guide. Make sure to review the hardware compatibility list for ESX Server 3.0.x and 3.5 at:

Lab Manager requires Microsoft .NET Framework 2.0. You must install .NET Framework 2.0, or .NET Framework 3.0 or 3.5, which both include .NET Framework 2.0


Upgrading Lab Manager

You can upgrade to Lab Manager 2.5.2 from Lab Manager 2.5.1 or Lab Manager 2.5.0.

NOTE: You do not need to undeploy Lab Manager virtual machines in order to upgrade.

To upgrade from Lab Manager 2.5.x to Lab Manager 2.5.2:

  1. Back up the Lab Manager database.
  2. Uninstall Lab Manager Server 2.5.x (program files only).
  3. Install Managed Server agent 2.5.2 on each Lab Manager Managed Server, using VMware-labmanager-agent-esx-2.5.2-<build number>.bin.
  4. Install Lab Manager Server 2.5.2, using VMware-labmanager-server-2.5.2-<build number>.exe.

See "Upgrading Lab Manager" in the Lab Manager 2.5.1 Installation Guide for more information.


Upgrading ESX Server

Use the following procedures to upgrade your Managed Servers from ESX 3.0.x to ESX Server 3.5. The upgrade process requires downtime for your virtual machines, so make sure to read through the entire process and plan your steps before you begin.

Preparing for the Upgrade

In order to upgrade your Managed Servers to ESX Server 3.5, you must be running Lab Manager 2.5.2 with ESX Server 3.0.x Managed Servers. If you are currently running Lab Manager 2.5.1 or earlier, you must first upgrade to Lab Manager 2.5.2 as described in the previous section.

VMware recommends that you back up your Lab Manager installation prior to upgrading. See "Backing Up and Restoring Lab Manager" for more information.

Before Upgrading ESX Server

If you want to ensure that Lab Manager saves the memory state of your virtual machines before you undeploy them, choose Preferences from the Lab Manager web console. Click the Defaults tab and choose Save Memory State.

  1. Undeploy all virtual machines from all Managed Servers.
    1. From the Lab Manager web console, choose Manage > Servers.
    2. Move the pointer over a Managed Server name and choose Disallow Deployments.
    3. Move the pointer over the same Managed Server name and choose Undeploy all VMs.
    4. Repeat these steps for each Managed Server.
  2. Remove all Managed Servers from Lab Manager Server.
    1. From the Lab Manager web console, choose Manage > Servers.
    2. Move the pointer over a Managed Server name and choose Remove.
    3. Repeat these steps for each Managed Server.

Upgrading ESX Server 3.0.x to ESX Server 3.5

To upgrade Lab Manager Managed Servers, use the procedures included in the VMware Infrastructure 3 Upgrade Guide. Some of the information included in that document is not relevant to Lab Manager. Use the following information, in conjunction with the Upgrade Guide, to upgrade ESX Server in a Lab Manager environment.

  • The backup and restore strategies described on page 16 cannot be used in the Lab Manager environment (with the exception of the VirtualCenter Backup section). Use the recommended Lab Manager backup strategies instead.
  • Upgrading from ESX Server 3.0.x to ESX Server 3.5 is considered a "minor" upgrade.
  • Lab Manager datastores already use the VMFS3 file system and do not need to be upgraded.
  • Lab Manager virtual machines already use the VM3 format and do not need to be upgraded.
  • Only in-place upgrades are supported with Lab Manager; not migration upgrades.
  • Of the four stages described on page 23 of the Upgrade Guide, you only need to complete stages 1 (if you are using VirtualCenter) and 2A. Stages 2B and 3 do not apply in a Lab Manager environment. Do not perform stage 4 at this time. Upgrading VMware Tools within virtual machines can be accomplished after the rest of this procedure is complete, and the virtual machines can be deployed and powered on using the Lab Manager console.
  • There are three ways to upgrade ESX Server. You can use: the graphical installer (see page 69), the text-based installer (see page 71), or esxupdate (see page 75).

After Upgrading ESX Server

There a few final steps to complete the upgrade process:

  1. Run the Managed Server agent 2.5.2 installer (VMware-labmanager-agent-esx-2.5.2-<build number>.bin.) on each Managed Server.

    NOTE:You must perform this step, even though the Lab Manager 2.5.2 Managed Server agent was previously installed.
  2. Add the upgraded Managed Servers back to the Lab Manager Server.
    1. In the left pane, click Servers.
    2. Click Add Server.
    3. Enter the information for a Managed Server and click Next.
    4. Enter additional information about the Managed Server and click Add.
    5. Repeat these steps for each Managed Server.
  3. Redeploy virtual machines.

Known Issues and Bugs

Review these bugs:

VMware Update Manager and Lab Manager

Do not use VMware Update Manager in a Lab Manager environment. Update Manager is a plug-in for VirtualCenter 2.5 that provides security monitoring and patching support for ESX Server hosts and virtual machines.

Media greater than 2GB in size

ESX Server 3.5 does not support the use of media greater than 2GB in size when served from a SMB media share. If you use the Insert Media command in Lab Manager and select an ISO image that is greater than 2GB and stored on an SMB storage server, Lab Manager does not mount the image and reports an error. To work around this issue, store ISO images that are greater than 2GB on NFS storage servers or use ESX Server 3.0.x Managed Servers.

LM Tools and Microsoft Windows Server 2003 templates

Lab Manager customizes virtual machines (IP address, machine name, security identifier (SID), and more) using LM Tools. Users can specify the default LM Tools SID mechanism in Settings > LM Tools, where they can choose SIDgen or Sysprep. The option you should choose can be affected by the mix of Windows Server 2003 32-bit and 64-bit templates in your Lab Manager environment.

  • Windows Server 2003 (32-bit templates only):
    You can choose either SID mechanism. If you choose Sysprep, copy the Windows Server 2003 (32-bit) Sysprep files to the appropriate Lab Manager directory (for example, C:\Program Files\VMware\VMware Lab Manager Server\Tools\LMTool\Sysprep\win2k3) before building the custom LM Tools ISO.
  • Windows Server 2003 (64-bit templates only):
    SIDgen does not support 64-bit operating systems, so in this case, you must use Sysprep. Copy the Windows Server 2003 (64-bit) Sysprep files to the appropriate Lab Manager directory before building the custom LM Tools ISO. Windows Server 2003 has different Sysprep files for 32-bit and 64-bit, so make sure to copy the correct files.
  • Windows Server 2003 (32-bit and 64-bit templates):
    In order to support 64-bit, you must use Sysprep. Copy the Windows Server 2003 (64-bit) Sysprep files to the appropriate Lab Manager directory before building the custom LM Tools ISO. Since the Windows Server 2003 (64-bit) Sysprep files will not work for Windows Server 2003 (32-bit), you must modify the SID mechanism for your Windows Server 2003 (32-bit) templates. In the Machine Template properties page, choose SIDgen for all Windows Server 2003 (32-bit) templates.

Configurations based on Microsoft 2003 and XP templates require manual logon

If you deploy configurations that use Windows 2003 and Windows XP guest operating systems, autologin does not work because of an issue with the LM Tools utility.

The workaround involves manually logging on to the system to allow LM Tools to operate properly.


DHCP IP address allocation on virtual machine running Windows NT 4.0 fails

If you base a configuration on a Windows NT 4.0 SP6 template published with a static IP setting, and you select the DHCP IP address allocation option for a virtual machine in that configuration, Windows NT keeps the static IP setting of the template rather than the DHCP setting of the virtual machine.


Lab Manager cannot recognize changes to the VMkernel network configuration

If you make a change to the VMkernel network, such as adding or removing the VMkernel, Lab Manager might take up to five minutes (the default refresh period configured in the Lab Manager Web console) to notice the change. Errors might occur if you attempt operations before the refresh period.

If you need Lab Manager to become alert to the change earlier than the refresh period, restart the VMware LM Monitor service.


Inserting .vfd floppy files into virtual machines running on ESX Server 3.0.2 or ESX Server 3.5

You cannot use the Insert Floppy command to insert a .vfd format floppy file from the Lab Manager media library into a virtual machine running on ESX Server 3.0.2 or 3.5. The workarounds are:

  • Rename the file using a .flp extension
  • Use a UNC path to point to the .vfd floppy (ESX Server 3.5 only)

Upgrading Lab Manager Server on a system with multiple NICs fails

If you upgrade Lab Manager Server on a machine with two or more NICS that have static IP addresses, the installer might generate error 1720.

The workaround is to disable all NICs not associated with the current Lab Manager installation. The only active NIC left on the system must be the one with the IP address used by Lab Manager.