VMware

Release Notes for VMware Lab Manager 3.0.2

Features | Documentation | Knowledge Base | Lab Manager Community


Last Document Update: June 8, 2009

VMware Lab Manager 3.0.2 | March 19, 2009 | Build number: 56


VMware Lab Manager, a virtual lab automation system, enables you to automate the setup, capture, store, and share multi-machine software configurations. You can capture a running software environment and share it instantly across your organization. Lab Manager also manages the ESX hosts through VMware vCenter Server and the Lab Manager agent installed on those hosts.

These release notes contain the following sections:

New Features

This section describes the new features and performance enhancements available in Lab Manager 3.0.2:

Support for VMware Virtual Infrastructure 3.5 Update 4

Lab Manager 3.0.2 supports Virtual Infrastructure 3.5 Update 4. For information on ESX Server 3.5 Update 4, see VMware ESX Server 3.5 Update 4 Release Notes, and for information on VirtualCenter 2.5 Update 4, see VirtualCenter 2.5 Update 4 Release Notes.

Support for Firefox 3

Lab Manager supports Firefox 3. When you upgrade to Firefox 3, you must install the updated XPI when you are prompted to do so.
The following operating systems support Firefox 3 on Lab Manager:

  • Microsoft Windows Server 2003 Standard Edition
  • Microsoft Windows Server 2003 Enterprise Edition
  • Microsoft Windows XP

Support for Organization-Based Fencing policy

Lab Manager provides a new policy for organization-based fencing, where you can isolate or fence configurations within an organization. Administrators can set the default fencing options (fenced or unfenced) at the organization level. This fencing policy option is available when any user of the organization deploys a workspace virtual machine using the Deploy with Defaults option.
For more details on fencing, see the Understanding Fencing section in the User's Guide for Lab Manager 3.0.

Support for 64GB RAM for virtual machines

Using Lab Manager 3.0.2 you can create a virtual machine with 65532MB (64GB) RAM. For more information on creating a virtual machine, see the Working with Virtual Machine Templates section in the User's Guide for Lab Manager 3.0.

Support for remote desktop option for DHCP virtual machines

In this release, the Remote Desktop option in Lab Manager supports virtual machines that are configured for DHCP. For more information on DHCP networking in Lab Manager, refer the Static IP and DHCP Networking section in the Installation and Upgrade Guide for Lab Manager 3.0.

Support for Windows 2000

Lab Manager supports Microsoft Windows 2000 Professional operating system. In Lab manager 3.0.2, you can set Microsoft Windows 2000 Professional as the guest operating system for your virtual machines.

System Requirements

Lab Manager requires VMware Infrastructure 3 Standard or Enterprise (VMware 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).
Lab Manager does not work with VMware Infrastructure 3 Foundation or VMware ESXi 3.5. For details of all requirements and procedures to set up the product, see the Installation and Upgrade Guide for Lab Manager 3.0.
For information on hardware compatibility for ESX 3.5, refer the guides on hardware compatibility.

Upgrading Lab Manager

You can upgrade Lab Manager from version 2.5.x, 3.0, or 3.0.1 to version 3.0.2.

  • To upgrade Lab Manager from version 3.0 or 3.0.1, install the Lab Manager 3.0.2 installer directly over 3.0.
  • To upgrade Lab Manager from version 2.5.x to 3.0.2, follow the procedure detailed for upgrading Lab Manager 2.5.x to 3.0, in the Upgrading Lab Manager section in the Installation and Upgrade Guide for Lab Manager 3.0.
Lab Manager 3.0.2 supports in-place upgrades also. You do not have to undeploy virtual machines for the upgrade.

Caution: During the upgrade to Lab Manager 3.0.2, if you find any issues with the NFS virtual machine datastore and you delete the datastore, the virtual machines stored on that datastore are also removed from Lab Manager.

Although virtual machine data is available on the datastore, Lab Manager does not have references to the data. Lab Manager attempts to remount the NFS datastores of the previous version. If it fails to mount a datastore, use the information displayed by the Upgrade window to view the logs and troubleshoot the problem. You can use the VI Client to remove a duplicate datastore from vCenter Server, or you can verify that the NFS server is properly configured and accessible. After you resolve the problem, click Retry.

To add the virtual machines back to Lab Manager, import each virtual machine after the upgrade.

Known Issues

This section describes known issues in this release:

I/O error while deploying a template or a virtual machine in Lab Manager

