Windows Media Services Management
Pack Guide for Operations Manager 2007
Raphael Burri
http://rburri.wordpress.com
raburri@bluewin.ch
February, 2009
Revision History
Release Date
Changes
January, 2008
Original release of this guide
March, 2008
Update to 1.0.1.57 (SP1 compatibility)
February, 2009
Update to 1.0.2.10 (Windows Media Services
2008 compatibility)
Contents
1
Windows Media Services Management Pack ................................................................. 4
2
Getting Started .................................................................................................................. 5
2.1
Before importing the Management Pack .......................................................................... 5
2.2
Other Requirements ......................................................................................................... 6
2.3
Customizing the management pack ................................................................................. 6
3
Elements of the Windows Media Services management pack ..................................... 7
3.1
Object Type Model ........................................................................................................... 7
3.2
Object Discovery .............................................................................................................. 8
3.2.1
3.3
Objects Discovered ....................................................................................................... 8
Monitors ............................................................................................................................ 9
3.3.1
Windows Media Services 9 Server Role monitors ........................................................ 9
3.3.1.1
Allow Client Connection Status ................................................................................ 10
3.3.1.2
Error Status .............................................................................................................. 10
3.3.1.3
Publishing Point Availability ..................................................................................... 11
3.3.1.4
Windows Service ...................................................................................................... 11
3.3.1.5
Data Source Bottleneck ........................................................................................... 11
3.3.1.6
Memory Usage ......................................................................................................... 12
3.3.1.7
Stream Data Packet Discards .................................................................................. 12
3.3.1.8
Streaming Bandwidth Bottleneck ............................................................................. 13
3.3.2
Windows Media Services 9 Publishing Point monitors ............................................... 14
3.3.2.1
Allow Client Connection Status ................................................................................ 14
3.3.2.2
Broadcast Status ...................................................................................................... 15
3.3.2.3
Error Status .............................................................................................................. 15
3.3.2.4
Source Available (disabled by default) ..................................................................... 16
3.4
Rules .............................................................................................................................. 17
3.4.1
Performance Data Collection Rules ............................................................................ 17
3.4.2
Delete old WMS log files ............................................................................................. 18
3.5
Tasks .............................................................................................................................. 19
3.5.1
Windows Media Services 9 Role Tasks ...................................................................... 19
3.5.2
Windows Media Services 9 Publishing Point Tasks ................................................... 20
3.6
Reports ........................................................................................................................... 21
3.6.1.1
4
WMS Performance Information Reports .................................................................. 22
Using the Management Pack ......................................................................................... 23
4.1
Console Views ................................................................................................................ 23
4.2
Configuring Overrides .................................................................................................... 24
1
Windows Media Services Management Pack
The Windows Media Services management pack monitors the health of Microsoft Windows Media Services 9
(WMS), installed on Windows Server 2003 and Microsoft Windows Media Services 2008 on Windows Server
2008.
It provides discovery, availability and performance monitors, performance collection rules, performance
reports and WMS related tasks.
It is important to understand that the Windows Media Services management pack has been developed
entirely for Operations Manager 2007. It is not a port of the MOM 2005 pack available from Microsoft. Nor
has functionality of the latter been integrated.
The management pack has been tested against Operations Manager 2007 SP1.
A detailed discussion about how to tune Windows Media Services 9 is published in the White Paper
‘Optimizing Windows Media Services’ that can be downloaded from here:
http://www.microsoft.com/windows/windowsmedia/howto/articles/optimize_web.aspx
Windows Media Services Management Pack Guide
b
4/24
2
Getting Started
2.1
Before importing the Management Pack
The management pack consists of a single file. Use the Import Management Pack function from the
Administration pane of the Operations Console to import the management pack. Make sure you have all the
management pack, the WMS management pack depends on, imported as well. The import wizard will let you
know if some are missing.
All dependencies are defined against management packs provided by Microsoft. If you can’t find them on
your Operations Manager installation media, you should be able to download them from here:
http://go.microsoft.com/fwlink/?LinkId=82105
The following table lists the management pack files and the dependencies (in grey)
Management Pack File
Version
Vendor
Custom.WMS.x.mp
1.0.2.10
Custom
System.ApplicationLog.Library.mp
6.0.5000.0
Microsoft
System.Health.Library.mp
6.0.5000.0
Microsoft
System.Library.mp
6.0.5000.0
Microsoft
System.Performance.Library.mp
6.0.5000.15
Microsoft
Microsoft.SystemCenter.DataWarehouse.Library.mp
6.0.5000.26
Microsoft
Microsoft.SystemCenter.DataWarehouse.Report.Library.mp
6.0.5000.0
Microsoft
Microsoft.SystemCenter.InstanceGroup.Library.mp
6.0.5000.0
Microsoft
Microsoft.SystemCenter.Library.mp
6.0.5000.0
Microsoft
Microsoft.Windows.Library.mp
6.0.5000.0
Microsoft
Microsoft.Windows.Server.Library.mp
6.0.5000.25
Microsoft
Microsoft.Windows.Server.2003.mp
6.0.5000.0
Microsoft
Microsoft.Windows.Server.2008.mp
6.0.6278.22
Microsoft
Windows Media Services Management Pack Guide
b
5/24
2.2
Other Requirements
The Windows Media Services management pack makes use of the WMS WMI Event handler to monitor the
WMS’ health. Check if it is enabled on your WMS servers. Use the Windows Media Services MMC snap-in,
select a WMS server and choose the Properties tab. Then select Event notification.
2.3
Customizing the management pack
The Windows Media Services management pack is sealed. Changes to it are not possible. Using overrides
almost all aspects of it can be customized. When doing so it is recommended that you store your overrides
for the Windows Media Services management pack in a specifically for this purpose created one. The
‘Default Management Pack’ should not be used.
Doing so simplifies exporting, reporting on or altering your changes. Furthermore the ‘Default Management
Pack’ will not be made dependant on the Windows Media Services management pack. Removing the
Windows Media Services management pack will be possible.
Windows Media Services Management Pack Guide
b
6/24
3
Elements of the Windows Media Services management pack
3.1
Object Type Model
The following diagram shows the type model of the Windows Media Services management pack. Inheritance
is shown vertically while Hosting and Health Roll up are drawn horizontally. Blue object types are part of the
management pack, while green ones already exist. They are defined by the management pack’s
dependencies.
Graphic 1
Windows Media Services Management Pack Guide
b
7/24
3.2
Object Discovery
3.2.1
Objects Discovered
The Windows Media Services management pack discovers objects of the following types:
Object Type
Automatically Discovery Rule
Attributes
Windows Media
Services 9 Server Role
Yes

