Default Parameters for CtxXcXDServersTest

To track the status of desktop OS machines in each delivery group configured in a site, use the CtxXcXDDesktopsTest test.

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

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

• To monitor a site and pull metrics on its performance, the eG agent communicates with a delivery controller in that site. If the target site contains only one controller, then, you need to configure the CONTROLLER IP ADDRESS parameter with the IP address of that controller, so that the eG agent can use that controller for monitoring the site. Note that in this case, if the controller stops functioning for any reason, the eG agent will not be able to monitor the site any longer. Some sites may be configured with multiple delivery controllers to ensure high-availability, and to optimize and load-balance user connections. When monitoring such a site, you have the option of configuring the CONTROLLER IP ADDRESS parameter with a comma-separated list of controllers. For instance, the list should be in the following format: 192.160.1.10,198.160.1.11,198.160.1.12. In this case, the eG agent checks the availability of each configured controller at run time, picks the controller that is up and running at that time, and communicates with that controller for collecting metrics on site performance. This way, you can ensure that the non-availability of a single controller, does not impact site monitoring.

• Specify the port number of the delivery controller (i.e., broker) in the site with which the eG agent should communicate for collecting performance metrics, in the CONTROLLER PORT text box.

• To connect to a delivery controller and pull out metrics from it, the eG agent requires Farm Administrator rights. In order to configure the eG agent with Farm Administrator privileges, specify the credentials of the Farm Administrator in the USERNAME and PASSWORD text boxes. This user should also be assigned the Allow log on locally security privilege on the Citrix XA/XD Site 7.x host. The steps for assigning the Allow log on locally security privilege are as follows:

  • Go to the Control Panel in the host.

  • From the list of control panel items, click the Administrative Tools to view the set of tools available for system administrators and advanced users.

  • Upon selecting the Local Security Policy tool in the Administrative Tools location, the Local Security Policy settings console will appear.

  • Next, navigate to the User Rights Assignment node in the Local Policies tree in the left panel of the settings console. This will display the security policies corresponding to the user rights in the right panel.

  • Now, select the Allow log on locally policy to assign the security privilege to the user.

• Confirm the PASSWORD by retping it in the CONFIRM PASSWORD text box.

• In the FULLY QUALIFIED DOMAIN NAME text box, specify the fully-qualified name of the domain to which the specified controller belongs.

• If you want the results of this test to be grouped by delivery group then set the REPORT BY DELIVERY GROUP flag to Yes. In this case therefore, the delivery groups containing the server OS machines will be the primary descriptors of this test; expanding them will reveal the secondary descriptors – i.e., the server OS machines in each delivery group. If you want the results of this test to be indexed only the names of the server OS machines, then set this flag to No.

• Indicate whether/not the controller used for metrics collection is SSL-enabled. By default, the SSL flag is set to Yes.

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