> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.trugrid.com/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# TruGrid RDS Manager Enterprise - Installation and Setup Guide

# In this article
* [Overview](#3-overview)
* [System requirements](#3-system-requirements)
* [Step 1 - Install the Data Collector](#3-step-1-install-the-data-collector)
* [Step 2 - Connect with the Enterprise Client](#3-step-2-connect-with-the-enterprise-client)
* [Step 3 - Deploy Session Host Agents (recommended)](#3-step-3-deploy-session-host-agents-recommended)
* [Upgrading](#3-upgrading)
* [Troubleshooting](#3-troubleshooting)
* [Contact](#3-contact)

### Overview

This guide covers installation, agent deployment, and upgrades for TruGrid RDS Manager Enterprise (RDSM Enterprise). RDSM Enterprise is a monitoring and analytics tool for administrators managing Remote Desktop Services and VDI environments.

For a full walkthrough of the Dashboard, Computers, Users & Sessions, Analytics, Alerts, Audit Log, and all other features, see the [TruGrid RDS Manager - User Guide](https://help.trugrid.com/en/article/trugrid-rds-manager-ytjfku/).

RDSM Enterprise consists of the following components:

| Component | Executable | What it does |
| ---- |
| Data Collector | TruGrid-RDSM-DC-Config.exe | Configuration manager and Windows service that collects session and performance data from all monitored hosts. Used to manage computer groups, configure access control, deploy Session Host Agents, and install the Data Collector service. Stores data in a local SQLite database. Runs on a domain-joined Windows Server |
| Enterprise Client | TruGrid-RDSM-Enterprise.exe | The admin dashboard. Connects to the Data Collector over HTTP (port 5743) or HTTPS (port 5744) using passthrough Windows Authentication. Self-contained executable - no installer needed. Can run on any domain-joined Windows PC |
| Session Host Agent (optional) | TruGrid-RDSM-Agent.exe | Lightweight Windows service installed on individual session hosts. Streams live telemetry to the Data Collector every 30 seconds. Enables logon performance phase breakdowns, Windows Security Event Log forwarding (4624 Logon, 4688 Process Creation), AgentOffline alerts, and Probe Diagnostics. Deployed via ZIP download or PsExec push from the Data Collector |

You can run the Data Collector and Enterprise Client on the same server (TruGrid Sentry server, management server, etc.)

![](https://storage.crisp.chat/users/helpdesk/website/-/f/4/7/3/f473d72e7d7c5000/image_19lwlj0.png)
### System requirements

**Data Collector host**
* Windows Server 2016 or later
* Domain-joined to an Active Directory environment
* .NET 10 runtime (bundled with the executable - no separate installation required)

**Enterprise Client**
* Windows 11 or Windows Server
* Domain-joined to the same Active Directory environment as the Data Collector host

**Network**
* Port 5743 (HTTP) and/or 5744 (HTTPS) open between the Enterprise Client and the Data Collector host
* Port 5744 (HTTPS) open between Session Host Agents and the Data Collector host (if deploying agents)
* For detailed network requirements, see [TruGrid RDS Manager Data Collector Service - Network Access Requirements](https://help.trugrid.com/en/article/trugrid-rds-manager-data-collector-service-network-access-requirements-hfraqt/)

**Data storage**
All collected data is stored in a SQLite database at `C:\ProgramData\TruGrid RDS Manager Enterprise` on the Data Collector host. No external database server is required.

### Step 1 - Install the Data Collector

**Firewall configuration**
Open inbound TCP ports 5743 and 5744 on the Data Collector host's Windows Firewall:

```
New-NetFirewallRule -DisplayName "TruGrid RDSM 5743 Inbound" -Direction Inbound -LocalPort 5743 -Protocol TCP -Action Allow -Profile Any
New-NetFirewallRule -DisplayName "TruGrid RDSM 5744 Inbound" -Direction Inbound -LocalPort 5744 -Protocol TCP -Action Allow -Profile Any
```

The firewall configuration can be skipped if both the Data Collector and Enterprise Client are on the same server. The Data Collector setup is still necessary before running the Client. The Client can then be pointed at `http://localhost:5743` (or `https://localhost:5744` for HTTPS).

**Installing the service**

Run TruGrid-RDSM-DC-Config.exe as Administrator on the server that will host the Data Collector service:

![](https://storage.crisp.chat/users/helpdesk/website/-/f/4/7/3/f473d72e7d7c5000/image_w7mazj.png)
| NOTE: You can use a Domain User account to run the Data Collector Service as long as the user has admin rights on the polled machines and the Data Collector server. Domain Admin account is recommended for installation. 

1. Open the **Windows Service** tab and click **Install Service**. A UAC prompt may appear - approve it.
2. On the **Settings** tab, verify the HTTP port (default: 5743) and set the polling interval (default: 60 seconds). Enable **Start polling automatically**, then click **Save Settings**.
3. Open the **Computer Groups** tab. Add AD security groups that contain the computers you want to monitor.
4. Open the **Access Control** tab. Add the Active Directory users or security groups that are permitted to connect as administrators. Leaving the list empty will deny all connections from the Enterprise Client.
5. Return to the **Windows Service** tab and click **Start Service**. Confirm the status changes to **Running**.
6. Verify that the Data Collector interface is in the Running state and that computers are reporting in. If they are, proceed to Step 2 and connect using the Enterprise Client.

| NOTE: If after taking these steps there are still no computers reporting in to the Data Collector, try restarting the service.

### Step 2 - Connect with the Enterprise Client

Copy TruGrid-RDSM-Enterprise.exe to any Windows PC on the domain. No installer is needed - it is a self-contained executable.
1. Launch the application. A **Connect** dialog will appear on startup.
2. Enter the Data Collector URL, for example: `http://192.168.1.100:5743` (use the server's IP address or hostname).
3. Click **Connect**. Passthrough Windows Authentication (NTLM/Kerberos) is used automatically - no password prompt.
4. The main Dashboard opens. Use the sidebar to navigate between Dashboard, Computers, Users & Sessions, Analytics, Alerts, and Audit Log.

| Example URLs |  |
| ---- |
| `http://dc01.contoso.local:5743` | HTTP |
| `https://dc01.contoso.local:5744` | HTTPS |

The Client remembers the last URL used and re-uses it on every launch. If your account is not on the Data Collector's allowed-users list, you will get a 401 Unauthorized response - ask your admin to add you to the Access Control list in the Data Collector Configurator.

### Step 3 - Deploy Session Host Agents (recommended)

Without agents, the Data Collector monitors hosts via agentless WMI polling. This provides basic session counts and CPU/memory readings at 60-second intervals. Installing the Session Host Agent on each monitored host unlocks higher-resolution data and additional telemetry:

| Capability | Agentless (WMI) | With Agent |
| ---- |
| Session counts, CPU, memory | Yes (60s interval) | Yes (30s interval) |
| Logon performance phase breakdown (Auth, Profile, GPO, Shell) | No | Yes |
| Windows Security Event Log forwarding (4624 Logon, 4688 Process Creation) | No | Yes |
| AgentOffline alerts | No | Yes |
| Probe Diagnostics on logon rows | No | Yes |

Agent deployment is optional but recommended for production environments. Hosts without agents continue to work via WMI polling.

**Downloading the agent package**
1. Open the Data Collector Configurator and go to the **Agents** tab.
2. Click **Download ZIP**. The Data Collector generates a self-contained ZIP file named `TruGrid-RDSM-Agent-<version>.zip`. The ZIP is pre-configured with the Data Collector's URL and certificate thumbprint baked into `appsettings.json` - no manual editing required

![](https://storage.crisp.chat/users/helpdesk/website/-/f/4/7/3/f473d72e7d7c5000/image_150hs0a.png)
The ZIP contains three files:
| File | Purpose |
| ---- |
| TruGrid-RDSM-Agent.exe | The agent executable (self-contained, no runtime dependencies) |
| appsettings.json | Configuration file with the Data Collector URL, certificate thumbprint, and heartbeat interval |
| install.cmd | Installation script that registers and starts the agent as a Windows service |

**Installing on a session host (manual)**

1. Copy the ZIP to the target session host and extract all three files to a temporary folder.
2. Open an elevated command prompt (Run as Administrator) in that folder.
3. Run `install.cmd`.

The script performs the following steps automatically:
* Stops and removes any previous agent installation
* Creates the install directory at `%ProgramFiles%\TruGrid\RDSM Agent`
* Creates the data directory at `%ProgramData%\TruGrid RDS Manager Enterprise\Agent`
* Copies the agent executable and configuration
* Registers the `TruGrid-RDSM-Agent` Windows service with automatic startup
* Configures service failure recovery (restart after 5, 10, and 30 seconds)
* Starts the service
* Cleans up the staging directory after installation

Once the service starts, the agent connects to the Data Collector and begins streaming telemetry. The host appears in the Agents tab of the Data Collector Configurator within 30 seconds.

**Pushing remotely with PsExec**
Click **Push with PsExec** in the Agents tab to deploy the agent to one or more hosts without logging into each one. The Data Collector copies the agent ZIP to the target host and runs the install script re
motely. The target host must be reachable over the network and the admin account must have local administrator rights on the target.

**Prerequisites**
The target host's machine account must be a member of one of the Active Directory groups configured in the **Computer Groups** tab. If the host is not in a recognized group, the agent will not be able to enroll with the Data Collector.

**Managing agents**
The Agents tab in the Data Collector Configurator shows all connected agents with their status, version, OS, last heartbeat, session count, CPU, memory, and audit policy status:

| Column | What it shows |
| ---- |
| Status | Online (green) or Offline |
| Machine | Host name |
| Agent Ver. | Installed agent build version |
| OS | Host operating system |
| Last seen | Time since last heartbeat |
| Sessions | Current session count on the host |
| CPU % | Current CPU usage |
| Mem % | Current memory usage |
| 4688 Audit | Whether Process Creation auditing is enabled on the host |
| 4624 Audit | Whether Logon auditing is enabled on the host |
| Action | **Force Update** pushes the latest bundled agent version to the host |

**Updating agents**
Click **Force Update** on any row in the Agents tab to push the latest agent version bundled with the Data Collector to that host. The agent restarts automatically after the update.

**Agent configuration reference**
The agent reads its configuration from `appsettings.json` in the data directory (`%ProgramData%\TruGrid RDS Manager Enterprise\Agent`). The key settings in the `Agent` section are:

| Setting | Description |
| ---- |
| CollectorUrl | The Data Collector URL the agent reports to (HTTPS, port 5744) |
| CertificateThumbprint | SHA-1 thumbprint of the Data Collector's certificate |
| AllowSelfSignedCertificate | Whether to accept self-signed certificates (true/false) |
| HeartbeatIntervalSeconds | How often the agent sends a heartbeat to the Data Collector (default: 30) |

These values are pre-populated when you download the ZIP from the Data Collector. Manual editing is only needed if the Data Collector's address or certificate changes after deployment.

### Upgrading

When a new version is available, update the Data Collector and Enterprise Client using the following process:
1. Close both the **Enterprise Client** and the **Data Collector Configurator** applications.
2. Replace both executables (TruGrid-RDSM-DC-Config.exe and TruGrid-RDSM-Enterprise.exe) with the new versions.
3. Open the **Data Collector Configurator**. From the **Dashboard** tab, click **Update**. This will stop the Data Collector Service and update it to the new version.
4. Start the Data Collector Service from the **Windows Service** tab.

Existing data is preserved across upgrades. The Data Collector Service executable is not updated by simply replacing the Configurator - the **Update** action in Step 3 is required.

**Enterprise Client auto-update**
The Enterprise Client checks for updates automatically. When a newer build is available, a blue update banner appears at the top of the Dashboard. Click **Download** to get the new version.

**Agent updates**
Session Host Agents can be updated individually from the **Agents** tab in the Data Collector Configurator using the **Force Update** button, or re-deployed via PsExec push with the new agent ZIP.

### Troubleshooting

**No computers appear after starting the Data Collector service.**
Verify that the AD security groups in the **Computer Groups** tab contain the correct computer accounts. Restart the Data Collector service after making changes. Confirm that WMI is accessible from the Data Collector host to the target session hosts (test with `Get-WmiObject -Class Win32_OperatingSystem -ComputerName <hostname>`).

**The Enterprise Client shows 401 Unauthorized.**
Your user account is not on the Data Collector's Access Control list. Open the Data Collector Configurator, go to the **Access Control** tab, and add your AD user or security group.

**An agent shows as Offline in the Agents tab even though the host is running.**
Check whether the TruGrid-RDSM-Agent service is running on the host (`sc.exe query TruGrid-RDSM-Agent`). If the service is stopped, start it. If it fails to start, check the Windows Event Log for errors. Verify that port 5744 (HTTPS) is open from the host to the Data Collector server.

**Logon Performance data is not appearing for a host.**
Logon performance phase breakdowns require the Session Host Agent. Hosts monitored via agentless WMI only do not generate logon performance data. Install the agent on the host to enable logon tracking.

**The 4688 Audit or 4624 Audit column shows Disabled.**
The agent reads Windows Security Event Log entries for these event IDs. If the audit policy is not enabled on the host, the agent cannot collect the data. Enable the audit policies via Group Policy or local security policy on the target host:
* **4624 (Logon):** Computer Configuration > Windows Settings > Security Settings > Advanced Audit Policy Configuration > Logon/Logoff > Audit Logon
* **4688 (Process Creation):** Computer Configuration > Windows Settings > Security Settings > Advanced Audit Policy Configuration > Detailed Tracking > Audit Process Creation

**The Data Collector Configurator shows "Service not installed."**
Run the Configurator as Administrator. If the service was previously installed and removed, click **Install Service** again on the **Windows Service** tab.

### Contact
For help with installation, configuration, or troubleshooting, contact TruGrid support at help@trugrid.com or use the **Chat with us** option on this help center.