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
n
If you upgrade to View 5.1 or later from an earlier release, and a valid keystore le is congured on the
Windows Server computer. The installation extracts the keys and certicates and imports them into the
Windows Certicate Store.
vCenter Server and View Composer
Before you add vCenter Server and View Composer to View in a production environment, make sure that
vCenter Server and View Composer use certicates that are signed by a CA.
For information about replacing the default certicate for vCenter Server, see "Replacing vCenter Server
Certicates" on the VMware Technical Papers site at hp://www.vmware.com/resources/techresources/.
If you install vCenter Server and View Composer on the same Windows Server host, they can use the same
SSL certicate, but you must congure the certicate separately for each component.
PCoIP Secure Gateway
To comply with industry or jurisdiction security regulations, you can replace the default SSL certicate that
is generated by the PCoIP Secure Gateway (PSG) service with a certicate that is signed by a CA.
Conguring the PSG service to use a CA-signed certicate is highly recommended, particularly for
deployments that require you to use security scanners to pass compliance testing. See “Congure the PCoIP
Secure Gateway to Use a New SSL Certicate,” on page 91.
Blast Secure Gateway
By default, the Blast Secure Gateway (BSG) uses the SSL certicate that is congured for the View
Connection Server instance or security server on which the BSG is running. If you replace the default, self-
signed certicate for a server with a CA-signed certicate, the BSG also uses the CA-signed certicate.
SAML 2.0 Authenticator
VMware Identity Manager uses SAML 2.0 authenticators to provide Web-based authentication and
authorization across security domains. If you want View to delegate authentication to
VMware Identity Manager, you can congure View to accept SAML 2.0 authenticated sessions from
VMware Identity Manager. When VMware Identity Manager is congured to support View,
VMware Identity Manager users can connect to remote desktops by selecting desktop icons on the Horizon
User Portal.
In View Administrator, you can congure SAML 2.0 authenticators for use with View Connection Server
instances.
Before you add a SAML 2.0 authenticator in View Administrator, make sure that the SAML 2.0 authenticator
uses a certicate that is signed by a CA.
Additional Guidelines
For general information about requesting and using SSL certicates that are signed by a CA, see “Benets of
Using SSL Certicates Signed by a CA,” on page 95.
When client endpoints connect to a View Connection Server instance or security server, they are presented
with the server's SSL server certicate and any intermediate certicates in the trust chain. To trust the server
certicate, the client systems must have installed the root certicate of the signing CA.
When View Connection Server communicates with vCenter Server and View Composer, View Connection
Server is presented with SSL server certicates and intermediate certicates from these servers. To trust the
vCenter Server and View Composer servers, the View Connection Server computer must have installed the
root certicate of the signing CA.
View Installation
80 VMware, Inc.