Agents Administration - Tests
 

Configuration of AWSLogonSimTest

This test emulates a user logging into an AWS WorkSpace and launching an desktop. In the process, the test reports the total duration of the simulation, time taken for the login to be authenticated, duration of desktop launch, and log out duration. Additionally, the test also captures failures (if any) at each step of the simulation. Using the insights provided by this test, the administrators can proactively detect logon slowness/failures and precisely pinpoint the root-cause of the anomaly - is it login authentication? desktop launch? or logout? This way, administrators are enabled to isolate the probable pain-points of their virtual , even before users begin to actively use the cloud desktops.

The default parameters associated with this test are:

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

    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 good practice to relook at the TEST PERIOD configuration every time one of the parameters mentioned above is modified, and increase it if required.

  • Specify the host for which the test is to be configured in the HOST text box.

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

  • Specify the URL for connecting to the AWS WorkSpace in the SITE URL text box. You can provide an HTTP or an HTTPS URL here.

  • To configure the published resources that are to be monitored, click the button against the PUBLISHED RESOURCES field. The CONFIGURATION OF PUBLISHED RESOURCES pop up window will then appear. Configure the following this pop up window:

    • In the Published resources text box, specify the published resource that is to be launched. The resource should be a virtual desktop. When providing the desktop name, make sure you provide the same name using which the desktop on the web console of the virtual private cloud. Also, make sure that the User you specify is authorized to launch the desktop configured in the Published resources.

      Note:

      • The resources can be specified either in lower case or upper case or a combination of both.

    • Then, using the Registration code, Domain, User, Password, and Confirm Password parameters, configure the credentials of the user who is authorized to launch the configured resources.

    • Registration code verification, is a security process in which the user provides an authentication to verify who they say they are. By default, the AWS WorkSpace is enabled with a registratoion code authentication. To authenticate the specified User login, the AWS WorkSpace client will require an additional layer of security other than the Password you have provided. This is the piece of information that only the User knows or has immediately in hand - such as a registration code that the AWS WorkSpace provides.

    • If you do not want to configure any more resources for launching, then click the Update button to save the changes. To add another resource for launching, click the Add More button. This will add an empty record in the CONFIGURATION OF PUBLISHED RESOURCES pop up window. Here, specify the names of more Published resources, and then use the Registration code, Domain, User, Password, and Confirm Password parameters to provide the credentials of a user who is authorized to launch those resources.

    • At any given point in time, you can exclude/delete a resource from the simulation by clicking the encircled - button corresponding to that resource.

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

  • 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 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, a published desktop may take a little longer to launch. In such environments, you can instruct the simulator to wait longer for launching the configured published resource, 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 LOGON DELAY 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, 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.

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

  • To make diagnosis more efficient and accurate, the eG Enterprise 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.