Agents Administration - Tests
 

Configuration of CtxXcXAEuemTest

With the CtxXcXAEuemTest test, administrators can receive deep visibility into the XenApp end of the Citrix logon process. This test takes an administrator into the XenApp server, reveals the users who are currently logged on to the server, and accurately reports the average time it took for the sessions of each user to start inside the server. This way, administrators can rapidly identify which user’s sessions are experiencing undue start-up delays. In addition, the test also provides a break-up of the session start-up duration. This way, the test precisely pinpoints where the delay occurred - - when user credentials were obtained? when credentials were validated? during profile loading? during login script execution? when mapping drives or creating printers?

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 the host name of the server for which the test is to be configured in the HOST text box.

  • Specify the port on which the cluster is listening in the PORT text box.

  • By default, the REPORT USING MANAGERTIME flag is set to Yes. This indicates that the user login time displayed in the DETAILED DIAGNOSIS page for this test and in the Thin Client reports will be based on the eG manager's time zone by default. Set this flag to No if you want the login times displayed in the DETAILED DIAGNOSIS page for this test and in the Thin Client reports to be based on the Citrix server's local time.

  • The REPORT BY DOMAIN NAME flag is set to Yes by default. This implies that by default, the detailed diagnosis of this test will display the domainname\username of each user session that logged out. This default setting ensures that administrators are able to quickly determine the domains to which the users who logged out belonged. You can set this flag to No if you want detailed diagnosis to display only the username of the users who logged out.

  • By default, REPORT BY CLIENT NAME flag is set to No. If set to Yes, this test will report metrics for each client machine from which users logged into the XenApp server - i.e., the host name of the client machines will be the descriptors of this test. In this case therefore, the User name column of the detailed diagnosis of this test will indicate the names of the users who logged into the XenApp server.

  • In the PROFILESIZELIMIT text box, specify the profile quota size (in MB). The default value is 100 MB.

  • In the FILESIZELIMIT text box, specify the file quota size (in MB). The default size is 10000 MB.

  • By default, when this test computes the size of a profile, it automatically excludes the following folders and their sub-folders from the computation:

    AppData\Local,AppData\LocalLow,Recycle.Bin,SkyDrive,WorkFolders. If need be, you can choose to include one/more of these default folders when computing the profile size; for this, all you need to do is remove those specific folders from the default EXCLUDE FOLDERS specification. For example, to include the SkyDrive and WorkFolders folders, simply remove them from the default specification above. Also, if required, you can exclude more folders from the profile size computation, by appending the corresponding folder names / folder name patterns to this default list. For instance, your specification can be: AppData\Local,AppData\LocalLow,Recycle.Bin,SkyDrive,WorkFolders,*Backup*,Favo*,*Desktop. In the case of this sample specification, in addition to the default list of excluded folders, all folders with names that embed the string Backup, with names that begin with the string Favo, and with names that end with the string Desktop, will be excluded from size computation. Moreover, all sub-folders within these folders will also be ignored during size computation.

  • By default, USER PROFILE DIR parameter is set to none. This implies that for XenApp servers operating on Windows 2008 and Windows 2012 platforms, the test will, by default, check the C:\Users directory for the user profile files. In some environments, the user profile-related files and folders may exist in a different directory. In such environments, you will have to specify the exact directory in which the user profiles exist, against the User Profile Dir parameter.

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