Configuration of 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.

The default parameters associated with this test are as follows:

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

• In the HOST text box, the IP address of the host for which the test is to be configured has to be specified.

• Specify the port at which the specified HOST listens to in the PORT text box. By default, this is NULL.

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

• To make diagnosis more efficient and accurate, the eG suite embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the DETAILED DIAGNOSIS capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option.

  The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:

  • The eG manager license should allow the detailed diagnosis capability.

  • Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.

• If multiple components of the same component type are awaiting configuration, then an APPLY TO OTHER COMPONENTS check box will appear in this page. Clicking on this check box will allow you to apply the configuration to all/selected components of that type.

• Once the necessary values have been provided, clicking on the UPDATE button will register the changes made.

When changing the configuration for specific servers, a “*” beside the text box corresponding to the parameter signifies that these values have to be manually configured by the user. The parameter values that require to be configured will typically be prefixed with a “$” or contain a series of “*”. A value of “none” in the parameter value indicates that the corresponding parameter value can be changed if required.