VMware VIEW 4.5 User manual

VMware View Installation Guide
View 4.5
View Manager 4.5
View Composer 2.5
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.
EN-000245-01

VMware View Installation Guide
2 VMware, Inc.
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:
[email protected]
Copyright ©2010 VMware, Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual
property laws. VMware products are covered by one or more patents listed at http://www.vmware.com/go/patents.
VMware is a registered trademark or trademark of VMware, Inc. in the United States and/or other jurisdictions. All other marks
and names mentioned herein may be trademarks of their respective companies.
VMware, Inc.
3401 Hillview Ave.
Palo Alto, CA 94304
www.vmware.com

Contents
About This Book 5
1System Requirements for Server Components 7
View Connection Server Requirements 7
View Administrator Requirements 9
View Composer Requirements 9
View Transfer Server Requirements 11
2System Requirements for Client Components 15
Supported Operating Systems for View Agent 15
Supported Operating Systems for View Client and View Client with Local Mode 16
Hardware Requirements for Local Mode Desktops 16
Client Browser Requirements for View Portal 18
Remote Display Protocol and Software Support 18
Adobe Flash Requirements 21
Smart Card Authentication Requirements 21
3Preparing Active Directory 23
Configuring Domains and Trust Relationships 23
Creating an OU for View Desktops 24
Creating OUs and Groups for Kiosk Mode Client Accounts 24
Creating Groups for View Users 24
Creating a User Account for vCenter Server 24
Create a User Account for View Composer 25
Configure the Restricted Groups Policy 25
Using View Group Policy Administrative Template Files 26
Prepare Active Directory for Smart Card Authentication 26
4Installing View Composer 29
Prepare a View Composer Database 29
Install the View Composer Service 34
Configuring Your Infrastructure for View Composer 36
5Installing View Connection Server 37
Installing the View Connection Server Software 37
Configuring User Accounts for vCenter Server and View Composer 51
Configuring View Connection Server for the First Time 54
Configuring View Client Connections 57
Sizing Windows Server Settings to Support Your Deployment 59
VMware, Inc. 3

6Installing View Transfer Server 67
Install View Transfer Server 67
Add View Transfer Server to View Manager 69
Configure the Transfer Server Repository 70
Firewall Rules for View Transfer Server 71
Installing View Transfer Server Silently 71
7Configuring Certificate Authentication 75
Replacing the Default Certificate 75
Add keytool and openssl to the System Path 76
Export an Existing Microsoft IIS SSL Server Certificate 76
Creating a New SSL Certificate 77
Configure a View Connection Server Instance or Security Server to Use a New Certificate 80
Configure a View Transfer Server Instance to Use a New Certificate 81
Configure SSL for Client Connections 82
Configure SSL for View Transfer Server Communications 82
Using Group Policy to Configure Certificate Checking in View Client 83
8Creating an Event Database 85
Add a Database and Database User for View Events 85
Prepare an SQL Server Database for Event Reporting 86
Configure the Event Database 86
9Installing and Starting View Client 89
Install the Windows-Based View Client or View Client with Local Mode 89
Start the Windows-Based View Client or View Client with Local Mode 90
Install View Client by Using View Portal 92
Install View Client on Mac OS X 93
Start View Client on Mac OS X 94
Set Printing Preferences for the Virtual Printer Feature 96
Using USB Printers 97
Installing View Client Silently 97
Index 101
VMware View Installation Guide
4 VMware, Inc.

About This Book
The VMWare View Installation Guide explains how to install the VMware® View server and client components.
Intended Audience
This book is intended for anyone who wants to install VMware® View. The information in this book is written
for experienced Windows or Linux system administrators who are familiar with virtual machine technology
and datacenter operations.
VMware Technical Publications Glossary
VMware Technical Publications provides a glossary of terms that might be unfamiliar to you. For definitions
of terms as they are used in VMware technical documentation, go to
http://www.vmware.com/support/pubs.
Document Feedback
VMware welcomes your suggestions for improving our documentation. If you have comments, send your
feedback to [email protected].
Technical Support and Education Resources
The following technical support resources are available to you. To access the current version of this book and
other books, go to http://www.vmware.com/support/pubs.
Online and Telephone
Support
To use online support to submit technical support requests, view your product
and contract information, and register your products, go to
http://www.vmware.com/support.
Customers with appropriate support contracts should use telephone support
for the fastest response on priority 1 issues. Go to
http://www.vmware.com/support/phone_support.html.
Support Offerings To find out how VMware support offerings can help meet your business needs,
go to http://www.vmware.com/support/services.
VMware Professional
Services
VMware Education Services courses offer extensive hands-on labs, case study
examples, and course materials designed to be used as on-the-job reference
tools. Courses are available onsite, in the classroom, and live online. For onsite
pilot programs and implementation best practices, VMware Consulting
VMware, Inc. 5

