Configuration of VmgDskUsrlogonTest

The process of a user logging into the physical desktop is fairly complex. First, the domain controller is discovered and the login credentials are authenticated. Then, the corresponding user profile is identified and loaded. Next, group policies are applied and logon scripts are processed to setup the user environment. In the meantime, additional processing may take place for a user - say, applying system profiles, creating new printers for the user, and so on. A slowdown in any of these steps can significantly delay the logon process for a user. Since logons on Windows happen sequentially, this may adversely impact the logins for other users who may be trying to access the physical desktop server at the same time. Hence, if a user complains that he/she is unable to access an application/desktop published on physical desktop, administrators must be able to rapidly isolate exactly where the logon process is stalling and for which user.

This test periodically monitors the user login and profile loading process and accurately identify where the process is bottlenecked. This test helps administrators to capture anomalies in the user login and profile loading process and report where the process is bottlenecked - in the authentication process? during profile loading? during GPO processing and if so, which GPO? which client side extension was processed by the GPO when the delay occurred? is the group policy processing mode impacting user logon?

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.

• Specify the nick name of the target component for which this test is to be configured in the HOST text box.

• Indicate the port at which the host listens to in the PORT text box. By default, this is NULL.

• To obtain the ‘inside view’ of performance of the desktops - i.e., to measure the internal performance of the physical desktops - this test uses a light-weight eG VM Agent software deployed on each of the desktops. Accordingly, INSIDE VIEW USING parameter is by default set to eG VM Agent.

• The REPORT POWERED OS is relevant only for those tests that are mapped to the Physical Desktops Details layer. If this flag is set to Yes (which is the default setting), then the 'inside view' tests will report measures for even those physical desktops that do not have any users logged in currently. Such desktops will be identified by their name and not by the username_on_physicalmachinename. On the other hand, if this flag is set to No, then this test will not report measures for those physical desktops to which no users are logged in currently.

• REPORT BY USER flag is set to Yes by default. This implies that the physical machines in environments will always be identified using the login name of the user. In other words, this test will, by default, report measures for every username_on_physicalmachinename.

• IS CLOUD VMs flag is set to Yes by default. This implies that the physical machines in environments will always be identified using the login name of the user. In other words, this test will, by default, report measures for every username_on_physicalmachinename.

• Specify the profile quota size (in MB) in PROFILESIZELIMIT text box. The default value is 500 MB. This means that, by default, the test will consider a user's profile as 'large' only if it is of a size higher than 500 MB. By default, the Is the user's profile size large? measure will report the value Yes, only if that user's profile is of a size greater than 500 MB. If you want to change when a user's profile is to be considered as a 'large profile', then change the value of this parameter accordingly.

• Takes the file quota size (in MB) in FILESIZELIMIT. The default size is 100 MB. This means that, by default, the test will consider all files that are of a size greater than 100 MB as 'large files'. The count and names of such files will alone be displayed, by default, as the value and detailed diagnosis (respectively) of the Large files in user's profile measure. If you want to change when a file is to be considered as a 'large file', then change the value of this parameter accordingly.

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