Agents Administration - Tests
 

Default Parameters for WVDAppTest

This test reports statistics pertaining to the different applications executing on the chosen Session Host / Azure Virtual Desktop and their usage. Resource-intensive / under-performing applications can thus be rapidly captured. Detailed diagnosis points you to the precise users whose experience may probably be impacted by poor application performance.

This page depicts the default parameters that need to be configured for the WVDAppTest test.

  • The TEST PERIOD list box helps the user to decide how often this test needs to be executed.

  • By default, the REPORT BY DOMAIN NAME flag is set to Yes. This implies that by default, the detailed diagnosis of this test will display the domainname\username of each user who accessed an application on the AVD. This way, administrators will be able to quickly determine which user logged into the AVD from which domain. If you want the detailed diagnosis to display only the user name of these users, set this flag to No.

  • Using the SHOW ONLY ACTIVE APPS flag, you can indicate whether the test should monitor all applications or applications that are currently active on the AVD. By default, this flag is set to Yes, indicating that only the currently active applications will be monitored by the eG agent. To monitor all applications, you need to set this flag to No. Active applications are those that have at least one instance currently running on the chosen session host.

  • By default, this test monitors all applications that are running on the chosen session host / AVD. If required, you can override this default setting, so the test monitors only specific applications. For this, first set the Show Only Whitelist Apps flag to Yes (default setting is No). Then, do the following:

    • Edit the eg_tests.ini file (in the <EG_INSTALL_DIR>\manager\config directory on a Windows manager, or the /opt/egurkha/manager/config directory on a Unix manager).
    • Against the WhiteListProcesses parameter in the [EXCLUDE_APPLICATIONS] section, provide a comma-separated list of applications that you want to monitor. For instance, your specification can be as follows:

      WhiteListProcesses=chrome,iexplore,lync,mstsc,notepad

    • Finally, save the file.

  • By default, the EXCLUDE parameter is set to none. This means that the test will monitor all the applications that are launched on the chosen Session Host, by default. If you want the test to disregard certain applications when monitoring, then provide a comma-separated list of process names that correspond to the applications you want to ignore, in the EXCLUDE text box. For instance, your specification can be: winword.exe,js.exe,taskmgr.exe. Your specification can include wild card patterns as well. For example: *win*,js*,*task.

  • The DD FREQUENCY parameter refers to the frequency with which detailed diagnosis measures are to be generated for this test. The default is 1:1. This indicates that, by default, detailed measures will be generated every time this test runs, and also every time the test detects a problem. You can modify this frequency, if you so desire. Also, if you intend to disable the detailed diagnosis capability for this test, you can do so by specifying none against DD FREQUENCY .

  • Once the above values are provided, click on the UPDATE button to register the changes made.

When changing default configurations of tests, the values with “$” indicate variables that will be replaced by the eG system according to the specific server being managed - for instance, $hostName is the host/nickname of the target host, $port is the port number of the server being monitored. E.g., for a server xyz:80, $hostName will be changed automatically by the eG manager to “xyz*” and $port will be changed to “80” when configuring a test.