Services provides offerings to help you assess, plan, build, and manage your
virtual environment. To access information about education classes,
certification programs, and consulting services, go to
http://www.vmware.com/services.
VMware View Installation Guide
6 VMware, Inc.

System Requirements for Server
Components 1
Hosts that run VMware View server components must meet specific hardware and software requirements.
This chapter includes the following topics:
n“View Connection Server Requirements,” on page 7
n“View Administrator Requirements,” on page 9
n“View Composer Requirements,” on page 9
n“View Transfer Server Requirements,” on page 11
View Connection Server Requirements
View Connection Server acts as a broker for client connections by authenticating and then directing incoming
user requests to the appropriate View desktop. View Connection Server has specific hardware, operating
system, installation, and supporting software requirements.
nHardware Requirements for View Connection Server on page 7
You must install View Connection Server on a 32-bit or 64-bit dedicated physical or virtual machine that
meets specific hardware requirements.
nSupported Operating Systems for View Connection Server on page 8
You must install View Connection Server on a supported operating system.
nVirtualization Software Requirements for View Connection Server on page 8
View Connection Server requires VMware virtualization software to function properly.
nNetwork Requirements for Replicated View Connection Server Instances on page 8
If you install replicated View Connection Server instances, configure the instances in the same location
and connect them over a high-performance LAN.
Hardware Requirements for View Connection Server
You must install View Connection Server on a 32-bit or 64-bit dedicated physical or virtual machine that meets
specific hardware requirements.
Table 1-1. View Connection Server Hardware Requirements
Hardware Component Required Recommended
Processor Pentium IV 2.0GHz processor or
higher
Dual processors
Networking One or more 10/100Mbps
network interface cards (NICs)
1Gbps NICs
VMware, Inc. 7

Table 1-1. View Connection Server Hardware Requirements (Continued)
Hardware Component Required Recommended
Memory
Windows Server 2008 64-bit
4GB RAM or higher At least 10GB RAM for deployments of 50 or more
View desktops
Memory
Windows Server 2003 32-bit
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.
These requirements also apply to additional View Connection Server instances that you install for high
availability or external access.
IMPORTANT The physical or virtual machine that hosts View Connection Server must use a static IP address.
Supported Operating Systems for View Connection Server
You must install View Connection Server on a supported operating system.
Table 1-2 lists the operating systems supported for View Connection Server.
These operating systems support all View Connection Server installation types, including standard, replicated,
security-server, and View Transfer Server installations.
Table 1-2. Operating System Support for View Connection Server
Operating System Version Edition Service Pack
Windows Server 2008 R2 64-bit Standard
Enterprise
N/A
Windows Server 2003 R2 32-bit Standard
Enterprise
SP2
Windows Server 2003 32-bit Standard
Enterprise
SP2
IMPORTANT If you use a Windows Server 2003 operating system, enable Physical Address Extension (PAE).
See the Microsoft KB article at http://support.microsoft.com/kb/283037.
Virtualization Software Requirements for View Connection Server
View Connection Server requires VMware virtualization software to function properly.
nIf you are using vSphere, you must have vSphere 4.0 Update 2 or vSphere 4.1.
nIf you are using VMware Infrastructure, you must have VMware Infrastructure 3.5 Update 5 and
VirtualCenter Server 2.5 Update 6.
nBoth ESX and ESXi hosts are supported.
Network Requirements for Replicated View Connection Server Instances
If you install replicated View Connection Server instances, configure the instances in the same location and
connect them over a high-performance LAN.
Do not use a WAN to connect replicated View Connection Server instances.
VMware View Installation Guide
8 VMware, Inc.

