Lab Manager 2.4 Release Notes

Notes on VMware Lab Manager 2.4, Build 202

Build 202 is the GA build of VMware Lab Manager.

The release notes contain these topics:

For the latest and in-depth information on the product, see the online Lab Manager 2.4 documentation set at http://www.vmware.com/support/pubs/labmanager_pubs.html.

Late Breaking News

NEW: Lab Manager now supports software and hardware-initiated iSCSI storage. You do not need to upgrade your Lab Manager Server or Managed Server software to take advantage of this new storage platform. Refer to the VMware Infrastructure 3 online library at http://www.vmware.com/support/pubs/vi_pubs.html to set up iSCSI storage. (Specifically, click the Search tab, enter iSCSI, and see "Configuring Hardware-Initiated iSCSI Storage" and "Configuring Software-Initiated iSCSI Storage" in the Server Configuration Guide section.) After setting up iSCSCI storage using the VI Client, you must complete the setup in Lab Manager.

To set up iSCSI storage in the Lab Manager Web console

  1. In the left pane of the console, click Servers.
  2. Move the pointer over the Managed Server name and choose Properties from the menu.
  3. At the bottom of the page, select the appropriate iSCSI storage.
  4. Click OK.


NEW: The Lab Manager Server component of Lab Manager requires Service Pack 1 or above for Microsoft Windows Server 2003.


For details on all requirements and procedures to set up the product, see the VMware Lab Manager Installation Guide at http://www.vmware.com/support/pubs/labmanager_pubs.html. Make sure to review the hardware compatibility list for ESX Server 3.0.1 at http://www.vmware.com/support/pubs/vi_pubs.html.
NEW: Japanese customers must use ESX Server 3.0.1 (English version) on the Managed Server systems in Lab Manager.

Key Updates

Review the key updates for Lab Manager 2.4 since the Release Candidate (RC1) release:

  • Context-sensitive online help. Updated content is available.
  • Product documentation. Updated content is available.

Upgrade Notes

Refer to this section for upgrade procedures and related topics.

Upgrade Procedures (Experimental Guidelines)

You can upgrade Lab Manager from the public beta or RC1 version to the GA version.

To upgrade Lab Manager

  1. Uninstall only the program files for the Lab Manager Server.
    For instructions on uninstalling program files, see "Uninstalling Lab Manager Server" in the VMware Lab Manager Installation Guide at http://www.vmware.com/support/pubs/labmanager_pubs.html.

  2. Install the Managed Server agent software over the existing Managed Server installation:
    • On the existing Managed Server, log on as root.
    • Copy VMware-labmanager-agent-esx-2.4.0-<build number>.bin to the existing Managed Server.
    • To run the installer, type:
      sh VMware-labmanager-agent-esx-2.4.0-<build number>.bin
      The software automatically updates the Managed Server agent software.
  3. Stop Lab Manager statistics:
    • On the existing Managed Server, log on as root.
    • Type:
      vmware-watchdog -k lmstatistics
      kill `cat /var/run/lmstatistic.pid`
  4. Install the Lab Manager Server using the VMware-labmanager-server-2.4.0-<build number>.exe file.

    For guidelines, see "Installing the Lab Manager Server Software" in the VMware Lab Manager Installation Guide at http://www.vmware.com/support/pubs/labmanager_pubs.html. When prompted, confirm to complete the upgrade process.

    This upgrade installation skips some of the steps for a fresh installation and automatically configures the new software.

  5. From any machine with network access to the Lab Manager Server, launch Internet Explorer and go to
    http://<Lab Manager Server IP address or name>.

    You can also launch the same page from the desktop by double-clicking the VMware Lab Manager icon.

  6. Browse and select the file with the GA license key.

  7. You can proceed to use the Lab Manager Web console.

Upgrade Issues

Review these issues related to the upgrade process.

Upgrading Lab Manager with a Custom LM Tools ISO

If you upgrade Lab Manager and you had a custom LM Tools ISO, VMware recommends rebuilding the ISO to ensure the custom image contains the new LM Tools installer.

Upgrading from the Public Beta to the GA version Does Not Clear Existing Fence Leaks

If you upgrade from the public beta version of Lab Manager to the GA version, the Lab Manager Web console may display a message that the Managed Server does not have available fence networks.

To address the issue, complete these instructions to clean up any fence leaks:

  • From the left pane, click Servers.
  • Move the cursor over the Managed Server name and choose Disallow Deployments from the menu.
  • Move the cursor over the Managed Server name and choose Undeploy all and cleanup from the menu.
  • Confirm to undeploy all virtual machines.

If you do not want to undeploy the virtual machines to address the issue, contact VMware Support.

Upgrading Lab Manager Requires Removal of Agent Restart Crontab Entry

After you upgrade Lab Manager, you might need to remove an entry in the Managed Server agent restart crontab to avoid a daily restart of the agent:

  • Open the /etc/crontab file on the Managed Server for editing.
  • If the following line exists, remove it:
  • 02 4 * * * root service lm-agent restart

    If the line does not exist, you can stop this procedure.

  • Restart crond:
  • service crond reload

Lab Manager Server Labels Managed Server as "Unreachable"

After you upgrade Lab Manager from the RC1 version to the GA version, alter the Lab Manager settings in the Web console:

  • In the left pane, click Settings.
  • Increase the Managed Server Hung Timeout (Seconds) to 30.

This process makes Lab Manager less sensitive to heavy loads on the Managed Server systems that might cause Lab Manager to label a Managed Server as "unreachable."

Additional Issues and Bugs

NEW: Review these Knowledge Base issues:

Changing the IP Address of the Lab Manager Server (Moving the Lab Manager Installation) (KB 6310337)
Changing the IP Address of a Managed Server System in a Lab Manager Environment (KB 1360208)
SIDgen Generates Error Because Of Account Access to Folders (KB 4369788)
Latency Disparity Slows Down Virtual Machine Console in Lab Manager (KB 6557579)
LM Tools with SIDgen Fails on Windows 2000 With Mac Services (KB 2855541)
Networking Issues in Lab Manager Configurations Using Suse Linux 9.3 Templates (KB 1134059)
Lack of Network Connectivity Might Generate Errors During Import and Export Operations (KB 2116375)

You can also search for all Lab Manager KB articles.

Review these bugs:

Bug 115761: Using a Custom SSL Port

If you use a custom SSL port rather than the default port of 443 when accessing the Lab Manager application, use https://<website>:<custom port>/LabManager and change the URL appropriately for Lab Manager. Any links generated with Lab Manager, such as LiveLink, require you to append the custom-SSL port to the web site for accessing Lab Manager. Edit the URL of the Lab Manager desktop icon on the Lab Manager Server to include the custom port.

Bug 131273: Addressing the ImportSSLCert.vbs Error During the Lab Manager Server Installation

If you see a script error regarding the ImportSSLCert.vbs file (Error 0x80004100E Code 8004100E), reinstall IIS.

Bug 134950: Uninstalling MSDE Before Reinstalling Lab Manager Generates Error

If you uninstall Lab Manager Server, uninstall MSDE, and then reinstall Lab Manager Server, you may see an error regarding the C:\Program Files\Microsoft SQL Server\MSSQL$VLM\Data directory.

To address this error, navigate to the directory noted in the error message, delete LabManager.mdf and LabManager_log.LDF, and reinstall Lab Manager.