VMware

Release Notes for VMware Lab Manager 3.0.1

Features | Documentation | Knowledge Base | Lab Manager Community

Last Document Update: April 21, 2009

Release date: November 06, 2008
Build number: 378

VMware Lab Manager is an application that enables you to create a shared virtual machine library that stores multimachine configurations in state and as a unit. Lab Manager also manages the ESX hosts through the VirtualCenter Server and the Lab Manager agent installed on those hosts. You can capture a complex and running software environment and share it instantly across your organization.

These release notes describe the following for Lab Manager 3.0.1.

New Features

This section describes the new features and performance enhancements available with Lab Manager 3.0.1:

  • New: Support for VMware Virtual Infrastructure 3.5 Update 4.
  • Support for running Lab Manager on English (US, UK, AUS), French, German, Italian, and Japanese versions of Microsoft Windows 2003
  • Optimization for higher scalability and lower response time
  • Support for VMware Virtual Infrastructure 3.5 Update 3
  • Ability to transfer ownership of Lab Manager objects such as network templates, virtual machine templates, configurations, and media files between different organizations.

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 VMware 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 or 3.0 to version 3.0.1.

  • To upgrade Lab Manager from version 3.0, install the Lab Manager 3.0.1 installer directly over 3.0.
  • To upgrade Lab Manager from version 2.5.x to 3.0.1, follow the same 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.
Caution: During the upgrade to Lab Manager 3.0.1, if you find any issue 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.
To add the virtual machines back to the Lab Manager, import each virtual machine after the upgrade.

Known Issues

This section describes known issues in this release.

Upgrading Lab Manager Fails When 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 group in 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.

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.

Workaround
Modify the following values in the configuration table in the database from true and false to 1 and 0 respectively:

  • AllowStaticIPAuto
  • AllowStaticIPManual
  • AllowDHCP
If you do not have access to an SQL server client:
  1. Copy the following SQL query into a text file.
    update config set value = N'1' where name = N'AllowStaticIPAuto' and CAST(value as nvarchar(4000)) = 'true'
    update config set value = N'0' where name = N'AllowStaticIPAuto' and CAST(value as nvarchar(4000)) = 'false'
    update config set value = N'1' where name = N'AllowStaticIPManual' and CAST(value as nvarchar(4000)) = 'true'
    update config set value = N'0' where name = N'AllowStaticIPManual' and CAST(value as nvarchar(4000)) = 'false'
    update config set value = N'1' where name = N'AllowDHCP' and CAST(value as nvarchar(4000)) = 'true'
    update config set value = N'0' where name = N'AllowDHCP' and CAST(value as nvarchar(4000)) = 'false'
  2. Save the text file as <name>.sql, where <name> is the name you want to give for the file.
  3. Log in as administrator and open a command prompt on the machine.
  4. Go to the directory where the <name>.sql file is saved.
  5. Run the following command:
    osql -E -S "localhost\vlm" -d "LabManager" -i <name>.sql

While Upgrading VirtualCenter to Update 3, Lab Manager Disconnects from VirtualCenter

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

Lab Manager Does Not Support Duplicate Names for Clusters, Resource Pools, and Standalone Hosts

Lab Manager 3.0.1 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 Machines Shows the Addressing Mode of NIC Incorrectly

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

Workaround
The details for the addressing mode of 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 as required other than the addressing mode, and save the settings.
  3. Remove the addressing mode from the network.

NICs Are Disconnected When Virtual Machines Are Powered On While Redeploying the Virtual Machines

If you power on a virtual machine during the redeploy-all operation on a host whose virtual machines are being redeployed, the NICs of that virtual machine are disconnected.

Workaround

  1. Go to the Properties page of the virtual machine.
  2. Disconnect each NIC.
  3. Again 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

While deploying a Linux virtual machine without a network connection, the virtual machine cannot retrieve the host name. When retrieving the host name the following error appears:
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|

Workaround
Ignore the error message.

Updated Values for Virtual Machine Memory and CPU Priority Are Not Reflected in Lab Manager

If you update the memory and CPU priority using Lab Manager for a virtual machine installed on a host that is not part of a cluster, Lab Manager and VirtualCenter do not reflect the changes.

Workaround
View the values 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 the user 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 required.

