How To Monitor Farm Health Using Medevac All About Citrix

After this, Farm Monitors scans every XenApp / Presentation server in the farm. When all elements of the farm are gathered, Farm Monitor pings these servers to see if they are online/reachable.
Please let me know if we can use Director 7.15 to monitor a XenApp 6.5 farm. I found an article on Citrix support page that mention something about Director 7.6 integration with XA 6.5 but I am not sure this will work for D 7.15 or higher. Thank you, Adrian.

A Citrix farm is slow, then all the users logging in to the farm will experience slowness. Therefore, performance monitoring is one of the most critical operations functions in a Citrix infrastructure. If we look back about a decade ago, Citrix deployments were simple and involved just two tiers. These consisted. A Citrix farm is slow, then all the users logging in to the farm will experience slowness. Therefore, performance monitoring is one of the most critical operations functions in a Citrix infrastructure. If we look back about a decade ago, Citrix deployments were. Deploying the BIG-IP LTM System with Citrix XenDesktop DEPLOYMENT GUIDE Version 1.1. Important: This guide has been archived. While the content in this guide is still valid for the products and versions listed in the document, it is no longer being updated and may refer to F5 or third party products or versions that have reached end-of-l.

Citrix Medevac is a fantastic tool but does not work fine with xenapp 6.5.

If you need check your XML Servicers healthy, you can use Perl to launch a script, it is the same used by Netscaler to monitoring the XML service, or very similar.

This script is tested with Perl Strawberry 5.x and works fine.

Only you need publish a app in the XML servers and you must launch the script to the specific servers and asking by this app. You can use a Batch file to run the script to the all brokers servers.

If you have xenapp 5, you can use this script to test all xenapp servers in the farm.

Ok, it is true. you can use third parties monitoring to acomplish this task, but come on..a lot off times this agents are not working. or maybe, if some 'monkey' of monitoring department call you at 3 A.M. you need a simple script to test really the healthy of all entire citrix farm.

If you have a txt file with all XML servers, you can create a batch script like thius to launch the perl script:

