VMware just posted an update to their VDI solution, VMware View Manager.  The latest version is a minor dot release upgrade to version 3.0.1.  However the update does contain a few new features such as the integration of ThinPrint to help with client printing and the ability to pass the machine name of the client device to the guest virtual machine. 

There are  also a number of fixes found in this release. 

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.

And the following issues were resolved in VMware View Manager 3.0.1:

• Delay in accessing View Portal page through View security server
  View security server maintains a set of connections for communication with the View connection server. If you deploy network infrastructure between the security server and the View connection server, the network infrastructure might break an established connection when it is not used for a period of time. The security server does not detect the break in connectivity until an attempt to reuse the connection is made and the TCP/IP stack times out. This might result in a delay of approximately 3 minutes for the View Portal page to load. This issue might occur only in environments where network infrastructure elements are configured to drop idle connections.

  This issue is fixed in View Manager 3.0.1. The fix provides for setting a flag on an active connection to indicate it should not be dropped even when not in use. 

• Performance issues with View Portal access when HTTPS port is queried on a regular basis
  Sending a non-SSL probe on the SSL port of connection server might cause the Connection Server to slow down. This might result in the following issues:

  • Slow web access to View Portal page
  • Native clients and WYSE terminals perform poorly

  The following error might be logged every thirty seconds in the View connection server logs:

  WARN <Thread-81> [Processor] Problem setting up HTTP connection: java.net.SocketException: Connection reset

  This issue is fixed in View Manager 3.0.1.

• Time zone is not displayed in Windows Vista virtual machines launched from View Client
  If you launch a Windows Vista virtual machine from View Client, the time zone entry for the registry key TimeZoneKeyName might not be displayed at the following location:
  
  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation
  
  This issue is fixed in View Manager 3.0.1. The fix provides for display of additional time zone information of the client, in Windows Vista and Windows 2008 operating systems.
• Dynamic drive redirection does not work through remote session
  You might need to disconnect or reconnect View Client for new drives/USB drives to be displayed in the virtual machine.
  
  This issue is fixed in View Manager 3.0.1. The fix enables dynamic drive changes to be reflected in the remote session and correctly handles device change notifications, and allows dynamic updates if redirection has been enabled.
• Windows Vista User Account Control (UAC) fails with VMware View installation
  If you use View Client to log in as a non-admin user on a Windows Vista virtual machine that has VMware View Agent installed and UAC enabled, and perform operations that require administrator privileges, the virtual machine might stop or fail. The following error might be written in the event log:
  
  Faulting application consent.exe, version 6.0.6001.18000, time stamp 0x47918d7b, faulting module wscredf.dll_unloaded, version 0.0.0.0, time stamp 0x490bbd79, exception code 0xc0000005, fault offset 0x100847c8, process id 0xc94, application start time 0x01c94405135a2147
  
  This issue is fixed in View Manager 3.0.1.

Click here to download VMware View Manager 3.0.1.