5.0
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 Transfer Server Requirements
- View Composer 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
- Upgrading ESX/ESXi Hosts and Virtual Machines
- Upgrading VMware View Desktops and Clients
- Applying VMware View Patches
- Upgrading vSphere Components Separately in a VMware View Environment
- Index
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.
Windows Server 2008
Navigate to C:\Users\All Users\VMware\View Composer\vmware-
sviconfig.log.
The upgrade script logs a message for each failure.
2 Examine the log records to identify the desktops that failed to upgrade.
Option Action
The desktop exists but is
unavailable.
Make the desktop available again.
Depending on the cause of the failure, you might have to restart the ESX host
or vCenter Server, or take another action.
The desktop does not exist.
Ignore the log message.
NOTE A deleted desktop might appear to exist in View Manager if an
administrator deletes the desktop virtual machine directly in vSphere.
3 Run the SviConfig databaseupgrade command again.
Upgrade to View Composer 2.7 and vCenter Server 5.0 on a Different
Machine
During the first maintenance window, after you upgrade View Connection Server, you can also upgrade
View Composer and vCenter Server, which are hosted on the same virtual or physical machine.
CAUTION When you migrate View Composer and vCenter Server to a new machine, you can use the same host
name and IP address on the new machine, or you can change the host name, the IP address, or both.
If you change the host name or IP address, however, you might not be able to recompose View Composer
desktop pools, even after you upgrade the parent virtual machine to View 5.0 Agent. Change the vCenter
Server host name or IP address only if you are willing to recreate View Composer desktop pools after the
upgrade.
Prepare the Source Machine for View Composer Migration
For vSphere 4.1.x and 5.0.x, vCenter Server is supported only on 64-bit Windows operating systems. If your
current vCenter Server and View Composer server are installed on a 32-bit Windows machine, you need to
move to a 64-bit Windows machine as part of the upgrade.
You upgrade View Composer to 2.6 on the source computer first and if necessary also upgrade
VirtualCenter Server to vCenter Server 4.0. You then migrate View Composer 2.6 and vCenter Server 4.0 to
the destination computer. After making sure that everything is working on the destination computer, you
upgrade to View Composer 2.7 and vCenter Server 5.0.
This procedure provides an overview of the tasks you must perform during the first maintenance window. To
complete some of these tasks, you might need step-by-step instructions found in other documents.
Chapter 5 Upgrading VMware View Server Components
VMware, Inc. 35