VMware View 5.0.1 Release Notes
Released 15 March 2012 | Build 640055 (View Manager), Build 481620 (View Composer)
Last Updated: 15 March 2012
These release notes cover the following topics:
What's New in View 5.0.1
This maintenance release includes the following components:
- VMware View Connection Server 5.0.1, which also includes replica server, security server, and View Transfer Server
- VMware View Agent 5.0.1
- VMware View Client for Windows 5.0.1
VMware View 5.0.1 is a maintenance release that resolves some known issues in the previous releases. For details, see the
Resolved Issues section.
VMware View 5.0.1 includes the following new features:
- New bundled Mac OS X client - The new PCoIP-enabled View Client for Mac OS X is now bundled with this release.
For more information, see the VMware View Client for Mac OS X
- Client SSL requirement - View Client for Windows 5.0.1, View Client 1.4 for Mac OS X, and the other View 1.4 clients require SSL for connections to View
Connection Server. Therefore, you must enter a fully qualified domain name for View Connection Server, rather than an IP address, in the View Server field of View Client.
By default, View Client then checks the server certificate that View Connection Server presents. For more information, see the topics about configuring certificate
checking in the VMware View Installation document and in the Using VMware View Client documents for the various platforms of View Client.
Top of Page
The View Client user interface, View Client online help, and new Using VMware View Client
for Windows document are available in Japanese, French, German, simplified Chinese, and Korean.
The following View 5.0 documents are also available in these languages: VMware View Administration, VMware View Installation,
VMware View Upgrades, and VMware View Architecture Planning. The View 5.0 documents still apply to this View 5.0.1 release.
Top of Page
- VMware View 5.0.1 is supported on the following versions of VMware vSphere:
- vSphere 5.0 and Update 1
- vSphere 4.1 Update 1 and Update 2
- vSphere 4.0 Update 3 and Update 4
- For the View Composer and the View Events databases, in addition to the supported database server versions listed in the VMware View 5.0 Installation document,
Microsoft SQL Server 2008 R2 Express SP1 is now supported.
- 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.
- For more system requirements, see the VMware View 5.0 Installation documentation.
- View Client for Windows 5.0.1, View Client 1.4 for Mac OS X, and the other View 1.4 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.
Top of Page
The resolved issues are grouped as follows:
Install and Upgrade
Previously, you could not include the space character in the security server password or a trailing space at the end of the password. If the security server password
contained a space, security
server installation failed with the message Unable to pair the Security Server with the specified Connection Server.
Previously, on rare occasions, when you used the Add Pool wizard, the following error message appeared: "There was an error while trying to determine domains.
[errorcode=3,000]." This message indicated that one of the domain objects in Active Directory was corrupted. This issue has been resolved.
A memory leak issue associated with copying and pasting text was addressed and resolved.
Occasionally, if you used a View desktop on multiple monitors and had some application windows open on each monitor, if the View desktop session got disconnected and
then reconnected, some of the application windows would change size, position, monitor, or some combination of these. This issue has been resolved.
Previously, on rare occasions, View Client could not connect to View Connection Server, and the client logs indicated a failure of the AcquireCredentialsHandle API,
with a 0x80090305 error. This situation occurred because the message framework component of View Client failed to load the secur32.dll system DLL dynamically. This
issue is now resolved by linking secur32.dll statically in Messageframework.dll.
With regards to the virtual printing feature, occasionally, one or more printers available from your client system would not become availab le from within your View
desktop. Or you would see printers listed in the View desktop that were not available to your client computer but were available from a client computer that you
previously used to connect to your View desktop. This issue has been resolved.
Previously, on Japanese systems, if you used location-based printing, in the View desktop, if you went to the Printers and Fax dialog box, clicked Preferences, and
then went to the "Page Setup" and "Advanced" tabs, you would find that the text at the bottoms of these tabs was truncated. This issue has been resolved.
Previously, when you first logged in to a checked out local desktop, the desktop would sometimes display the following error: There are currently no logon servers available to service
the logon request. This issue was most likely to occur for a Windows Vista or Windows 7 guest operating system on a full virtual machine from a manual or
Previously, if you opened a command prompt in a View desktop and ran the set command, the list of environment variables displayed would sometimes not include the volatile
environment variables for View Client. This issue has been resolved.
Previously, you could configure dedicated View desktops to be suspended if users had logged out but not if they had disconnected without logging out. This issue has
been resolved so that you can now configure dedicated View desktops to be suspended when users disconnect. This functionality helps to conserve resources. To enable
"Suspend on disconnect":
- Open ADSI Edit.
- In the console tree, click ADSI Edit.
- From the Action menu, select "Connect to."
- In the "Select or type a domain or server " field, specify the server name as localhost:389.
- Under "Connection point," click "Select or type a distinguished name or naming context ", and then specify the distinguished name as DC=vdi,DC=vmware,DC=int
and click OK.
The ADAM ADSI Edit main window appears.
- Expand the ADAM ADSI tree, and expand OU=Properties.
- Select OU=Global and select CN=Common in the right pane.
- Select Action > Properties, and under the pae-NameValuePair attribute, add new entry suspendOnDisconnect=1.
- Restart View Connection Server.
Top of Page
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. 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 5.0. 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 5.0 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 Update 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.
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.
View Client and Remote Desktop Experience
In Table 8-7, "View Client Configuration Template: Security Settings" of the VMware View Administration documentation, in the row for Certificate Verification
Mode, the registry key pertains only to 32-bit View Client systems. The correct registry key to use for setting the CertCheckMode value on 64-bit Windows client
systems is HKLM\SOFTWARE\Wow6432Node\VMware, Inc.\VMware VDM\Client\Security.
For languages other than English, text might be truncated in the Configure SSL dialog box of View Client.
Workaround: Refer to the Using VMware View Client guide for an explanation of the various configuration options available.
This guide has been localized.
If RSA SecurID authentication is enabled and you use View Client in local mode without a network connection, if you then reestablish a network connection and attempt
to perform operations such as checking in the desktop or accessing a remote desktop, the client exits unexpectedly. Attempts to restart the client fail.
Workaround: Because the client process wswc.exe is actually still running when you attempt to restart the client, the restart fails. You must stop the
wswc.exe process before restarting the client.
On Japanese systems with the following configuration there is a problem with Japanese proportional fonts in Internet Explorer 9 on a View desktop: The client system
an be any number of supported platforms, such as iPad, Windows, zero client. The display protocol must be PCoIP, and the Windows7 3D rendering option must be enabled
in View Administrator. This issue is fixed in vSphere 5 Update 1 or later.
On 3D-enabled desktops, some users might experience increased latency when running applications that use native Windows APIs. The problem can be exacerbated when multiple monitors and the maximum (1920x1200) display resolution are configured.
Workaround: See In View 5.0, 3D-enabled Windows 7 desktops configured with multiple monitors at max resolution can have increased latency with certain Windows applications. (KB 2006611)
When a user presses Ctrl+Alt+Del in a PCoIP desktop session, the Ctrl and Alt keys are not released on the client host.
Workaround: Press Ctrl+Alt again.
On desktops that connect using PCoIP and are configured with multiple monitors, if a user plays a slide show in Microsoft PowerPoint 2010 or 2007, specifies a resolution, and plays the slides on the second monitor, part of each slide appears on each monitor.
Workaround: On the host client system, resize the screen resolution on the second monitor to the desired resolution. Return to the View desktop and start the slide show on the second monitor.
On desktops that connect using PCoIP, if users play slides in Microsoft PowerPoint 2010 or 2007 and specify a resolution, the slides are played at that chosen resolution and are not scaled to the current resolution.
Workaround: Choose "Use current resolution" as the playback resolution.
Although you can use multiple monitors for View desktops that have Windows XP and Windows Vista operating systems, some monitor configurations have issues. You must configure the maximum display resolution correctly. For example, to have a 1200x1920 monitor stacked on top of a 1920x1200 monitor, you must configure the maximum resolution to accommodate this combined height. A resolution of 2560x1600 would be appropriate in this case. This issue does not occur with Windows 7 View desktops.
When a large number of desktops are running concurrently, some desktops might display the following error dialog: "TPAutoConnect User Agent has stopped working."
Workaround: Restart the TPAutoConnect service. For example:
net stop tpautoconnsvc
net start tpautoconnsvc
If a user runs Adobe ConnectNow on a View desktop to share the screen with other users, black frames remain on the screen after the screen sharing begins.
When the PCoIP group policy 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 group policy 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 multi-media redirection (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 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 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.
On Windows 7 client machines, View Client exits when the smart card removal policy is triggered.
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
Occasionally with Windows 7 View desktops that have Windows Aero enabled, if you are using a laptop as a client system and you close the laptop, when you later open the laptop, the local mode desktop stops responding. Suspending the client system causes the local mode desktop to freeze.
Workaround: Resize the View Client window or minimize it and then restore it. The View desktop becomes locked and you can press Ctrl+Alt+Ins to log in again.
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.
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.
View Persona Management
Files and folders specified as exceptions to the "Files and folders excluded from roaming" and "Windows roaming profiles synchronization" lists do not show up in the user's desktop when a user logs in. For example, if you specify folder ABC in the "Files and folders excluded from roaming (exceptions)" group policy, and set the "Remove local persona at logoff" group policy, folder ABC does not appear when the user logs in.
Workaround: Manually create the exception folder on the desktop. View Persona Management downloads user data from the remote profile repository to the local folder. This workaround applies only to folders. There is no workaround for individual files that are configured as exceptions to the "Files and folders excluded from roaming" and "Windows roaming profiles synchronization" lists.
View Persona Management might not correctly replicate a user persona to the central repository if the desktop virtual machine is extremely low on disk space.
When you provision linked-clone desktops that are customized by Sysprep, some desktops might fail to customize.
Workaround: Refresh the desktops. If a small number of desktops still fail to customize, refresh them again.
If you upgrade a virtual machine with an IDE controller from Windows XP to Windows 7, take a snapshot of the virtual machine, and create a linked-clone pool, the linked clones cannot be customized, and pool creation fails.
Workaround: Add a SCSI controller and a disk to the virtual machine. Next, launch VMware Tools and install a VMware SCSI controller driver on the virtual machine. Next, take a snapshot and create the linked-clone pool.
Do not change the log on account for the VMware View Composer Guest Agent Server service in a parent virtual machine. By default, this is the Local System account. If you change this account, the linked clones created from the parent do not start.
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