Skip to content

Overview

About Accops User Experience Manager and Components

Accops User Experience Manager (AUEM) is a suite of components that monitors system performance, suggests corrective actions, and shares details with Accops Reporting Server (ARS) for detailed analysis. AUEM in an Accops VDI environment helps:

  1. Administrators:

    1. View and analyze server level reports

    2. View and analyze user level reports

    3. Report anomalies

    4. Understand root cause of experience dissatisfaction and improvise

  2. End-users:

    1. Notify anomalies

    2. Suggest remediation

    3. View processes and actions to stop processes that are using resources excessively

    4. Improvise system performance using remediation suggested

Terminology

Term Meaning
AUEM The overall suite covering AWEM, AUPM, and the Tray Agent.
AWEM (Accops Windows Event Monitor) Windows service that analyzes system events tied to user activity.
AUPM (Accops User Performance Manager) Windows service that monitors resource utilization (CPU, RAM, network) and evaluates anomalies against configured thresholds.
Tray Agent The end-user application in the system tray. Shows notifications, Task Manager, network latency, and notification history.
DVM Agent The Accops HyWorks Desktop Agent running on the Session Host/VDI desktop. Has its own, separate detailed activity-logging path to ARS.
ARS (Accops Reporting Server) The centralized reporting and analytics platform all of the above send data to.

How the pieces fit together

AWEM, AUPM, and the Tray Agent all run on the Session Host/VDI desktop alongside the DVM Agent, and all report to ARS over TCP port 9200. The DVM Agent also sends detailed user session and process monitoring events to ARS. For the full picture, install steps, and every port/version requirement, see AUEM Installation and Basic Configurations and the ARS Installation Guide.

Local monitoring, anomaly detection, and end-user notifications work as soon as AUEM is enabled, whether or not ARS is configured. ARS is only required for centralized, cross-desktop reporting and historical analysis; see ARS Settings to send data there.

What do you want to do?

I want to... Go to
Find where detailed user session/process activity is logged DVM Agent Activity Logging
Enable System Monitoring, User Logon Monitoring and Anomalies Detection and Notifications Enable AUEM
Understand how AUEM/DVM data reaches ARS ARS Settings
Set or change anomaly thresholds (CPU, memory, process count, latency) Anomalies threshold Settings
Change which Windows events are monitored AWEM Configuration
Change what the Tray Agent shows end-users, or its data retention Tray Agent Configuration
See what reports and graphs this produces on ARS Reports and Output on ARS
Fix a monitoring, logging, or notification problem Troubleshooting

AUEM Components

AUEM consists of the following components:

AWEM (Accops Windows Event Monitor)

AWEM runs as a Windows service and analyzes the system events based on the user activities. It collects the events data and analyzes the recorded data to identify the time span of the different activities. It helps system administrators identify issues in a user session based on the analyzed data sent to the server by the application. AWEM monitors critical system events and sends the event data to ARS, or dumps it to an output file. See AWEM Configuration for event channels and thresholds.

AUPM (Accops User Performance Manager)

AUPM runs as a Windows service and monitors the system performance based on the resource utilization (CPU, RAM, Network), and sends performance data to ARS based on the threshold values. See AUPM Configuration for threshold defaults and anomaly evaluation logic.

Tray Agent

Tray Agent performs the following tasks:

  • Notifies the users for the anomalies which are affecting or may affect performance.

  • Notifies recommended actions that can be taken on reported anomalies that are found based on the resource utilization.

  • Launches Task Manager for end-users to view and manage processes running in user sessions, and view memory and CPU utilization.

  • Shows session network health.

  • Shows history of anomalies.

See Tray Agent Configuration for the full feature walkthrough (Task Manager, Network Latency, Notification History) and its settings.

Anomalies

Any kind of excessive utilization of resources, memory, CPU, number of applications, or a weak network in session, that can affect user experience, is termed an anomaly.

AUPM detects anomalies and notifies users to take corrective actions. It also reports such incidents to ARS for auditing and analysis. Anomalies are evaluated across four areas: process count, CPU utilization by processes, memory utilization by processes, and session connection network health.

Every evaluation type, its threshold defaults, and the exact corrective actions offered to the user (ignore, close process, logout) are documented once, on AUPM Configuration, rather than repeated here.