Even a high-performance WAN with low average latency and high throughput might have periods when the
network cannot deliver the performance characteristics that are needed for View Connection Server instances
to maintain consistency.
If the View LDAP configurations on View Connection Server instances become inconsistent, users might not
be able to access their desktops. A user might be denied access when connecting to a View Connection Server
instance with an out-of-date configuration.
View Administrator Requirements
Administrators use View Administrator to configure View Connection Server, deploy and manage desktops,
control user authentication, initiate and examine system events, and carry out analytical activities. Client
systems that run View Administrator must meet certain requirements.
View Administrator is a Web-based application that is installed when you install View Connection Server. You
can access and use View Administrator with the following Web browsers:
nInternet Explorer 7
nInternet Explorer 8
nFirefox 3.0
nFirefox 3.5
To use View Administrator with your Web browser, you must install Adobe Flash Player 10. Your client system
must have access to the internet to allow Adobe Flash Player to be installed.
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.
View Composer Requirements
View Manager uses View Composer to deploy multiple linked-clone desktops from a single centralized base
image. View Composer has specific installation and storage requirements.
nSupported Operating Systems for View Composer on page 10
View Composer supports 64-bit and 32-bit operating systems with specific requirements and limitations.
You must install View Composer on the same physical computer or virtual machine as vCenter Server.
nDatabase Requirements for View Composer on page 10
View Composer requires an SQL database to store data. The View Composer database must reside on,
or be available to, the vCenter Server computer.
nVirtualization Software Requirements for View Composer Features on page 11
You must create linked-clone virtual machines on hosts that run ESX/ESXi 4 or later, and you must
configure linked-clone pools in vSphere mode, to take advantage of several View Composer and vSphere
features.
Chapter 1 System Requirements for Server Components
VMware, Inc. 9

Supported Operating Systems for View Composer
View Composer supports 64-bit and 32-bit operating systems with specific requirements and limitations. You
must install View Composer on the same physical computer or virtual machine as vCenter Server.
64-Bit Operating Systems
Table 1-3 lists the 64-bit operating systems supported for View Composer. Standard and Enterprise editions
are supported.
Table 1-3. 64-Bit Operating System Support for View Composer
vCenter Server Version Operating System Service Pack
4.1 Windows Server 2008 R2 N/A
4.1 Windows Server 2008 SP2
4.1 Windows Server 2003 R2 SP2
4.1 Windows Server 2003 SP2
4.0 Update 2 Windows Server 2008 SP2
32-Bit Operating Systems
Table 1-4 lists the 32-bit operating systems supported for View Composer. Standard and Enterprise editions
are supported.
Table 1-4. 32-Bit Operating System Support for View Composer
vCenter Server Version Operating System Service Pack
4.0 Update 2 Windows Server 2003 SP2
2.5 Update 6 Windows Server 2003 R2 SP2
2.5 Update 6 Windows Server 2003 SP2
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 vCenter Server computer.
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 1-5. For example, View Composer can use the Microsoft SQL Server 2005 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 1-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 Installation Guide
10 VMware, Inc.

Table 1-5. Supported Database Servers for View Composer
Database vCenter Server 4.1 vCenter Server 4.0 U2 VC Server 2.5 U6
Microsoft SQL
Server 2000 SP4
Standard
No No Yes
Microsoft SQL
Server 2005 Express
Yes Yes Yes
Microsoft SQL
Server 2005 SP3
Standard and
Enterprise
Yes Yes Yes
Microsoft SQL
Server 2008 SP1
Standard and
Enterprise
Yes Yes No
Microsoft SQL
Server 2008 SP1
Standard and
Enterprise 64-bit
Yes Yes No
Oracle 9i Release 2 No No Yes
Oracle 10g Release 2 Yes Yes No
Oracle 11g Release 1 Yes Yes No
Virtualization Software Requirements for View Composer Features
You must create linked-clone virtual machines on hosts that run ESX/ESXi 4 or later, and you must configure
linked-clone pools in vSphere mode, to take advantage of several View Composer and vSphere features.
nStoring linked-clone virtual machines on local datastores
nRedirecting disposable data to separate, non-persistent disks
nStoring replicas and linked clones on separate datastores
nCreating pools from a parent virtual-machine snapshot that uses hardware version 7
nUsing Sysprep customization specifications for linked-clone virtual machines.
In addition, Sysprep is supported for linked clones only on vSphere 4.1 software. You cannot use Sysprep
on vSphere 4.0 or VMware Infrastructure 3.5 software.
View Transfer Server Requirements
View Transfer Server is an optional View Manager component that supports check in, check out, and replication
of desktops that run in local mode. View Transfer Server has specific installation, operating system, and storage
requirements.
nInstallation Requirements for View Transfer Server on page 12
You must install View Transfer Server as a Windows application in a virtual machine that meets specific
requirements.
Chapter 1 System Requirements for Server Components
VMware, Inc. 11

