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
Set the PSG Certificate Friendly Name in the Windows Registry
The PSG identies the SSL certicate to use by means of the server name and certicate Friendly name. You
must set the Friendly name value in the Windows registry on the View Connection Server or security server
computer on which the PSG is running.
The certicate Friendly name vdm is used by all View Connection Server instances and security servers. By
contrast, you can congure your own certicate Friendly name for the PSG certicate. You must congure a
Windows registry seing to enable the PSG to match the correct name with the Friendly name that you will
set in the Windows certicate store.
The PSG can use the same SSL certicate as the server on which the PSG is running. If you congure the
PSG to use the same certicate as the server, the Friendly name must be vdm.
The Friendly name value, in both the registry and the Windows certicate store, is case sensitive.
Prerequisites
n
Verify that the Window registry contains the correct subject name that is used to reach the PSG port and
that matches the PSG certicate subject name or subject alternate name. See “Verify That the Server
Name Matches the PSG Certicate Subject Name,” on page 92.
n
Verify that the certicate Friendly name is congured in the Windows local computer certicate store.
See “Congure a PSG Certicate in the Windows Certicate Store,” on page 92.
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, SSLCertWinCertFriendlyName, to this registry key.
4 Modify the SSLCertWinCertFriendlyName value and type the certicate Friendly name to be used by the
PSG.
For example: pcoip
If you use the same certicate as the server, the value must be vdm.
5 Restart the VMware Horizon View PCoIP Secure Gateway service to make your changes take eect.
What to do next
Verify that client devices continue to connect to the PSG.
If you are using a security scanner for compliance testing, scan the PSG port.
(Optional) Force a CA-Signed Certificate to Be Used for Connections to the PSG
You can ensure that all client connections to the PSG use the CA-signed certicate for the PSG instead of the
default legacy certicate. This procedure is not required to congure a CA-signed certicate for the PSG.
Take these steps only if it makes sense to force the use of a CA-signed certicate in your View deployment.
In some cases, the PSG might present the default legacy certicate instead of the CA-signed certicate to a
security scanner, invalidating the compliance test on the PSG port. To resolve this issue, you can congure
the PSG not to present the default legacy certicate to any device that aempts to connect.
I Performing this procedure prevents all legacy clients from connecting to this server over PCoIP.
View Installation
94 VMware, Inc.