7.0
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 View 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
- View Administrator and View 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 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 your ESXi hosts are not running ESXi 6.0 U1b or later, and you cannot upgrade, you might also need to
enable TLSv1.0 connections to ESXi hosts from View Composer.
Prerequisites
n
Verify that you have View Composer 7.0 or a later release installed.
n
Verify that you can log in to the View Composer machine as an Administrator to use the Windows
Registry Editor.
Procedure
1 On the machine that hosts View Composer, open the Windows Registry Editor (regedit.exe).
2 Navigate to HKLM\System\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS
1.0\Client
If this key does not already exist, create this key.
3 Delete the value Enabled if it exists.
4 Create or edit the DWORD value DisabledByDefault and set it to 0.
5 Restart the VMware Horizon View Composer service.
TLSv1.0 connections from View Composer to vCenter are now enabled.
6 In the Windows Registry on the View Composer machine, navigate to HKLM\SOFTWARE\VMware,
Inc.\VMware View Composer.
7 Create or edit the String value EnableTLS1.0 and set it to 1.
8 If the View Composer host is a 64-bit machine, navigate to HKLM\SOFTWARE\WOW6432Node\VMware,
Inc\VMware View Composer.
9 Create or edit the String value EnableTLS1.0 and set it to 1.
10 Restart the VMware Horizon View Composer service.
TLSv1.0 connections from View Composer to ESXi hosts are now enabled.
Configuring Your Infrastructure for View Composer
You can take advantage of features in vSphere, vCenter Server, Active Directory, and other components of
your infrastructure to optimize the performance, availability, and reliability of View Composer.
Configuring the vSphere Environment for View Composer
To support View Composer, you should follow certain best practices when you install and configure
vCenter Server, ESXi, and other vSphere components.
These best practices let View Composer work efficiently in the vSphere environment.
n
After you create the path and folder information for linked-clone virtual machines, do not change the
information in vCenter Server. Instead, use View Administrator to change the folder information.
If you change this information in vCenter Server, View cannot successfully look up the virtual machines
in vCenter Server.
n
Make sure that the vSwitch settings on the ESXi host are configured with enough ports to support the
total number of virtual NICs that are configured on the linked-clone virtual machines that run on the
ESXi host.
n
When you deploy linked-clone desktops in a resource pool, make sure that your vSphere environment
has enough CPU and memory to host the number of desktops that you require. Use vSphere Client to
monitor CPU and memory usage in resource pools.
Chapter 6 Installing View Composer
VMware, Inc. 49