What's New in View Manager 4.0.1

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

This release includes the following new features.

Localization of VMware View

The View Client and online help for View Client are now available in Japanese, French, German, and simplified Chinese. The View Manager Administration Guide, View Manager Release Notes, Getting Started with VMware View document, View Upgrade Guide, and View Architecture Planning Guide are also available in these languages.

VirtualCenter 2.5 Update 6 and ESX 3.5 Update 5 Support

View Manager 4.0.1 includes support for VirtualCenter 2.5 Update 6 and ESX 3.5 Update 5.

Enhancements to the PCoIP Display Protocol

PCoIP now supports the following features:

• Virtual Printing, which allows end users to use local or network printers from a View desktop without requiring that additional print drivers be installed in the View desktop.
• Single sign-on support for third party providers such as Sentillion and Imprivata.
• View Client supports international keyboards when using PCoIP.

For PCoIP-related bug fixes, see the View Client Resolved Issues section.

View Administrator

• Occasionally, when using View Portal to connect to a security server and access a View desktop, if the browser was Internet Explorer 7, the status of the View desktop was shown as Not Connected.
• During linked clone creation, the Desktop Sources tab in View Administrator gave an incorrect error status after provisioning and customization.

View Client

• Occasionally, when attempting to play a video in a View desktop, an error message was displayed: The application has failed to start because vdp_rdpvcbridge.dl was not found. The video played after clicking OK.
• If you used the Virtual Printing feature and attempted to print a page from a Firefox 3.x browser in a View desktop, garbage characters were printed.
• User authentication with the Giesecke & Devrient smart card called Smartcafe Expert 3 always failed.
• If you set a View Client policy for RDP settings so that users could not change the Windows display theme, the setting was ignored, and end users could change the theme in a View desktop.
• If you used the PCoIP display protocol, occasionally when you clicked to display a menu and then moved the mouse to another menu, one of the menus did not display correctly. Sometimes a keyboard delay also occurred.
• If you used View Client at the same time as other applications that attempted to always keep their window on top, the View Client froze. This situation occurred rarely, and usually with software that attempted to start local applications from within the View desktop.
• When View Client users connected to a Windows 7 desktop using PCoIP, the desktop console in the vSphere Client initially blanked out for privacy. However after several minutes, sometimes a small window screen of the desktop appeared in the View Client, like Restore Down.
• When connecting to a Windows 7 desktop using PCoIP, it sometimes took a long time for the connection to complete.
• When connected to Windows Vista desktops using PCoIP, if the guest system went into Sleep mode, the virtual machine put the guest into Stand by mode, causing the connection to hang and new connection attempts to fail.
• With View 4.0.1, a new group policy setting has been added that pertains to using a Proxy Auto Config (PAC) file with View Client. Usually, View Client follows Internet Explorer's proxy configuration. If Internet Explorer is configured to use a PAC file to determine proxy settings, View Client might sometimes exit unexpectedly, particularly on multicore machines. The new GPO tells View Client to ignore Internet Explorer's configuration regarding PAC files. Use this GPO if you use PAC files and have this specific problem. If the GPO is set, View Client can still work with a proxy server if Internet Explorer is also configured with a fixed proxy server.
• With View 4.0.1, you can now have a true multiple-monitor session when using a Windows 7 View Client to access a Windows 7 View desktop over Microsoft RDP. In a true multiple-monitor session, the Windows taskbar is displayed only on the primary monitor, and if you maximize an application window, the window expands to the full screen of only the monitor that contains it.

View Composer

• When creating a persistent linked-clone desktop pool, if you stored the user profile with the OS disk and did not use vSphere mode, the desktops that were created did not store the profile with the OS disk but instead were created with a user data disk.
• With View 4.0.1, when you run the support script on a View desktop, the View Agent support script now collects additional View Composer information and logs, including information about registry settings, profile redirection, SysPrep logs, and more.

Miscellaneous

• When connecting to a desktop using PCoIP, the keyboard locale in the desktop kept its original setting when the keyboard locale in the client operating system was Japanese.
• On a View desktop, the GINA (Graphical Identification and Authentication) did not always load, and you couldn't always to boot into Windows, if you uninstalled a third-party application that previously was part of a GINA chain. To avoid this issue, you had to uninstall View Agent before you uninstalled the third-party application.
• In View 4.0.1, the size of the RSA key in View Agent has been reduced from 1024 bits to 512 bits. This reduces the time required for message validation. You can configure the global size default of the RSA key. If you want to change it from 512 back to 1024, set pae-MSGSecOptions to "keySize=1024" in the same "OU=common" object as in pae-MsgSecPublicKey.