Starting or Stopping VMwareSLAMonitor Service Times Out When Upgrading to
Lab Manager 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, installer displays an Abort/Retry/Ignore dialog box.
Click Retry to continue the installation.
If retrying fails after a couple of times, click Ignore and continue the installation. After completing the installation, perform one of the following:

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

Using Lab Manager with HA Clusters

If you are using HA clusters with Lab Manager, disable the admission control.
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. 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 has 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 virtual NICs from virtual machines running a UNIX guest operating system, Lab Manager does not correctly remove references to the deleted NIC. 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 NIC 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-idMAC from the guest operating system of the virtual machine template.

SUSEPlugger 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 in virtual machines might cause problems with Lab Manager networking.

Workaround
Disable IP forwarding in all virtual machine 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
Disable the antivirus software from blocking outgoing e-mail or install a mail server on the same system on which the Lab Manager server runs.
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, ttylinux-4-ESX3, and a sample configuration, 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

Microsoft Windows NT Guest Operating System Does Not Support the None Network

Do not connect any of the NICs 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 Shows Error

When you try to deploy a virtual machine that did not have a MAC address, before it was upgraded to Lab Manager 3.0 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 virtual NIC with the same IP address.

Resolved Issues

This section describes the issues resolved in this release.

Character Limitation for Template and Configuration Names Removed

In Lab manager 3.0.1, there are no restrictions on the type of characters for the virtual machine template name and the configuration name. The names of the configuration machines can contain only 15 characters in Windows and 20 characters in Linux.

Customizing Deployment Lease When Creating Virtual Machine Templates and Workspace Configurations Is Ignored

In Lab Manager 3.0, the value you enter for the deployment lease while creating the virtual machine templates and workspace configurations is ignored. Lab Manager 3.0 uses the system default value when deploying the templates and configurations.
This issue is resolved in this release.

Lab Manager Does Not Support Active Directory Built-In or Predefined Groups

Active Directory includes a number of built-in groups like Account Operators, Administrators, Backup Operators, and so on, and predefined groups like Domain Admins, Domain Users, Enterprise Admins, and so on. Although you can add these groups to a Lab Manager organization, Lab Manager does not support these groups, and members of these groups are not able to log in to the Lab Manager Web console.
The issue is resolved in this release.

Guest Operating System Are Not Customized in Imported Configuration Virtual Machines

If you export a configuration that was never deployed (and never customized) and then import it, the virtual machines in the configuration are not customized when you deploy them.
The issue is resolved in this release.

NFS Media Store Directory Path Limitations

Lab Manager does not support symbolic links or root (/) when specifying the directory path for an NFS media store.
The issue is resolved in this release.

Modifying Lab Manager Installation ID

Installation ID is used to generate MAC addresses for virtual machines. If you have more than one Lab Manager installation in the same network, each installation must have a unique ID ranging from 1 to 63. Lab Manager randomly assigns an ID and allows an administrator to manually edit the IDs during ID conflicts.
When you change the installation ID, ensure that:

  • Machines and networks are powered off, and virtual machines are undeployed during this process. Lab Manager checks for deployed machines.
  • All users are logged out before changing the installation ID.
  • Users log in to the system only after changing the installation ID.
  • Administrators also are not using the Lab Manager during this process.
To change the Lab Manager Installation ID:
  1. In the left pane, select Resources and click the Hosts tab.
  2. Move the pointer over each host name and select Unprepare from the menu.
  3. In the left pane, click Settings, change the Lab Manager Installation ID, and click OK.
  4. In the left pane, select Resources and click the Hosts tab.
  5. Move the pointer over each host name and select Prepare from the menu.
  6. Click the Physical Networks tab.
  7. Move the pointer over the name of each physical network and select Properties from the menu.
  8. Specify a vSwitch for each host that uses the physical network and click OK.
If modifying the installation ID process fails, you must manually correct the Lab Manager networks. This might involve creating or deleting VirtualCenter port groups managed by Lab Manager.

Naming Physical Networks and Network Templates

Although Lab Manager allows you to create multiple physical networks and network templates with the same name, VMware does not recommend doing so. If you try to import a configuration that contains two or more physical networks with the same name, or two or more virtual networks with the same name, the import operation fails, and Lab Manager reports The configuration XML file is in an invalid format.
The 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.