In Lab Manager, deploying a template or a virtual machine in a configuration might fail with the VIM API displaying the following error:
I/O Error occurred
Workaround
Retry deploying the virtual machine or the template.

System message appears while upgrading Lab Manager to 3.0.x

While upgrading Lab Manager from 3.0.x to 3.0.x, if the installation contains fenced configurations, the following system message appears:
Virtual router which was POWERED ON has changed its state from VirtualCenter.
You can ignore this message.

Deploying a configuration fails when connected to a physical and None network

While deploying a configuration with two virtual machine templates, of which one is connected to the physical network and the other connected to a physical as well as a None network, deployment fails and Lab Manager displays the following error:
Folder does not exist.
Workaround
Reconnect Lab Manager to vCenter Server.

Installing Lab Manager fails on German Windows Server 2003 SP1

Installing Lab Manager fails on German version of Microsoft Windows Server 2003 Service Pack 1, Enterprise Edition. After clicking Next on the VMwareLMWeb Password window, the installation fails with the following error message:
Invalid password
Workaround
Install Lab Manager on Microsoft Windows Server 2003 Service Pack 2.

Uninstalling Lab Manager might result in an error

While uninstalling Lab Manager, Lab Manager might display the following error:
Setup Failed to Launch UnlockFolder.exe
Workaround
Click OK in the error text box. You can successfully uninstall Lab Manager.

Guest customization fails if configuration machine name contains period mark

If the name of a configuration machine contains period (.), guest customization fails.

Upgrading Lab Manager fails if the Windows user belongs to a Lab Manager group

If the user or the administrator who is installing Lab Manager belongs to a Lab Manager group, the Lab Manager upgrade installation fails and displays error 28047.
Workaround
Before upgrading, make sure that the user installing Lab Manager does not belong to any Lab Manager group such as VMwareLMClientAccts or VMwareLMServerAccts.
To remove the user from the group:

  1. On the Lab Manager server, click Start > Administrative Tools > Computer Management.
  2. In the console tree, click Local Users & Groups
  3. Open Groups.
  4. Double-click the Lab Manager group of which the user is a member.
  5. Remove the user installing Lab Manager, the Windows administrator, or any non-Lab Manager user, from the groups (VMwareLMClientAccts must have VMwareLMWeb, and VMwareLMServerAccts must have Network Service).
    To remove the user, select the user and click Remove.
  6. Log off Windows and then log on again.
  7. Proceed with the Lab Manager installation.

Lab Manager disconnects from vCenter when upgrading vCenter Server

When you upgrade vCenter and you have Lab Manager installed, allow vCenter to upgrade completely even when the Lab Manager is disconnected from the vCenter Server.
During the upgrade process, Lab Manager is disconnected from the vCenter and Lab Manager cannot perform certain functions. When Lab Manager loses the connection to the vCenter Server, Lab Manager attempts to reconnect. After upgrading vCenter completely, the connection from the Lab Manager to the vCenter is restored. If you want to connect immediately, you can force the connection process. For information on connecting Lab Manager to vCenter, refer Managing vCenter and Datacenters section in the User's Guide for Lab Manager 3.0.

Lab Manager does not support duplicate names for clusters, resource pools, and standalone hosts

Lab Manager does not support duplicate names for clusters, resource pools, and standalone hosts. When upgrading from Lab Manager 3.0, all duplicate names are automatically changed to avoid conflict.

Properties page of virtual machine shows incorrect addressing mode for NIC

If the addressing mode for a NIC is removed from the network, the Properties pages of virtual machines show one of the addressing modes that are available on the network. If you save the changes, the displayed addressing mode is saved for the NIC.

Workaround
The details of the addressing modes for NICs are available in the IP pool page of the configuration network and in the configuration detail list.
To change the virtual machine settings without disturbing the NIC addressing mode:

  1. Add the removed addressing modes back to the network.
  2. Modify the virtual machine settings other than the addressing mode, as required.
  3. Save the settings.
  4. Remove the addressing mode from the network.

NICs are disconnected while redeploying powered-on virtual machines

If you power-on a virtual machine during the redeploy-all operation on a host machine, the vNICs of that virtual machine are disconnected.

Workaround

  1. Go to the Properties page of the virtual machine.
  2. Disconnect each NIC.
  3. Go to the Properties page of the virtual machine.
  4. Reconnect each NIC.
This re-establishes connectivity.

Linux guest operating systems without network connections fail to retrieve host name

