Documentation

Contents
Contents
Contents
Contents
!
This documentation applies to a beta version of uberAgent (docs for the latest official release)

Dynamic Application Identification and Executables on Network Drives

uberAgent automatically groups related processes to applications because humans think in applications, not in processes ? and uberAgent is designed for humans. When troubleshooting performance problems it is not enough to know that, say, SelfService.exe has a problem. You need to know that Citrix Receiver generates all those IOs. uberAgent shows you exactly that and makes it easy to analyze the impact your applications have on overall system performance.

In two cases the automatic application identification on the uberAgent’s endpoint may not work as expected:

  • The application was started using a mapped network drive.
  • The application was started using a UNC path.

Problem cause

Due to the fact that the uberAgent service on the endpoint is running in the context of the Local System, the service cannot access the executable and determine the application’s name dynamically.

Workaround

To solve the problem you can implement a static process to application mapping using uberAgent’s configuration.

Example

############################################
# Executable to application name mappings (for problem cases)
#
# Format: process.exe = Application name
#
############################################
[ProcessToApplicationMapping]
SelfService.exe = Citrix Receiver

Leave a Reply

Your email address will not be published. Required fields are marked *