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
What to do next
Specify the account in View Administrator when you congure View Composer domains in the Add
vCenter Server wizard and when you congure and deploy linked-clone desktop pools.
Create a User Account for Instant-Clone Operations
Before you deploy instant clones, you must create a user account that has the permission to perform certain
operations in Active Directory.
Select this account when you add an instant-clone domain administrator before deploying instant-clone
desktop pools. For more information, see "Add an Instant-Clone Domain Administrator" in the Seing Up
Virtual Desktops in Horizon 7 document.
Procedure
1 In Active Directory, create a user account in the same domain as the Connection Server or in a trusted
domain.
2 Add the Create Computer Objects, Delete Computer Objects, and Write All Properties permissions to
the account on the container for the instant-clone computer accounts.
The following list shows the required permissions for the user account, including permissions that are
assigned by default:
n
List Contents
n
Read All Properties
n
Write All Properties
n
Read Permissions
n
Reset Password
n
Create Computer Objects
n
Delete Computer Objects
Make sure that the permissions apply to the correct container and to all child objects of the container.
Configure the Restricted Groups Policy
To be able to connect to a remote desktop, users must belong to the local Remote Desktop Users group of the
remote desktop. You can use the Restricted Groups policy in Active Directory to add users or groups to the
local Remote Desktop Users group of every remote desktop that is joined to your domain.
The Restricted Groups policy sets the local group membership of computers in the domain to match the
membership list seings dened in the Restricted Groups policy. The members of your remote desktop
users group are always added to the local Remote Desktop Users group of every remote desktop that is
joined to your domain. When adding new users, you need only add them to your remote desktop users
group.
Prerequisites
Create a group for remote desktop users in your domain in Active Directory.
Chapter 5 Preparing Active Directory
VMware, Inc. 31