VMware

VMware View 4.6 Release Notes

View version 4.6 | 24 February 2011 | Build: 366101 (View Manager), 349155 (View Composer)

Last Updated: 6 May 2011

These release notes cover the following topics:

What's New in View 4.6

VMware View 4.6 includes the following new features:

  • Security servers can now accommodate PCoIP connections - Security servers now include a PCoIP Secure Gateway component. The PCoIP Secure Gateway connection offers the following advantages:
    • The only remote desktop traffic that can enter the corporate data center is traffic on behalf of a strongly authenticated user.
    • Users can access only the desktop resources that they are authorized to access.
    • No VPN is required, as long as PCoIP is not blocked by any networking component.
    • Security servers with PCoIP support run on Windows Server 2008 R2 and take full advantage of the 64-bit architecture.

    For more information, see the VMware View Architecture Planning document.

  • Enhanced USB device compatibility - View 4.6 supports USB redirection for syncing and managing iPhones and iPads with View desktops. This release also includes improvements for using USB scanners, and adds to the list of USB printers that you can use with thin clients. For more information, see the list of View Client resolved issues.
  • Keyboard mapping improvements - Many keyboard-related issues have been fixed. For more information, see the list of View Client resolved issues.
  • New timeout setting for SSO users - With the single-sign-on (SSO) feature, after users authenticate to View Connection Server, they are automatically logged in to their View desktop operating systems. This new timeout setting allows administrators to limit the number of minutes that the SSO feature is valid for.

    For example, if an administrator sets the time limit to 10 minutes, then 10 minutes after the user authenticates to View Connection Server, the automatic login ability expires. If the user then walks away from the desktop and it becomes inactive, when the user returns, the user is prompted for login credentials. For more information, see the VMware View Administration documentation.
  • VMware View 4.6 includes more than 160 bug fixes - For descriptions of selected resolved issues, see Resolved Issues.
  • Support for Microsoft Windows 7 SP1 operating systems
  • Support for Internet Explorer 9

Top of Page

Internationalization

View Client and online help for View Client are available in Japanese, French, German, and simplified Chinese. The following documentation is also available in these languages: VMware View Administration, VMware View Installation, VMware View Upgrades, and VMware View Architecture Planning.

Top of Page

Compatibility Notes

  • VMware View 4.6 is supported on the following versions of vSphere:
    • vSphere 4.1 or later
    • vSphere 4.0 Update 2 or later
    • VMware Infrastructure 3 version 3.5 Update 5 or later and VirtualCenter Server 2.5 Update 6 or later
  • For system requirements, see the VMware View Installation documentation or the VMware View Upgrades documentation.
  • 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 Upgrades documentation.

Top of Page

Known Issues

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.
  • Do not include the space character in the security server password. If the security server password contains a space, security server installation will fail with the message Unable to pair the Security Server with the specified Connection Server.
  • 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 not respond.
    Workaround: Make sure that the system locale matches the language of the version of Windows that you are using.

View Administrator

  • 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 Composer fails.
  • 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.

View Client

  • 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 Task Manager.
  • 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:
    • 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 Device Manager.
    Workaround: Upgrade your client system to Windows Vista SP1 or higher.
  • 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:
    • Show Common Tasks in Folders
    • Fade or Slide Menus into View
    Workaround: Workarounds are described in Microsoft KB article 819946 (http://support.microsoft.com/kb/819946). Do one of the following:
    • Turn off the Fade or Slide Menus into View visual effect
    • Use Windows classic folders
    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.

Smart Card

  • 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.
  • Enabling the "Use deduplication for Local Mode operations" setting in View can cause data corruption in the datacenter copies of View desktops. By default, this setting is disabled. For more information, see KB 1028195.
  • When you first log in to a checked out local desktop, the desktop might display the following error: There are currently no logon servers available to service the logon request. This issue is most likely to occur for a Windows Vista or Windows 7 guest operating system on a full virtual machine from a manual or automatic pool.
    Workaround: Below the error message on the guest desktop, click OK and log in manually. The error does not reoccur on subsequent logins.
  • 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.

View Composer

  • 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)

Miscellaneous

  • 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.
  • Do not set the video RAM size to greater than 30MB. If you do, vMotion will fail. (KB 1011971)
  • 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 operation.

Top of Page

Resolved Issues

The resolved issues are grouped as follows:

View Administrator

  • Occasionally, if the secure tunnel feature was enabled and a View Client attempted to establish a PCoIP connection to a View desktop, if there was a network interruption between View Connection Server and the View desktop when the session was being established, the end user got disconnected, but if you looked in View Administrator, the status would incorrectly state that the remote desktop session, or Console session, was still connected.
  • In the View Administrator Desktops inventory list, the Starts with filter type would not work correctly when you searched by Datastore name.
  • Adding more than 1500 View desktops to any one view management folder in View Administrator when creating desktop pools caused authentication failures when administrators attempted to log in to View Administrator.
  • Administrators could not connect to View Administrator through a load balancer that was off-loading SSL authentication and passing traffic over HTTP to View Connection Server, through port 80. When an administrator tried to log in, View Administrator displayed a nondescript Java window.
  • Using View Administrator to log a connected end user out of a View desktop sometimes failed. The log message "Preventing the View Client's 'Disconnect and logoff' option, because the username/password or PIN dialog is being shown" would be generated by the agent on the affected virtual machine. Disconnecting and reconnecting with the same end user would fail with a LOGOFF_IN_PROGRESS error until the session was truly logged out, either by using direct RDP or a vSphere console or by rebooting the virtual machine.

