Agents Administration - Tests
 

Configuration of WVDUserTest

An Azure Virtual Desktop environment is a shared environment in which multiple users connect to a single session host / virtual desktop and access a wide variety of applications. When resources are shared, excessive resource utilization by a single user could impact the performance for other users. Therefore, continuous monitoring of the activities of each and every user on the server is critical. Towards this end, the WVDUserTest assesses the traffic between the user terminal and the chosen session host / Azure Virtual Desktop, and also monitors the resources taken up by a user's session on the AVD. The results of this test can be used in troubleshooting and proactive monitoring. For example, when a user reports a performance problem, an administrator can quickly check the bandwidth usage of the user's session, the CPU/memory/disk usage of this user's session as well as the resource usage of other user sessions. The administrator also has access to details on what processes/applications the user is accessing and their individual resource usage. This information can be used to spot any offending processes/ applications.

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.

  • By default, the USERNAMES parameter is set to all. This means that the test monitors all users who are logged into a chosen session host, by default. If you want the test to monitor only specific users, then provide a comma-separated list of user names to be monitored, here - for example, john,julie,joanne

  • Specify the time duration (in minutes) of inactivity beyond which a session is considered to be “idle” by this test. By default, the IDLE TIME parameter is set to 30 (minutes). This implies that by default, the test counts all sessions that have been inactive for over 30 minutes as idle sessions.

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