VMware View 4.6.2 Release Notes
Released 11 December 2012 | Build 916912 (View Manager), Build 349155 (View Composer)
Last Updated: 5 December 2012
These release notes cover the following topics:
What's New in View 4.6.2
This maintenance release includes the following components:
- VMware View Connection Server 4.6.2, which also includes replica server, security server, and View Transfer Server
- VMware View Agent 4.6.2
VMware View 4.6.2 is a maintenance release that resolves potential security and other known issues in the previous releases.
Top of Page
The View Client user interface, View Client online help, and Using VMware View Client
for Windows document are available in Japanese, French, German, Simplified Chinese, and Korean.
The following View 4.6 documents are also available in these languages: VMware View Administration, VMware View Installation,
VMware View Upgrades, and VMware View Architecture Planning. The View 4.6 documents still apply to this View 4.6.2 release.
View 4.6.2 Connection Server supports Japanese, French, German, and Simplified Chinese, but not Korean.
Top of Page
- VMware View 4.6.2 is supported on the following versions of vSphere:
- vSphere 4.1, Update 1, and Update 2
- vSphere 4.0 Update 2, Update 3, and Update 4
- VMware Infrastructure 3 version 3.5 Update 5 or later and VirtualCenter Server 2.5 Update 6 or later
- Supported browsers for View Administrator and View Portal include Internet Explorer 7, 8, and 9, as well as Firefox 3.6.24, 8.0, and 8.0.1.
- In addition to the supported operating systems listed in the VMware View 4.6 Installation document, VMware View 4.6.2 adds support for the following operating
- For View Agent: 32-bit and 64-bit Windows 7 Enterprise SP1.
- For View Client: 32-bit and 64-bit Windows 7 Enterprise SP1.
- For View Connection Server, security server, and View Transfer Server: 64-bit Windows Server 2008 R2 Enterprise SP1.
- You can download the latest versions of View Client for use with View 4.6.2.
For more information about system requirements, see the VMware View 4.6 Installation documentation or the
VMware View 4.6 Upgrades documentation.
- By default, View Clients require SSL for connections to View Connection Server. Therefore, if you do not configure View Connection Server to use SSL, HTTPS connections from View clients will fail, unless they connect to a load balancer or other intermediate device that is configured to make onward connections using HTTP.
- VMware View supports smart cards and smart card readers that use a PKCS#11 or Microsoft CryptoAPI provider.
- For information about compatibility between different versions of VMware View components, see the compatibility matrix
in the VMware View 4.6 Upgrades documentation.
Top of Page
In previous releases, when you launched View Administrator in a deployment without Internet connection, the browser displayed a blank page. This issue has been resolved.
The known issues are grouped as follows:
Installation and Upgrade
You cannot install View Transfer Server on a virtual machine that uses LSI SAS or PVSCSI disk controllers
and runs in vSphere 4 or later. If the virtual machine's guest operating system is Windows 2008, where LSI SAS
controllers are configured by default, you must ensure that the virtual machine has the proper disk-controller
configuration (LSI Logic Parallel) before you begin installing the operating system.
In a linked clone desktop, you cannot uninstall or upgrade View Agent from View 4.0.x and earlier releases to View 4.6. A View Composer
Agent error causes the upgrade installation to fail, and the linked clone virtual machine is left with no View Agent or View Composer
Agent, which leaves the virtual machine with no link to the View Composer base image.
Workaround: Upgrade View Agent to View 4.6 on the parent virtual machine and recompose the linked clone desktop.
Note: You can upgrade View Agent 4.5, starting with the View 4.5 RC build, to a later View release.
The version of VMware Tools that corresponds to vSphere 4.0 Update 1 and Update 2 includes driver versions that are incompatible
with View desktops. Symptoms can include a black screen instead of correct desktop display.
Workaround: Install View Agent in the guest operating system after the vSphere 4.0 Upgrade 1 or Update 2 version
of VMware Tools is installed. When you install View Agent, it includes the correct versions of drivers.
When you upgrade View Agent, a Files in Use dialog box appears if an older version of View Agent was previously installed with the
PCoIP Smart Card option selected.
Workaround: In the Files in Use dialog box, click Ignore to continue the installation.
If the system locale (set in Control Panel > Regional and Language options > Advanced > Language for non-Unicode
programs) does not match the language of the version of Windows that you are using, installation of the View Connection Server does
Workaround: Make sure that the system locale matches the language of the version of Windows that
you are using.
When you select a vCenter Server resource pool for a linked-clone desktop pool, View Administrator lets you select a vApp or a
resource pool. Linked clones must reside in a resource pool. If a vApp is selected, no linked clones are provisioned and View
In View Administrator, if you click the Events error or warning icon in the quick status panel, the Events page displays only
error or warning events. If you clear the Events filter, all event types are displayed. If you navigate to another View
Administrator page and again click the same Events icon in the quick status panel, the Events page displays all event types
instead of errors or warnings only.
In View Administrator, events are not refreshed automatically for persistent disks. Therefore when you navigate to the Events
tab of a persistent disk after detaching or attaching it, you might see the events from a different persistent disk.
Workaround: Click the Refresh button.
In View Administrator, if you enter a non-ASCII DNS server name in the network share path for a ThinApp repository, View fails to access
the network path and does not add it as a ThinApp repository.
Workaround: Create a DNS alias (CNAME) with ASCII characters to point to the server name. Use the CNAME in the network path.
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.
Because VMware View Client for Windows 5.0.1 is bundled with VMware View 4.6.2 and because View 5.0.1 is available in Korean, whereas View 4.6.2 is not, if you use
View Client on a Korean system, you will find that messages that originate from View Client are available in Korean, but messages that originate from View Connection
Server 4.6.x appear in English.
When the PCoIP GPO setting, "Disable sending CAD when users press Ctrl+Alt+Del," is enabled, the Send Ctrl+Alt+Del option in the
Options menu in View Client does not work. This GPO setting should disable sending CAD only when users press the Ctrl+Alt+Del keys in the View desktop.
- If you use PCoIP connections, audio input works with USB devices only.
If you lock and then unlock the client system while playing a video in the desktop with MMR enabled, playback does not continue.
When connected using RDP, View Client stops responding. When connected using PCoIP, you can seek in the media player but there
is no video or audio playback. Restarting the media player does not re-enable MMR, and View Client does not close when you
disconnect and log off.
Workaround: You must manually kill the wswc.exe and vmware-remotemks.exe processes in
When using RDP and a secure tunnel connection to the desktop, View Client might hang when you stop or pause a video with
MMR enabled on Windows clients.
Workaround: Use a direct connection to the desktop or use PCoIP instead of RDP if you have MMR enabled.
When certain codecs are installed on the client system and MMR is enabled, View Client might crash when playing a video in
Windows Media Player.
Workaround: Uninstall the codec.
In Windows 7 desktops when connected using PCoIP in multiple-monitor display mode, if you choose Show On: Monitor Generic
Non-PnP Monitor for any monitor other than the primary monitor in PowerPoint 2010, a black screen is displayed instead
of a slide show.
Workaround: If you are using PowerPoint 2010 in a Windows 7 desktop, you must use Show On: Primary
Monitor for a slide show.
When connected to a Windows 7 or Windows 2008 64-bit View desktop from View Client for Mac OS X, audio does not work.
If the Enable RDP Auto-Reconnect View Client Configuration group policy is enabled, USB devices are not automatically reconnected to the View desktop
after a direct RDP connection to the View Agent is lost. The USB devices are also not available on the client system.
Workaround: Deselect Connect USB Devices > device to make the USB device available on the client system. Then select
Connect USB Devices > device to make the USB device available in the desktop.
If you redirect a local USB drive to a desktop session, and disconnect or log out of the desktop session while writing data to the drive, an exFAT file system
on the drive might be corrupted. You might see an error such as the following when you attempt to write to the USB drive: Error 0x80071AC3: The operation
could not be completed because the volume is dirty. Please run chkdsk and try again.
Workaround: Before you redirect a USB drive to a desktop session, back up the files on the USB drive to another local drive. If the file system
on the USB drive does become corrupted, you can try to copy any valuable data from the USB drive to another local drive, although this operation might fail.
Reformat the USB drive, and restore the data from the backup copy.
For some newer USB printers, if the color setting for the printer on the local machine is different from the color setting in the Virtual Printer settings for the
View desktop, the local client settings take precedence. For example, if the client computer setting is to print in color but the Virtual Printer setting is to print
gray-scale, the document is printed in color.
When playing a video in a Vista desktop, playback controls are not visible if Windows Media Player is in full screen mode.
Multi-media redirection (MMR) does not play properly in a View Client PCoIP desktop when you connect a projector or external monitor to a laptop computer with
certain ATI graphics cards. Sometimes it displays only a black box.
On Windows Vista systems running View Client, the guest desktop user can access
a USB device that is in use on the client system if no locking mechanism is in place.
Notepad does not lock a file, whereas Word does.
If you try to connect to an NLA-enabled Vista machine from an NLA-enabled Windows XP client,
the connection fails with the error message An authentication error has occurred
(Code: 0x80090303). Remote Computer: <IP.Address>.
The same error occurs if you try to connect directly with RDP to the NLA-enabled Vista machine.
Workaround: You can connect from Windows Vista clients.
If you are running View Client on Windows Vista build 6.0.6000, you might encounter the following problems:
Workaround: Upgrade your client system to Windows Vista SP1 or higher.
- It is not possible to add a printer in the Control Panel.
- If you try to connect to a desktop using RDP, View Client hangs. The system log will include the error An internal communication error occurred.
Redirected printing will no longer function for a single user session. Check the status of the Terminal Services Device Redirector in the System folder of
If View Client is started from the command line using a command such as wswc.exe -serverURL <IP.Address> -domainName <domain_name>,
the user is prompted for a user name and password. If the user waits about 15 seconds and then clicks Cancel, the wswc.exe process
remains running until another View Client is launched interactively or from the command line.
Workaround: Manually stop the wswc.exe process.
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.
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
- 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
- Turn off the Fade or Slide Menus into View visual effect
- Use Windows classic folders
If you use ActivClient's smart card removal policy and set it to lock screen, after a client is disconnected and reconnected
using PCoIP, a No Reader message appears in the ActivClient agent tray and the desktop is not locked when the smart card is removed.
Workaround: Use the Windows smart card removal policy instead of ActivClient's smart card removal policy.
If you are using smart card credentials to log in and you want to switch protocols, you must log off and log on again.
If users remove their smart cards while they are logged in, the View desktop exits as expected.
However, on busy Windows Vista desktops, the following informational message might be delayed for one or two minutes:
Your smart card was removed, so you have been logged out of the View Connection Server.
Users accessing View Administrator might be prompted to select a certificate (KB 1007609)
View Client with Local Mode and View Transfer Server
If you set an SSO timeout limit for View users, and a user checks out a desktop for use in local mode, a checkout operation that takes longer than
the SSO timeout value causes the user's SSO credentials to expire. For example, if the SSO timeout limit is 10 minutes, and a checkout takes 20
minutes, the user must log in again to connect to the local desktop.
Note: By default, SSO is enabled with no time limit. An SSO timeout limit must be explicitly configured in View LDAP.
Workaround: Extend the SSO timeout limit.
If you are using ESX 3.5, when you check out a desktop and power it on for the first time using View Client with Local Mode, networking might not be ready inside
the guest because new network devices are being detected and drivers are being installed. This can cause failures to authenticate to the Active Directory domain
controller if cached credentials are not present.
Workaround: Networking works correctly on subsequent reboots. To avoid this problem, you can first connect remotely before checking out the desktop.
Do not reconfigure a powered off View Transfer Server using vSphere Client, for example to add memory. Reconfiguration
will cause View Transfer Server's required SCSI controllers to be removed.
Workaround: Make sure that View Transfer Server virtual machines do not require reconfiguration after
they are put into use. If reconfiguration is required, remove and re-add the View Transfer Server from View Administrator.
This will require a reboot.
If you edit a pool and switch the datastores on which persistent disks and OS disks are stored, View Composer cannot
rebalance linked clones that are affected by the switch.
For example, you might create a pool and store OS disks on datastore1 and View Composer persistent disks on datastore2.
Later, you might edit the pool and select datastore2 for OS disks and datastore1 for persistent disks. The rebalance operation
cannot move the OS disks to datastore2 or the persistent disks to datastore1.
View Composer skips the affected linked clones and rebalances linked clones that are not affected by the switched datastores.
When you create an automated pool of 100 or more desktops, View Composer does not warn you to limit the prefix name to 12
characters. In an automated pool, desktop names can be no longer than 15 characters, including the prefix name and the
autogenerated number. For example, if you create an automated pool with a 13-character prefix
and set the maximum pool size higher than 100 desktops, View Connection Server cannot provision more than 99 desktops.
Workaround: When you create an automated pool of 100-999 desktops, limit the prefix to 12 characters.
When you create a pool of 1,000 or more desktops, limit the prefix to 11 characters.
vSphere optimizes virtual machine cloning by using the SCSI data mover extended-copy feature. However, a side effect of this
optimization is that linked clone pool provisioning can be slowed down by concurrent full cloning tasks.
Workaround: Do not concurrently provision a linked clone pool and a large full clone pool if the two pools are on
the same SCSI array, sharing the same data mover. Similarly, do not configure a linked clone pool to share a SCSI array
with a full clone pool that uses the delete-desktop-after-logoff policy.
Linked clones that use BusLogic controllers might become unusable when recomposed to a base image that uses an LSI Logic controller.
Linked clones affected by this issue are unable to boot their operating systems, and the administration interface shows errors such
as: View Composer agent initialization state error (-1): Illegal state (waited 360 seconds).
There is no workaround. Changing SCSI type during a recompose is not a supported operation.
Sysprep Customized Clones of Windows Server 2008, Windows 7, or Windows Vista Virtual
Machines Prompt For Network Location Selection Upon Power On (KB 1008378)
If a user enters a non-ASCII View Connection Server name in View Client when connecting to a desktop, the ViewClient_Broker_URL environment
variable might not be set on the desktop.
On Windows 7, if you pin a View Connection Server or View Client desktop session in a jump list and reconnect to it with different connection settings,
the item might appear under both Pinned and Recent servers in the jump list.
To ensure that non-English versions of virtual applications that are captured by ThinApp display the correct language user interface,
during the ThinApp capture you must open the natively installed version on the capture machine before you start the post-scan
Top of Page