VMware just released an updated version of it’s Desktop Virtualization (VDI) solution: VMware View Manager version 3.0.1.

This is an updated version which replaces the 3.0 version, with the previous version not available for download anymore, this release is a true bugfix release with some minor functionality improvements.

Below is a part of the information from the release notes:

What’s New in View Manager 3.0.1

View Manager 3.0.1 includes the following enhancements:

• Integrates the ThinPrint Virtual Channel Gateway module so that View deployments can communicate with ThinPrint server.
  Important: ThinPrint’s .print engine for VMware View must be installed on the target print server prior to installing View 3.0.1.
  Print jobs originating from virtual machines are subject to different licensing criteria on ThinPrint server. In order to provide the print server with information about the origin of a print request, View uses the TPVCGateway module as the print provider.
• Provides the capability for the Windows View Client to pass the machine name of the client device to the guest virtual machine.
  On the guest virtual machine, ViewClient_Machine_Name environment variable is set to represent the client machine name at initial login. It is also updated when the client reconnects to the guest virtual machine. In order to assist with third-party integration, a mechanism is provided to allow scripts to be executed on login and reconnect. The details of the scripts are held in a Windows registry key that can be set manually or by using a Group Policy Object (GPO). View Manager 3.0.1 provides an update to the vdm_agent.adm template to include this definition. The registry keys are
  HKLM\Software\Policies\VMware, Inc.\VMware VDM\Agent\Configuration\CommandsToRunOnConnect and  
  HKLM\Software\Policies\VMware, Inc.\VMware VDM\Agent\Configuration\CommandsToRunOnReconnect
  The commands to be run are defined as name=value pairs where the value is the command that is executed.  For example, to specify multiple commands, you can enter:
  Command1 = CMD /C c:\script1.vbs
  Command2 = CMD /C c:\script2.vbs
  Note: Other applications might have set the CLIENTNAME variable in some circumstances. In order to avoid collisions, this variable is not modified or updated.
• Contains bug fixes described in Resolved Issues.