How to View Active Directory details for Citrix Users

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.

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

1. Navigate to the Settings page in the top right hand corner
2. Click the link for Security and User Accounts
3. At the bottom of the page there will be a section labeled Global Security Settings, see the field for *Active Directory/LDAP Path for Verify. By default, the primary domains rootDSE path is listed (GC://rootDSE). To add additional ldap connections, create a semi-colon delimited list of all of the domains where AD lookups are applicable, LDAP:// as the pre-fix, case sensitive.
   1. Versions 12.1.0.2 & later of GPM: For the additional paths, you'll need to specify the domain that Goliath will connect to in the format of "LDAP://{domain name}".
      1. 1. For example, LDAP://test.local
      2. If the domain controller uses a non-standard LDAP port (i.e. not 389 or 636), this can be defined by defining a domain controller and appending the port "LDAP://{{domain controller}}:####/{domain name}".
         1. For example, LDAP://SV-DC05:50000/test.local
      3. In general, the domain controller can also be optionally defined in the format "LDAP://{{domain controller}}/{domain name}".
         1. For example, LDAP://SV-DC05/test.local
   2. Versions 12.1.0 & 12.1.0.1 of GPM: For the additional paths, you'll need to specify the domain controller that Goliath will connect to in the format of "LDAP://{{domain controller}}/{domain name}".
      1. 1. For example, LDAP://SV-DC05/test.local
      2. If the domain controller uses a non-standard LDAP port (i.e. not 389 or 636), this can be defined by appending as "LDAP://{{domain controller}}:####/{domain name}".
         1. For example, LDAP://SV-DC05:50000/test.local
   3. Example of multiple paths, "GC://rootDSE; LDAP:///tech.local; LDAP://SVR-AD01/test.goliathtechnologies.com"
      
      1. 
      2.