When you deploy a Linux virtual machine without a network connection, the virtual machine fails to retrieve the host name and displays the following error:
Could not look up internet address for <host name>. This will prevent GNOME from operating correctly.
It may be possible to correct the problem by adding <host name> to the file /etc/hosts.
|log in anyway|...|try again|

You can ignore the error message.

Updated values for virtual machine memory and CPU Priority are not reflected in Lab Manager

If you use Lab Manager to update the memory and CPU Priority for a virtual machine installed on a host that is not part of a cluster, Lab Manager and vCenter do not reflect the changes.
Workaround
View the values by using the VI Client connected to the host directly.

User cannot customize some user and group attributes of LDAP when using the Active Directory Connector

When using the Active Directory Connector for LDAP, you cannot customize the following attributes even when the UI allows you to edit the attribute field. These attributes are available under Settings > LDAP.

  • Group Membership Identifier
  • Membership
  • Object Class (in LDAP Group Attributes)
Workaround
If you want to enter customized values for the attributes of the Active Directory, use the OpenLDAP connector. You can use the Custom schema and set the values as required.

Starting or stopping VMwareSLAMonitor service times out when upgrading Lab Manager to 3.0.x

When upgrading Lab Manager 2.5.x to 3.0.x, starting or stopping the VMwareSLAMonitor service times out or fails.
Workaround
When VMwareSLAMonitor service times out or fails, the installer displays an Abort/Retry/Ignore dialog box.
Click Retry to continue the installation.
If retrying fails a couple of times, click Ignore and continue the installation. After completing the installation, perform one of the following:

  1. Reboot the Lab Manager server.
  2. Restart the SQL Server database-instance service (MSSQL$VLM).

Lab Manager displays an error when HA moves deployed virtual machines

When VMware HA moves deployed virtual machines in a configuration that uses fencing, Lab Manager might display the following system message: Virtual router external physical network adapter manipulated. If you are using HA clusters with Lab Manager, disable the admission control.
To restore network connectivity to the configuration:

  1. Undeploy the configuration.
  2. Save its state.
  3. Redeploy the configuration.

Windows Vista and Windows 2008 virtual machines report incorrect guest operating system

Windows Vista and Windows 2008 virtual machines created in Lab Manager 2.5.x, ESX Server 3.0.x, or VirtualCenter 2.x have an unrecognized guest operating system in Lab Manager 3.0. This might cause problems with customization. To address the problem, modify the virtual machine properties.
To modify the guest operating system for a virtual machine:

  1. In the left pane, click Workspace.
  2. Move the pointer over the configuration name and select Open from the menu.
  3. Move the pointer over the virtual machine name and select Properties from the menu.
    The Properties window appears.
  4. Set the correct guest operating system.
  5. Click Update.
To modify the guest operating system for a virtual machine template
  1. In the left pane, click VM Templates.
  2. Move the pointer over the undeployed virtual machine template name and select Properties from the menu.
    The Virtual Machine Template Properties window appears.
  3. Set the correct guest operating system.
  4. Click Update.

UNIX guest operating systems taking a long time to boot

When you remove vNICs from virtual machines running a UNIX guest operating system, Lab Manager does not correctly remove references to the deleted vNIC. This can cause delays in booting the guest operating system.
Workaround
Wait for the guest operating system to boot, or remove the files (ifcfg-ethn) that reference the deleted vNIC from the guest operating system.

Guest customization fails in SLES 9 virtual machines

When you install SLES 9 on a virtual machine template, the guest operating system creates a file that interferes with the guest customization in virtual machines based on the template.
Workaround
Remove the file ifcfg-eth-id<MAC> from the guest operating system of the virtual machine template.

SUSEPlugger related conflicts

Using SUSEPlugger in virtual machines might cause problems with Lab Manager guest operating system customization. To avoid conflicts, manually disable SUSEPlugger in all virtual machine templates.
To disable SUSEPlugger:

  1. Open the file ~/.kde/share/config/susepluggerrc.
  2. Remove the section that starts with [network ctrl].

IP Forwarding conflicts

Use of IP forwarding or DHCP servers in unfenced virtual machines or templates might cause problems with Lab Manager networking.
Workaround
Disable IP forwarding and DHCP servers in all unfenced virtual machines and templates.

Antivirus software blocks SMTP Email alerts from Lab Manager

