Project MedEvac 2.11

MedEvac Tool Version 2.11

Created Date: September 20, 2006

Updated Date: November 3, 2006

Description

The MedEvac tool is used to run checks against a Presentation Server farm to verify environment health.

This tool can be used to check the following components of a Presentation Server farm:

Verify XML Service health:
Verifies that the XML Service is able to respond to an XML, Web Interface, Program Neighborhood Agent or Program Neighborhood Client request
Verifies that the XML brokers are able to contact the data collector
Verify data collector health:
Verifies data collector is able to provide a least loaded server for the specified application
Verifies IMA Service on the data collector is functioning properly
Verifies the IMA Service can read the data collector's local host cache
Verifies that the IMA Service can read its dynamic store data
Verifies at least one server in the farm has this application published
Verify least-loaded server health:
Verifies Terminal Services on least-loaded server.
Verifies Remote Procedure Call (RPC) Service on least-loaded server.

Prerequisites

Windows XP, Windows Server 2003
In order to perform the RPC test the user running this tool must have rights to remotely open the registry for the server in question—only read access is required

How to use MedEvac 2.11

1. Selecting servers for testing:

a. You can manually enter a server name in the Servers field and click the Add… button.

b. You can also enumerate Terminal Servers in your Domain by specifying a Domain name in the Domain field and clicking the drop-down box under Servers.

c. You can also enumerate servers in your Presentation Server farm by specifying an XML broker in the XML Broker field, the XML Port in the XML Port field and clicking the drop-down box under Servers.

d. The server's IP addresses may also be used.

e. The server's fully qualified domain name (FQDN) may also be used.

2. Running the XML Least Loaded Server test:

a. Make sure all fields under Tests are filled out with the correct information.

b. Make sure a valid server has been added under the Servers field.

c. Select the XML Least Loaded Server check box.

d. Click the Test button.

3. Running the XML Ticketing test:

a. Make sure all fields under Tests are filled out with the correct information.

b. Make sure a valid server has been added under the Servers field.

c. Select the XML Ticketing check box.

d. Click the Test button.

4. Running the Terminal Services Test:

a. Make sure all fields under Tests are filled out with the correct information.

b. Make sure a valid server has been added under the Servers field.

c. Select the Terminal Services Test check box.

d. Click the Test button.

e. If you are currently logged on with a user that does not have proper rights to enumerate servers and sessions on the test servers, provide MedEvac with the correct credentials using the User Name, Domain, and Password fields.

5. Running the RPC test:

a. Make sure all fields under Tests are filled out with the correct information.

b. Make sure a valid server has been added under the Servers field.

c. Select the RPC Test check box.

d. Click the Test button.

e. If you are currently logged on with a user that does not have proper rights to read the test server’s registry remotely, provide MedEvac with the correct credentials using the User Name, Domain, and Password fields.

6. Running LLS RPC and Terminal Services test:

a. Make sure all fields under Tests are filled out with the correct information.

b. Make sure a valid server has been added under the Servers field.

c. Select the LLS RPC and Terminal Services Test check box.

d. Select the Terminal Services and/or RPC check box (es).

e. You can also select to run these tests on an interval by specifying:

i. A number in the Count: field, which is the amount of times the tests run.

ii. A number in the Delay: field, which is be the amount of time in seconds to wait between tests.

f. Click the Test button.

Test Details

XML Least Loaded Server test: This test retrieves the least-loaded server from the zone data collector using the XML Service of the server specified in the Servers field.
XML Ticketing test: This test retrieves a ticket from the server specified in the Servers field.
Terminal Services test: This test checks Terminal Services health on the server specified in the Servers field.
RPC test: This test checks RPC health on the server specified in the Servers field.
LLS RPC and Terminal Services test: This test retrieves the least loaded server from the zone data collector using the XML Service of the server specified in the Servers field.
-And-
It checks Terminal Services health (if selected) on the least-loaded server returned from the Least Loaded Server test.
-And-
It checks RPC health (if selected) on the least-loaded server returned from the Least Loaded Server test.

Uninstalling MedEvac 2.11

No uninstallation is necessary; simply delete the executable from the machine.

Fixed in this Version

There was a problem with the XML tests that would cause the tests to return as failures when checking servers where the XML port was being shared with Internet Information Services (IIS). The server would not end the connection causing MedEvac to hang and eventually time out.

This problem was fixed by checking if we have reached the end of the transmission without waiting for the server to end the connection.

[Fixed in version 1.5]

MedEvac looked like it was hung while it was performing tests; a secondary thread has been added to prevent this behavior from occurring.

[Fixed in version 2.1]

When running in silent mode, MedEvac did not save a log if the Append Date to File Name option was not set in the configuration file passed to it. MedEvac now looks at both options independently when fixing this problem.

[Fixed in version 2.11]

