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
Configuring Your Infrastructure for View Composer
You can take advantage of features in vSphere, vCenter Server, Active Directory, and other components of
your infrastructure to optimize the performance, availability, and reliability of View Composer.
Configuring the vSphere Environment for View Composer
To support View Composer, you should follow certain best practices when you install and configure
vCenter Server, ESX/ESXi, and other vSphere components.
These best practices let View Composer work efficiently in the vSphere environment.
n
After you create the path and folder information for linked-clone virtual machines, do not change the
information in vCenter Server. Instead, use View Administrator to change the folder information.
If you change this information in vCenter Server, View Manager cannot successfully look up the virtual
machines in vCenter Server.
n
Make sure that the vSwitch settings on the ESX/ESXi host are configured with enough ports to support
the total number of virtual NICs that are configured on the linked-clone virtual machines that run on
the ESX/ESXi host.
n
When you deploy linked-clone desktops in a resource pool, make sure that your vSphere environment
has enough CPU and memory to host the number of desktops that you require. Use vSphere Client to
monitor CPU and memory usage in resource pools.
n
In vSphere 5.1 and later, a cluster that is used for View Composer linked clones can contain more than
eight ESX/ESXi hosts if the replica disks are stored on VMFS5 or later datastores or NFS datastores. If
you store replicas on a VMFS version earlier than VMFS5, a cluster can have at most eight hosts.
In vSphere 5.0, you can select a cluster with more than eight ESXi hosts if the replicas are stored on NFS
datastores. If you store replicas on VMFS datastores, a cluster can have at most eight hosts.
n
Use vSphere DRS. DRS efficiently distributes linked-clone virtual machines among your hosts.
NOTE Storage vMotion is not supported for linked-clone desktops.
Additional Best Practices for View Composer
To make sure that View Composer works efficiently, check that your dynamic name service (DNS) operates
correctly, and run antivirus software scans at staggered times.
By making sure that DNS resolution operates correctly, you can overcome intermittent issues caused by
DNS errors. The View Composer service relies on dynamic name resolution to communicate with other
computers. To test DNS operation, ping the Active Directory and View Connection Server computers by
name.
If you stagger the run times for your antivirus software, performance of the linked-clone desktops is not
affected. If the antivirus software runs in all linked clones at the same time, excessive I/O operations per
second (IOPS) occur in your storage subsystem. This excessive activity can affect performance of the linked-
clone desktops.
Chapter 4 Installing View Composer
VMware, Inc. 37