Installation
Table Of Contents
- View Installation
- Contents
- View Installation
- System Requirements for Server Components
- System Requirements for Guest Operating Systems
- Installing View in an IPv6 Environment
- Setting Up View in an IPv6 Environment
- Supported vSphere, Database, and Active Directory Versions in an IPv6 Environment
- Supported Operating Systems for View Servers in an IPv6 Environment
- Supported Windows Operating Systems for Desktops and RDS Hosts in an IPv6 Environment
- Supported Clients in an IPv6 Environment
- Supported Remoting Protocols in an IPv6 Environment
- Supported Authentication Types in an IPv6 Environment
- Other Supported Features in an IPv6 Environment
- Installing View in FIPS Mode
- Preparing Active Directory
- Configuring Domains and Trust Relationships
- Creating an OU for Remote Desktops
- Creating OUs and Groups for Kiosk Mode Client Accounts
- Creating Groups for Users
- Creating a User Account for vCenter Server
- Creating a User Account for a Standalone View Composer Server
- Create a User Account for View Composer AD Operations
- Create a User Account for Instant-Clone Operations
- Configure the Restricted Groups Policy
- Using Horizon 7 Group Policy Administrative Template Files
- Prepare Active Directory for Smart Card Authentication
- Disable Weak Ciphers in SSL/TLS
- Installing View Composer
- Prepare a View Composer Database
- Configuring an SSL Certificate for View Composer
- Install the View Composer Service
- Enable TLSv1.0 on vCenter and ESXi Connections from View Composer
- Configuring Your Infrastructure for 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 Components Silently by Using MSI Command-Line Options
- 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 Client Endpoints to Trust Root and Intermediate Certificates
- Configuring Certificate Revocation Checking on Server Certificates
- Configure the PCoIP Secure Gateway to Use a New SSL Certificate
- Setting View Administrator to Trust a vCenter Server or View Composer Certificate
- Benefits of Using SSL Certificates Signed by a CA
- Troubleshooting Certificate Issues on View Connection Server and Security Server
- Configuring View for the First Time
- Configuring User Accounts for vCenter Server and View Composer
- Configuring View Connection Server for the First Time
- Horizon Administrator and Horizon Connection Server
- Log In to View Administrator
- Install the Product License Key
- Add vCenter Server Instances to View
- 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 Remote Desktop Logon Storms
- Accept the Thumbprint of a Default SSL Certificate
- Configuring Horizon Client Connections
- Configure the PCoIP Secure Gateway and Secure Tunnel Connections
- Configure the Blast Secure Gateway
- Configuring External URLs for Secure Gateway and Tunnel Connections
- Set the External URLs for a View Connection Server Instance
- Modify the External URLs for a Security Server
- Give Preference to DNS Names When View Connection Server Returns Address Information
- Allow HTML Access Through a Load Balancer
- Allow HTML Access Through a Gateway
- 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 Control Port for PCoIP Secure Gateway on Connection Server Instances and on Security Servers
- Replace the Default Port for View Composer
- Change the Port Number for HTTP Redirection to Connection Server
- Prevent HTTP Redirection for Client Connections to Connection Server
- Enable Remote Access to View Performance Counters on Connection Servers
- Sizing Windows Server Settings to Support Your Deployment
- Configuring Event Reporting
- Index
6 Restart the View Composer service to make your changes take eect.
Example: SviConfig ReplaceCertificate
The following example replaces the certicate that is bound to the View Composer port:
sviconfig -operation=ReplaceCertificate
-delete=false
Configure Client Endpoints to Trust Root and Intermediate
Certificates
If a View server certicate is signed by a CA that is not trusted by client computers and client computers
that access View Administrator, you can congure all Windows client systems in a domain to trust the root
and intermediate certicates. To do so, you must add the public key for the root certicate to the Trusted
Root Certication Authorities group policy in Active Directory and add the root certicate to the Enterprise
NTAuth store.
For example, you might have to take these steps if your organization uses an internal certicate service.
You do not have to take these steps if the Windows domain controller acts as the root CA, or if your
certicates are signed by a well known CA. For well known CAs, the operating system venders preinstall
the root certicate on client systems.
If your server certicates are signed by a lile-known intermediate CA, you must add the intermediate
certicate to the Intermediate Certication Authorities group policy in Active Directory.
For client devices that use other operating systems than Windows, see the following instructions for
distributing root and intermediate certicates that users can install:
n
For Horizon Client for Mac, see “Congure Horizon Client for Mac to Trust Root and Intermediate
Certicates,” on page 89.
n
For Horizon Client for iOS, see “Congure Horizon Client for iOS to Trust Root and Intermediate
Certicates,” on page 90.
n
For Horizon Client for Android, see documentation on the Google Web site, such as the Android 3.0
User's Guide
n
For Horizon Client for Linux, see the Ubuntu documentation
Prerequisites
Verify that the server certicate was generated with a KeyLength value of 1024 or larger. Client endpoints
will not validate a certicate on a server that was generated with a KeyLength under 1024, and the clients will
fail to connect to the server.
Procedure
1 On your Active Directory server, use the certutil command to publish the certicate to the Enterprise
NTAuth store.
For example: certutil -dspublish -f path_to_root_CA_cert NTAuthCA
View Installation
88 VMware, Inc.