5.1
Table Of Contents
- VMware View Upgrades
- Contents
- VMware View Upgrades
- VMware View Component Compatibility Matrix
- VMware View Upgrade Overview
- System Requirements for Upgrades
- View Connection Server Requirements
- View Composer Requirements
- View Transfer Server Requirements
- View Administrator Requirements
- Supported Operating Systems for Windows-Based View Client and View Client with Local Mode
- Hardware Requirements for Local Mode Desktops
- Client Browser Requirements for View Portal
- Supported Operating Systems for View Agent
- Preparing for a VMware View Upgrade
- Upgrading VMware View Server Components
- Upgrade ESX/ESXi 4.0.x, 4.1.x, or 5.0.x Hosts and Their Virtual Machines
- Upgrading VMware View Desktops and Clients
- Applying VMware View Patches
- Upgrading vSphere Components Separately in a VMware View Environment
- Index
The -exp option creates an exportable key pair. If a future migration is required, the keys can be exported
from this computer and imported to another computer. If you previously migrated the keys to this
computer without using the -exp option, you can import the keys again using the -exp option so that you
can export the keys in the future.
The registration tool imports the key pair data into the local key container.
What to do next
Install the new View Composer service on the destination computer. Provide the DSN and ODBC data source
information that allows View Composer to connect to the same database information that was used by the
original View Composer service. For installation instructions, see "Installing View Composer" in the VMware
View Installation document.
Complete the steps to migrate View Composer to a new computer and use the same database. See “Migrate
View Composer with an Existing Database,” on page 36.
Upgrade vCenter Server
Perform a vCenter Server upgrade as part of the same maintenance window during which you upgrade other
View server components. Before you upgrade vCenter Server, you must back up some View data. After the
upgrade, if View Composer is running on the same server, you must restart the View Composer service.
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
Back up the vCenter Server database and the View Composer database.
n
Back up the View LDAP database from a View Connection Server instance by using the vdmexport.exe
utility.
For instructions, see the VMware View Administration document. If you have multiple instances of
View Connection Server in a replicated group, you need to export the data from only one instance.
n
Perform the tasks listed in “Preparing for Upgrades That Include vSphere,” on page 23.
n
Verify that the server on which vCenter Server is installed has a CA (certificate authority)-signed SSL
server certificate installed and configured. After you upgrade View Connection Server, if vCenter Server
does not use a CA-signed certificate, the default self-signed certificate is shown as invalid in View
Administrator, and a message indicates that vCenter Server is unavailable.
n
Complete the prerequisites listed in the vSphere Upgrade Guide, using the version of the guide that
corresponds to the version of vSphere that you plan to upgrade to.
Procedure
1 Upgrade vCenter Server as described in the vSphere Upgrade Guide.
2 If View Composer is installed on the same host, restart the View Composer service.
3 Log in to View Administrator and examine the dashboard to verify that the vCenter Server and View
Composer icons are green.
If either of these icons is red and an Invalid Certificate Detected dialog box appears, you must click
Verify and either accept the thumbprint of the untrusted certificate, as described in "What to Do Next,"
or install a valid CA-signed SSL certificate.
For information about replacing the default certificate for vCenter Server, see the vSphere Examples and
Scenarios document.
VMware View Upgrades
40 VMware, Inc.