nSupported Operating Systems for View Transfer Server on page 12
You must install View Transfer Server on a supported operating system with the required amount of
RAM.
nStorage Requirements for View Transfer Server on page 13
View Transfer Server transfers static content to and from the Transfer Server repository and dynamic
content between local desktops and remote desktops in the datacenter. View Transfer Server has specific
storage requirements.
Installation Requirements for View Transfer Server
You must install View Transfer Server as a Windows application in a virtual machine that meets specific
requirements.
The virtual machine that hosts View Transfer Server must meet several requirements regarding network
connectivity:
nIt must be managed by the same vCenter Server instance as the local desktops that it will manage.
nIt does not have to be part of a domain.
nIt must use a static IP address.
CAUTION You must configure the virtual machine that hosts View Transfer Server with an LSI Logic Parallel
SCSI controller. You cannot use a SAS or VMware paravirtual controller.
On Windows Server 2008 virtual machines, the LSI Logic SAS controller is selected by default. You must change
this selection to a BusLogic or LSI Logic controller before you install the operating system.
The View Transfer Server software cannot coexist on the same virtual machine with any other View Manager
software component, including View Connection Server.
You can install multiple View Transfer Server instances for high availability and scalability.
Supported Operating Systems for View Transfer Server
You must install View Transfer Server on a supported operating system with the required amount of RAM.
Table 1-6. Operating System Support for View Transfer Server
Operating System Version Edition Service Pack Minimum RAM
Windows Server 2008 R2 64-bit Standard
Enterprise
N/A 4GB
Windows Server 2003 R2 32-bit Standard
Enterprise
SP2 2GB
Windows Server 2003 32-bit Standard
Enterprise
SP2 2GB
IMPORTANT Configure two virtual CPUs for virtual machines that host View Transfer Server.
VMware View Installation Guide
12 VMware, Inc.

Storage Requirements for View Transfer Server
View Transfer Server transfers static content to and from the Transfer Server repository and dynamic content
between local desktops and remote desktops in the datacenter. View Transfer Server has specific storage
requirements.
nThe disk drive on which you configure the Transfer Server repository must have enough space to store
your static image files. Image files are View Composer base images.
nView Transfer Server must have access to the datastores that store the desktop disks to be transferred. The
datastores must be accessible from the ESX host where the View Transfer Server virtual machine is
running.
nView Transfer Server can transfer a maximum of 60 disks concurrently.
During a transfer operation, a local desktop's virtual disk is mounted on View Transfer Server. The View
Transfer Server virtual machine has four SCSI controllers, each with 15 slots. This configuration allows
60 disks to be attached to the virtual machine at one time.
nBecause local desktops can contain sensitive user data, make sure data is encrypted during its transit over
the network.
In View Administrator, you can configure data-transfer security options on each View Connection Server
instance. To configure these options in View Administrator, click View Configuration > Servers, select a
View Connection Server instance, and click Edit.
nWhen View Transfer Server is added to View Manager, its Distributed Resource Scheduler (DRS)
automation policy is set to Manual, which effectively disables DRS.
To migrate a View Transfer Server instance to another ESX host or datastore, you must place the instance
in maintenance mode before you begin the migration.
When View Transfer Server is removed from View Manager, the DRS automation policy is reset to the
value it had before View Transfer Server was added to View Manager.
Chapter 1 System Requirements for Server Components
VMware, Inc. 13

VMware View Installation Guide
14 VMware, Inc.

