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
If a SAML authenticator is congured for use with a View Connection Server instance, View
Connection Server also performs certicate revocation checking on the SAML server certicate.
Obtaining a Signed SSL Certificate from a CA
If your organization does not provide you with an SSL server certicate, you must request a new certicate
that is signed by a CA.
You can use several methods to obtain a new signed certicate. For example, you can use the Microsoft
certreq utility to generate a Certicate Signing Request (CSR) and submit a certicate request to a CA.
See the Scenarios for Seing Up SSL Certicates for View document for an example that shows you how to use
certreq to accomplish this task.
For testing purposes, you can obtain a free temporary certicate based on an untrusted root from many CAs.
I You must follow certain rules and guidelines when you obtain signed SSL certicates from a
CA.
n
When you generate a certicate request on a computer, make sure that a private key is generated also.
When you obtain the SSL server certicate and import it into the Windows local computer certicate
store, there must be an accompanying private key that corresponds to the certicate.
n
To comply with VMware security recommendations, use the fully qualied domain name (FQDN) that
client devices use to connect to the host. Do not use a simple server name or IP address, even for
communications within your internal domain.
n
Do not create certicates for servers using a certicate template that is compatible only with a Windows
Server 2008 enterprise CA or later.
n
Do not generate certicates for servers using a KeyLength value under 1024. 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. Certicate validations that are performed by View Connection Server will also
fail, resulting in the aected servers showing as red in the View Administrator dashboard.
For general information about obtaining certicates, consult the Microsoft online help available with the
Certicate Snap-in to MMC. If the Certicate Snap-in is not yet installed on your computer, see “Add the
Certicate Snap-In to MMC,” on page 84.
Obtain a Signed Certificate from a Windows Domain or Enterprise CA
To obtain a signed certicate from a Windows Domain or Enterprise CA, you can use the Windows
Certicate Enrollment wizard in the Windows Certicate Store.
This method of requesting a certicate is appropriate if communications between computers remain within
your internal domain. For example, obtaining a signed certicate from a Windows Domain CA might be
appropriate for server-to-server communications.
If your clients connect to View servers from an external network, request SSL server certicates that are
signed by a trusted, third-party CA.
Prerequisites
n
Determine the fully qualied domain name (FQDN) that client devices use to connect to the host.
To comply with VMware security recommendations, use the FQDN, not a simple server name or IP
address, even for communications within your internal domain.
n
Verify that the Certicate snap-in was added to MMC. See “Add the Certicate Snap-In to MMC,” on
page 84.
n
Verify that you have the appropriate credentials to request a certicate that can be issued to a computer
or service.
View Installation
82 VMware, Inc.