Configuration of WVDBrowserTest

In recent times, browsers have become one of the common ways to access many applications in enterprises. The same browser may be used for accessing multiple applications. Further, users may even use browsers to access non-corporate web sites from their environment. In modern architectures, a lot of the processing is done by the scripts executed on browsers. This further adds processing tasks to the browsers. VDI administrators need to know when exactly specific browser instances started taking up excessive resources (CPU, memory, disk) and most importantly, what URLs were accessed when a browser started taking up resources. The WVDBrowserTest helps administrators in this regard!

This test auto-discovers the browsers accessed by each user connected to and AVD, and for each browser, reports the number of sessions initiated and the number of processes running. This test also reports the URLs that were accessed when a browser started taking up resources. Using this test, administrators can figure out the URL and browser that is responsible for excessive resource utilization by a user.

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, this test will report metrics for each domainname\username logged into the chosen Session Host / Azure Virtual Desktop. This way, administrators will be able to quickly determine which user logged in from which domain. If you want the test to report metrics for the username alone, then set this flag to No.

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