VMware

VMware View 4.6.1 Release Notes

Released 15 March 2012 | Build 640196 (View Manager), Build 349155 (View Composer)

Last Updated: 18 September 2012

These release notes cover the following topics:

What's New in View 4.6.1

This maintenance release includes the following components:

  • VMware View Connection Server 4.6.1, which also includes replica server, security server, and View Transfer Server
  • VMware View Agent 4.6.1
  • VMware View Client for Windows 5.0.1

VMware View 4.6.1 is a maintenance release that resolves some known issues in the previous releases. For details, see the Resolved Issues section.

VMware View 4.6.1 includes the following new features:

  • Bundled with View 5.0.1 View Client for Windows
  • 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 Release Notes.
  • 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

Internationalization

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 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.1 release.

View 4.6.1 Connection Server supports Japanese, French, German, and Simplified Chinese, but not Korean.

Top of Page

Compatibility Notes

  • VMware View 4.6.1 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.1 adds support for the following operating systems:
    • For View Agent: 32-bit and 64-bit Windows 7 Enterprise SP1 and Professional SP1.
    • For View Client: 32-bit and 64-bit Windows 7 Enterprise SP1 and Professional SP1.
    • For View Connection Server, security server, and View Transfer Server: 64-bit Windows Server 2008 R2 Enterprise SP1.

    For more information about system requirements, see the VMware View 4.6 Installation documentation or the VMware View 4.6 Upgrades 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.
  • 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

Resolved Issues

The resolved issues are grouped as follows:

Security

  • Previously, in View Agent the VMware XPDM and WDDM display drivers had buffer overrun conditions, and the XPDM display driver did not properly check for NULL pointers. Exploitation of these issues could have led to local privilege escalation on View virtual desktops.

    In order to remediate the problem, you must update the VMware View Agent in your current pre-4.6.1 View desktops. The XPDM and WDDM drivers are part of the View Agent.

    The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the names CVE-2012-1509 (XPDM buffer overrun), CVE-2012-1510 (WDDM buffer overrun), and CVE-2012-1508 (XPDM null point dereference) to these issues.
  • Previously, a cross-site scripting vulnerability in View Portal allowed for running a script in the browser of a user who clicked a URL containing a malicious request to the portal. The attacker would have needed to trick the user into clicking the malicious URL.

    The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2012-1511 to this issue.

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.

View Administrator

  • 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.
  • Previously, in View Administrator, the list of users and groups could display up to 1000 entries. If you used the filter to select a user outside the list, you would not be able to display information for that user. If you used the export option to create a .csv file of users and groups, that file was limited to including 1000 or fewer entries. This limit has been removed.
  • Previously, if you used a nonstandard port for vCenter Server (that is, a port other than 443), then when you attempted to enable View Composer, you would see the following error message: No View Composer server found. Either an incorrect port was entered or a network connection error occurred." This issue has been resolved.

View Client

  • Previously, if you launched View Client and selected the "Log in as current user" check box, connected to a View desktop, selected Options > Autoconnect to this Desktop from the menu bar, and then closed View Client and launched it again, you would occasionally not be able to connect to the desktop. This issue is resolved so that both aspects of single sign-on work correctly together.
  • 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.
  • Previously, if you had a script that used the ViewClient_Machine_Name environment variable to identify which View Client system was connecting to a View desktop, the behavior might not work correctly. For example, rather than using the location-based printing feature, you could use ViewClient_Machine_Name in a script to dynamically map the local printer to the View session and thereby achieve roaming printer functionality. Previously, the correct printer would not get mapped. An incorrect value would remain in the View desktop's Windows registry. This issue has been resolved.
  • Previously, if you configured location-based printing and assigned several printers to a client, the default printer used would be the last printer in the list, regardless of which printer was actually set to be used as the default. This issue as been resolved.
  • With regards to the virtual printing feature, occasionally, one or more printers available from your client system would not become available 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 using a smart card with View Client to connect to a security server, if you were using the PCoIP display protocol, when you entered the PIN, you would see the error message, "No user found for your certificate." Also the Event View would show the following errors: "Failed to convert SID" and "Unable to obtain user information from AD, error =1." This issue has been resolved.
  • Previously, enabling the "Use deduplication for Local Mode operations" setting in View could cause data corruption in the datacenter copies of View desktops. For more information, see KB 1028195.
  • 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 automatic pool.

Miscellaneous

  • Previously, when you configured kiosk mode, the user account name for the client had to start with the characters "custom-" or else use the MAC address. Now you can specify other prefixes for the account name. For instructions, see the "Usage Notes" section of the chapter about kiosk mode in the VMware View 5.0 Administration document. (The instructions are not included in the 4.6 version of the document.)
  • Previously, if linked-clone desktops with persistent disks (sometimes called user data disks) were deleted, you were always prompted to select whether you wanted the disk to be archived. For linked-clone pools that had been created with View 4.0 or earlier, regardless of your selection, the disks would be deleted. This issue has been resolved so that if the desktop was created with View 4.0 or earlier, you will no longer be prompted to archive the disk. The disk is deleted. You are prompted to archive the disk only if it was created in View 4.5 or later.
  • Previously and occasionally, when attempting to scan a ThinApp repository to import an application, you would get an error message, saying that the application was invalid. This issue happened when the application used as an entry point was an executable installed on the physical file system rather than in the package. This issue has been resolved.
  • Previously if you restarted View Connection Server, connections from View Clients to View desktops would be dropped. This issue is now resolved so that if you have direct connections between View Clients and View desktops, you can restart View Connection Server and these direct connections will not be dropped.
  • Previously, on rare occasions, for PCoIP sessions, View Client would suddenly disconnect from the View desktop, and attempts to reconnect would fail until you rebooted the View desktop. This issue has been resolved.
  • Previously, in situations of high network latency, such as if you were working from home and you played a YouTube video for a while (to trigger packet retransmission) and if you were frequently getting disconnected from your ISP, then you might find PCoIP connections to your View desktop getting disconnected more often than RDP connections. This issue has been resolved.
  • Previously, if you configured a View desktop to use a screen saver, occasionally when the screen saver was being used you had to move the mouse to dismiss the screen saver because pressing keyboard keys had no effect. This issue occurred only if you were using the PCoIP display protocol. If no password was set, the keystrokes would still be sent to the View desktop, even though the screen saver was still in use. 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":
    1. Open ADSI Edit.
    2. In the console tree, click ADSI Edit.
    3. From the Action menu, select "Connect to."
    4. In the "Select or type a domain or server " field, specify the server name as localhost:389.
    5. 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.
    6. Expand the ADAM ADSI tree, and expand OU=Properties.
    7. Select OU=Global and select CN=Common in the right pane.
    8. Select Action > Properties, and under the pae-NameValuePair attribute, add new entry suspendOnDisconnect=1.
    9. Restart View Connection Server.
  • Previously, if Lotus Notes was running in a Windows XP View desktop and you connected to that desktop from a Windows XP client system, any appointments in the Lotus Notes calendar that fell within daylight savings time were off by 1 hour. This issue did not occur if you connected from a Windows Vista or Windows 7 client system. This issue has been resolved.
  • 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.

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

  • Because VMware View Client for Windows 5.0.1 is bundled with VMware View 4.6.1 and because View 5.0.1 is available in Korean, whereas View 4.6.1 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 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.
  • 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.
  • 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