Agents Administration - Tests
 

Default Parameters for WVDAppLaunchTest

When a user complains that it is taking too long to launch applications on an Azure Virtual Desktop, administrators must be able to quickly identify the applications that are being currently accessed by that user, know how much time each application took to launch, and thus pinpoint that application that is the slowest in launching. The WVDAppLaunchTest test provides these valuable insights to the administrators. This test auto-discovers all the applications that are currently launched on the chiosen Session Host / Azure Virtual Desktop, and for each discovered application, reports the average and maximum time that application took to launch. This way, the test points administrators to applications that are slow in launching. Detailed diagnostics provided by the test also reveals the users who are currently accessing the applications and the launch time of the application as perceived by each user session; in the process, the test accurately pinpoints which user was attempting to launch the application when the slowness was observed.

This page depicts the default parameters that need to be configured for the WVDAppLaunchTest 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 session that launched an application on the chosen Session Host / AVD. This default setting ensures that administrators are able to quickly determine the domains to which the users belonged. You can set this flag to No if you want detailed diagnosis to display only the username of the users who are logged into the chosen AVD.

  • 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.