System Requirements for Client
Components 2
Systems running View client components must meet certain hardware and software requirements.
View Client uses Microsoft Internet Explorer Internet settings, including proxy settings, when connecting to
View Connection Server. Ensure that your Internet Explorer settings are accurate and that you can access the
View Connection Server URL through Internet Explorer.
This chapter includes the following topics:
n“Supported Operating Systems for View Agent,” on page 15
n“Supported Operating Systems for View Client and View Client with Local Mode,” on page 16
n“Hardware Requirements for Local Mode Desktops,” on page 16
n“Client Browser Requirements for View Portal,” on page 18
n“Remote Display Protocol and Software Support,” on page 18
n“Adobe Flash Requirements,” on page 21
n“Smart Card Authentication Requirements,” on page 21
Supported Operating Systems for View Agent
The View Agent component assists with session management, single sign-on, and device redirection. You must
install View Agent on all virtual machines, physical systems, and terminal servers that will be managed by
View Manager.
Table 2-1 lists the operating systems supported for View Agent.
Table 2-1. View Agent Operating System Support
Guest Operating System Version Edition Service Pack
Windows 7 64-bit and 32-bit Enterprise and
Professional
N/A
Windows Vista 32-bit Business and
Enterprise
SP1 and SP2
Windows XP 32-bit Professional SP3
Windows 2008 R2 Terminal Server 64-bit Standard N/A
Windows 2008 Terminal Server 64-bit Standard SP2
VMware, Inc. 15

Table 2-1. View Agent Operating System Support (Continued)
Guest Operating System Version Edition Service Pack
Windows 2003 R2 Terminal Server 32-bit Standard SP2
Windows 2003 Terminal Server 32-bit Standard SP2
IMPORTANT If you use Windows 7 in a virtual machine, the virtual machine must be hosted on an ESX 4.0 or
ESX 4.1 server. For ESX 4.0, the version must be ESX 4.0 Update 2 or higher. For ESX 4.1, the version must be
ESX 4.1 or higher.
Supported Operating Systems for View Client and View Client with
Local Mode
Users run View Client to connect to their View desktops. You must install View Client or View Client with
Local Mode on a supported operating system.
Table 2-2 lists the operating systems supported for View Client.
Table 2-2. View Client Operating System Support
Operating System Version Edition Service Pack
Windows 7 32-bit and 64-bit Home, Enterprise,
Professional, and Ultimate
N/A
Windows XP 32-bit Home and Professional SP3
Windows Vista 32-bit Home, Business, Enterprise,
and Ultimate
SP1 and SP2
Mac OS X Leopard 10.5 N/A N/A N/A
Mac OS X Snow Leopard 10.6 N/A N/A N/A
IMPORTANT View Client with Local Mode is supported only on Windows systems and only on physical
computers. In addition, to use this feature, your VMware license must include View Client with Local Mode.
View Client with Local Mode is the fully supported feature that in earlier releases was an experimental feature
called View Client with Offline Desktop.
A Windows 7 or Windows Vista View desktop that is created on an ESX 3.5 host cannot produce 3D and
Windows Aero effects. This limitation applies even when the desktop is checked out for local use on a
Windows 7 or Windows Vista client computer. Windows Aero and 3D effects are available only if the View
desktop is created using vSphere 4.x.
NOTE VMware partners offer thin client devices for VMware View deployments. The features and Linux
operating systems that are available for each thin client device are determined by the vendor and model and
the configuration that an enterprise chooses to use. For information about the vendors and models for thin
client devices, see the Thin Client Compatibility Guide, available on the VMware Web site.
Hardware Requirements for Local Mode Desktops
When you check out a View desktop to run on your local computer, the hardware on the client computer must
support both the local system and the virtual machine that now runs on it.
PC Hardware
Table 2-3 describes the hardware requirements for various View desktop operating systems.
VMware View Installation Guide
16 VMware, Inc.

