The AWS WorkSpaces Logon Simulator Test

How often should the test be executed. The default is 15 minutes.

Note:

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

• If multiple desktops are configured for launching against PUBLISHED RESOURCES: In this case, the test will repeat the entire sequence of steps for every configured desktop - i.e., after a desktop is launched, the test will logoff and then log in again to attempt the launch of the next desktop. This can increase the duration of the simulation.
• If the value of the Launch Timeout and/or the Logoff Delay parameters of the test is significantly increased: If this is done, then the simulator will wait that much longer for the desktop 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.

The host for which the test is to be configured.

Specify the port used to connect to the Amazon WorkSpaces here. By default, this will be NULL.

Specify the URL for connecting to the virtual private cloud associated with the Amazon WorkSpaces here. You can provide either an HTTP or an HTTPS URL.

To know how to configure the resources to be monitored, refer to the How to Configure Published Resources for Monitoring? topic.

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.

Specify the domain to which the user belongs to here.

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

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

In some environments, one/more published desktops 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 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, this 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, this 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.

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 for the Windows user session to always remain 'active'. To this effect, this flag is set to Yes by default.

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.