VMware

VMware Virtual Desktop Manager (VDM) 2 Release Notes

Features | Documentation | Knowledge Base | VDI Community | VDM Community

Notes on VMware VDM 2.1, Build 596

Build 596 is a release build of VMware VDM 2.1.

The release notes contain the following:

New in VDM 2.1

VDM 2.1 includes the following improvements and new features

  • Pools spanning datastores in order to better manage resources
  • Localization of VDM Web Access and Client for Windows in Japanese and German
  • Command line parameters for VDM Client
  • Integrate MMR multimedia extensions DLL with VDM Client (Windows XP)
  • Allow end users to change password
  • Multiple sessions per user within a pool
  • Improvements to logging
  • Allow end users to restart their VM
  • Defined process for bulk import of individual desktops
  • VDM Configuration Backup (command-line only)
  • Allow blocking of incoming RDP connections that are not from VDM Clients
  • Allow VDM administrators to set default desktop (command line only)

Key Features in VDM 2.1

VDM has the following key features

End-to-End Functionality

  • Central administration of desktops from any location — Manage virtual desktops in a data center where you can more easily perform upgrades, patches and desktop maintenance.
  • Scalable management — Store and manage thousands of virtual desktops on hundreds of physical servers from a single management console.
  • Streamlined provisioning — Deploy new desktops in minutes instead of days or weeks using automatic desktop provisioning.
  • Desktop isolation — Give each end user an isolated virtual desktop and help to eliminate the availability and performance problems associated with shared application technologies.
  • Failure redundancy — Enable a high level of fault tolerance for your virtual desktop infrastructure with robust technology for connection redundancy and reliability.

Enterprise-Class Connection Brokering

  • Access management — Deploy VMware Virtual Desktop Manager (VDM) to manage user access to centralized virtual desktops.
  • Flexible provisioning — Deploy individual desktops for each user or create persistent and non-persistent desktop pools.
  • Strong network security — Protect sensitive corporate information using SSL tunneling to ensure that all connections are completely encrypted.
  • Support for strong authentication — Strengthen access control through two-factor authentication using RSA SecurID®.
  • Complete integration with Microsoft® Active Directory — Control access to centralized desktops using your existing directory services infrastructure.
  • Flexibility — Provide end users with their own desktop that they can customize to suit their needs and access from anywhere, or provision desktops that are more restricted and revert to a known consistent state upon log-off.
  • Access to local devices — Allow users to access local printers, USB devices and other peripherals.

Before You Begin

Before you begin with installation and configuration of VMware VDM, see the following guidelines.

General Installation Guidelines

The following guidelines apply to all installations types (new installations and upgrades).

  • Synchronize time — Make sure that you have synchronized time across VDM Connection Server and desktop virtual machines.  By default, virtual machines pick up the time from the ESX host at boot up and you may have to synchronize time on the ESX hosts through the ntpd service.
  • Validate your Internet Explorer settings — VDM Client uses Microsoft Internet Explorerô internet settings, including proxy settings, when connecting to VDM Connection Server. Ensure that your Internet Explorer settings are accurate and that you can access the VDM Connection Server URL through Internet Explorer.
  • Before creating an automatically provisioned desktop pool, do the following:
    • Validate the VirtualCenter guest customization specification if you intend to use one — Make sure that the guest customization specification in VirtualCenter is accurate. You should use VirtualCenter to deploy and customize a VM from your template using that customization specification and fully test the resulting VM (in other words, DHCP, authentication) before using that customization specification in VDM Administrator.
    • Validate network ports on ESX — Make sure you have a sufficient number of ports on the virtual switch which is used for the guest VMs. The default value for ESX server is 24; it may not be sufficient when creating a large pool of desktop VMs.
  • Install required Microsoft Windows patches — For Windows XP desktop VMs, make sure you have RDP patches referenced by Microsoft Knowledge Base (KB) articles 323497 and 884020.  Failure to do this may result in a Windows Sockets failed error message on the client.  You can find these KB articles at the following URLs:
  • It is recommended that you upgrade VDM Client machines to use Microsoft Remote Desktop Connection (RDC) 6.0 — This recommendation applies to machines running Windows XP and Windows XPe. Windows 2000 does not support RDC 6.0.Windows Vista comes with RDC 6.0 installed.

    RDC 6.0 can be downloaded at the following Microsoft download site: Microsoft downloads

  • VDM does not support using link-local (169.254.x.x) addresses for desktop virtual machines — Configure desktop virtual machines to use DHCP or static IP addresses.

Backing up Configuration Data (VDM 2.1 and later)

VMware recommends that you backup configuration data. For information about backing up configuration data, see the VMware technical note at the following URL:

http://www.vmware.com/pdf/vdm_config_data_export_import.pdf

Upgrading VDM

VDM supports upgrading from the released build of VDM 2.0 to the released build of VMD 2.1. Keep in mind the following issues when upgrading VDM Clients:

Troubleshooting VDM

The following URLs for VMware KB articles contain troubleshooting information for VDM. The KB articles are continually updated with new troubleshooting information.

Fixed Bugs

Known issues fixed in VDM 2.1

Known Issues and Restrictions

This section contains known issues and restrictions for all versions of VMware VDM.

Known Issues and Restrictions in VDM 2.1

The following are known issues and restrictions for VMware VDM 2.1. The items listed in this section are links to Knowledge Base articles.

VDM Administrator

VDM Connection Server

VDM Web Access

VDM Client

USB Redirection

The USB redirection feature of VDM Client provides generic support for redirecting locally attached USB devices to the desktop virtual machine. The feature has been successfully tested with a range of devices, including printers, scanners, mass storage devices, phones and PDAs. See the KB article at the following URL for details about known issues with redirecting specific USB devices in VDM http://www.vmware.com/info?id=346 .

Known Issues and Restrictions in VDM 2.0

The following are known issues and restrictions for VMware VDM 2.0. The items listed in this section are links to Knowledge Base articles.

VDM Administrator

VDM Connection Server

VDM Web Access

VDM Client

USB Redirection

The USB redirection feature of VDM Client provides generic support for redirecting locally attached USB devices to the desktop virtual machine. The feature has been successfully tested with a range of devices, including printers, scanners, mass storage devices, phones and PDAs. See the KB article at the following URL for details about known issues with redirecting specific USB devices in VDM http://www.vmware.com/info?id=346 .