View Client

  • If you used View Client on a client system that had Windows 7 SP1, Internet Explorer 9 beta, Microsoft KB 2482017, or Microsoft KB 2467023 installed, the client would not be able to establish a connection to View Connection Server.
  • With some thin clients and zero clients that use PCoIP, occasionally the display resolution would change to only 800 X 600, even though a higher resolution was set, or a phantom second monitor would appear on a single-monitor display if the desktop belonged to a pool that was configured for two monitors.
  • With the PCoIP remote display protocol, pressing the Break key or the Windows Pause key would sometimes not behave as expected. The Break and Pause keys use Windows key code 19 and BIOS key code 69. With PCoIP, the Windows key code generated would be 19, but the BIOS key code generated would be 0. Therefore, for applications that used the BIOS key code, pressing the Break or Pause key might not behave as expected.
  • Users connecting to remote desktops with PCoIP could not use the Ctrl+Alt+Del or Ctrl+Alt+Ins if they pressed the Delete key or the Insert key in a numeric keypad in some keyboards.
  • If you clicked Cancel during View Client with Local Mode installation while it is copying files, and then ran the installer again, the installation would fail.
  • Authentication might fail if you used RDP to connect to a desktop session that was running a Windows XP guest operating system on a virtual machine with two CPUs. No desktop was displayed and the Windows login dialog reappeared. The issue was more likely to occur if you logged in several times without rebooting the guest system, or if you used SSO with View.
  • View Connection Server would occasionally not clear its internal JMS cache properly unless it was restarted. This situation prevented end users from being able to connect to their View desktops.
  • When View Client attempted to connect to a Windows 7 desktop using PCoIP, a blank black screen would appear instead of the Windows Security dialog box if the Windows 7 desktop failed to perform single sign-on, for example, if the desktop did not join the domain.
  • Previously, if you attempted to use USB redirection with printers that use a DOT4 USB printer driver, such as are used in newer HP printers, printing would not work.
  • Using a USB scanner sometimes caused View desktops to stop responding and resulted in an error message on a blue screen.
  • When the Autoconnect USB Devices feature was enabled, either from the Connect USB Device menu item, or through the command-line option "wswc -connectUSBOnInsert true", or by enabling the GPO called "Connect USB devices to the desktop when they are plugged in," USB redirection would sometimes fail on some devices if you plugged in multiple devices to a client system at the same time.
  • In large and complex Active Directory environments, logging in to View desktops with a smart card sometimes timed out as a result of searching through all alternateSubjectNames formats such as RFC822 when extracting the list of UPNs.
  • Previously, you could not use USB redirection with an iPad. Now, with View 4.6, you can connect and sync an iPod Touch, iPhone, or iPad to View Client systems so that the View desktop can see and manage devices with an iOS operating system.
  • If you ran Lotus Notes on a local client system when you also had View Client running and if you were using PCoIP, if you then opened an email on the local client and the email had a Lotus Notes (.nsf) file attachment, clicking the button for selecting or deselecting the attachment would not work.

View Composer

  • Previously, if you started a refresh or recompose operation on two or more pools at about the same time, if these pools were managed by the same vCenter Server and were set to do the same kind of operations, the operations of one pool would have priority over the others. With View 4.6 all pools have their operations added to the operation queue in a round-robin fashion.
  • Occasionally, when you attempted to start a recompose operation on a large desktop pool, containing, for example, 500 desktops, the operation would fail, and in the vSphere Client the status for the vCenter Server task would say, "Unable to execute requested operation for VM in the current state (power off)".
  • Windows XP desktops that used QuickPrep for customization spent unnecessary time removing service dependencies.

Miscellaneous

  • Changing non-critical options in the vCenter Server Settings dialog in View Administrator caused View to reconnect to vCenter Server, which interrupted current provisioning tasks, causing them to fail. If the option to stop on error was enabled, the current provisioning failure might have caused provisioning to stop for the pool. For example, provisioning stopped if you changed the vCenter Server description. Provisioning stopped even if you did not change any options in the dialog and clicked OK instead of Cancel.
  • Occasionally, if a desktop was set to be refreshed or deleted after log-off, the desktop was not refreshed or deleted but instead was reused. This situation sometimes arose if the user had reset the desktop, shut it down without logging off of View Client, or exited unexpectedly, such as might happen when the ESX host was restarted. With View 4.6, the desktop is now marked as "Already used" so that it will not be used again. Administrators can manually refresh or delete such desktops.
  • When provisioning linked-clone desktops with the View 4.5 Agent and Danish Windows XP operating system, the desktops failed to join the domain. A "Customization failed with: 6" error was generated.
  • Occasionally, when using the View PowerCLI Cmdlets, if you have multiple vCenter Servers and you use get-desktopvm, some of the returned values might be incorrect.
  • In some environments it was possible to configure domain filtering using vdmadmin to exclude multiple domains such that the trust enumeration code would continuously loop. If this happened, you might see the following behavior:
    • View Administrator would not list any of the domains.
    • The VMWare View Framework Component service might crash.
    • Restarting the VMware View Connection Server service might fail.

    Eventually, View Connection Server might go into an unusable state.

Top of Page