VMware View Upgrades View 5.0 View Manager 5.0 View Composer 2.7 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new edition. To check for more recent editions of this document, see http://www.vmware.com/support/pubs.
VMware View Upgrades You can find the most up-to-date technical documentation on the VMware Web site at: http://www.vmware.com/support/ The VMware Web site also provides the latest product updates. If you have comments about this documentation, submit your feedback to: docfeedback@vmware.com Copyright © 2009–2011 VMware, Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws.
Contents VMware View Upgrades 5 1 VMware View Component Compatibility Matrix 7 2 VMware View Upgrade Overview 9 3 System Requirements for Upgrades 11 View Connection Server Requirements 11 Hardware Requirements for View Connection Server 11 Supported Operating Systems for View Connection Server 12 Upgrade Requirements for View Connection Server 12 Virtualization Software Requirements for View Connection Server 13 View Transfer Server Requirements 13 Installation Requirements for View Transfer Server 13 S
VMware View Upgrades Use the Data Migration Tool to Migrate to the New Machine 37 Manually Migrate View Composer to the New Machine 39 6 Upgrading ESX/ESXi Hosts and Virtual Machines 43 Upgrade ESX 3.5 Hosts and Their Virtual Machines 43 Upgrade ESX 4.0.x or 4.1.
VMware View Upgrades VMware View Upgrades provides instructions for upgrading from VMware View™ 4.0.x, 4.5.x, or 4.6.x to View 5.0. You can also use this guide when you upgrade to View 5.0 patch releases. If you also upgrade from vSphere 4.0 or vSphere 4.1 to vSphere 5.0, this guide tells you which steps of that upgrade to do at various stages of the VMware View upgrade. For VMware View 5.
VMware View Upgrades 6 VMware, Inc.
1 VMware View Component Compatibility Matrix Because large enterprises must often perform phased upgrades, VMware View components are designed to be forward and backward compatible. VMware View 5.0 components are compatible with most VMware View 4.0.x, 4.5.x, and 4.6.x components. Although components are forward and backward compatible, View Connection Server compatibility with View Agents is limited to interoperability during a View Connection Server upgrade or downgrade.
VMware View Upgrades Until both View Connection Server and View Composer are upgraded, View Composer operations do not work. If you have View Connection Server 5.0 and View Composer 2.0, 2.5, or 2.6, users can connect to their desktops, but no new linked-clone desktops can be created, and recompose, rebalance, and refresh operations do not work. Also, you cannot edit settings for linked-clone pools. IMPORTANT As the table shows, View Agent 4.0.x is not compatible with View Composer 2.7.
VMware View Upgrade Overview 2 Upgrading an enterprise VMware View deployment involves several high-level tasks. Upgrading is a multistage process in which procedures must be performed in a particular order. You must complete the upgrade process in a specific order. If you do not complete each upgrade stage before moving on, you can lose data and server access. Order is also important within each upgrade stage. NOTE This overview relates to upgrades for major, minor, and maintenance releases.
VMware View Upgrades This server transfers data that end users need to check out and run View desktops locally on their client systems. View Client with Local Mode is the fully supported feature that in earlier releases was an experimental feature called View Offline Desktop. 7 Upgrade View Composer on the existing host or, if you are also upgrading to vSphere 5.0, migrate to a new machine. See “Upgrade to View Composer 2.7 and vCenter Server 5.0 on a Different Machine,” on page 35.
System Requirements for Upgrades 3 Hosts and virtual machines in a VMware View deployment must meet specific hardware and operating system requirements.
VMware View Upgrades Table 3-1. View Connection Server Hardware Requirements (Continued) Hardware Component Required Recommended Memory 4GB RAM or higher At least 10GB RAM for deployments of 50 or more View desktops 2GB RAM or higher 6GB RAM for deployments of 50 or more View desktops, and enable Physical Address Extension (PAE) See the Microsoft KB article at http://support.microsoft.com/kb/283037.
Chapter 3 System Requirements for Upgrades If you plan to perform fresh installations of View Connection Server instances on additional physical or virtual machines, see the complete list of installation requirements in the VMware View Installation document. Virtualization Software Requirements for View Connection Server View Connection Server requires VMware virtualization software to function properly. n n If you are using vSphere, you must use one of the following supported versions: n vSphere 4.
VMware View Upgrades Supported Operating Systems for View Transfer Server You must install View Transfer Server on a supported operating system with at least the minimum required amount of RAM. Table 3-3.
Chapter 3 System Requirements for Upgrades Table 3-5 lists the supported database servers and versions. For a complete list of database versions supported with vCenter Server, see the VMware vSphere Compatibility Matrixes on the VMware vSphere documentation Web site. Table 3-5. Supported Database Servers for View Composer Database vCenter Server 5.0 and later vCenter Server 4.1 U1 and later vCenter Server 4.
VMware View Upgrades To display text properly, View Administrator requires Microsoft-specific fonts. If your Web browser runs on a non-Windows operating system such as Linux, UNIX, or Mac OS, make sure that Microsoft-specific fonts are installed on your computer. Currently, the Microsoft Web site does not distribute Microsoft fonts, but you can download them from independent Web sites.
Chapter 3 System Requirements for Upgrades Table 3-7. Processor Requirements Client Computer Requirement Description PC Standard x86 or x86 64-compatible Number of CPUs Multiprocessor systems are supported CPU speed For a Windows XP local desktop, 1.3GHz or faster; 1.6 1GHz recommended For a Windows 7 desktop, 1.3GHz or faster; for Aero effects, 2.
VMware View Upgrades Display A 32-bit display adapter is recommended. 3D benchmarks, such as 3DMark '06, might not render correctly or at all when running Windows Vista or Windows 7 virtual machines on some graphics hardware. To play video at 720p or higher requires a multiprocessor system. For CPU and GPU requirements to support Windows 7 Aero, see Table 3-7.
Chapter 3 System Requirements for Upgrades To use the View Persona Management feature, you must install View Agent on Windows 7, Windows Vista, or Windows XP virtual machines. View Persona Management does not operate on physical computers or Microsoft Terminal Servers. IMPORTANT If you use Windows 7 in a virtual machine, the host must be ESX/ESXi 4.0 Update 3 or later, ESX/ESXi 4.1 Update 1 or later, or ESXi 5.0 or later. VMware, Inc.
VMware View Upgrades 20 VMware, Inc.
Preparing for a VMware View Upgrade 4 Before you start the upgrade process, you must review system requirements for the new version, back up databases, take snapshots of virtual machines that host server components, and document configuration settings.
VMware View Upgrades For instructions, see the administration guide for your current version of VMware View: the View Manager 4 Administration Guide, the VMware View 4.5 Administrator's Guide, or the VMware View 4.6 Administration document. If you have multiple instances of View Connection Server in a replicated group, you need only export the data from one instance. n Document the IP address and system name of the machine on which View Connection Server is installed.
Chapter 4 Preparing for a VMware View Upgrade 9 For all linked-clone desktop pools, disable provisioning of new virtual machines. Because View Composer might be upgraded during a different maintenance window than its desktop pools, provisioning must be postponed until both components are upgraded. 10 If any desktop pools are set to refresh the OS disk on logoff, edit the Desktop/Pools settings for that pool and set Refresh OS disk on logoff to Never.
VMware View Upgrades 24 VMware, Inc.
Upgrading VMware View Server Components 5 The server components that you must upgrade include View Connection Server, View Client, and View Agent. Depending on the optional components you use, you might also need to upgrade View Composer. If you plan to use View Client with Local Mode, you must also install or upgrade a View Transfer Server instance. Depending on how large your View deployment is, you might perform the upgrade process incrementally, over several maintenance windows. For VMware View 5.
VMware View Upgrades n If you are upgrading from View 4.0.x, 4.5.x, or 4.6.x and are unfamiliar with the vdmexport.exe utility, print the instructions for using it from the View Manager 4 Administration Guide, the VMware View 4.5 Administrator's Guide, or the VMware View 4.6 Administration document. You will use this utility to back up the View LDAP database as part of the upgrade procedure.
Chapter 5 Upgrading VMware View Server Components 13 If you use security servers, in View Administrator, go to View Configuration > Servers and remove any duplicate security servers from the list. The new automated security server pairing mechanism can produce duplicate entries in the Security Servers list if the full system name does not match the name that was assigned when the security server was originally created.
VMware View Upgrades Procedure 1 Verify that an upgraded instance of View Connection Server is running and is accessible to the new machine where you plan to install View Connection Server. When you install View Connection Server on the new host, you will point to this existing instance. 2 On the new machine, install a replicated instance of View Connection Server. The View LDAP on the new instance will replicate that of the upgraded source instance.
Chapter 5 Upgrading VMware View Server Components Procedure 1 On all View Connection Server instances except the one chosen to be the new standard View Connection Server instance, uninstall View Connection Server and the View LDAP instance. If the operating system on the virtual machine is Windows Server 2003, the View LDAP instance is called ADAM Instance VMwareVDMDS. If the operating system is Windows Server 2008, the View LDAP instance is called AD LDS Instance VMwareVDMDS.
VMware View Upgrades What to do next If you use View Composer, see “Upgrade View Composer Only,” on page 31 or “Upgrade to View Composer 2.7 and vCenter Server 5.0 on a Different Machine,” on page 35. If you have finished upgrading View server components, at your next maintenance window, continue with the VMware View upgrade. n If you are also upgrading vSphere components, see Chapter 6, “Upgrading ESX/ESXi Hosts and Virtual Machines,” on page 43.
Chapter 5 Upgrading VMware View Server Components What to do next If you use View Composer, see “Upgrade View Composer Only,” on page 31 or “Upgrade to View Composer 2.7 and vCenter Server 5.0 on a Different Machine,” on page 35. If you have finished upgrading View server components, at your next maintenance window, continue with the VMware View upgrade. n If you are also upgrading vSphere components, see Chapter 6, “Upgrading ESX/ESXi Hosts and Virtual Machines,” on page 43.
VMware View Upgrades 2 In to View Administrator verify or, if necessary, change the port number used for View Composer. a Edit the configuration for the vCenter Server instance and make sure that the View Composer port is set to 18443. The port number must match the port number specified during the View Composer upgrade. 3 b Supply the vCenter Server password. c Select the Enable View Composer check box and click OK.
Chapter 5 Upgrading VMware View Server Components Run SviConfig to Manually Upgrade the Database With the SviConfig command-line utility, you can upgrade the View Composer database separately from the View Composer software. This utility also creates a log file to simplify troubleshooting if the upgrade fails. No database schema changes have been made between View Composer 2.0.x, 2.5.x, or 2.6.x and View Composer 2.7.
VMware View Upgrades 4 Enter the command to start the VMware View Composer service. net start svid A complete log of the upgrade process is created. Option Description Windows Server 2003 C:\Documents and Settings\All Users\Application Data\VMware\View Composer\Logs\vmware-sviconfig.log Windows Server 2008 C:\Users\All Users\VMware\View Composer\vmware-sviconfig.log What to do next If the database upgrade fails, see “Troubleshooting a View Composer Database Upgrade Failure,” on page 34.
Chapter 5 Upgrading VMware View Server Components Cause The database-upgrade software contacts vCenter Server to get additional data about desktops. The database upgrade might fail if the desktops are not available, the ESX host is not running, or vCenter Server is not available. Solution 1 See the View Composer SviConfig log file for more information. Option Action Windows Server 2003 Navigate to C:\Documents and Settings\All Users\Application Data\VMware\View Composer\Logs\vmware-sviconfig.log.
VMware View Upgrades Prerequisites n Determine when to perform this procedure. Choose an available desktop maintenance window. For information about how much time is required, see the vSphere Upgrade Guide. n Complete the tasks listed in “Preparing for Upgrades That Include vSphere,” on page 22. These tasks include backing up the View Composer database and the vCenter Server database and making a copy of the SSL certificate folder located at %ALLUSERSPROFILE%\Application Data\VMware\VMware VirtualCenter
Chapter 5 Upgrading VMware View Server Components 7 Migrate the RSA key container used by View Composer. a On the source machine, open a command prompt and change directories to the directory where the aspnet_regiis program is located. cd %windir%\Microsoft.NET\Framework\v2.0.xxxxx You might have several copies of the aspnet_regiis program on the computer. Use the one in the v2.0.xxxxx directory. b Type the aspnet_regiis command to save the RSA key pair in a local file.
VMware View Upgrades n 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. n Verify that you have the correct license keys for vSphere if you are upgrading Virtual Infrastructure components to vSphere. Procedure 1 On the new, destination machine, set the host name and IP address.
Chapter 5 Upgrading VMware View Server Components c Deselect the Enable View Composer check box and click OK. You apply the new vCenter Server settings before you enable View Composer. d After a few moments, edit the vCenter Server settings again to select Enable View Composer and click OK. View Composer and vCenter Server instances are upgraded and are backward-compatible with existing View 4.0.x, 4.5.x, and 4.6.x View Clients and with desktop sources that have the View 4.0.x, 4.5.x, or 4.6.
VMware View Upgrades 2 Migrate the RSA key container used by View Composer. a On the destination machine, open a command prompt and change directories to the directory where the aspnet_regiis program is located. cd %windir%\Microsoft.NET\Framework\v2.0.xxxxx You might have several copies of the aspnet_regiis program on the computer. Use the one in the v2.0.xxxxx directory. b Use the aspnet_regiis command to import the RSA key pair. aspnet_regiis -pi “SviKeyContainer” “path\keys.
Chapter 5 Upgrading VMware View Server Components c Deselect the Enable View Composer check box and click OK. You apply the new vCenter Server settings before you enable View Composer. d After a few moments, edit the vCenter Server settings again to select Enable View Composer and click OK. View Composer and vCenter Server instances are upgraded and are backward-compatible with existing View 4.0.x, 4.5.x, and 4.6.x View Clients and with desktop sources that have the View 4.0.x, 4.5.x, or 4.6.
VMware View Upgrades 42 VMware, Inc.
Upgrading ESX/ESXi Hosts and Virtual Machines 6 Upgrading ESX/ESXi hosts and virtual machines to vSphere 5.0 is the most time-consuming aspect of this middle phase of a VMware View upgrade. Upgrading from ESX/ESXi 3.5 involves more steps than upgrading from ESX/ESXi 4.x. This chapter includes the following topics: n “Upgrade ESX 3.5 Hosts and Their Virtual Machines,” on page 43 n “Upgrade ESX 4.0.x or 4.1.x Hosts and Their Virtual Machines,” on page 44 Upgrade ESX 3.
VMware View Upgrades d Use VMotion to move the virtual machines back onto the host. e Perform post-upgrade tasks for ESXi hosts. Every host must be a member of a cluster, as mentioned in the prerequisites. 2 If an upgraded host does not reconnect itself to vCenter, use vSphere Client to reconnect the host to the vCenter Server. 3 If you use View Composer, after all ESX/ESXi hosts are upgraded, on the vCenter Server host, restart the View Composer service.
Chapter 6 Upgrading ESX/ESXi Hosts and Virtual Machines n Perform the ESX/ESXi upgrade preparation tasks listed in the vSphere Upgrade Guide. Procedure 1 Upgrade ESX/ESXi hosts to vSphere 5.0, cluster by cluster. For instructions, see the vSphere Upgrade Guide. If you have many clusters, this step could take several maintenance windows to complete. Upgrading ESX/ESXi hosts includes the following tasks: a Use VMotion to move the virtual machines off of the ESX/ESXi host.
VMware View Upgrades 46 VMware, Inc.
Upgrading VMware View Desktops and Clients 7 The desktop and client components that you can upgrade include View Client for Windows, View Client for Mac, thin clients provided by VMware partners, and the View Agent, which runs inside the operating systems of View desktops.
VMware View Upgrades n 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. Procedure 1 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.
Chapter 7 Upgrading VMware View Desktops and Clients Upgrade View Composer Desktop Pools Part of the final phase of a VMware View upgrade includes upgrading View Composer desktop pools. Upgrading pools that were created with View Composer requires that you use a snapshot taken after upgrading View Agent on the parent virtual machine.
VMware View Upgrades 3 Use the snapshot you created after upgrading the parent virtual machine to recreate or recompose desktop pools. Option Action View 4.0.x pools For floating desktop pools, delete virtual desktops from the pool and recreate the desktop pool. For dedicated pools, recompose the desktop pool. View 4.5.x and 4.6.x pools For both floating and dedicated pools, recompose the desktop pool.
Chapter 7 Upgrading VMware View Desktops and Clients Procedure 1 2 Have end users upgrade to View 5.0 Client. Option Action View Client For View Client installers that are hosted on the VMware Web site, such as View Client for Windows and View Client with Local Mode, download and send the View Client to your end users or post it on a Web site and ask end users to download the installer and run it.
VMware View Upgrades Procedure 1 If you plan to upgrade View Agent on the virtual machine in the datacenter, have end users check in their local mode desktops. 2 On the client system, run the View 5.0 Client with Local Mode installer. If end users have the required administrative privileges on their computers, you have several options for providing end users with the installer: 3 n Download the installer from the VMware Web site and send it to your end users.
Chapter 7 Upgrading VMware View Desktops and Clients 3 Upgrade all components that need to be upgraded. These components might include View Connection Server, View Transfer Server, View Composer, vCenter Server, ESX/ESXi hosts, virtual machines, VMware Tools in virtual machines, and View Agent in virtual machines. 4 If you do not already have View Transfer Server installed and configured, install and configure a View Transfer Server instance, as described in the VMware View 5.0 Installation document.
VMware View Upgrades 54 VMware, Inc.
Applying VMware View Patches 8 Patch releases can include installer files for the following VMware View components: View Connection Server, View Composer, View Agent, and various View clients. The patch components that you must apply depend on the bug fixes that your View deployment requires.
VMware View Upgrades 3 On one of the View Connection Server instances in a replicated group, download the installer file for the patch version of VMware View Connection Server. Your contact at VMware will provide instructions for this download. 4 Use the Windows Add/Remove Programs utility to remove your previously installed View Connection Server, but do not remove Adam Instance VMwareVDMDS. 5 Run the installer that you downloaded for the patch release of VMware View Connection Server.
Chapter 8 Applying VMware View Patches 4 Verify that the VMware View Composer service restarts after the installer wizard closes. 5 If applicable, apply the patch for View Agent on a parent virtual machine and create a desktop pool for testing purposes. a Use the Windows Add/Remove Programs utility to remove your previously installed View Agent. b Download and run the VMware View Agent patch installer on a parent virtual machine. Your contact at VMware will provide instructions for this download.
VMware View Upgrades 8 If you canceled any refresh or recompose operations for any linked-clone desktop pools, schedule the tasks again. What to do next Apply the patch to one or more View clients, as applicable. Apply a Patch for View Clients Applying a patch involves uninstalling the current version and then installing the patch version. Procedure 1 On each client system, download the installer file for the patch version of VMware View Client.
Upgrading vSphere Components Separately in a VMware View Environment 9 If you upgrade vSphere components separately from VMware View components, you must back up some View data and reinstall some View software. Instead of performing an integrated upgrade of VMware View and vSphere components, you can choose to first upgrade all View components and then upgrade vSphere components, or the reverse. You might also upgrade only vSphere components when a new version or update of vSphere is released.
VMware View Upgrades 60 VMware, Inc.
Index A I aspnet_regiis command 35, 37, 39 Internet Explorer, supported versions 15, 18 B L backward compatibility 7 blade PCs 47 browser requirements 15, 18 LDAP 21 LDAP upgrade 25 license requirements 12 linked-clone desktop management, upgrade procedure 47 load balancers 21 local desktop configuration, hardware requirements 16 local desktop upgrade 51, 52 C cluster upgrades 43, 44 compatibility matrix for View components 7 CPU requirements, local mode desktops 16 D data migration tool for vCent
VMware View Upgrades SSL certificate backups 22 sviconfig utility 32–34 SviKeyContainer key container 35 system requirements for VMware View upgrades 11 T Technical Support, VMware 5 thin clients 47, 50 U upgrade check list 9 upgrade preparation vCenter Server 22 View Composer 22 View Connection Server 21 VMware View components 21 utilities sviconfig 32–34 vdmadmin.exe 27 vdmexport.exe 21, 25 V vCenter Server, upgrade preparation tasks 59 vCenter Server upgrade, upgrade preparation tasks 22 vdmadmin.