If the ENTER key was pressed while running MedEvac with the user interface, MedEvac would exit. That is the default behavior for dialog-based applications. In this version the default behavior has been changed to start performing tests or adding servers to the list depending what field has focus.

[Fixed in version 2.11]

Added Features

You can now import and export the server lists created within MedEvac.

Save Server List Button: This button saves the current displayed server list to a file with an .msl extension.
Import Server List Button: This button populates MedEvac's server list with the contents of the saved .msl file.

[Implemented in version 1.5]

Buttons for the import and save server list have been removed and placed in the Edit main menu.

[Implemented in version 2.0]

A new option in the servers' drop-down box now allows you to add all servers listed in the drop-down box.

[Implemented in version 2.0]

You can now browse for the Presentation Servers in a specific farm by specifying the XML Browser, the XML Port Number, and clicking the drop-down box for servers.

[Implemented in version 2.0]

You can now browse for the application name by specifying the XML Browser, the XML Port Number, and clicking on the drop-down box for the application name.

[Implemented in version 2.0]

The Log Window is now detached and resizable.

[Implemented in version 2.0]

Silent mode has been implemented, which allows for MedEvac to run in the background, save test results to a log file, and send emails in case of test failure.

The following procedure describes how to use this feature:

Open MedEvac and go to View > Silent Settings from the main menu.
Set all settings and save it to the settings file of your choice.
Create a list of servers to run the test against and save it to a file.
Run MedEvac and pass them as parameters.

Note: For a list of switches run MedEvac with the /? switch or go to Help > Command Line Switches from the main menu.

[Implemented in version 2.0]

Email alerts through Simple Mail Transfer Protocol (SMTP) have been implemented when running MedEvac in Silent Mode.

The following procedure describes how to use this feature:

1. MedEvac must run in Silent Mode using command line switches.

2. All fields pertaining to this feature must be filled out:

The SMTP Server Name field is used to specify the server running the SMTP service.
The SMTP Port field is used to specify the port in which the SMTP port is running. (Default: 25)
The From field is used to specify which e-mail the mail will come from. (Default: medevac@citrix.com)
The To field is used to specify to whom the e-mail will be sent, multiple e-mail addresses can be specified separated by semicolons ";".
The Importance field specifies the importance of the email and can be set to Low, Normal, or High.
The Subject field can be used to place any subject you desire.
The Message field is used to specify the message you will receive. Four variables have been defined for this field:

i. [SERVERNAME] - This variable is replaced with the server name in which the test was running on.

ii. [TESTNAME] - This variable is replaced with name of the test that failed.

iii. [ERRORNUMBER] - This variable is replaced with the error number returned by the failed test.

iv. [ERRORMSG] - This variable is replaced with the error message returned by the failed test.

[Implemented in version 2.0]

Log files are not overwritten with the Append date to log file option selected.

However, the log file is overwritten if you schedule MedEvac to run two or more times on the same day because it appends only the month, day and year to the file name.

[Implemented in version 2.0]

During the LLS (Least Loaded Server Tests) MedEvac now requests the address of the least-loaded server each time it runs the tests.

[Implemented in version 2.0]

Added a secondary thread in order to perform tests so MedEvac no longer looks like it is hung while performing tests.

[Implemented in version 2.1]

Added a progress bar to give the user an idea of how much work is left to finish all selected tests.

[Implemented in version 2.1]

Support

Support for MedEvac is limited but we still would like to hear from you so all questions, concerns, bugs and comments can be submitted to the "Comments" section on this page.

Disclaimer

These software applications are provided to you as is with no representations, warranties or conditions of any kind. You may use and distribute it at your own risk. CITRIX DISCLAIMS ALL WARRANTIES WHATSOEVER, EXPRESS, IMPLIED, WRITTEN, ORAL OR STATUTORY, INCLUDING WITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NONINFRINGEMENT. Without limiting the generality of the foregoing, you acknowledge and agree that (a) the software application may exhibit errors, design flaws or other problems, possibly resulting in loss of data or damage to property; (b) it may not be possible to make the software application fully functional; and (c) Citrix may, without notice or liability to you, cease to make available the current version and/or any future versions of the software application. In no event should the code be used to support of ultra-hazardous activities, including but not limited to life support or blasting activities. NEITHER CITRIX NOR ITS AFFILIATES OR AGENTS WILL BE LIABLE, UNDER BREACH OF CONTRACT OR ANY OTHER THEORY OF LIABILITY, FOR ANY DAMAGES WHATSOEVER ARISING FROM USE OF THE SOFTWARE APPLICATION, INCLUDING WITHOUT LIMITATION DIRECT, SPECIAL, INCIDENTAL, PUNITIVE, CONSEQUENTIAL OR OTHER DAMAGES, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. You agree to indemnify and defend Citrix against any and all claims arising from your use, modification or distribution of the code.