With Goliath Performance Monitor v12.1.0, Goliath now displays the AD OU, City, State, Department and Country for Citrix users. This data is available on the Citrix Session display and within some of the Citrix Reports. To view this information, please ensure the following prereqs are configured. This article has been updated for version 14.0 of GPM.
Prerequisites
- The Goliath User, the user running the MonitorIT Server Service, must be an AD user.
- If you are running local SQL Server or SQL Express, the service runs as Local System by default.
- When using Remote SQL Server, per the Goliath Performance Monitor Prerequisites, this account must have database_owner rights to the SQL database
- For environments that have Citrix users authenticating from domain(s) different then the domain the Goliath Server is a member of (i.e. One-Way or Two-Way trusted domains), the above mentioned account must also be added to the other domains Active Directory with the same sAMAccountName and password. It must also be a Domain Admin in the trusted domains.
- For example, if the Goliath Server user account is "Corp/Test123" with password "AFG". Then in the trusted "TEST" domain, there must be a user "TEST/Test123" with password "AFG" that is a domain admin in order make the LDAP bind.
- For each Active Directory domain that Citrix users are a member of, including the domain the Goliath Server is a member of, the appropriate LDAP path must be defined in technology. See the section below for configuration details.
Define the Active Directory LDAP Path
You must be logged in as a Goliath administrator. Non-admin users do not see the Security card.
- In the left sidebar, click Settings.
- Click the Security card.
- In the Security dialog, scroll to the last field, Active Directory LDAP Path to verify.
- By default the field contains the primary domain’s Global Catalog path, GC://rootDSE. To add more domains, enter a semicolon-separated list of paths. Each entry must start with LDAP:// (case sensitive) or be GC://rootDSE.
- Click Save. The new path takes effect immediately, no service restart is needed. Users already looked up keep their cached values until their next scheduled refresh, so new columns can take one Citrix inventory cycle to fill in.
Path formats:
| Format | Example | Use when |
|---|---|---|
| LDAP://{domain name} | LDAP://test.local | Let Goliath locate a domain controller for the domain. |
| LDAP://{domain controller}/{domain name} | LDAP://SV-DC05/test.local | Pin the lookup to a specific DC. |
| LDAP://{domain controller}:{port}/{domain name} | LDAP://SV-DC05:50000/test.local | The DC listens on a non-standard LDAP port (not 389 or 636). |
Example of multiple paths:
GC://rootDSE; LDAP://tech.local; LDAP://SVR-AD01/test.goliathtechnologies.comNotes:
- An entry without a scheme:// prefix is rejected on save with “Invalid value for adLdapPath”. Clearing the field and saving resets it to GC://rootDSE.
- This same path is used to verify console logins when “Verify via Active Directory” is enabled for a user, so changing it affects both.
Where the AD details appear
- Session grids. Open Dashboards → Citrix EUE, then click the Apps & RDS Desktop Sessions or VDI Sessions card. In the grid’s options menu choose Configure Columns, and under User Details tick City, Country, State, Dept and Org Unit. These columns are hidden by default.
- Citrix EUE dashboard. The “Users Exceeding Thresholds” table has an AD OU tab that groups users by organizational unit. The “Users to Watch” widget’s Location column is built from the user’s AD City and State.
- Reports. Citrix reports can be filtered by AD OU in the report wizard.
These fields are collected for Citrix (XenApp/XenDesktop) sessions only. VMware Horizon session grids do not offer them.