Installation

Table Of Contents
n
A prefix for the tables in the event database, for example, VE_. The prefix enables the database to be
shared among Horizon 7 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 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 Horizon Administrator, select View Configuration > Event Configuration.
2 In the Event Database section, click Edit, enter the information in the fields provided, and click OK.
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 Horizon 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 Horizon 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 Horizon 7 events in Syslog format so that the event data can be accessible to analytics
software.
You need to configure only one host in a 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.
View Installation
VMware, Inc. 149