5.2
Table Of Contents
- VMware Horizon View Installation
- Contents
- VMware Horizon View Installation
- System Requirements for Server Components
- System Requirements for Guest Operating Systems
- Preparing Active Directory
- Configuring Domains and Trust Relationships
- Creating an OU for View Desktops
- Creating OUs and Groups for Kiosk Mode Client Accounts
- Creating Groups for View Users
- Creating a User Account for vCenter Server
- Create a User Account for View Composer
- Configure the Restricted Groups Policy
- Using View Group Policy Administrative Template Files
- Prepare Active Directory for Smart Card Authentication
- Installing 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 Products Silently by Using MSI Command-Line Options
- Installing View Transfer Server
- 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 View Clients to Trust Root and Intermediate Certificates
- Configuring Certificate Revocation Checking on Server Certificates
- Configuring Certificate Checking in View Client for Windows
- Configure the PCoIP Secure Gateway to Use a New SSL Certificate
- View Transfer Server and SSL Certificates
- Setting View Administrator to Trust a vCenter Server or View Composer Certificate
- Benefits of Using SSL Certificates Signed by a CA
- Configuring View for the First Time
- Configuring User Accounts for vCenter Server and View Composer
- Where to Use the vCenter Server User and Domain User for View Composer
- Configure a vCenter Server User for View Manager, View Composer, and Local Mode
- View Manager Privileges Required for the vCenter Server User
- View Composer Privileges Required for the vCenter Server User
- Local Mode Privileges Required for the vCenter Server User
- Configuring View Connection Server for the First Time
- View Administrator and View Connection Server
- Log In to View Administrator
- Install the View Connection Server License Key
- Add vCenter Server Instances to View Manager
- 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 View Desktop Logon Storms
- Accept the Thumbprint of a Default SSL Certificate
- Configuring View Client Connections
- 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
- Replace the Default Ports for View Transfer Server
- Sizing Windows Server Settings to Support Your Deployment
- Configuring User Accounts for vCenter Server and View Composer
- Adding the View Desktops Plug-in to the vSphere Web Client
- Configuring Event Reporting
- Index
sso-admin@domain is the username and domain of a user with vCenter SSO administrator privileges. On
a vCenter Server that runs on Windows Server, the default vCenter SSO administrator user is
Admin@System-Domain. On a vCenter Server Virtual Appliance, the default user is root@localos.
3 At the prompt, type the View Administrators user password.
4 At the prompt, type the vCenter SSO administrator user password.
A return code of 0 indicates that the configuration was successful.
NOTE When you type the password, the following warning message might appear. You can ignore this
message:
log4j: WARN No appenders could be found for logger
<com.vmware.vim.vmomi.core.types.impl.VmodlContextImpl>.
log4j: WARN Please initialize the log4j system properly.
5 If necessary, restart the VMware vSphere Web Client Service.
In certain cases, this service must be restarted to allow the registration to take effect.
The service resides on the vCenter Server or another computer, not on the View Connection Server
computer.
6 (Optional) Verify that the View Connection Server pod, View Desktops plug-in, and View Connection
Server instance were registered successfully by using the regtool.cmd showDetails command.
For example: regtool.cmd showDetails -u view-admin@domain
What to do next
Log in to the vSphere Web Client to verify that the View Desktops plug-in was added. See “Search for View
Users in the vSphere Web Client,” on page 119.
Search for View Users in the vSphere Web Client
In View Desktops in the vSphere Web Client, you can perform a quick search or simple search for a View
user, display the desktops that are associated with that user, and examine the underlying virtual machines.
After you first configure the View Desktops plug-in, perform this task to verify that the plug-in was added
to the vSphere Web Client.
When you search for a View user in the vSphere Web Client, View Desktops displays floating desktops on
which the user is logged in and dedicated desktops that are assigned to the user. Note that a floating
desktop is displayed even when the session is in a disconnected state. If a user is entitled to a floating
desktop pool but not logged in, no floating desktops in that pool are displayed.
This procedure uses quick search. You can also use a simple search to search for View users. In this Tech
Preview, you cannot use an advanced search to search for View users.
Prerequisites
n
Verify that the View Desktops plug-in was configured with the vCenter Lookup Service and registered
with the vSphere Web Client. See “Configure View to Recognize the vCenter Lookup Service,” on
page 117 and “Register the View Desktops Plug-in,” on page 118.
n
Verify that you can log in to the vSphere Web Client as a user with the View Administrators role or
View Administrators (Read only) role and with the vSphere Administrator privilege for the View
desktop virtual machines and vCenter Server folders that store the virtual machines.
If you search for desktops without having the vSphere Administrator privilege, the virtual machine
names are displayed as disabled links and you cannot access the virtual machine information.
Chapter 9 Adding the View Desktops Plug-in to the vSphere Web Client
VMware, Inc. 119