Table 2-3. 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 GHz
recommended
For a Windows 7 desktop, 1.6GHz or faster; for Aero effects,
2.2GHz or faster
Intel processors Pentium 4, Pentium M (with PAE), Core, Core 2, Core i3,
Core i5, and Core i7 processors
For Windows 7 Aero: Intel Dual Core
AMD processors Athlon, Athlon MP, Athlon XP, Athlon 64, Athlon X2, Duron,
Opteron, Turion X2, Turion 64, Sempron, Phenom, and
Phenom II
For Windows 7 Aero: Althon 4200+ and above
64-bit operating systems Intel Pentium 4 and Core 2, and Core i7 processors with
EM64T and Intel Virtualization Technology
Most AMD64 processors (except the earliest revision C
Opteron processors)
GPU for Windows 7 Aero nVidia GeForce 8800GT and above
ATI Radeon HD 2600 and above
Disk Space
If you use a default setup for the operating system in the View desktop, the actual disk space needs are
approximately the same as those for installing and running the operating system and applications on a physical
computer.
For example, Microsoft recommends 16GB of hard disk space for a machine that runs a 32-bit Windows 7
operating system. If you configure a 16GB virtual hard disk for a 32-bit Windows 7 virtual machine, only the
amount of disk space actually used is downloaded when you check out the local desktop. For a desktop that
is allocated 16GB, the actual download size might be 7GB.
After the desktop is downloaded, the amount of disk spaced used can grow to 16GB if you configured a 16GB
hard disk. Because a snapshot is taken during replication, an additional equivalent amount of disk space is
required. For example, if 7GB of disk space is currently being used for the local desktop, the snapshot consumes
an additional 7GB on the client computer.
IDE and SCSI hard drives are supported.
Memory
You need enough memory to run the host operating system on the client computer, plus the memory required
for the View desktop's operating system and for applications on the client computer and the View desktop.
VMware recommends that you have 2GB and above for Windows XP and Windows Vista, and 3GB and above
for Windows 7. For more information on memory requirements, see your guest operating system and
application documentation.
The total amount of memory you can assign to all virtual machines running on a single computer is limited
only by the amount of RAM on the computer. The maximum amount of memory for each View desktop on
32-bit client computers is 8GB and on 64-bit computers it is 32GB.
Chapter 2 System Requirements for Client Components
VMware, Inc. 17

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 the table in “PC Hardware,” on page 16.
Client Browser Requirements for View Portal
From a client system, you can browse to a View Connection Server instance and use View Portal to install a
Mac-based View Client, a Windows-based View Client, or View Client with Local Mode. If yo use Internet
Explorer, View Portal indicates when a new version of View Client is available for download.
To use View Portal, you must have one of the following Web browsers:
nInternet Explorer 7
nInternet Explorer 8
nFirefox 3.0
nFirefox 3.5
If you use Internet Explorer and you already have View Client installed, if the version available from View
Connection Server is newer than that installed on the client device, you can choose to upgrade. If the version
is the same as that on the client device, View Portal starts the View Client installed on the local system.
NOTE View Portal does not support Linux. A native client for Linux is available only through certified VMware
partners.
Remote Display Protocol and Software Support
Remote display protocols and software provide access to the desktops of remote computers over a network
connection. View Client supports the Microsoft Remote Desktop Protocol (RDP), PCoIP from VMware, and
Hewlett-Packard Remote Graphics Software (RGS) display protocols.
nVMware View with PCoIP on page 19
PCoIP provides an optimized desktop experience for the delivery of the entire desktop environment,
including applications, images, audio, and video content for a wide range of users on the LAN or across
the WAN. PCoIP can compensate for an increase in latency or a reduction in bandwidth, to ensure that
end users can remain productive regardless of network conditions.
nMicrosoft RDP on page 20
Microsoft Remote Desktop Connection (RDC) uses RDP to transmit data. RDP is a multichannel protocol
that allows a user to connect to a computer remotely.
nHP RGS Software on page 20
View Client supports connections to desktops using HP RGS when connecting to HP Blade PCs, HP
Workstations, and HP Blade Workstations. VMware does not bundle or license HP RGS with View. You
must contact HP to license a copy of HP RGS version 5.2.5 to use with View.
nMultimedia Redirection (MMR) on page 21
Multimedia redirection (MMR) delivers the multimedia stream directly to client computers by using a
virtual channel.
VMware View Installation Guide
18 VMware, Inc.