Name

Install Directory

Default Path

Log Directory

Version

Name

Install Directory

Default Path

Log Directory

Version
Windows Media Server 9
Publishing Point
Discovery

PP Name

PP Path

PP Type
Windows Media
Services 9 Server
Reverse Proxy Role
Yes
Custom Windows Media
Services 9 Role
Discovery and Custom
Windows Media Services
9 Role Details Discovery
Custom Windows Media
Services 9 Role
Discovery and Custom
Windows Media Services
9 Role Details Discovery
Windows Media
Services 9 Publishing
Point (Broadcast)
Yes
Windows Media
Services 9 Publishing
Point (Cache/Proxy)
Yes (if the
WMS Server
is a Reverse
Proxy
Windows Media Server 9
Publishing Point
Discovery

PP Name

PP Path

PP Type
Windows Media
Services 9 Publishing
Point (On Demand)
Yes
Windows Media Server 9
Publishing Point
Discovery

PP Name

PP Path

PP Type
Windows Media Services Management Pack Guide
b
8/24
3.3
Monitors
The management pack defines a series of monitors that keep track of the health of the objects discovered
and generate alerts. These are targeted against different object types.
3.3.1
Windows Media Services 9 Server Role monitors
A total of eight monitors are targeted against the Windows Media Services 9 Server Role. Where feasible,
recovery tasks are included to support troubleshooting an erroneous state.
Simplified Health Explorer screen shot:
Windows Media Services Management Pack Guide
b
9/24
3.3.1.1 Allow Client Connection Status
Windows Media Services can be set to deny new clients to connect to the server. Before performing
maintenance, this can be used to drain out connections to the server. Under normal circumstances a WMS
server denying new connections is considered a warning condition.
Severity
Alert Name
Possible
Diagnostic
Overrides
and Recovery
Implementation Details
Tasks
Warning
Windows Media Server
does not allow client
connections
Only
standard
Allow new
client
connections
checking COM object
WMSServer.server
every minute
3.3.1.2 Error Status
Windows Media Services may report an error state condition. This monitor checks if that is the case.
Severity
Alert Name
Possible
Diagnostic
Overrides
and Recovery
Implementation Details
Tasks
Warning
Windows Media Server
has a critical error
Only
standard
none
checking COM object
WMSServer.server
every minute
Windows Media Services Management Pack Guide
b
10/24
3.3.1.3 Publishing Point Availability
This is a Dependency Rollup monitor, mapping the health of individual Publishing Points hosted by this
server to the WMS server role.
Rollup Policy
Alert settings
Worst of any member
do not generate an alert
3.3.1.4 Windows Service
Checks if the WMS windows service (WMServer) is running.
Severity Alert Name
Possible
Diagnostic
Overrides
and Recovery
Implementation Details
Tasks
Critical
Windows Media Server
Service stopped
Only standard
Start
windows
service
Microsoft.Windows.Check
NTServiceStateMonitorTy
pe
3.3.1.5 Data Source Bottleneck
Threshold type monitor targeting at the performance counter Windows Media Services\Current Late Read
Rate. This counter should not be higher than zero over an extended period of time. If it does it indicates that
WMS server is not able to read from its data sources fast enough.
Severity
Alert Name
Possible
Diagnostic
Overrides
and
Implementation Details
Recovery
Tasks
Warning
Windows Media Server
data source bottleneck
Only standard
Windows Media Services Management Pack Guide
none
Consecutive Samples over
Threshold monitor

Sample Interval: 5 min

Threshold: > 0

N° of samples: 3
b
11/24
3.3.1.6 Memory Usage
Combined performance counter threshold. It looks at how much of the physical memory of the server is used
by the WMS service. If the WMServer process uses too much, the overall performance of the WMS server will
suffer. If the WMS server is mainly used for publishing broadcast media, the threshold should be set to 70%.
For an on-demand scenario, WMServer should not use more than 50% of the server’s physical memory.
Severity
Alert Name
Possible
Diagnostic
Overrides
and
Implementation Details
Recovery
Tasks
Warning
Windows Media Server
doesn't have enough
free memory
Standard
none
Threshold
Consecutive Samples over
Threshold monitor
Frequency

Sample Interval: 5 min

Threshold: >= 50

N° of samples: 3
The % value is calculated by using
a WMI query for the total physical
memory installed and by querying
Process\Private Bytes\WMServer
3.3.1.7 Stream Data Packet Discards
Threshold type monitor targeting at the performance counter ‘Windows Media Services\Current Stream Error
Rate’. If this value is higher than zero for an extended period of time, it indicates, that the WMS server is
unable to keep up with the demand. It is likely to suffer from late reads as well.
Severity
Alert Name
Possible
Diagnostic
Overrides
and
Implementation Details
Recovery
Tasks
Warning
Windows Media Server
is dropping packets
Only standard
Windows Media Services Management Pack Guide
none
Consecutive Samples over
Threshold monitor

Sample Interval: 5 min

Threshold: > 0

N° of samples: 2
b
12/24
3.3.1.8 Streaming Bandwidth Bottleneck
Threshold type monitor which compares the two performance counters ‘Windows Media Services\Current
Player Allocated Bandwidth (kbps)’ and ‘Windows Media Services\Current Player Send Rate (kbps)’. If the
send rate is dropping below the allocated bandwidth, WMS is unable to service all clients. Usually this
indicates an outbound network bottleneck.
Severity
Alert Name
Possible
Diagnostic
Overrides
and
Implementation Details
Recovery
Tasks
Warning
Windows Media Server
is failing to stream data
fast enough
Only standard
Windows Media Services Management Pack Guide
none
Consecutive Samples over
Threshold monitor

Sample Interval: 5 min

Threshold: > 0

N° of samples: 3
b
13/24
3.3.2
Windows Media Services 9 Publishing Point monitors
Windows Media Services knows different types of Publishing Points. Since their monitoring requirements are
slightly different, three sub object types are defined in management pack. The monitors described here are
targeted at the relevant object types.
Simplified screen shot of the Health Explorer:
3.3.2.1 Allow Client Connection Status
As the WMS server on the whole, a single WMS Publishing Point can set to deny new clients to. Under
normal circumstances a WMS Publishing Point denying connections is considered a warning condition. The
monitor is targeted at the generic object type ‘Windows Media Services 9 Publishing Point’. Hence it is
active for all Publishing Points, regardless of their type.
Severity
Alert Name
Possible
Diagnostic
Overrides
and Recovery
Implementation Details
Tasks
Warning
Windows Media Services
Publishing Point does not
allow client connections
Only
standard
Windows Media Services Management Pack Guide
Allow new
client
connections
checking COM object
WMSServer.server
every 2 minutes
b
14/24
3.3.2.2 Broadcast Status
Broadcast type WMS Publishing Points can be stopped. This is considered a warning condition. The monitor
is targeted only at ‘Windows Media Services 9 Publishing Point (Broadcast)’ object types only.
Severity
Alert Name
Possible
Diagnostic
Implementation Details
Overrides
and Recovery
Tasks
Warning
Windows Media Services
Publishing Point stopped
Only
standard
Start
Broadcast
Publishing
Point
checking COM object
WMSServer.server
every 2 minutes
3.3.2.3 Error Status
A WMS Publishing Point may report an error state. This monitor checks if that is the case. The monitor is
targeted at the generic object type ‘Windows Media Services 9 Publishing Point’. Hence it is active for all
Publishing Points, regardless of their type.
Severity
Alert Name
Possible
Diagnostic
Overrides
and Recovery
Implementation Details
Tasks
Warning
Windows Media Server
has a critical error
Only
standard
Windows Media Services Management Pack Guide
none
checking COM object
WMSServer.server every 2
minutes
b
15/24
3.3.2.4 Source Available (disabled by default)
The monitor is targeted only at ‘Windows Media Services 9 Publishing Point (On Demand)’. It checks the
WMS server’s log file for 404 (file not found) events in the context of the Publishing Point.
This monitor is not enabled by default. Consider it as an example for how to write a monitor which reacts on
events in the WMS server’s log file. If required, it may be enabled for the Publishing Points it is required for
by Overrides.
Severity
Alert Name
Possible
Diagnostic
Overrides
and Recovery
Implementation Details
Tasks
Warning
Windows Media Server
(disabled) Publishing Point source
is not available
Only
standard
Windows Media Services Management Pack Guide
none
Generic CSV log reader

Directory: WMS log
directory according to
discovery

Pattern: WMS_*.log

Separator: “ “ (white space)
b
16/24
3.4
Rules
The Rules defined for the management pack collect performance counters to be used by reports or are used
internally to trigger the monitors described above. The following description only lists the performance
counter collection rules. All of them are targeted at ‘Windows Media Services 9 Publishing Point’ object
type. Currently no performance data is collected on individual Publishing Points.
3.4.1
Performance Data Collection Rules
Rule Name
Performance Counter
Implementation Details
Collect Windows Media
Services\Current Player
Send Rate (Kbps)
Windows Media

Interval: 5 min
Services\Current Player

Optimization Tolerance: 15 %
Collect Process\Private
Bytes % of Physical
Memory\WMServer
Windows Media

Interval: 30 min
Services\Private Bytes % of
The % value is calculated by using a WMI
query for the total physical memory installed
and by querying Process\Private
Send Rate (Kbps)
Physical Memory\WMServer
Bytes\WMServer
Collect Windows Media
Services\Current
Streaming Players
Windows Media Services\

Interval: 5 min
Current Connected Players

Optimization Tolerance: 15 %
Collect Redirector\Bytes
Received/sec
Redirector\Bytes

Interval: 5 min
Received/sec

Optimization Tolerance: 15 %
Collect Windows Media
Services\Current Player
Allocated Bandwidth
(Kbps)
Windows Media Services\

Interval: 5 min
Current Player Allocated

Optimization Tolerance: 15 %
Collect LogicalDisk\Disk
Read Bytes/sec\_Total
LogicalDisk\ Disk Read

Interval: 5 min
Bytes/sec\ _Total

Optimization Tolerance: 15 %
Collect Process\Private
Bytes\WMServer
Process\Private

Interval: 5 min
Bytes\WMServer

Optimization Tolerance: 15 %
Collect Windows Media
Services\Current Late
Read Rate
Windows Media

Interval: 5 min
Services\Current Late Read

Optimization Tolerance: 15 %
Bandwidth (Kbps)
Rate
Windows Media Services Management Pack Guide
b
17/24
Rule Name
Performance Counter
Implementation Details
Collect Windows Media
Services\Current Player
Overallocated Bandwidth
%
Windows Media

Services\Current Player
compares the two performance counters
Overallocated Bandwidth %
Windows Media Services\Current Player
Interval: 5 min
Allocated Bandwidth (kbps)
and Windows
Media Services\Current Player Send Rate
(kbps)
Collect Windows Media
Services\Current File
Read Rate (Kbps)
Windows Media Services\

Interval: 5 min
Current File Read Rate

Optimization Tolerance: 15 %
Collect Windows Media
Services\Current Late
Send Rate
Windows Media Services\

Interval: 5 min
Current Late Send Rate

Optimization Tolerance: 15 %
Collect Windows Media
Services\Current Stream
Error Rate
Windows Media Services\

Interval: 5 min
Current Stream Error Rate

Optimization Tolerance: 15 %
3.4.2
(Kbps)
Delete old WMS log files
The rule ‘Delete old WMS log files’ deletes files found in the log directory of the Windows Media
Server. It is disabled by default. If required, override the rule for the servers you require it running.
Rule Name
Default Settings
Overrides
Delete old WMS log files

Disabled

Enable

Runs every night

File age

Deletes log files (*.log) older than 100
days

Execution time
Windows Media Services Management Pack Guide
b
18/24
3.5
Tasks
Tasks are targeted at object types. Whenever an object of a specific type is selected within the Operations
Manager GUI, the relevant tasks can be executed against that specific object.
Some of these tasks are defined as recoveries. They are available in the context of an alert, the Health
Explorer or the knowledge of a monitor.
3.5.1
Windows Media Services 9 Role Tasks
Four tasks are targeted at WMS Server roles.
Name
Parameters Implementation Details
Allow new client
connections
None
script COM object ‘WMSServer.server’
Deny new client
connections
None
script COM object ‘WMSServer.server’
Start windows service
None
Net start command
Stop windows service
None
Net stop command
Windows Media Services Management Pack Guide
b
19/24
3.5.2
Windows Media Services 9 Publishing Point Tasks
As with the monitors, the tasks targeted at the Publishing Points are also specific to their type.
‘Allow / Deny new client connections’ are available for all publishing point object types.
‘Start / Stop Broadcast Publishing Point’ is only possible for ‘Broadcast’ types.
The built in Cache and Proxy types do not have any tasks configured.
Name
Parameters Implementation Details
Allow new client
connections
None
script COM object ‘WMSServer.server’
Deny new client
connections
None
script COM object ‘WMSServer.server’
Start Broadcast
Publishing Point
None
script COM object ‘WMSServer.server’
Stop Broadcast
Publishing Point
None
script COM object ‘WMSServer.server’
Windows Media Services Management Pack Guide
b
20/24
3.6
Reports
Three reports are included with the Windows Media Services management pack. To successfully execute
them, they must be targeted against ‘Windows Media Services Role’ or ‘Windows Media Services Server
Group’.
Additionally Operations Manager’s standard reports can also be used. Specifically ‘ Alerts’, ‘Availability’
and ‘Health’ will contain valuable information.
Windows Media Services Management Pack Guide
b
21/24
3.6.1.1 WMS Performance Information Reports
Report Name
Description
WMS Bandwidth Performance Analysis
Displays a chart with the following performance items:
WMS Data Source Performance Analysis
WMS Memory Performance Analysis
Windows Media Services Management Pack Guide

Windows Media Services\Current Streaming
Players

Windows Media Services\Current Late Send Rate

Windows Media Services\Current Player Allocated
Bandwidth (kbps)

Windows Media Services\Current Player Send
Rate (kbps)

Windows Media Services\Current Player Over
allocated Bandwidth %
Displays a chart with the following performance items.

Windows Media Services\Current Streaming
Players

Windows Media Services\Current Late Read Rate

Logical Disk\ Disk Read Bytes/sec\_Total

Redirector\Bytes Received/sec
Displays a chart with the following performance items.

Process\Private Bytes % of Physical
Memory\WMServer

Process\Private Bytes\WMServer
b
22/24
4
Using the Management Pack
After importing the management pack, Operations Manager will automatically discover any instances of
Windows Media Services installed. Most monitoring and data collection is going to work automatically.
4.1
Console Views
In Operations Manager’s Console, the monitoring pane contains the following views under ‘ Windows Media
Services’.

Alert View

Performance View

State View
As these are rather basic, consider using ‘My Workspace‘ or adding views to a custom management pack to
get a more customized view especially if you are using a large amount of WMS servers.
Using the ‘Distributed Application Designer’ you can integrate the WMS objects into your custom diagram
view. When adding components to your application, refer to the diagram on page 7 to choose the correct
object types.
Windows Media Services Management Pack Guide
b
23/24
4.2
Configuring Overrides
Overrides are particularly useful to change the behavior of the management pack’s monitors. The following
table contains scenarios and lists which monitors would have to be overridden.
Overrides can be configured for individual servers, groups or all objects of a type.
Note that it is recommended to use a specifically created management pack for your overrides instead of
saving them into ‘Default Management Pack’.
Scenario
Overrides to configure
WMS is mainly used for Change the default threshold of the monitor ‘Memory Usage’ targeted at
broadcast type
‘Windows Media Services 9 Server Role’ from 50% to 70%
publishing point
Exclude publishing
points from monitoring
Disable all or individual of the following monitors:
‘Error Status’ at ‘Windows Media Services 9 Publishing Point’
‘Allow Client Connection Status (Broadcast)’ at ‘Windows Media
Services 9 Publishing Point (Broadcast)’
‘Broadcast Status’ at ‘Windows Media Services 9 Publishing Point
(Broadcast)’
‘Allow Client Connection Status (On Demand)’ at ‘Windows Media
Services 9 Publishing Point (On Demand)’
or disable publishing point discovery rule
‘Windows Media Services 9 Publishing Point Discovery’ at ‘Windows
Media Services 9 Server Role’
Windows Media Services Management Pack Guide
b
24/24