FOR /F 'eol=; tokens=1 delims=; ' %%i in (xmlbroker.txt) do (

CitrixTestXMLService_v02.pl %%i 8080 'notepad-xml-service' %historic_file% %Log_file%

How to monitor farm health using medevac all about citrix service

And this is the Perl Script:

# This script can be run at the command line on a laptop or server

# to verify functionality of the Citrix XML Service

# perl test_xml_service.pl <ipaddress> <xml_port> [ appname ] #

use IO::Socket;

my $now_string = localtime;

if ($#ARGV < 1) {

print 'nUsage: perl test_xml_service.pl <ipaddress> <xml_port> [app name]n';

}

my $xml_port = $ARGV[1];

my $app = $ARGV[2] || 'notepad';

chop($hostname);

open(LOGFILE, '>>', $ARGV[3]);

How To Monitor Farm Health Using Medevac All About Citrix Access

my $xml_request = '<?xml version='1.0' encoding='UTF-8'?>n' .

'<!DOCTYPE NFuseProtocol SYSTEM 'NFuse.dtd'>n' .

'<RequestAddress>n' .

'<Name>n' .

'</Name>n' .

'</NFuseProtocol>n';

my $header = 'POST /scripts/wpnbr.dll HTTP/1.1rn' .

'Content-Length: $content_lengthrn' .

'rn';

print 'Header:n';

print 'XML Request:n';

How To Monitor Farm Health Using Medevac All About Citrix Service

print '-------nn';

my $socket1 = IO::Socket::INET->new(PeerAddr => $ip_address,PeerPort => $xml_port,

Proto => 'tcp') || die $ARGV[0] . ':' . $ARGV[1] . ' -> $@ ' . $now_string . ' ;n';

my @output;

if (m/</NFuseProtocol>/) {

last;

else {

}

push @output, $_;

my $output;

{

print LOGFILE $ARGV[0] . ' ' . $ARGV[1] . ' ' . ' -> exit 0 - ' . $now_string . 'n';

How To Monitor Farm Health Using Medevac All About Citrix Employee

}

@output = 'null';

print STDERR $ARGV[0] . ':' . $ARGV[1] . ' -> exit 1 ' . $now_string . ' ;n';

How To Monitor Farm Health Using Medevac All About Citrix Portal

print LOGFILE $ARGV[0] . ':' . $ARGV[1] . ' -> exit 1 - ' . $now_string . ' ;n';

downloadWhy can't I download this file?

Description

Relevant Links

Backup the Farm Data Store Regularly
This database contains the persistent farm information including published applications, servers, policies, and other settings. If it is corrupted or the database server fails, without a current backup, the farm must be recreated. Remember to also verify the integrity of the data store backups by performing test restores on another server or instance.

Build at Least One Test Environment/Farm
A test environment is critical for testing new applications, updates, and settings before rolling them out into production. Having one or more test servers in a production farm is not sufficient because they still connect to the production database and can potentially impact the production servers in the farm. Create a separate farm or farms for testing with settings that closely resemble what is used in production.

None

Keep Abreast with Updates and Hotfixes
Operating system, application, and Citrix hotfixes and updates should be up-to-date to prevent issues from arising and maintain the performance, stability, and security of the environment. Always test updates and hotfixes in a test environment prior to rolling them out into production. With XenApp, all Hotfix Rollup Packs (HRPs) should be applied after testing and individual hotfixes applied only if denoted as critical or to address a specific problem being faced.

CTX120842
CTX127228

Implement a Change Management Plan
Most enterprise XenApp deployments are administered by several individuals or teams which can make it challenging when trying to track down changes. Creating a change management plan within your organization makes it easier to pinpoint changes and makes troubleshooting more efficient. In addition, the Configuration Logging feature of XenApp can be enabled to record changes made within the management console for later viewing.

Search “Configuration Logging” at Citirx Product Documentation web site.

Avoid Non-Native/Third-Party Printer Drivers
Printing problems are one of the most frequent areas that Citrix Technical Support sees on a regular basis. One of the main factors attributed to printing problems are because of non-native or third party printer drivers which are not designed or tested to work in multi-user environments such as Terminal Services/Remote Desktop Services. Always use native/inbox printer drivers and the Citrix Universal Print Drivers to prevent printing problems.

CTX111967
CTX126093
CTX119815

Shadows of evil glitches. Get Familiar with Common Tools
Different tasks and problems call for different set of tools. It is important to familiarize yourself with the Citrix and third party tools and their usage, both from a proactive and reactive standpoint.

CTX122827
CTX126294

Know the Types of Memory Dumps
Dumps are created when processes or the operating system itself crashes. Dump files can also be manually generated when troubleshooting issues such as hangs or memory leaks. It is important for administrators to understand the types of dump files available and ensure that their servers are properly configured for kernel or complete memory dumps.

Understand Zones and Data Collector
Zones are groupings of XenApp servers designed to create a hierarchical structure and efficiently handle changes as they are made. Every server farm has at least one zone and the number of zones should be kept minimum to avoid additional complexity. Each zone has a data collector which manages the dynamic information for servers in that zone. The data collector is determined by a preference that the administrator sets. Every zone should have one server set as Most Preferred and one or more servers with a preference of Preferred to take over the role if the data collector becomes unavailable.

Search “Zones” at Citirx Product Documentation web site.
CTX126335

Monitor Farm Health
It is important to ensure the health of all servers in a XenApp environment and be alerted when problems arise or might soon arise. XenApp includes a Health Monitoring and Recovery feature which consists of various tests on core components. If any tests should fail, alerts can be triggered along with actions such as removing a server from load balancing. In addition, standalone tools such as MedEvac can be used to periodically assess farm health. For more comprehensive monitoring, the Citrix EdgeSight product can be used.

Search “Health Monitoring and Recovery” at Citirx Product Documentation web site.
CTX107935

Review Plug-in/Receiver Considerations
Administrators should ensure that users connecting to the XenApp environment are doing so with the appropriate plug-in or receiver type and that it is updated and properly configured. Plug-ins can be installed, updated and configured on client devices through Active Directory as well as with Receiver using Merchandising Server.

Refer to the “Receiver and Plug-ins” at Citirx Product Documentation web site.