The Horizon Connection Server stores application level events and actions in a dedicated database rather than log files. This makes day-to-day administration easier while off-loading these events to a separate system for resiliency. An events database is configured after Connection Server deployment. It must only be configured one time, even in the case of multiple grouped Connection Servers, as the configuration will be applied to the other servers automatically. Satisfies: SRG-APP-000089-AS-000050, SRG-APP-000091-AS-000052, SRG-APP-000092-AS-000053, SRG-APP-000095-AS-000056, SRG-APP-000096-AS-000059, SRG-APP-000097-AS-000060, SRG-APP-000098-AS-000061, SRG-APP-000099-AS-000062, SRG-APP-000100-AS-000063, SRG-APP-000101-AS-000072, SRG-APP-000266-AS-000168, SRG-APP-000343-AS-000030, SRG-APP-000495-AS-000220, SRG-APP-000499-AS-000224, SRG-APP-000503-AS-000228, SRG-APP-000504-AS-000229, SRG-APP-000505-AS-000230, SRG-APP-000509-AS-000234
1. Log in to the Horizon Connection Server Console. 2. From the left pane, navigate to Monitor >> Events. If the right pane is empty or shows "Events DB is not configured", this is a finding.
1. Log in to the Horizon Connection Server Console. 2. From the left pane, navigate to Settings >> Event Configuration. 3. In the right pane, under "Event Database", click "Edit" and enter the necessary database information in the fields provided. 4. Click "OK". Note: Horizon Connection Server supports MSSQL, Oracle, and PostgreSQL database types. Consult Omnissa documentation for more detailed database setup information and minimum required privileges.