RDS Application Process Launches Test
To know which published applications on the Microsoft RDS server are currently accessed by users and how many instances of each application have been launched presently, use the RDS Application Process Launches test. Detailed diagnostics, if enabled, reveal the users accessing the published applications and the thin clients from which the users are connecting to the Microsoft RDS server.
This test is disabled by default. To enable the test, go to the enable / disable tests page using the menu sequence : Agents -> Tests -> Enable/Disable, pick the Microsoft RDS as the desired Component type, set Performance as the Test type, choose the test from the disabled tests list, and click on the < button to move the test to the ENABLED TESTS list. Finally, click the Update button.
Note:
If an application is launched by a user using the Run as Administrator option, this test will not report the launch duration of such an application as the eG agent does not have privileges to track applications launched with administrator privilege.
Target of the test : A Microsoft RDS server
Agent deploying the test : An internal agent
Outputs of the test : One set of results for every ‘published application’ on the Microsoft RDS server that is currently launched
Parameters | Description |
---|---|
Test period |
This indicates how often should the test be executed. |
Host |
The host for which the test is to be configured. |
Port |
Refers to the port used by the Microsoft RDS server . |
Report by Domain Name |
By default, this flag is set to Yes. This implies that by default, the detailed diagnosis of this test will display the domainname\username of each user who logged into the Microsoft RDS server. This way, administrators will be able to quickly determine which user logged in from which domain. If you want the detailed diagnosis to display the username alone, then set this flag to No. |
Exclude |
By default, this parameter is set to none. This means that the test will monitor all the applications that are launched on the Microsoft RDS server, by default. If you want the test to disregard certain applications when monitoring, then provide a comma-separated list of process names that correspond to the applications you want to ignore, in the exclude text box. For instance, your specification can be: winword.exe,js.exe,taskmgr.exe. Your specification can include wild card patterns as well. For example: *win*,js*,*task |
Show Only Whitelist Apps |
In some highly secured virtual environments, administrators whitelist an index of business-critical and most commonly used applications that are permitted to be present and active on the target Virtual Apps server. The goal of whitelisting is to protect the target server from potentially harmful applications and prevent any unauthorized files from executing. Application whitelisting places control over which applications are permitted to run on the target server and is controlled by the administrators, rather than the end-user. In such environments, administrators may wish to monitor only the applications that are whitelisted on the target server. To achieve this, administrators can set the Show Only Whitelist Apps flag to Yes. By default, this flag is set to No indicating that this test monitors all applications executing on the target server. By default, eG Enterprise offers a comma separated list of pre-defined applications specified against the WhiteListProcesses option in the [EXCLUDE_APPLICATIONS] section of the eg_tests.ini file available in the <eG_INSTALL_DIR>./manager/config folder. Setting the Show Only Whitelist Apps flag to Yes will enable this test to monitor only the applications that are listed against the WhiteListProcesses option. If administrators wish to add or remove one or more applications to/from this pre-defined list, then, they can do so by specifying the applications against the WhiteListProcesses option. |
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. |
Detailed Diagnosis |
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:
|
Measurement | Description | Measurement Unit | Interpretation |
---|---|---|---|
Launch count |
Represents the number of instances of this published application that have been launched currently. |
Number |
Use the detailed diagnosis of this measure to know which users are currently accessing the application and the clients from which the users are connecting. |
Avg time to launch application |
Indicates the average time taken by this application to launch. |
Secs |
Compare the value of this measure across applications to know which application took the longest time to launch. User experience with this application will naturally be poor. |
Max time to launch application |
Indicates the maximum time taken by this application to launch. |
Secs |
Compare the value of this measure across applications to know which application registered the highest launch time during the last measurement period. To know which user experienced this delay in launching, use the detailed diagnosis of the Launch count measure. |