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
Hardware Requirements for Standalone View Composer
With View 5.1 and later releases, View Composer is no longer required to be installed on the same physical or
virtual machine as vCenter Server. If you install View Composer on a separate server, you must use a dedicated
physical or virtual machine that meets specific hardware requirements.
A standalone View Composer installation works with vCenter Server installed on a Windows Server computer
and with the Linux-based vCenter Server Appliance. VMware recommends having a one-to-one mapping
between each View Composer service and vCenter Server instance.
Table 3-4. View Composer Hardware Requirements
Hardware Component Required Recommended
Processor 1.4 GHz 64-bit processor or
faster and 2 CPUs
Intel Itanium 2 processor for
Itanium-based systems
2GHz or faster and 4 CPUs
Networking One or more 10/100Mbps
network interface cards (NICs)
1Gbps NICs
Memory 4GB RAM or higher 8GB RAM or higher for deployments of 50 or more
View desktops
Disk space 40GB 60GB
IMPORTANT The physical or virtual machine that hosts View Composer must use a static IP address.
Database Requirements for View Composer
View Composer requires an SQL database to store data. The View Composer database must reside on, or be
available to, the View Composer server host.
If a database server already exists for vCenter Server, View Composer can use that existing database server if
it is a version listed in Table 3-5. For example, View Composer can use the Microsoft SQL Server 2005 or 2008
Express instance provided with vCenter Server. If a database server does not already exist, you must install
one.
View Composer supports a subset of the database servers that vCenter Server supports. If you are already
using vCenter Server with a database server that is not supported by View Composer, continue to use that
database server for vCenter Server and install a separate database server to use for View Composer and View
Manager database events.
IMPORTANT If you create the View Composer database on the same SQL Server instance as vCenter Server, do
not overwrite the vCenter Server database.
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.
VMware View Upgrades
14 VMware, Inc.