Agents Administration - Tests
 

Default Parameters for WVDLogonSimTest

This test emulates a user logging into an AVD Web Client and launching an application/desktop. In the process, the test reports the total duration of the simulation, time taken for the login to be authenticated, the time taken for application/desktop ennumeration, duration of application/desktop launch, and log out duration. Additionally, the test also captures failures (if any) at each step of the simulation.

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

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

    Note:

    Some parameter changes can sometimes impact the simulation duration. Most often, this can happen in the following situations:

    • If multiple applications/desktops are configured for launching against PUBLISHED RESOURCES: In this case, the test will repeat the entire sequence of steps for every configured application/desktop - i.e., after an application is launched, the test will logoff and then log in again to attempt the launch of the next application. This can increase the duration of the simulation.

    • If the value of the LAUNCH TIMEOUT and/or the WEB LOGOFF DELAY parameters of the test is significantly increased: If this is done, then the simulator will wait that much longer for the application launch or logoff to happen, thereby increasing simulation duration.

    Sometimes, these changes can cause the simulation to take more time than the configured TEST PERIOD.

    If this happens, the test will fail after logging an error to that effect in the <EG_AGENT_INSTALL_DIR>\agent\error_log file. To avoid this, it would be a good practice to relook at the TEST PERIOD configuration every time one of the parameters mentioned above is modified, and increase it if required.

  • In the SITE URL text box, specify the URL for connecting to the AVD Web Client. By default, the SITE URL is specified as https://rdweb.wvd.microsoft.com/arm/webclient in this text box.

  • The simulator needs to run in the account of a user who has local administrator rights on the simulation end point - i.e., the system on which the external agent has been installed. Specify the name of this user in the CONSOLE USERNAME text box. This user should also be logged in at all times for the simulator to run continuously.

  • If the user specified in CONSOLE USERNAME belongs to a domain, then, specify the name of the domain in the CONSOLE DOMAIN text box. By default, none is specified against this text box.

  • By default, the LAUNCH TIMEOUT parameter is set to 90 seconds. This implies that the simulator will wait for a maximum of 90 seconds (by default) for an application/desktop to launch. If the application/desktop does not launch even after the 90 seconds have elapsed, then the simulation will be automatically terminated, and the simulator will mark that application/desktop launch as ‘failed’. Accordingly, the App_launch_availability measure for that published resource (i.e., application/desktop) will report the value 0, and no launch duration will be reported for the same.

    In some environments, one/more published applications may take a little longer to launch than the rest. In such environments, you can instruct the simulator to wait longer for launching each of the configured published resources, by increasing the LAUNCH TIMEOUT. The high time out setting for resource launch ensures that the simulator captures and reports only genuine launch failures, and does not treat a launch delay as a failure.

  • By default, the WEB LOGOFF DELAY parameter is set to 30 seconds. This implies that the simulator will wait for a maximum of 30 seconds (by default) after each resource launch, for the logoff to occur. If the logoff does not happen even after 30 seconds have elapsed, then the simulation will be automatically terminated, and the simulator will mark the logoff attempt as ‘failed’. A logoff duration will hence not be computed or reported in this case.

    In some environments, even during normal operation, logoff may take longer. In such environments, you can instruct the simulator to wait longer for the logoff to occur, by increasing the web logoff delay. The high time out setting for logoff ensures that the simulator waits for the log off to complete and captures and reports the accurate logoff duration.

  • By default, the logon simulator will automatically take screenshots of failure conditions and displays the same in the layer model against the measure that reported failure as well as in the graphical view of the detailed diagnosis. To this effect, the SCREENSHOT REQUIRED flag is set to Yes, by default. If you do not wish to view the screenshot for the simulation, then, set this flag to No.

  • By default, the SUCCESS SCREENSHOT REQUIRED flag is set to No indicating that the logon simulator will not capture a screenshot and display the same in the graphical view of the detailed diagnosis if the simulation performed was successful. If you wish to capture a screenshot for successful simulations too and display the same, then, set this flag to Yes.

  • In the SUCCESS SCREENSHOT FREQUENCY text box, specify the frequency i.e., measurement period for which a screenshot captured for a successful simulation should be retained in the layer model/graphical view. By default, this is set to 5 indicating that the screenshot captured for a successful simulation will be displayed for the subsequent 5 measurement periods provided, the logon simulation is successful during all those 5 measurement periods.

  • For the logon simulation to be successful on the simulation endpoint at all times, it is important to maintain the Windows session in ‘active’ state always. To this effect, the ENABLE SESSION ACTIVE flag is set to Yes by default.

  • The DD FREQUENCY 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 necessary values have been provided, clicking on the UPDATE button will 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.