Agents Administration - Tests
 

Default Parameters for VmgApplaunchTest

When a user complains that it is taking too long to launch applications on physical machines, administrators must be able to quickly identify the applications that are being currently accessed by that user, know how much time each application took to launch, and thus pinpoint that application that is the slowest in launching. The VmgApplaunchTest provides these valuable insights to the administrators. This test auto-discovers all the applications that are currently launched on the physical machines, and for each discovered application, reports the average and maximum time that application took to launch. This way, the test points administrators to applications that are slow in launching. Detailed diagnostics provided by the test also reveals the users who are currently accessing the applications and the launch time of the application as perceived by each user session; in the process, the test accurately pinpoints which user was attempting to launch the application when the slowness was observed.

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

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

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

  • In some highly secure environments, administrators whitelist an index of business-critical and most commonly used applications that are permitted to be present and active on the target physical machine. 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 /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.

  • By default, EXCLUDE parameter is set to none. This means that the test will monitor all the applications that are launched on the target 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

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

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