5.2
Table Of Contents
- VMware Horizon View Installation
- Contents
- VMware Horizon View Installation
- System Requirements for Server Components
- System Requirements for Guest Operating Systems
- Preparing Active Directory
- Configuring Domains and Trust Relationships
- Creating an OU for View Desktops
- Creating OUs and Groups for Kiosk Mode Client Accounts
- Creating Groups for View Users
- Creating a User Account for vCenter Server
- Create a User Account for View Composer
- Configure the Restricted Groups Policy
- Using View Group Policy Administrative Template Files
- Prepare Active Directory for Smart Card Authentication
- Installing View Composer
- Installing View Connection Server
- Installing the View Connection Server Software
- Installation Prerequisites for View Connection Server
- Install View Connection Server with a New Configuration
- Install a Replicated Instance of View Connection Server
- Configure a Security Server Pairing Password
- Install a Security Server
- Firewall Rules for View Connection Server
- Reinstall View Connection Server with a Backup Configuration
- Microsoft Windows Installer Command-Line Options
- Uninstalling View Products Silently by Using MSI Command-Line Options
- Installing View Transfer Server
- Configuring SSL Certificates for View Servers
- Understanding SSL Certificates for View Servers
- Overview of Tasks for Setting Up SSL Certificates
- Obtaining a Signed SSL Certificate from a CA
- Configure View Connection Server, Security Server, or View Composer to Use a New SSL Certificate
- Configure View Clients to Trust Root and Intermediate Certificates
- Configuring Certificate Revocation Checking on Server Certificates
- Configuring Certificate Checking in View Client for Windows
- Configure the PCoIP Secure Gateway to Use a New SSL Certificate
- View Transfer Server and SSL Certificates
- Setting View Administrator to Trust a vCenter Server or View Composer Certificate
- Benefits of Using SSL Certificates Signed by a CA
- Configuring View for the First Time
- Configuring User Accounts for vCenter Server and View Composer
- Where to Use the vCenter Server User and Domain User for View Composer
- Configure a vCenter Server User for View Manager, View Composer, and Local Mode
- View Manager Privileges Required for the vCenter Server User
- View Composer Privileges Required for the vCenter Server User
- Local Mode Privileges Required for the vCenter Server User
- Configuring View Connection Server for the First Time
- View Administrator and View Connection Server
- Log In to View Administrator
- Install the View Connection Server License Key
- Add vCenter Server Instances to View Manager
- Configure View Composer Settings
- Configure View Composer Domains
- Allow vSphere to Reclaim Disk Space in Linked-Clone Virtual Machines
- Configure View Storage Accelerator for vCenter Server
- Concurrent Operations Limits for vCenter Server and View Composer
- Setting a Concurrent Power Operations Rate to Support View Desktop Logon Storms
- Accept the Thumbprint of a Default SSL Certificate
- Configuring View Client Connections
- Replacing Default Ports for View Services
- Replace the Default HTTP Ports or NICs for View Connection Server Instances and Security Servers
- Replace the Default Ports or NICs for the PCoIP Secure Gateway on View Connection Server Instances and on Security Servers
- Replace the Default Port for View Composer
- Replace the Default Ports for View Transfer Server
- Sizing Windows Server Settings to Support Your Deployment
- Configuring User Accounts for vCenter Server and View Composer
- Adding the View Desktops Plug-in to the vSphere Web Client
- Configuring Event Reporting
- Index
n
Storage 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 and Upgrade Requirements for View Transfer Server
You must install View Transfer Server as a Windows application in a virtual machine that meets specific
requirements.
IMPORTANT If users will be checking out local desktops that use the space-efficient sparse disk format (SE-
Flex), available starting with vSphere 5.1, View Transfer Server must be hosted on a vSphere 5.1 or later
virtual machine (virtual hardware version 9). The SE Sparse disk format allows stale or deleted data within
a guest operating system to be reclaimed with a wipe and shrink process.
To use the space reclamation feature, you must verify that your vCenter Server and hosts are version 5.1
with ESXi 5.1 download patch ESXi510-201212001 or later. In an ESXi cluster, verify that all the hosts are
version 5.1 with download patch ESXi510-201212001 or later.
The virtual machine that hosts View Transfer Server must meet several requirements regarding network
connectivity:
n
It must be managed by the same vCenter Server instance as the local desktops that it will manage.
n
It does not have to be part of a domain.
n
It must use a static IP address.
The View Transfer Server software cannot coexist on the same virtual machine with any other View
Manager software component, including View Connection Server.
Do not manually add or remove PCI devices on the virtual machine that hosts View Transfer Server. If you
add or remove PCI devices, View might be unable to discover hot-added devices, which might cause data
transfer operations to fail.
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 at least the minimum required
amount of RAM.
Table 1‑6. Operating System Support for View Transfer Server
Operating System Version Edition Minimum RAM
Windows Server 2008 R2 64-bit Standard
Enterprise
4GB
Windows Server 2008 R2 SP1 64-bit Standard
Enterprise
4GB
IMPORTANT Configure two virtual CPUs for virtual machines that host View Transfer Server.
VMware Horizon View Installation
12 VMware, Inc.