Windows Media Services Management Pack Guide
| Archived content. No warranty is made as to technical accuracy. Content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist. |
Windows Media Services 9 Series Management Pack for Microsoft Operations Manager 2000 SP1
Updated : April 1, 2004
Developed by the Windows Media Platform Group, Digital Media Division
On This Page
Recommended Knowledge and Skills
Overview of the Windows Media Services Management Pack
Deploying the Windows Media Services Management Pack
Operations Tasks
Known Issues
Reference
Acknowledgements
Recommended Knowledge and Skills
To deploy and operate the Microsoft® Windows Media® Services Management Pack, it is recommended that you possess the following knowledge and skills:
Working knowledge of the monitoring features in Microsoft Operations Manager 2000 (MOM).
Basic understanding of the three MOM design architectures, and knowledge of the specific design architecture that is deployed in your organization. For more information about MOM design architectures, see Chapter 2, "Architecture Overview," of the MOM SP1 Deployment Guide.
Familiarity with the recommended process for deploying Management Packs as described in Chapter 7, "Deploying Management Packs," of the MOM SP1 Deployment Guide.
Administrative and working knowledge of Windows Media Services 9 Series in Windows Server™ 2003. For more information, see Windows Media Services 9 Series Help.
Working knowledge of common Windows Media Services performance issues, limitations, and performance monitoring techniques. For more information, see Optimizing Microsoft Windows Media Services 9 Series.
Overview of the Windows Media Services Management Pack
The Microsoft Windows Media Services Management Pack collects internal Windows Media server events generated by Windows® Management Instrumentation (WMI) so you can monitor the operation of the server running Windows Media Services 9 Series. This Management Pack highlights operation and performance issues that may indicate possible service outages or configuration problems, so you can take corrective or preventative actions quickly. This Management Pack also includes rules for two sets of performance object counters in Windows Media Services 9 Series that monitor server performance, and public views that monitor client traffic on your server network. You can use these counters and public views to monitor server performance, health, and availability.
Server Operation
The WMS WMI Event Handler plug-in enables you to monitor specific aspects of server operation. After enabling and configuring the WMS WMI Event Handler plug-in in Windows Media Services 9 Series, this Management Pack can collect local or remote notification of server events to monitor the following server functions:
Server. Reports server status or property changes.
Client. Reports client-side events that occur in Windows Media Player.
Limit. Reports server limits whenever they are changed or reached.
Playlist. Reports playlist-related events.
Cache. Reports any events pertaining to cache activity.
Publishing point. Reports changes in publishing point status or properties.
Plug-in. Reports publishing point and server plug-in activity.
All WMI event classes, except for the client WMI event class, are enabled by default in Windows Media Services 9 Series.
Server Performance
Windows Media Services 9 Series provides two sets of performance object counters that you can use to monitor your Windows Media servers and publishing points. The Windows Media performance counters can provide useful information in the following scenarios:
View real-time usage statistics. Performance counters provide information about the current usage of the server, such as the number of currently connected players, the amount of bandwidth used, and the number of distribution streams.
Identify streaming problems. Performance counters provide information to help you identify and troubleshoot issues in your streaming system, such as the number of stream errors and resend requests.
Monitor encoder and distribution streams. Encoder and distribution server packet counters help identify when streams from an encoder or streams through a distribution server are failing.
Report peak usage. Most counters provide peak values, which enable you to track the maximum usage or capacity of your system.
Public Views
This Management Pack collects performance data for sampling purposes and displays the collected data in public views that can be used to monitor the health of the server running Windows Media Services 9 Series. The following public views allow you to monitor the health and availability of your Windows Media Services environment by observing client traffic on your server network:
Connection Queue Length. The current number of client (player and distribution server) connection requests that are pending.
Connection Rate. The current number of clients that are connecting to the server every second.
Player Connections. The current number of players with unicast connections. Distribution server connections to the origin server are not included in this number.
Streaming Players. The current number of players that are streaming data through all protocols. This does not include players that are stopped or paused.
Windows Media Services Components
Windows Media Services is scalable by design to support a range of deployments, from small Internet radio stations that have hundreds of connection requests to large-scale streaming media Web sites that generate millions of requests. Windows Media Services includes a server component and administrative components that are used to administer the server. The administrative Windows Media Services snap-in is used locally on the same Windows Media server, while Windows Media Services Administrator for the Web is used on a remote computer to administer the local Windows Media server.
Single Server Configuration
In a single-server configuration, the Windows Media Services Management Pack is deployed only on the server component. No other Management Packs are required to monitor Windows Media Services.
Network Configuration
In a network configuration, MOM can provide central monitoring and automatic problem notification for the Windows Media server network, continuously monitoring the individual servers on the network. Deployment of Windows Media Services Management Pack is accomplished by installing a MOM agent on all Windows Media server computers in the network, including the cache/proxy server in a Windows Media Services cache/proxy system.
Clustered Server Configuration
Windows Media Services can be installed on clustered servers. By default, when clustered servers are running the Windows Server 2003, Enterprise Edition or Windows Server 2003, Datacenter Edition operating systems, events that are logged in the event log of one node in the cluster are also shown in the event log of the other nodes. To monitor these servers by using MOM, Event Log Replication must be disabled on each of the servers within the cluster. For more information, see the "Clustered Servers" section in Chapter 6, "Deploying Agents," in the MOM SP1 Deployment Guide.
Deploying the Windows Media Services Management Pack
MOM is a WMI-based console that you use to manage your servers. When you install Windows Media Services Management Pack, MOM subscribes to different WMI events that report on your Windows Media server activity. MOM also sets alerts that enable you to respond to situations as they arise. Windows Media Services includes the WMS WMI Event Handler plug-in, which is responsible for communicating event information between the Windows Media Services service and MOM. For more information about WMI events and classes in Windows Media Services, see the Windows Media Services SDK.
Setup and Configuration
The Windows Media Services 9 Series WMI Event Handler plug-in is responsible for communicating event information between the Windows Media Services service and other services and programs, including MOM. The plug-in reports all Windows Media Services events (except for client WMI events) by default.
Windows Media Services 9 Series also provides two sets of performance object counters that you can use to monitor your Windows Media servers and publishing points: Windows Media Services and Windows Media Publishing Points. Windows Media performance counter statistics are reported as Event Log events to the Performance Counters processing rule group in Windows Media Services Management Pack.
This section describes how to configure the following features to suit your needs:
Configuring WMI event reporting
Configuring performance counter event reporting
Configuring WMI Event Reporting
To customize WMI event reporting so that MOM evaluates only the rules that are most important to your system, you can do one of the following:
Change WMI event class reporting in Windows Media Services 9 Series
Turn off a processing rule in MOM to stop it from monitoring an event from a WMI event class.
To configure WMS WMI Event Handler plug-in properties
In the Windows Media Services 9 Series console tree, click the server or publishing point for which you want to report WMI events.
In the details pane, click the Properties tab.
In Category, click Event notification.
Click WMS WMI Event Handler, and then click Properties.
In the WMS WMI Event Handler Properties dialog box, in Classes, select the check box for each WMI event class you want to report. For more information on the event classes, see Windows Media Services 9 Series Help.
To turn off a WMI event processing rule
In the MOM console tree, expand Microsoft Operations Manager (default), Rules, Processing Rule Groups, Microsoft Windows Media Services, Windows Media Services 9 Series.
In the console tree, click the Event processing rules folder that contains the processing rule that you want to turn off.
In the details pane, right-click the processing rule that you want to turn off, and then click Properties.
On the General tab, clear the Enabled check box.
Configuring Performance Counter Event Reporting
In Windows Media Services 9 Series Management Pack, performance counter statistics are reported to the Performance Counters processing rule group by the Event Log service in Windows Server 2003. By default, the Event Log service is configured to start automatically when Windows starts and cannot be stopped; therefore no additional configuration is required.
If the startup type for this service is set to Disabled, change the setting to Automatic so that this processing rule group can monitor performance counter statistics in Windows Media Services 9 Series.
To customize performance counter event reporting so that MOM evaluates only the rules that are most important to your system, do the following:
- Turn off a processing rule in MOM to stop it from monitoring an event in the Performance Counters processing rule group.
To turn off a performance counter processing rule
In the MOM console tree, expand Microsoft Operations Manager (default), Rules, Processing Rule Groups, Microsoft Windows Media Services, Windows Media Services 9 Series, Performance Counters.
In the details pane, right-click the performance counter processing rule that you want to turn off, and then click Properties.
On the General tab, clear the Enabled check box.
Windows Media Services Management Pack Monitoring Scenarios
Server Health
The Threshold Performance Counters processing rule group in this Management Pack contains rules that monitor server CPU and memory usage, as well as critical Windows Media server limits. The threshold values for each rule in this Management Pack are predefined, and they will need to be adjusted so that they continue to function appropriately in your production environment. After you study your production environment and determine its performance boundaries, you should change the default threshold values for each rule so that they generate alerts when counter values reach 75 percent of monitored limits. Although you can enter threshold values so that alerts are generated when counter values reach a higher or lower percentage of the limit that is monitored, the 75 percent threshold value is effective for most Windows Media server installations.
To make effective use of the rules in the Threshold Performance Counters processing rule group, we recommend that you first perform network load tests using Windows Media Load Simulator 9 Series to determine the maximum capacity of your server and establish appropriate limits for your system. You can specify limits at both server and publishing point levels to specify the performance boundaries for your Windows Media server. By adjusting the limit values, you can ensure that stream transmission does not exceed the capabilities of your server, network, or audience.
This section describes how to adjust threshold values and create an alert response that signals when a threshold value has been exceeded.
Setting Threshold Performance Boundaries
Use the following procedure to adjust threshold values on the Threshold tab for each performance threshold rule in this Management Pack.
To adjust threshold values
In the MOM console tree, expand Microsoft Operations Manager (default), Rules, Processing Rule Groups, Microsoft Windows Media Services, Windows Media Services 9 Series, Threshold Performance Counters.
In the details pane, right-click the performance counter processing rule that you want to adjust, and then click Properties.
In the performance threshold rule Properties dialog box, on the Threshold tab, enter a threshold value. We suggest using a value that is approximately 75 percent of the corresponding limit that the rule is monitoring.
For more information about defining thresholds for performance counters, see Microsoft Operations Manager Online Help.
Configuring Alert Responses
In the Properties dialog box for a threshold performance counter, you can configure a response that occurs when the rule generates an alert, such as launching a script or sending an e-mail message to the server administrator or a notification group. The default notification group for processing rule responses in this Management Pack is Windows Media Services Administrators. No responses are preconfigured for the rules in the Threshold Performance Counters processing rule group. For more information about configuring a response to threshold performance counter alerts, see Microsoft Operations Manager Online Help.
Critical Publishing Points
The Windows Media Services Management Pack contains the Publishing Point Events processing rule Critical Publishing Point Stopped, which can be used to monitor one or more publishing points deemed critical to network or business operations. To use this rule, you must enter the publishing point name in the rule properties and then turn on the rule. You can make copies of this rule for each of your critical publishing points, giving each copy of the rule the unique publishing point name.
This section describes how to enable and create rules for your critical publishing points
Configuring the Critical Publishing Point Stopped Rule
The Critical Publishing Point Stopped processing rule is provided so that publishing points deemed critical to network or business operations can be monitored. An alert is raised when this event occurs. This rule is not enabled by default.
To use this rule, you must enter the publishing point name in the rule properties and then turn on the rule. Perform the following procedure to do this:
To enable the Critical Publishing Point Stopped rule
In the list of Publishing Point Events processing rules, click Critical Publishing Point Stopped, and then on the Action menu, click Properties.
In the Critical Publishing Point Stopped Properties dialog box, on the Criteria tab, click Advanced.
In the Advanced Criteria dialog box, click Parameter 18 in the box that displays the rule criteria, and then click Remove.
In the Define more criteria box, do the following:
In the Field box, select Parameter 18.
In the Condition box, select equals.
In the Value box, type the name of the publishing point.
Click Add to List, and then click Close.
In the Critical Publishing Point Stopped Properties dialog box, on the General tab, click Enabled.
(Optional) In the Name box, rename Critical Publishing Point Stopped to Publishing_Point_Name Stopped, where Publishing_Point_Name is the name of the critical publishing point. This is useful if you want to create additional Critical Publishing Point Stopped rules to monitor other critical publishing points.
Creating Additional Critical Publishing Point Stopped Rules
If you have multiple publishing points that are critical to network or business operations, you can create additional Critical Publishing Point Stopped processing rules for each one so that they can be monitored individually. Each additional rule must have a unique rule name. Perform the following procedure to do this.
To create additional Critical Publishing Point Stopped rules
In the list of Publishing Point Events processing rules, click Critical Publishing Point Stopped.
On the Action menu, click Copy.
On the Action menu, click Refresh.
On the Action menu, click Paste.
The Copy Knowledge Authoring Entry dialog box appears.
In the Copy Knowledge Authoring Entry dialog box, click Copy the knowledge authoring entry for the new processing rule.
The Copy of Critical Publishing Point Stopped rule is added to the list of Publishing Point Events processing rules.
In the Copy of Critical Publishing Point Stopped rules properties, complete the procedure "To enable the Critical Publishing Point Stopped rule" to enable the new rule.
Negative Acknowledgements
Negative acknowledgements (NACKs) are client resend requests to the Windows Media server. Ordinarily, these requests occur when the server or network is overloaded and packets cannot be sent through the User Datagram Protocol (UDP) reliably. In this situation, clients must request that packets be resent. An attacker could also launch a denial of service attack by sending a high number of NACK requests to the server.
The Windows Media Services Management Pack contains two useful processing rules in the Event Log Events processing rule group that monitor NACK requests against a Windows Media Server: NACKs Warning and Stop Receiving NACKs. The limit for the NACKs Warning processing rule is set to a value such that only a high number of NACK requests will generate an alert. If you receive an alert from the Nacks Warning processing rule, investigate and resolve any network issues immediately. If the network does not appear to be at fault, you can review the Windows Media server log files to determine whether clients are instigating a denial of service attack, and then take appropriate action. For more information, see Logging Model for Windows Media Services 9 Series.
In the event that the number of NACKs received by the server exceeds the limit defined in the Stop Receiving NACKs processing rule, the server will stop receiving NACKs for one minute. This NACK warning limit is set so that only a very high number of NACK requests (indicative of a denial of service attack) will generate this alert.
Agent Log File Settings
The general recommendations for configuring agent logs are sufficient for use with the Windows Media Services Management Pack. See Chapter 6, "Deploying Agents," in the MOM SP1 Deployment Guide.
Security Settings
The Windows Media Services Management Pack does not require specific security settings for the Consolidator and Agent Manager (CAM) components on the server running MOM and the MOM agent service account on the Windows Media servers that are monitored. For more information about security requirements for the agent, see the "Security Requirements" section in Chapter 6, "Deploying Agents," in the MOM SP1 Deployment Guide.
Operations Tasks
We recommend that you review and prioritize all alerts on a daily basis. In addition, you should perform other tasks on a regular basis, depending on your environment. Many important problems do not cause alerts, but they still require periodic attention. You can perform the daily, weekly, and monthly tasks as specified in the tables in this section, adjusting the frequency of these tasks to meet the needs of your particular environment.
Daily Tasks
On a daily basis, perform the following tasks:
Review all open alerts.
Verify that all servers running Windows Media Services 9 Series are communicating with the MOM console.
Review warnings. (Optional)
Reviewing All Open Alerts
Review all new alerts in the following priority order:
Critical errors
Critical Windows Media Services alerts (see the "Reference" section in this document for a list of the critical events and alerts in this Management Pack)
Warnings (optional)
Informational messages (optional)
It is expected that not all problems can be repaired in one day or less. Commonly, parts must be ordered, or computers must be scheduled for restart. Be sure to follow up on these open alerts so that they are addressed in a timely manner.
To review open alerts
In the MOM console tree, expand Microsoft Operations Manager (default), Monitor, All Open Alerts.
Review all alerts that are older than 24 hours to make sure they are addressed in a timely manner.
Verifying That All Windows Media Servers Are Communicating with the MOM Console
Communication failure between a server running Windows Media Services 9 Series and the monitoring infrastructure prevents you from receiving alerts so that you can examine and resolve them.
To verify that a Windows Media server is communicating with the MOM console
In the MOM console tree, expand Microsoft Operations Manager (default), Monitor, All Agents.
In the details pane, click the Last Contact column heading. This column sorts all computers based on last contact time. If the last contact time is greater than five minutes, determine why the server computer is not communicating with MOM.
Reviewing Warnings
We recommend that you review warnings because they indicate pending failures. Reviewing warnings is not required, and they are not displayed by default.
To review warnings
In the MOM console tree, expand Microsoft Operations Manager (default), Monitor, All Open Alerts.
In the details pane, click the Severity column heading to sort by severity, and then review all warnings.
Weekly Tasks
The Windows Media Services Management Pack contains no specific weekly tasks.
Monthly Tasks
In addition to the tasks that you perform daily, review the following reports on a monthly basis:
Microsoft Operations Manager Report: Most Common Alerts by Processing Rule Group
Microsoft Operations Manager Report: Most Common Events
These reports help identify the areas where your system needs the most attention. They list the alerts and events that happen most often in your environment. By identifying the origin of these problems (or simply filtering the events and disabling the rules), you can:
Decrease the number of notifications to the operators and administrators
Decrease the number of false alarms
Increase the stability and availability of the Windows Media Services 9 Series environment
Increase the visibility of alerts that need attention
Also, you should review other reports as appropriate for your installation on a monthly basis.
As Needed Tasks
If you receive a critical error alert from the Critical Error processing rule in either the Publishing Point Event or Server Event processing rule groups, review the rule's Knowledge Base for information to help you address the issue. We recommend that you have a contingency plan in place for such events.
Known Issues
The Add and Remove processing rules in the Publishing Point Events processing rule group monitor the events that are invoked when Windows Media Services attempts to add or remove a publishing point on the Windows Media server. However, these events do not indicate whether the publishing point was added or removed successfully. This section contains procedures that you can use to create custom processing rules in MOM that report whether the publishing point was added or removed successfully.
To create a Publishing Point: Add Succeeded rule
In the list of Publishing Point Events processing rules, click Add.
On the Action menu, click Copy.
On the Action menu, click Refresh.
On the Action menu, click Paste.
The Copy Knowledge Authoring Entry dialog box appears.
In the Copy Knowledge Authoring Entry dialog box, click Copy the knowledge authoring entry for the new processing rule.
The Copy of Add rule is added to the list of Publishing Point Events processing rules.
Click Copy of Add, and then on the Action menu, click Properties.
In the Copy of Add Properties dialog box, on the Criteria tab, click Advanced.
In the Advanced Criteria dialog box, do the following:
In the Field box, select Parameter 19.
In the Condition box, select equals.
In the Value box, type 0 (0x0).
Click Add to List, and then click Close.
In the Copy of Add Properties dialog box, on the General tab, in the Name box, rename Copy of Add to Add Succeeded.
To create a Publishing Point: Add Failed rule
In the list of Publishing Point Events processing rules, click Add.
On the Action menu, click Copy.
On the Action menu, click Refresh.
On the Action menu, click Paste.
The Copy Knowledge Authoring Entry dialog box appears.
In the Copy Knowledge Authoring Entry dialog box, click Copy the knowledge authoring entry for the new processing rule.
The Copy of Add rule is added to the list of Publishing Point Events processing rules.
Click Copy of Add, and then on the Action menu, click Properties.
In the Copy of Add Properties dialog box, on the Criteria tab, click Advanced.
In the Advanced Criteria dialog box, do the following:
In the Field box, select Parameter 19.
In the Condition box, select not equals.
In the Value box, type 0 (0x0).
Click Add to List, and then click Close.
In the Copy of Add Properties dialog box, on the General tab, in the Name box, rename Copy of Add to Add Failed.
To create a Publishing Point: Remove Succeeded rule
In the list of Publishing Point Events processing rules, click Remove.
On the Action menu, click Copy.
On the Action menu, click Refresh.
On the Action menu, click Paste.
The Copy Knowledge Authoring Entry dialog box appears.
In the Copy Knowledge Authoring Entry dialog box, click Copy the knowledge authoring entry for the new processing rule.
The Copy of Remove rule is added to the list of Publishing Point Events processing rules.
Click Copy of Remove, and then on the Action menu, click Properties.
In the Copy of Remove Properties dialog box, on the Criteria tab, click Advanced.
In the Advanced Criteria dialog box, do the following:
In the Field box, select Parameter 19.
In the Condition box, select equals.
In the Value box, type 0 (0x0).
Click Add to List, and then click Close.
In the Copy of Remove Properties dialog box, on the General tab, in the Name box, rename Copy of Remove to Remove Succeeded.
To create a Publishing Point: Remove Failed rule
In the list of Publishing Point Events processing rules, click Remove.
On the Action menu, click Copy.
On the Action menu, click Refresh.
On the Action menu, click Paste.
The Copy Knowledge Authoring Entry dialog box appears.
In the Copy Knowledge Authoring Entry dialog box, click Copy the knowledge authoring entry for the new processing rule.
The Copy of Remove rule is added to the list of Publishing Point Events processing rules.
Click Copy of Remove, and then on the Action menu, click Properties.
In the Copy of Remove Properties dialog box, on the Criteria tab, click Advanced.
In the Advanced Criteria dialog box, do the following:
In the Field box, select Parameter 19.
In the Condition box, select not equals.
In the Value box, type 0 (0x0).
Click Add to List, and then click Close.
In the Copy of Remove Properties dialog box, on the General tab, in the Name box, rename Copy of Remove to Remove Failed.
Reference
Processing Rules that Generate Events and Alerts
This section lists the processing rule groups and event processing rules within the Windows Media Services Management Pack. These are found in the MOM console tree at the following location:
Processing Rule Groups \ Microsoft Windows Media Services \ Windows Media Services 9 Series
Processing Rule Group: Cache Events
The Cache Events processing rule group contains processing rules for events that are invoked by activity related to caching content in a Windows Media Services 9 Series cache/proxy system.
Table 1. Processing Rules in the Cache Events Rule Group
Rule |
Default Alert Severity |
|---|---|
Download Complete |
Information Alert Disabled |
Download Start |
Information Alert Disabled |
Hit |
Information Alert Disabled |
Miss |
Information Alert Disabled |
Prestuff Complete |
Information Alert Disabled |
Redirect |
Information Alert Disabled |
Redirect to Proxy |
Information Alert Disabled |
Processing Rule Group: Client Events
The Client Events processing rule group contains processing rules for events that are invoked when a client either connects to or disconnects from a server or changes the state of a presentation.
Table 2. Processing Rules in the Client Events Processing Rule Group
Rule |
Default Alert Severity |
|---|---|
Begin User Session |
Information Alert Disabled |
Connect |
Information Alert Disabled |
Disconnect |
Information Alert Disabled |
End User Session |
Information Alert Disabled |
Play |
Information Alert Disabled |
Stop |
Information Alert Disabled |
Processing Rule Group: Event Log Events
The Event Log Events processing rule group contains processing rules for errors related to hardware, software, and system problems.
Table 3. Processing Rules in the Event Log Event Processing Rule Group
Rule |
Default Alert Severity |
|---|---|
Accept Connection Failed |
Warning |
Active Script Error |
Warning |
Archiving Disk Full |
Information |
Archiving Failed |
Warning |
Archiving Packet Loss Detected |
Warning Alert Disabled |
Archiving Source Interrupt Detected |
Warning |
Cannot Open Wrapper Playlist |
Warning |
Cannot Read Directory Playlist |
Warning |
Cannot Read Playlist |
Warning |
Failed Security Init |
Warning |
Invalid Character Found in Path Template |
Information Alert Disabled |
Logging Default File Used |
Information Alert Disabled |
Logging Directory Created |
Information Alert Disabled |
Logging Open Failed |
Warning |
Logging Open Succeeded |
Information Alert Disabled |
Logging Open Succeeded With No Header |
Warning |
Logging Resume Writing |
Information Alert Disabled |
Logging Stop Writing |
Warning |
Logging Write Failed |
Warning |
Logging Write Succeeded |
Information Alert Disabled |
Multicast Format Not Found |
Warning |
Multicast Sink Stopped |
Warning |
NACKs Warning |
Warning |
Namespace Open Failed |
Warning |
Playlist Player Stream Error |
Warning |
Playlist Player Stream Error Extended |
Warning |
Plug-in Requires Enterprise Server |
Warning |
Port in Use |
Warning |
Proxy Access Denied |
Warning |
Publishing Point Plug-in Error |
Warning |
Publishing Point Plug-in Information |
Information Alert Disabled |
Publishing Point Plug-in Warning |
Warning |
Server Error |
Warning |
Server Information |
Information Alert Disabled |
Server Plug-in Error |
Warning |
Server Plug-in Information |
Information Alert Disabled |
Server Plug-in Warning |
Warning |
Server Warning |
Warning |
Service Handler Installation Failed |
Warning |
Service Request Error |
Information Alert Disabled |
Started |
Information Alert Disabled |
Stop Receiving NACKs |
Warning |
Stopped |
Warning Disabled |
WMI Enable Failed |
Warning |
Wrong OS Version |
Warning |
Processing Rule Group: Limit Changed Events
The Limit Changed Events processing rule group contains processing rules for events that are invoked when server or publishing point property limits are modified.
Table 4. Processing Rules in the Limit Changed Events Processing Rule Group
Rule |
Default Value |
|---|---|
CPU Utilization During Connection |
Information Alert Disabled |
Connected Players |
Information Alert Disabled |
Connection Rate |
Information Alert Disabled |
Diagnostic Events |
Information Alert Disabled |
Distribution Bandwidth |
Information Alert Disabled |
Distribution Connection Bandwidth |
Information Alert Disabled |
Distribution Connections |
Information Alert Disabled |
FEC Packet Span |
Information Alert Disabled |
Incoming Bandwidth |
Information Alert Disabled |
Player Acknowledgement Timeout |
Information Alert Disabled |
Player Bandwidth |
Information Alert Disabled |
Player Cache Delivery Rate |
Information Alert Disabled |
Player Connection Bandwidth |
Information Alert Disabled |
Player Inactivity Timeout |
Information Alert Disabled |
Processing Rule Group: Limit Hit Events
The Limit Hit Events processing rule group contains processing rules for events that are invoked when server or publishing point limits are reached.
Table 5. Processing Rules in the Limit Hit Events Processing Rule Group
Rule |
Default Alert Severity |
|---|---|
CPU Utilization During Connection |
Warning |
Connected Players |
Warning |
Connection Rate |
Warning |
Distribution Bandwidth |
Warning |
Distribution Connection Bandwidth |
Warning |
Distribution Connections |
Warning |
Incoming Bandwidth |
Warning |
Player Acknowledgement Timeout |
Warning |
Player Bandwidth |
Warning |
Player Connection Bandwidth |
Warning |
Player Inactivity Timeout |
Warning |
Processing Rule Group: Performance Counters
The Performance Counters processing rule group contains processing rules that collect performance data for monitoring server performance.
Table 6. Processing Rules in the Performance Counters Processing Rule Group
Rule |
Default Value |
|---|---|
Current Cache Downloads |
Enabled |
Current Connected Players |
Enabled |
Current Connection Queue Length |
Enabled |
Current Connection Rate |
Enabled |
Current File Read Rate (Kbps) |
Enabled |
Current Incoming Bandwidth (Kbps) |
Enabled |
Current Late Read Rate |
Enabled |
Current Late Send Rate |
Enabled |
Current Outgoing Distribution Allocated Bandwidth (Kbps) |
Enabled |
Current Outgoing Distribution Connections |
Enabled |
Current Outgoing Distribution Send Rate (Kbps) |
Enabled |
Current Player Allocated Bandwidth (Kbps) |
Enabled |
Current Player Send Rate (Kbps) |
Enabled |
Current Stream Error Rate |
Enabled |
Current Streaming HTTP Players |
Enabled |
Current Streaming MMS Players |
Enabled |
Current Streaming Players |
Enabled |
Current Streaming RTSP Players |
Enabled |
Current UDP Resend Requests Rate |
Enabled |
Current UDP Resends Sent Rate |
Enabled |
Peak Connected Players |
Enabled |
Peak Outgoing Distribution Allocated Bandwidth (Kbps) |
Enabled |
Peak Outgoing Distribution Connections |
Enabled |
Peak Outgoing Distribution Send Rate (Kbps) |
Enabled |
Peak Player Allocated Bandwidth (Kbps) |
Enabled |
Peak Player Send Rate (Kbps) |
Enabled |
Peak Streaming Players |
Enabled |
Total Advertisements |
Enabled |
Total Connected Players |
Enabled |
Total Late Reads |
Enabled |
Total Late Sends |
Enabled |
Total Outgoing Distribution Bytes Sent |
Enabled |
Total Outgoing Distribution Connections |
Enabled |
Total Player Bytes Sent |
Enabled |
Total Server Uptime |
Enabled |
Total Stream Denials |
Enabled |
Total Stream Errors |
Enabled |
Total Stream Terminations |
Enabled |
Total Streaming Players |
Enabled |
Total UDP Resend Requests |
Enabled |
Total UDP Resends Sent |
Disabled |
Processing Rule Group: Playlist Events
The Playlist Events processing rule group contains processing rules that monitor events invoked by activity related to broadcast playlists.
Table 7. Processing Rules in the Playlist Events Processing Rule Group
Rule |
Default Alert Severity |
|---|---|
Cue |
Information Alert Disabled |
Failover |
Information Alert Disabled |
Modify |
Information Alert Disabled |
Switch |
Information Alert Disabled |
Processing Rule Group: Plug-in Events
The Plug-in Events processing rule group contains processing rules that monitor events invoked by activity related to server or publishing point plug-ins.
Table 8. Processing Rules in the Plug-in Events Processing Rule Group
Rule |
Default Alert Severity |
|---|---|
Add |
Information Alert Disabled |
Disable |
Information Alert Disabled |
Enable |
Information Alert Disabled |
Error |
Error Alert Disabled |
Load Type Change |
Information Alert Disabled |
Name Change |
Information Alert Disabled |
Property Change |
Information Alert Disabled |
Remove |
Information Alert Disabled |
Selection Order Change |
Information Alert Disabled |
Processing Rule Group: Publishing Point Events
The Publishing Point Events processing rule group contains processing rules that monitor events invoked when the status of a publishing point changes or when a change is made to publishing point plug-in properties.
Table 9. Processing Rules in the Publishing Point Events Processing Rule Group
Rule |
Default Alert Severity |
|---|---|
Add |
Information Alert Disabled |
Allow Client to Start and Stop Change |
Information Alert Disabled |
Allow Clients to Connect Change |
Information Alert Disabled |
Allow Content Caching Change |
Information Alert Disabled |
Allow Player Side Disk Caching Change |
Information Alert Disabled |
Buffer Setting Change |
Information Alert Disabled |
Critical Error |
Critical Error |
Critical Publishing Point Stopped |
Warning |
Distribution Password Change |
Information Alert Disabled |
Distribution User Name Change |
Information Alert Disabled |
Enable Client Wildcard Directory Access Change |
Information Alert Disabled |
Enable FEC Change |
Information Alert Disabled |
Enable Wrapper Path Change |
Information Alert Disabled |
Name Change |
Information Alert Disabled |
Path Change |
Information Alert Disabled |
Property Change |
Information Alert Disabled |
Remove |
Information Alert Disabled |
Start |
Information Alert Disabled |
Start Archive |
Information Alert Disabled |
Start Without Data |
Information Alert Disabled |
Stop |
Information Alert Disabled |
Stop Archive |
Information Alert Disabled |
Stream End |
Information Alert Disabled |
Wrapper Path Change |
Information Alert Disabled |
Processing Rule Group: Server Events
The Server Events processing rule group contains processing rules that monitor events invoked when the status of a server changes or when a change is made to server properties.
Table 10. Processing Rules in the Server Events Processing Rule Group
Rule |
Default Alert Severity |
|---|---|
Allow Clients to Connect Change |
Information Alert Disabled |
Critical Error |
Critical Error |
Download Complete |
Information Alert Disabled |
Download Start |
Information Alert Disabled |
Offline |
Information Alert Disabled |
Online |
Information Alert Disabled |
Plug-in Load Type Change |
Information Alert Disabled |
Property Change |
Information Alert Disabled |
Reverse Proxy Mode Change |
Information Alert Disabled |
Processing Rule Group: Threshold Performance Counters
The Threshold Performance Counters processing rule group contains the threshold rules that monitor the basic health of the Windows Media server and the Windows Media Services process (WMServer.exe). The primary function of these rules is to alert the administrator that resource usage is approaching server hardware limits or server property values specified in Windows Media Services 9 Series. When a Windows NT performance counter value exceeds a defined threshold, an alert is generated for server administrators to react accordingly.
Table 11. Processing Rules in the Threshold Performance Counters Processing Rule Group
Rule |
Default Alert Severity |
|---|---|
CPU Usage is High |
Warning |
Current Connected Players is High |
Warning |
Current Connection Queue Length is High |
Warning |
Current Incoming Bandwidth is High |
Warning |
Current Late Read Rate is High |
Warning |
Current Outgoing Distribution Allocated Bandwidth is High |
Warning |
Current Outgoing Distribution Send Rate is Reaching Network Bandwidth |
Warning |
Current Player Send Rate is High |
Warning |
Current Player Send Rate is Reaching Network Bandwidth |
Warning |
Current UDP Resend Requests Rate is High |
Warning |
Current UDP Resends Sent Rate is High |
Warning |
Memory Usage is High |
Warning |
Reports
The Windows Media Services Management Pack does not include reports.
Scripts
The Windows Media Services Management Pack does not include scripts.
Computer Groups
The Windows Media Services Management Pack includes the following computer group:
Microsoft Windows Media Services 9 Series Server
Finds computers with Microsoft Windows Media Services 9 Series installed.
Default Notification Group
The default notification group for processing rule responses the Windows Media Services Management Pack is Windows Media Services Administrators. The default notification group does not include operators. For information about adding operators to this notification group, see Microsoft Operations Manager Online Help.
Acknowledgements
Program Manager: Chris Knowlton
Developer: Charles Huang
Tester: David Chen
Writer: David M. Nelson
Technical Reviewers: Windows Media Services Management Pack Team
Editor: Terrence Dorsey