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
Configure the Event Database
The event database stores information about View events as records in a database rather than in a log file.
You configure an event database after installing a View Connection Server instance. You need to configure
only one host in a View Connection Server group. The remaining hosts in the group are configured
automatically.
NOTE The security of the database connection between the View Connection Server instance and an
external database is the responsibility of the administrator, although event traffic is limited to information
about the health of the View environment. If you want to take extra precautions, you can secure this channel
through IPSec or other means, or you can deploy the database locally on the View Connection Server
computer.
You can use Microsoft SQL Server or Oracle database reporting tools to examine events in the database
tables. For more information, see the VMware Horizon View Integration document.
You can also generate View events in Syslog format so that the event data can be accessible to third-party
analytics software. You use the vdmadmin command with the -I option to record View event messages in
Syslog format in event log files. See "Generating View Event Log Messages in Syslog Format Using the -I
Option" in the VMware Horizon View Administration document.
Prerequisites
You need the following information to configure an event database:
n
The DNS name or IP address of the database server.
n
The type of database server: Microsoft SQL Server or Oracle.
n
The port number that is used to access the database server. The default is 1521 for Oracle and 1433 for
SQL Server. For SQL Server, if the database server is a named instance or if you use SQL Server
Express, you might need to determine the port number. See the Microsoft KB article about connecting
to a named instance of SQL Server, at http://support.microsoft.com/kb/265808.
n
The name of the event database that you created on the database server. See “Add a Database and
Database User for View Events,” on page 121.
n
The username and password of the user you created for this database. See “Add a Database and
Database User for View Events,” on page 121.
Use SQL Server Authentication for this user. Do not use the Integrated Windows Authentication
security model method of authentication.
n
A prefix for the tables in the event database, for example, VE_. The prefix enables the database to be
shared among View installations.
NOTE You must enter characters that are valid for the database software you are using. The syntax of
the prefix is not checked when you complete the dialog box. If you enter characters that are not valid
for the database software you are using, an error occurs when View Connection Server attempts to
connect to the database server. The log file indicates all errors, including this error and any others
returned from the database server if the database name is invalid.
Procedure
1 In View Administrator, select View Configuration > Event Configuration.
2 In the Event Database section, click Edit, enter the information in the fields provided, and click OK.
Chapter 10 Configuring Event Reporting
VMware, Inc. 123