VMware View Manager 3.1.3 Release Notes
View Manager Version 3.1.3 | 05 May 2010 | Build: 252693 (View Manager), 161885 (View Composer)
Last Updated: 05 May 2010
These release notes cover the following topics:
What's New in View Manager 3.1.3
VMware View Manager 3.1.3 is a maintenance release that resolves some known issues in the previous releases. Refer the Resolved Issues section for more details.
Before You Begin
Before you begin installing and configuring VMware View components, review
the General Installation Guidelines section.
Important: View 3.1.3 does not support VMware vSphere. View 3.1.3 supports the VMware Infrastructure versions listed in the System Requirements section of the VMware View Manager Administration Guide and VirtualCenter 2.5 Update 6 and ESX 3.5 Update 5.
General Installation Guidelines
The following guidelines apply to all installation types (new
installations and upgrades).
- Install VMware Infrastructure 3 version 3.5 Update 3 or above – Install VMware Infrastructure 3 version 3.5 Update 3 or above if you want to use View Composer or Offline Desktop features.
When upgrading, strictly follow the recommendations in the VMware VirtualCenter Upgrade Guide.
- View Client with Offline Desktop is an experimental feature. Install the VMware View Client with Offline Desktop if you want to use Offline Desktop.
View Client with Offline Desktop cannot be installed on the same machine as VMware Workstation, VMware ACE, VMware Player, or VMware Server.
- View Client, View Client with Offline Desktop, and View Agent cannot be installed on the same machine.
- Synchronize time – Use the VMware Tools time synchronization function to ensure that virtual machines are synchronized to ESX. ESX must synchronize to an external NTP source, for example, the same time source as Active Directory. For additional information, see Timekeeping in VMware Virtual
Machines information guide.
- Validate your Internet Explorer settings – View
Client uses Microsoft Internet Explorer internet settings, including proxy settings, when
connecting to View Connection Server. Ensure that your Internet Explorer settings are
accurate and that you can access the View Connection Server URL through
- Before creating an automatically provisioned desktop pool,
do the following:
- Validate the vCenter guest customization
specification if you intend to use one – Make sure that the
guest customization specifications in vCenter are accurate. You
should use vCenter to deploy and customize a virtual machine from your
template using that customization specification and fully test the
resulting virtual machine (in other words, DHCP, authentication) before using that
customization specification in View 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 virtual machines. The default value for ESX is 24, which might not
be sufficient when creating a large pool of desktop virtual machines.
- Install required Microsoft Windows patches – For
Windows XP desktop virtual machines, make sure you have RDP patches referenced by
Microsoft Knowledge Base (KB) articles 323497 (http://support.microsoft.com/kb/323497) and 884020 (http://support.microsoft.com/kb/884020). Failure to do this might result in a Windows Sockets failed error message on the client.
- Upgrade View Client machines to
use Microsoft Remote Desktop Connection (RDC) 6.x – This recommendation applies to machines running
Windows XP and Windows XPe. Windows 2000 does not support RDC
6.x. Windows Vista comes with RDC 6.x installed. RDC 6.x can be downloaded at the following Microsoft download site: Microsoft downloads
- View does not support using link-local (169.254.x.x)
addresses for virtual desktops –
Configure virtual desktops to use DHCP or static IP addresses.
- VMware View provides Common Access Card (CAC) support for Actividentity and Gemalto smart cards. View does not currently offer SSO support which enables single sign-on from a client device to a virtual desktop without requiring a user to re-enter a pin.
The known issues are grouped as follows:
- Administrator window does not list users after a query (KB 1013502)
If you press the F5 key to refresh the page while configuring a desktop pool, a Java error might be displayed.
Workaround: Do not press F5 to refresh the page. If the error appears, you must close all active Web browser instances and then restart them.
- When using View Administrator with Internet Explorer version 6, the OK and Cancel buttons on the Global Settings page (Configuration > Global Settings > Edit) might not be visible when the screen resolution is set to 800x600.
Workaround: Change the screen resolution to 1024x768.
- An authentication error is displayed if a non-ASCII value for the external URL is entered when configuring a View Server in View Administrator.
Workaround: Use only ASCII characters in the View Server External URL.
- Removing a View Manager ADAM Instance Causes an Error (KB 1007591)
MMR might fail after restarting a virtual machine in vCenter (KB 1013503)
- View Client for Windows supports connections to desktops using the HP RGS protocol. View Portal does not support RGS connections. Linux thin clients do not support RGS connections.
- Only HP Blade PCs, HP Workstations, and HP Blade Workstations are supported. virtual machines are not supported.
- Vista desktops are not supported.
- Only direct connections are supported. Tunnel connections are not supported.
- Smart cards (CAC) are not supported.
- Multiple monitors are not supported.
- When you are connected to a desktop using the HP RGS protocol, if you right-click a file, folder, or network connection, you might see a red screen and repeated Network connection warning errors. This problem occurs if you right-click an item to select that item and the following settings are turned on:
Workaround: Workarounds are described in Microsoft KB article 819946 (http://support.microsoft.com/kb/819946). Do one of the following:
- Show Common Tasks in Folders
- Fade or Slide Menus into View
Alternatively, select the item before you right-click it. To select an item, either click the item or rest the mouse pointer on the item.
- Turn off the Fade or Slide Menus into View visual effect
- Use Windows classic folders
- View Client fails to connect to the View Security Server if a standard server FQDN with localized characters is specified during security server installation.
Workaround: Specify the IP address of the standard server during security server installation.
- VMware View Client requires HTTP 1.1 to be enabled in Internet Explorer (KB 1011655)
- When a user connects to a desktop through multiple View Clients desktop sessions are disconnected (KB 1007581)
- View Portal on Mac OS does not support connection to Windows Vista desktops (KB 1007584)
Common Access Card
Offline Desktop (Experimental)
- On rare occasion, linked clone deletion might fail, with an error indicating that the MoID is missing.
Workaround: Manually delete the desktop from VI Client.
- If the system disk of a Master VM is configured as a dynamic disk, linked clones might fail to power on with a blue screen and Stop message 0x0000007B.
Configure the system disk of the Master VM as a basic disk, not a dynamic disk.
- Unable to remove source and replica virtual machines associated with View Composer desktop pools (KB 1008704)
- If the connection to the database is lost during linked clone operations (including linked clone creation, resynchronization, and destruction), View Composer might crash. View Composer will attempt to restart automatically, causing another crash which is logged as a Service cannot be started exception in the Windows event log.
Workaround: Restart the database server if it is not running. Then restart the View Composer service from the Windows Services control panel.
- Re-registering a linked clone in VirtualCenter changes the BIOS UUID of the linked clone (KB 1013505)
- During linked clone creation, the Desktop Sources tab in View Administrator indicates an error status and the error message View Composer agent initialization state error is logged. The error status appears after provisioning and customization.
Workaround: It is safe to ignore this status. After a couple of minutes, linked clone creation completes successfully.
- Active Directory credentials required to create a linked clone in View Composer (KB 1007697)
- Rebalance fails for existing virtual machines if linked clones are moved another local storage (KB 1007699)
- Non-ASCII user names and passwords for VirtualCenter are not recognized by View Composer. (KB 1007702)
- Static DNS server setting is lost when a recompose is performed from a Windows XP virtual machine to a Windows Vista virtual machine. (KB 1007707)
- Error message might appear when creating linked clones (KB 1007710)
- Virtual machine template list is not refreshed after creating a pool (KB 1007721)
- Cloned virtual machines might show Error state after a transient failure (KB 1007820)
The resolved issues are grouped as follows:
View 3.1.3 addresses a cross-site scripting vulnerability in View Manager. For an attacker to exploit the vulnerability, the attacker would have had to lure the user to click on the attacker's URL.
The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2010-1143 to this issue.
Install and Upgrade
View Connection Server now retains the existing Smart Card Authentication setting (set to Optional or Required in View Administrator) after upgrade.
- The value of the Number of days to keep production logs group policy setting determines how many days of log files are retained and therefore how many days of events can be displayed in View Administrator. The default value for this setting is 7.
In previous releases, it was possible to set the Show last ## days of events option in View Administrator to a value up to 31, regardless of the value of the Number of days to keep production logs group policy setting.
With 3.1.3, the setting for Number of days to keep production logs determines the maximum value for Show last ## days of events. However, if Number of days to keep production logs is set to a value greater than 100, only a value up to 100 can be selected. The default value for Show last ## days of events and Number of days to keep production logs is still 7.
With View 3.1.3, a new group policy setting has been added to determine whether the View Client window is always the topmost window. If Always on top is enabled, this setting prevents the Windows taskbar from obscuring a full-screen View Client window. This setting is enabled by default.
When using View Client and RES Subscriber at the same time, desktop sessions could freeze when starting a subscribed application in a desktop.
Setting the Enable the Shade View Client Configuration group policy setting to false no longer causes a desktop connection failure.
When two clients simultaneously logged in to an automated non-persistent desktop pool with the same user credentials, the user occasionally got connected to a different desktop if there were intermittent network problems. For a persistent desktop pool, the user was unable to reconnect to the desktop.
If the connection between View Client and the virtual desktop is dropped, for example due to poor network reliability, the user is forced to start a new connection and re-authenticate to reconnect to the desktop.
With View 3.1.3, the new Enable RDP Auto-Reconnect group policy setting has been added to take advantage of the automatic reconnect feature of RDP. This setting only needs to be enabled if poor connectivity causes re-authentication requests on reconnect. This setting is disabled by default.
You must upgrade both View Client and View Agent to be able to use this new group policy setting. This setting works for direct connections, but not for tunneled connections.
On rare occasion, View Connection Server services displayed an out of memory error, and the server had to be rebooted.
View Connection Server occasionally hung with an Out of memory Java heap space error due to pool information locking contention.
Occasionally desktops remained in the ConnectPending state after a connection was made. Users failed to connect with the error All sessions are busy.
In some cases, the desktop status did not change to Ready from Maintenance after recomposing or refreshing an automated persistent pool.
With View 3.1.3, the new Determines if the VMware View Client should use proxy.pac file group policy setting has been added that pertains to using a Proxy Auto Config (PAC) file with View Client. Usually, if Internet Explorer is configured to use a PAC file, View Client ignores this information. The new GPO tells View Client to use the PAC file to determine proxy settings. However, if you enable this group policy setting, View Client might
sometimes exit unexpectedly, particularly on multicore machines. If the group policy is not set, View Client can still work with a proxy server if Internet
Explorer is also configured with a fixed proxy server.
- A spurious fatal error message, Unable to load alternate GINA, was being written to the View Agent log file. This error message was reported when no additional alternate GINA chaining was configured on the View Agent machine.
When using View Portal or thin clients in a multiple connection server environment, the creation of Foreign Security Principals (FSPs) no longer causes conflict entries.
The View Connection Server service occasionally shut down when it couldn't allocate a 64K block of memory because the heap was heavily fragmented. A function that allocates 64K block of memory from the heap was only freeing a 63.5K block of memory. Now it frees the full 64K block.
- A handle leak occurred when certain registry keys (such as Forced DNS Name) existed, but the value of those keys did not.