how to set up SSL, see “Setting up SSL for SMTP Email Alerts” on page 47.
Using MAPI to Send Alerts
To use MAPI to send alerts, you must:
• Select the MAPI connection servers
• Create a mail profile for Resource Manager
• Enable the Resource Manager MAPI mail service
• Configure Resource Manager to use MAPI email alerts
Selecting the MAPI Connection Servers
You need to select one or more servers in the server farm to be the MAPI connection servers. When email alerts are generated in the farm, they are passed to one of the configured MAPI servers, which then sends the actual email. You can configure as many MAPI connection cervers as you want. Alerts are sent through a randomly selected MAPI server, although if the server on which an alert is generated is also a MAPI server, that server sends the email.
Each MAPI connection cerver must be able to access a mail server (for example, Microsoft Exchange Server). It must have an email client installed (for example, Microsoft Outlook) that conforms to the X-400 protocols.
Creating an Email Profile for Resource Manager
On each MAPI connection server, you need to configure an email profile for Resource Manager to use. The profile must have the same name and details on all of your MAPI connection servers. Citrix recommends that you give the profile a name that is easy to recognize (for example, Resource Manager). The profile is used throughout the server farm.
When you create the email profile, ensure that you include the email system that you want to use; for example, Microsoft Exchange Server. You can also specify an address book for the profile.
After you set up the profile, it is a good idea to test that you can log on to your email system using the profile and that you can send a message.
Note A user who is configured to use the email profile can log on to the email system without being prompted for logon credentials.
For more information about configuring email profiles, refer to Citrix Knowledge Base article CTX333658 available at http://knowledgebase.citrix.com.
Enabling the Resource Manager MAPI Mail Service
Email alerts are managed by a service called Citrix Resource Manager Mail. This service is installed automatically on all servers on which you install Resource Manager. You need to enable the service on each MAPI Connection Server.
To enable the Citrix Resource Manager mail service on a MAPI connection server
1. Open the Windows Control Panel.
2. To open the Services dialog box, open Administrative Tools, then open Services.
3. In the Properties dialog box for the Citrix Resource Manager mail service, click the General tab and ensure that the startup type for the service is set to Automatic.
4. From the Log On tab, select This account.
5. Enter the details of the local user account, including the domain, that you want Resource Manager to use for email alerts. Ensure that you type the account and domain details exactly, or browse to the account so that you can be sure that the details you enter are correct.
6. Ensure that the Resource Manager Mail service is started.
Configuring Resource Manager to Use MAPI Email Alerts
After you set up the MAPI connection servers, you must set up Resource Manager to use email alerts for the server farm. For example, you need to specify the alert recipients. These settings apply to the entire server farm. See the Resource Manager online help system for more information about MAPI email alerts.
Chapter 5 Alerting Administrators to Poor Server Performance 47 Document Center
Setting up SSL for SMTP Email Alerts
1. Install the certification path of your certificate authority on each Resource Manager server. In the Microsoft Management Console, add the root certificate path in the following location:
Certificates (Local Computer)\Trusted Root Certification Authorities\Certificates
This step enables each server to trust certificates issued by your certificate authority.
2. In the left pane of the Presentation Server Console, click Resource Manager.
3. In the right pane, click Email. From the Email tab:
A. Specify the SMTP server by typing its fully qualified domain name (FQDN). For example:
smtpserver1.mydepartment.mycompany.com B. Click Use SSL to send email alerts.
C. Click OK.
Preparing Your System for SMS Alerts
To send an SMS message to a cell/mobile phone, a Resource Manager server makes a call through its modem to a number that is designated by the cell/mobile service provider. It then sends data to the service provider’s computer, instructing it to send an SMS message to the cell/mobile phone of the person who is to receive the alert.
If you want to use SMS alerts, ensure that at least one Resource Manager server in the server farm has a modem. This can be an analog modem or an ISDN card.
You need to investigate the modem requirements of the service providers for the cell/mobile phones to which you want to send alerts. Some service providers require a specific type of modem (usually analog). Where this is the case, at least one server with that type of modem must be in the server farm before you can use SMS alerts for that service provider.
Important This section assumes that you have access to a certificate authority and an appropriate root certificate, and are familiar with the procedure of adding a certificate path to a Windows server. You must also ensure that your SMTP server supports SSL and is properly configured to use SSL in your network environment.
If the people that you want to receive SMS alerts use a variety of service providers, you need to know the details of the gateway that Resource Manager must use to communicate with each service provider. Each provider is likely to have a different telephone number, and may employ a different protocol to carry the messages. Some service providers offer an analog line, others offer ISDN.
You probably need to configure a range of numbers to call and a range of protocols to use.
The alert recipients you set up will be used for all the servers in the server farm.
You can modify Resource Manager alert recipients for any individual server.
Configuring Resource Manager to Use SMS
When you are sure that you fulfilled all the requirements for SMS alerts, you can configure the way in which Resource Manager uses SMS for alerts in the server farm. For example, you need to specify the alert recipients. These settings apply to the entire server farm. You can also specify SMS alert recipients for individual servers.You need to select one or more servers in the server farm to send the SMS alerts. Such a server is called a TAPI Server. For more information about
configuring Resource Manager to use SMS, see the Resource Manager online help system.
Preparing Your System for SNMP Alerts
Resource Manager can send five different SNMP alerts:
• The Resource Manager server is down
• The metric on the Resource Manager server changed to green status
• The metric on the Resource Manager server changed from green to yellow status
• The metric on the Resource Manager server changed from red to yellow status
• The metric on the Resource Manager server changed to red status To receive SNMP messages, a computer on a network requires an SNMP management tool that enables it to listen for messages. A number of third-party commercial tools are available.
Chapter 5 Alerting Administrators to Poor Server Performance 49 Document Center
You need to install and set up the Windows Server 2003 SNMP service on every server that has a metric configured to send SNMP alerts.
If you want Resource Manager to send alerts for the Count metric on any applications that are running in the server farm, ensure that the Farm Metric Server has the Windows SNMP service enabled and running.
Running a Script when an Alert Threshold Is Breached
You can create an executable file to run on a local Resource Manager server when a server metric indicates that a problem condition exists. For example, you can use a script to take a server offline when its free disk space goes below 5%, or to restart a database following a database-related error.
The script you select runs under the LocalService account, and starts every time the metric enters a red alarm state (not just the first time). It must, therefore, be one that can run as an automated response to alarms (that is, without a user interface) and it must terminate automatically and release all resources.
You identify the script to run when adding or editing a metric in a monitoring profile in the Configure Performance Metric Thresholds dialog box on the Access Management Console. See “Configuring Metrics” on page 29 for more information on adding and editing metrics.
Because versions of Presentation Server prior to 4.5 cannot use monitoring profile functionality, perform the following procedure to run a script.
To run a script for servers running Presentation Server 4.0 or earlier 1. In the left pane of the Presentation Server Console, expand the Servers
folder, then click the name of the local server for which you want to add a script.
2. In the right pane, click the Resource Manager tab to display the current status of the server.
3. Select the metric for which you want to run the script; right-click and select Properties. The Server Metric Properties dialog box opens.
4. From the Script configuration tab, click Run Script on transition up to red.
Note After you install the SNMP service, you must restart the computer for Resource Manager alerts to be sent or received.
5. Click Browse to locate the script. The script must be on a local drive and the System account must have access to run it. Select only executable files here and be aware that they run as a process in the background.
6. To copy metric configuration to other servers or applications, click Apply to other servers.
To copy the configuration of the current metric to other metrics in the Metrics list, click Copy properties to other metrics.
7. Click OK to confirm your changes and Resource Manager runs the executable file when the metric indicator you specified turns red.
Receiving Failed Import Alerts
Resource Manager warns you of failed attempts to update the summary database, and can be configured to send alerts under these circumstances. In its red state, an icon on the Summary Database tab identifies failures to commit any record in the last attempted update to the database, and the Summary Database
Configuration dialog box allows you to notify administrators of any such failure.
For further information, see “Monitoring the Status of the Summary Database” on page 57 and “Setting up a Summary Database” on page 19.
Receiving License Server Connection Failure Alerts
With the Citrix Licensing feature, Citrix licensing is handled by one or more license servers. Computers running Citrix Presentation Server communicate with license servers to ensure that client sessions are licensed appropriately. A license server connection failure alert is raised when a server cannot communicate with its associated license server. This may be due to a hardware failure on the license server, the license service on the license server malfunctioning, or network problems between the license server and the computer running Citrix Presentation Server.
When contact with a license server is lost, the computer running Citrix
Presentation Server lapses into a licensing grace period. Typically, the licensing grace period is 30 days. During this period, the Citrix Presentation Server software is fully functional and connections to the server work normally. Contact with the license server must be reestablished before the grace period ends, or the software is reduced automatically to single user mode and only the administrator can log on to the server.
Note You cannot type directly in the box; you must click Browse.
C
HAPTER6
Document Center
Recording the History of Servers and Applications
Overview
This chapter explains how you can use Resource Manager to store details of server performance, application instances, and resource usage in a summary database. Topics include:
• How Resource Manager information gets into a summary database
• What information you should record in a summary database
• Scheduling data collection for a summary database
For information about how to set up a summary database, see “Setting up a Summary Database” on page 19.
Resource Manager and the Summary Database
Each Resource Manager server creates a summarized version of its daily activity.
This information is known as summary data. There are various types of summary data:
• Server-specific performance metrics
• Server-specific session information
• Farm-wide application metrics
• Farm-wide server events (for example, server-down)
• Alert metrics
Farm-wide metric and server event information is generated as summary data by the Farm Metric Server in addition to its own server-specific information and metrics. Farm-wide metrics are routed from servers to the Farm Metric Server through the zone data collector.
Summary data is kept in temporary summary files that are stored locally on each server in a database-compatible format. Each hour, Resource Manager adds the summary data gathered over the previous hour to the summary files. Summary files are stored in the following folders: \\Program Files\Citrix\Citrix Resource Manager\SummaryFiles folder for 32-bit servers, and \\Program Files
(x86)\Citrix\Citrix Resource Manager\SummaryFiles folder for 64-bit servers.
On a daily basis, the summary data held by each server in the server farm is collected by the Database Connection Server. The Database Connection Server then updates the summary database. After the summary database is updated, summary files are overwritten with new data.
The following diagram represents a typical server farm using the Resource Manager summary database. It shows the flow of both server-specific and farm-wide summary data from the farm servers to the summary database through the Database Connection Server.
A diagram showing a server farm using a summary database SERVER FARM data sent once a day
Daily summary data
Server B
Chapter 6 Recording the History of Servers and Applications 53