The strategy for upgrading View Agent depends on the type of desktop source.

This procedure provides an overview of the tasks you must perform to upgrade View Agent in a variety of virtual machines used as desktop sources. To complete some of these tasks, you might need the step-by-step instructions found in the vSphere Client online help or in the VMware View Administration document, available by clicking the Help button in View Administrator.


If you are upgrading View Agent from a version earlier than 4.5 and if you have used a group policy object (GPO) to disable Windows firewall, the installer returns one of the following errors and the upgrade is rolled back:

Error 28014. Unable to close the firewall.
Warning 28013 Unable to open the firewall.
Internal Error 28051 Shared Access.

If you encounter error 28014 or warning 28013, you must use a GPO to enable firewall services and run the installer again to upgrade the agent. If you encounter internal error 28051, click OK in the error message box to continue the upgrade.

Perform the following preparation tasks:

If you are upgrading ESX hosts and virtual machines, complete the procedure described in Upgrading ESX/ESXi Hosts and Virtual Machines.

Verify that you have a domain user account with administrative privileges on the hosts that you will use to run the installer and perform the upgrade.


On parent virtual machines and virtual machine templates, download and run the installer for View Agent 5.0.

You can download the installer from the VMware Web site. Step-by-step instructions for running the View Agent installer appear in the VMware View Administration document.


Take a snapshot of each upgraded parent virtual machine that you use to create linked-clone desktop pools with View Composer.

You use the new snapshot for recomposing all the virtual machines in the pool.

For instructions on taking snapshots, see the vSphere Client online help.


If you use full-clone desktops or other virtual machines that you added as individual desktops or as part of a manual pool, upgrade View Agent by using whatever third-party tools you usually use for software upgrades.

View desktops that were called individual desktops in View 4.0.x deployments are added to manual pools in View 4.5 and later versions. In the case of individual desktops, the manual pool contains only one desktop.


For automated and manual Windows 7 pools that are not linked-clone pools, to use the Windows 7 3D rendering feature available with View 5.0, edit the pool and power the virtual machine desktops off and on.


Configure the following pool settings:

Set the pool to use the PCoIP display protocol.

Set Allow users to choose protocol to No.

Turn on the Windows 7 3D Rendering feature.


Power off each virtual machine and power it on again.

Restarting a virtual machine, rather than powering off and on, does not cause the setting to take effect.


If you use Windows Terminal Servers or physical or blade PCs as desktop sources, download and run the installer for View Agent 5.0 on these physical machines.

You can download the installer from the VMware Web site.


Use a View Client that has not been upgraded to verify that you can log in to the upgraded View 5.0 desktop sources with your old View Client software.

If you use View Composer desktop pools, recompose or recreate the pools. See Upgrade View Composer Desktop Pools.

Upgrade View Clients. See Upgrade View Clients and Upgrade View Local Mode Clients.