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
Prerequisites
Verify that all client devices that connect to this server, including thin clients, run Horizon Client 5.2 for
Windows or Horizon Client 2.0 or later releases. You must upgrade the legacy clients.
Procedure
1 Start the Windows Registry Editor on the View Connection Server or security server computer where
the PCoIP Secure Gateway is running.
2 Navigate to the HKEY_LOCAL_MACHINE\SOFTWARE\Teradici\SecurityGateway registry key.
3 Add a new String (REG_SZ) value, SSLCertPresentLegacyCertificate, to this registry key.
4 Set the SSLCertPresentLegacyCertificate value to 0.
5 Restart the VMware Horizon View PCoIP Secure Gateway service to make your changes take eect.
Setting View Administrator to Trust a vCenter Server or View
Composer Certificate
In the View Administrator dashboard, you can congure View to trust a vCenter Server or View Composer
certicate that is untrusted.
VMware strongly recommends that you congure vCenter Server and View Composer to use SSL
certicates that are signed by a CA. Alternatively, you can accept the thumbprint of the default certicate for
vCenter Server or View Composer.
Similarly, VMware recommends that you congure SAML 2.0 authenticators to use SSL certicates that are
signed by a CA. Alternatively, in the View Administrator dashboard you can congure View to trust an
untrusted SAML 2.0 server certicate by accepting the thumbprint of the default certicate.
Benefits of Using SSL Certificates Signed by a CA
A CA is a trusted entity that guarantees the identity of the certicate and its creator. When a certicate is
signed by a trusted CA, users no longer receive messages asking them to verify the certicate, and thin
client devices can connect without requiring additional conguration.
You can request an SSL server certicate that is specic to a Web domain such as www.mycorp.com, or you can
request a wildcard SSL server certicate that can be used throughout a domain such as *.mycorp.com. To
simplify administration, you might choose to request a wildcard certicate if you need to install the
certicate on multiple servers or in dierent subdomains.
Typically, domain-specic certicates are used in secure installations, and CAs usually guarantee more
protection against losses for domain-specic certicates than for wildcard certicates. If you use a wildcard
certicate that is shared with other services, the security of the VMware Horizon product also depends on
the security of those other services. If you use a wildcard certicate, you must ensure that the private key is
transferrable between servers.
When you replace the default certicate with your own certicate, clients use your certicate to authenticate
the server. If your certicate is signed by a CA, the certicate for the CA itself is typically embedded in the
browser or is located in a trusted database that the client can access. After a client accepts the certicate, it
responds by sending a secret key, which is encrypted with the public key contained in the certicate. The
secret key is used to encrypt trac between the client and the server.
Chapter 8 Configuring SSL Certificates for View Servers
VMware, Inc. 95