|
Default Parameters for PVSFarmTest
This test helps you understand the composition of your Citrix Provisioning server farm, and also proactively alerts critical problems such as:
- A sudden break in the connectivity between the Provisioning server farm and the Citrix Licensing server;
- Inaccessibility of the database server
This page depicts the default parameters that need to be configured for the PVSFarmTest.
This test executes commands using the Management Command Line Interface (MCLI) of the Provisioning server to collect the required metrics. To enable the test to execute the commands, the eG agent, by default, auto-discovers the full path MCLI.exe on the target Provisioning server. This is why, the MCLI PATH is set to none by default. If, for some reason, the eG agent is unable to auto-discover the MCLI path, then you will have to manually specify the path here using the following pointers:
- Typically, in a 32-bit Windows system, the MCLI.exe will be available in the following location by default: <System_Root>\Program Files\Citrix\Provisioning Services Console
- In a 64-bit Windows system on the other hand, the MCLI.exe will be available in the following location by default: <System_Root>\Program Files (x86)\Citrix\Provisioning Services Console
To report farm-related metrics, this test should run using the credentials of a user who fulfills the following requirements:
Should belong to the Security group with ‘Farm Administrator’ access.
Should belong to the Local Administrators group on the Citrix PVS host.
Should be allowed to logon locally and to interact with desktop.
To know the steps for creating such a user, click here.
Once this is done, then configure this test with the DOMAIN NAME, DOMAIN USER, and DOMAIN PASSWORD of a user in this security group.
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.
|