Antivirus software can generate errors like the following:
The SMTP settings are not properly configured. Failed to send email: The message could not be sent to the SMTP server.
The transport error code was 0x800ccc15. The server response was not available.
Workaround

  1. Disable the antivirus software from blocking outgoing email or install a mail server on the system on which the Lab Manager server runs.
  2. Make sure that Lab Manager sends email through the local SMTP server.

Sample virtual machine template and configuration are not available

When you install Lab Manager, the installation includes a sample virtual machine template, called ttylinux-4-ESX3, and a sample configuration, called Sample Configuration. If Lab Manager is unable to prepare any ESX host during installation, the sample files are not installed.

Sample virtual machine template does not support customization script

The sample virtual machine template, ttylinux-4-ESX3, does not support the Customization Script option in the virtual machine template pop-up menu.

Microsoft SQL Server 2005 setup error

If you cancel the Lab Manager installer before it completes installing SQL Server 2005 and launch the installer again, the following error appears:
An installation package for the product Microsoft SQL Server Native Client cannot be found. Try the installation again using a valid copy of the installation package 'sqlncli.msi'.
Remove any installed SQL Server 2005 components before you install Lab Manager.
To remove SQL Server 2005 components

  1. On the Lab Manager server, select Start > Control Panel > Add or Remove Programs.
  2. Remove the following SQL Server 2005 components:
    • Microsoft SQL Server Native Client
    • Microsoft SQL Server Setup Support Files (English)
    • Microsoft SQL Server VSS Writer

Windows NT guest operating system does not support the None network

Do not connect any of the vNICs for Windows NT virtual machines or virtual machine templates to the None network.

Deploying virtual machine that did not have MAC address before upgrading to Lab Manager 3.0 results in error

When you try to deploy a virtual machine that did not have a MAC address before you upgraded to Lab Manager 3.0, Lab Manager displays the following error:
Error message: Virtual Machine <VM_Name>.vmx does not have ethernet device with MAC address nn:nn:nn:nn:nn:nn
Workaround
Reset the MAC address for the virtual machine and deploy it again.

Networks with overlapping IP pools

You must not create networks with overlapping IP pools. If you create physical or virtual networks with overlapping IP pools and use these networks in the same configuration, your host might have more than one virtual machine or vNIC with the same IP address.

Resolved Issues

This section describes the issues resolved in this release.

Unable to delete a disconnected datastore unless the host is unprepared

In the previous version of Lab Manager, you cannot delete a disconnected datastore unless the host is unprepared. In this release, you can delete a datastore if it is disconnected from all hosts. The following warning message appears when you try to delete the disconnected datastore: Deleting a datastore cannot be undone, and will remove all virtual machines from Lab Manager on this datastore.
The warning message window also displays the virtual machines that are deleted.

Efficient load balancing for I/O activities

In previous versions, all I/O activities occur through a single host. In this release, I/O load is distributed among the hosts that perform the I/O activity, whenever possible.

While importing virtual machine templates using Move option, Lab Manager copies and deletes them instead of moving the templates

In the previous release, while importing virtual machine templates from vCenter using the Move (delete original) option, Lab Manager copies the templates and later deletes them from vCenter Server. In this release, Lab Manager moves the templates completely from vCenter while importing them.

Upgrading Lab Manager from 2.5.3 to 3.0 fails

Upgrading Lab Manager from version 2.5.3 to 3.0 fails with the following error:
[Microsoft][ODBC SQL Server Driver][SQL Server]Conversion failed when converting the varchar value 't' to data type int.
This issue is resolved in this release.

Virtual machine shows an error when updating the properties

If you do not have the rights to edit CPU, memory, or network settings, the virtual machine displays the following error when you are updating the virtual machine properties:
Exception has been thrown by the target of an invocation
This issue is resolved in this release.

Live cloning in vCenter causes loss of Lab Manager virtual machine data

When you perform cloning in vCenter on a running virtual machine that is managed by Lab Manager, some of the data in the disk chain of that virtual machine might become unavailable to other virtual machines. This issue is resolved in this release.
You cannot clone Lab Manager virtual machines in vCenter.

SSMove might lose data when destination datastore is NFS

When you upgrade Lab Manager from 2.5.x to 3.0 or 3.0.1, and use SSMove with destination datastore as NFS, you might loose data.
This issue is resolved in this release.

Knowledge Base Articles

This section lists the VMware Knowledge Base articles published in this release. If you face any of the issues listed below, click the appropriate link or go to the VMware Knowledge Base and search using the article number.