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
- 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
- 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 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 Secure HTML Access
- 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
- 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
3 (Optional) In the Event Settings window, click Edit, change the length of time to show events and the
number of days to classify events as new, and click OK.
These settings pertain to the length of time the events are listed in the View Administrator interface.
After this time, the events are only available in the historical database tables.
The Database Configuration window displays the current configuration of the event database.
4 Select Monitoring > Events to verify that the connection to the event database is successful.
If the connection is unsuccessful, and error message appears. If you are using SQL Express or if you are
using a named instance of SQL Server, you might need to determine the correct port number, as
mentioned in the prerequisites.
In the View Administrator Dashboard, the System Component Status displays the event database server
under the Reporting Database heading.
Configure Event Logging for Syslog Servers
You can generate View events in Syslog format so that the event data can be accessible to analytics software.
You need to configure only one host in a View Connection Server group. The remaining hosts in the group
are configured automatically.
If you enable file-based logging of events, events are accumulated in a local log file. If you specify a file
share, these log files are moved to that share.
n
Use a local file only for quick troubleshooting during configuration, perhaps before the Events database
is configured, so that you have some way to see events.
The maximum size of the local directory for event logs, including closed log files, before the oldest files
are deleted, is 300MB. The default destination of the Syslog output is %PROGRAMDATA
%\VMware\VDM\events\.
n
Use a UNC path to save log files for a long-term record of events, of if you do not have a Syslog server,
or if your current Syslog server does not meet your needs.
You can alternatively use a vdmadmin command to configure file-based logging of events in Syslog format.
See the topic about generating View event log messages in Syslog format using the -I option of the vdmadmin
command, in the View Administration document.
IMPORTANT Syslog data is sent across the network without software-based encryption, and might contain
sensitive data, such as user names. VMware recommends using link-layer security, such as IPSEC, to avoid
the possibility of this data being monitored on the network.
Prerequisites
You need the following information to configure View Connection Server so that events can be recorded in
Syslog format or sent to a Syslog server, or both:
n
If you plan to use a Syslog server to listen for the View events on a UDP port, you must have the DNS
name or IP address of the Syslog server and the UDP port number. The default UDP port number is
514.
n
If you plan to collect logs in a flat-file format, you must have the UNC path to the file share and folder
in which to store the log files, and you must have the user name, domain name, and password of an
account that has permission to write to the file share.
Procedure
1 In View Administrator, select View Configuration > Event Configuration.
View Installation
118 VMware, Inc.