VMware View with PCoIP
PCoIP provides an optimized desktop experience for the delivery of the entire desktop environment, including
applications, images, audio, and video content for a wide range of users on the LAN or across the WAN. PCoIP
can compensate for an increase in latency or a reduction in bandwidth, to ensure that end users can remain
productive regardless of network conditions.
PCoIP is supported as the display protocol for View desktops with virtual machines and with physical
machines that contain Teradici host cards.
PCoIP Features
Key features of PCoIP include the following:
nRemote connections using Virtual Private Networks (VPNs) are supported.
nConnections to Windows desktops with the View Agent operating system versions listed in “Supported
Operating Systems for View Agent,” on page 15 are supported.
nConnections from Windows clients with the View Client operating system versions listed in “Supported
Operating Systems for View Client and View Client with Local Mode,” on page 16 are supported.
nMMR redirection is supported for Windows XP and Vista clients. MMR redirection is not supported for
Windows 7 View Clients and is not supported on Windows 7 View desktops.
nUSB redirection is supported.
nAdobe Flash bandwidth reduction is supported.
nAudio redirection with dynamic audio quality adjustment for LAN and WAN is supported.
nMultiple monitors are supported. You can use up to four monitors and adjust the resolution for each
monitor separately, with a resolution of up to 2560x1600 per display. Pivot display and autofit are also
supported.
n32-bit color is supported for virtual displays.
nClearType fonts are supported.
nText copy and paste between the local system and the desktop is supported, up to 64 kilobytes. You cannot
copy and paste system objects such as folders and files between systems.
Video Quality
480p-formatted video You can play video at 480p or lower at native resolutions when the View
desktop has a single virtual CPU. If the operating system is Windows 7 and
you want to play the video in high-definition Flash or in full screen mode, the
desktop requires a dual virtual CPU.
720p-formatted video You can play video at 720p at native resolutions if the View desktop has a dual
virtual CPU. Performance might be affected if you play videos at 720p in high
definition or in full screen mode.
1080p-formatted video If the View desktop has a dual virtual CPU, you can play 1080p formatted
video, although the media player might need to be adjusted to a smaller
window size.
PCoIP Limitations
PCoIP has the following limitation: View clients that use PCoIP can connect to security servers, but PCoIP
sessions with the desktop ignore the security server. PCoIP uses UDP for streaming audio and video, but
security servers support only TCP.
Chapter 2 System Requirements for Client Components
VMware, Inc. 19

Recommended Guest Operating System Settings
Recommended guest operating system settings include the following settings:
nFor Windows XP desktops: 768MB RAM or more and a single CPU
nFor Windows 7 desktops: 1GB of RAM and a dual CPU
Client Hardware Requirements
Client hardware requirements include the following:
n800MHz or higher processor speed.
nx86-based processor with SSE2 extensions.
nSee the VMware View Architecture Planning Guide for information about RAM sizing for specific monitor
configurations.
Microsoft RDP
Microsoft Remote Desktop Connection (RDC) uses RDP to transmit data. RDP is a multichannel protocol that
allows a user to connect to a computer remotely.
Following are RDP-related requirements and considerations for different Windows operating systems and
features.
nFor Windows XP and Windows XPe systems, you should use Microsoft RDC 6.x.
nWindows Vista comes with RDC 6.x installed.
nWindows 2000 supports RDC 5.0. It does not support RDC 6.x.
nYou must have RDC 6.0 or later to use multiple monitors.
nFor Windows XP desktop virtual machines, you must install the RDP patches listed in Microsoft
Knowledge Base (KB) articles 323497 and 884020. If you do not install the RDP patches, a Windows Sockets
failed error message might appear on the client.
nThe View Agent installer configures the local firewall rule for inbound RDP connections to match the
current RDP port of the host operating system, which is typically 3389. If you change the RDP port number,
you must change the associated firewall rules.
You can download RDC 6.1 from the Microsoft Web site.
HP RGS Software
View Client supports connections to desktops using HP RGS when connecting to HP Blade PCs, HP
Workstations, and HP Blade Workstations. VMware does not bundle or license HP RGS with View. You must
contact HP to license a copy of HP RGS version 5.2.5 to use with View.
HP RGS consists of a server-side component, called RGS Sender, and a client-side component, the RGS
Receiver. Before you can configure View to use HP RGS, you must install HP RGS Sender in the remote desktop
operating system and install HP RGS Receiver in the desktop. Do not install RGS USB on either the sender or
receiver.
You must add the RGS Sender application or port as an exception to any firewall software. The default RGS
port is 42966. See the HP RGS documentation on the HP Web site for information on installing and configuring
HP RGS components.
VMware View Installation Guide
20 VMware, Inc.