1. Rob Stevens Microsoft robsteve@microsoft.com
6/26/2018 4:57 PM
MOM 2005 Management Packs
Rob Stevens
Microsoft
© Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

2. Agenda Introduction to management packs in MOM 2005
MOM 2005 Management Pack Features
State Monitoring and Service Discovery
Service Monitoring
Automation and Tasks
Diagram Authoring
Building custom management packs
Extending and customizing Microsoft management packs
Resources

3. MOM 2005 Delivers Event and performance management Enterprise ready
6/26/2018 4:57 PM
MOM 2005 Delivers
Event and performance management
Enterprise event collection
Rules-based filtering and consolidation
Proactive alerting/action response
Enterprise ready
Central console
Full redundancy
Extensible
MCF
Automation
Scripts
Tasks
Diagnostics
Reporting
Web-based management reports
Scheduled Publishing
Applications/Role Monitoring
Health Model
Rules libraries
Built-in knowledge-base
© Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

4. What can management packs provide?
Monitor line of business applications or business process
Monitor the state of your business
Monitor third party applications and components
Understand how my application are actually being used

5. What's new with MPs with MOM 2005?
State Monitoring
Topology
SQL Server Reporting Services Reports
Tasks
Improved Knowledge

6. Application Stack
Microsoft provides Management Packs for Windows and Microsoft applications
Management Packs for the rest of the enterprise stack: Management Pack Ecosystem
All Management Packs produced by application owners/experts
Microsoft Applications
3rd Party Applications
Extensions: Backup, Anti Virus, etc.
Microsoft Applications
Windows
Server Hardware / Storage
Network

7. Management Pack Ecosystem
6/26/2018 4:57 PM
Management Pack Ecosystem
Microsoft Applications
Application Center 2000
BizTalk Server 2002 Enterprise Edition
Commerce Server 2000
Exchange Server 2003 / 2000 / 5.5
Host Integration Server 2000
Identity Integration Server 2003
Internet Security and Acceleration Server 2000
Live Communications Server 2003 (LCS)
Microsoft Operations Manager 2000
Project Server 2003
Proxy Server 2.0
SharePoint Portal Server 2003
Site Server 3.0
SNA Server 4.0
SQL Server 2000 / 7.0
Systems Management Server 2003 / 2.0
Windows
Windows Operating Systems
Active Directory
DNS service
IIS versions 4.0 / 5.0 / 6.0
Windows System Resource Manager
Server clusters
Component Services (formerly MTS 2.0)
Message Queuing (MSMQ)
Distributed Transaction Coordinator (MS DTC)
.NET Framework
Windows Internet Name Service (WINS)
Windows SharePoint Services
Network Load Balancing
Routing and Remote Access service
Terminal Services
File Replication Services
Advanced Deployment Services
Group Policy
(As of June ‘04)
Third Party Management Packs
Applications
Citrix: MetaFrame Windows XP
NetIQ XMPs: Oracle, Domino, Antivirus, Security
Active Directory
Full Armor Fazam Auditing NetPro Directory Analyzer
Hardware
HP Insight Manager
Dell OpenManage
Platforms
eXc Software: IBM AS400, IBM z/OS, Unix, Linux
Metilinx: Linux/Unix
Devices
JalaSOFT: Cisco Routers and Switches
© Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

8. MOM 2005 Management Packs Management Packs on the MOM 2005 CD
Exchange 2000 and 2003 Server
Internet Information Services
MOM 2005 and MOM 2000 Transition
Security (MBSA)
SQL Server 2000
Windows Active Directory
Windows Server Cluster
Windows DNS
Windows Server (2000, 2003, NT4)
Tier 2 Management Packs
Windows Update Services
Virtual Server 2005
Web Services
Application Center 2000
Terminal Services
DHCP
Remote File Systems
Print Server
DFS
FRS
LCS
RRAS

9. MOM 2000 Management Packs And MOM 2005
MOM 2000 Management Packs run fine on MOM 2005 servers  Investment in MOM 2000 Management Packs preserved
Exceptions
MOM 2000 Access-based reports do not migrate forward to MOM 2005
Some scripts use objects that were deprecated in MOM 2000 and are gone in MOM 2005

10. Management Packs Management Pack imported via MOM Server
6/26/2018 4:57 PM
Management Packs
Management Pack imported via MOM Server
Discovery finds computers in need of a given Management Pack
MOM deploys appropriate Management Packs
No need to touch managed nodes to install Management Packs
Rules: Implement all MOM monitoring behavior
Watch for indicators of problems
Verify key elements of functionality
Management Packs provide a definition of server health
A Management Pack provides a definition of server health. Variations from this definition are indicators of conditions that need intervention to avoid a potential outage or to recover from an incident. This is a different approach than has been taken my management tools in the past which tend to provide a plethora of scripts from which the user can choose to employ, leaving the user unclear which are really “important” to deploy. A management pack is designed with this question already answered -- this hard investigative work has been done for you by the people who develop the application itself.
Management Pack do this using a variety of elements.
The most fundamental is that of Rules which are MOM’s basic unit of instruction. Rules can be as simple as detecting the occurrence or absence of a given event, whether a performance count has exceeded a threshold, or as complex as running a series of scripts to perform synthetic transactions to verify server response times and availabilities.
These rules create Alerts which is how MOM will call attention to detected conditions that require intervention on the part of the administrator to prevent potential outages or quickly address issues affecting server performance or availability. The alerts are prioritized to assist operators getting attention for issues in order of the criticality of the problem.
These alerts contain rich Knowledge to direct how administrators can quickly address the detected problems. This is a huge aspect of Management Packs. While it is great to detect conditions and alert administrators of problems, knowledge takes this to the next level by empowering front line and lower level operators or administrators address more issues quickly without having to resort to costly escalation to the next level of support.
State monitoring is a new features in server and application monitoring products. It provides a real time view of the condition of my line-of-business servers and applications, verifying that the critical services are available and that they are providing end users with good performance. This real time feedback offers an additional dimension to help operations staff prioritize issues and provide the highest overall availability and ensure the lowest overall impact when problems occur.
New in MOM 2005 are Tasks which take MOM’s capabilities from observing, detecting and alerting to deep investigation and issue resolution by taking specific diagnostic or management actions. Tasks are initiated on demand by the administrator and can include tasks that run on the Console, Management server or Managed node.
Reports leverage the new MOM 2005 data warehouse and SQL Reporting Services to provide management with the information they need to analyze performance of their data center operations and the services they provide, as well as the service owner with rich information about its usage for capacity planning.
Finally the MOM infrastructure allows Management Packs to automatically identify types of servers (e.g. SQL server, Exchange servers, Domain Controllers etc) and deploy then the corresponding Management Pack without any admin interaction or every having to deploy anything on the managed server.
Additional Information:
Management Packs
Management Packs are a container and distribution vehicle that MOM uses to deploy the configuration information that is required for the monitoring of a system or application.
The Management Pack module consists of a collection of rules, knowledge, and public views that enable the management of a system or application. MOM can collect an array of information from many different sources. By using Management Pack modules, you can specify how MOM collects, handles, and responds to information.
The richness and biggest value in MOM comes from the knowledge of how a system is monitored in the form of a Management Pack, which contains the following types of configuration information to enable this:
List of Rule Groups that are folder for rules.
List of Rules for each Rule Group
List of Provider Instances that Rules refer to
List of Scripts that Rules need to call as a response
List of Registry based Computer Attributes needed for the discovery of the application being monitored
List of Computer Groups whose formula depends on the Computer Attributes specified
List of Computer Group, Rule Group association in which the rule targets are specified
List of Notification Groups that notification responses uses in rules
List of view instances definition that defines how the operation data produced by the management should be viewed
List of Tasks users might need for the management of the application
Service Discovery Class Schema that defines the entities that will be managed and their properties as well as their relationship to other properties
Topology Diagram Definitions that describes how the service discovery data should be viewed as a topology from the application point of view.
Product Knowledge associated with the rules which specify how problems should be corrected, how management pack should be used.
Management Pack formats
Management Packs have three formats:
The first format is a binary file called an AKM file. Management Packs are usually distributed in this format.
The second format is an XML file that describes the contents in human readable form. This format is used to edit and compare Management Packs.
The third format is the format used to store information in the database by importing a Management Pack (in other formats) into the database.
Authoring Management Packs
There are three methods that you can use to author a Management Pack:
First, create the configuration object definitions in the Administrator console and then export these definitions to an AKM file.
Second, create/edit an XML file that describes configuration information. This file is later converted to an AKM file or imported into the MOM database.
Third, programmatically create the Management Pack using a scriptable object model. The results are then saved in any format.
© Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

11. Management Pack Features
6/26/2018 4:57 PM
Management Pack Features
Alerts: Calls attention to critical events that require administrator intervention
Product Knowledge: Provides guidance for administrators to resolve outstanding alerts
Views: Provide targeted drill down details about server health
Performance plots, collections of specific events/alerts, groups of servers , topology, etc.
State Monitoring: At a glance view of the state of my servers and applications by server role
Detail to component level
Tasks: Enable administrators to investigate and repair issues from the MOM console
Context sensitive diagnostics and remediation
Reports: Historical data analytics
Assess operations performance and capacity planning
A Management Pack provides a definition of server health. Variations from this definition are indicators of conditions that need intervention to avoid a potential outage or to recover from an incident. This is a different approach than has been taken my management tools in the past which tend to provide a plethora of scripts from which the user can choose to employ, leaving the user unclear which are really “important” to deploy. A management pack is designed with this question already answered -- this hard investigative work has been done for you by the people who develop the application itself.
Management Pack do this using a variety of elements.
The most fundamental is that of Rules which are MOM’s basic unit of instruction. Rules can be as simple as detecting the occurrence or absence of a given event, whether a performance count has exceeded a threshold, or as complex as running a series of scripts to perform synthetic transactions to verify server response times and availabilities.
These rules create Alerts which is how MOM will call attention to detected conditions that require intervention on the part of the administrator to prevent potential outages or quickly address issues affecting server performance or availability. The alerts are prioritized to assist operators getting attention for issues in order of the criticality of the problem.
These alerts contain rich Knowledge to direct how administrators can quickly address the detected problems. This is a huge aspect of Management Packs. While it is great to detect conditions and alert administrators of problems, knowledge takes this to the next level by empowering front line and lower level operators or administrators address more issues quickly without having to resort to costly escalation to the next level of support.
State monitoring is a new features in server and application monitoring products. It provides a real time view of the condition of my line-of-business servers and applications, verifying that the critical services are available and that they are providing end users with good performance. This real time feedback offers an additional dimension to help operations staff prioritize issues and provide the highest overall availability and ensure the lowest overall impact when problems occur.
New in MOM 2005 are Tasks which take MOM’s capabilities from observing, detecting and alerting to deep investigation and issue resolution by taking specific diagnostic or management actions. Tasks are initiated on demand by the administrator and can include tasks that run on the Console, Management server or Managed node.
Reports leverage the new MOM 2005 data warehouse and SQL Reporting Services to provide management with the information they need to analyze performance of their data center operations and the services they provide, as well as the service owner with rich information about its usage for capacity planning.
Finally the MOM infrastructure allows Management Packs to automatically identify types of servers (e.g. SQL server, Exchange servers, Domain Controllers etc) and deploy then the corresponding Management Pack without any admin interaction or every having to deploy anything on the managed server.
Additional Information:
Management Packs
Management Packs are a container and distribution vehicle that MOM uses to deploy the configuration information that is required for the monitoring of a system or application.
The Management Pack module consists of a collection of rules, knowledge, and public views that enable the management of a system or application. MOM can collect an array of information from many different sources. By using Management Pack modules, you can specify how MOM collects, handles, and responds to information.
The richness and biggest value in MOM comes from the knowledge of how a system is monitored in the form of a Management Pack, which contains the following types of configuration information to enable this:
List of Rule Groups that are folder for rules.
List of Rules for each Rule Group
List of Provider Instances that Rules refer to
List of Scripts that Rules need to call as a response
List of Registry based Computer Attributes needed for the discovery of the application being monitored
List of Computer Groups whose formula depends on the Computer Attributes specified
List of Computer Group, Rule Group association in which the rule targets are specified
List of Notification Groups that notification responses uses in processing rules
List of view instances definition that defines how the operation data produced by the management should be viewed
List of Tasks users might need for the management of the application
Service Discovery Class Schema that defines the entities that will be managed and their properties as well as their relationship to other properties
Topology Diagram Definitions that describes how the service discovery data should be viewed as a topology from the application point of view.
product knowledge associated with the rules which specify how problems should be corrected, how management pack should be used.
Management Pack formats
Management Packs have three formats:
The first format is a binary file called an AKM file. Management Packs are usually distributed in this format.
The second format is an XML file that describes the contents in human readable form. This format is used to edit and compare Management Packs.
The third format is the format used to store information in the database by importing a Management Pack (in other formats) into the database.
Authoring Management Packs
There are three methods that you can use to author a Management Pack:
First, create the configuration object definitions in the Administrator console and then export these definitions to an AKM file.
Second, create/edit an XML file that describes configuration information. This file is later converted to an AKM file or imported into the MOM database.
Third, programmatically create the Management Pack using a scriptable object model. The results are then saved in any format.
© Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

12. Mom Rule: Unit Of Instruction/Policy
6/26/2018 4:57 PM
Mom Rule: Unit Of Instruction/Policy
Event Rules
Collection rules
Filtering rules
Missing event rules
Consolidation rules
Duplicate Alert Suppression
Performance Rules
Measuring
Threshold
Alert Rules
Rule
Provider
NT event log
Perfmon data
WMI
SNMP
Log files
Syslog
Criteria
Response
Alert
Script
SNMP trap
Pager
Task
Managed Code
File Transfer
Where source=DCOM and Event ID=1006
Knowledge
Product Knowledge
Links to Vendor
Company Knowledge
Links to Centralised Company knowledge
© Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

13. State rules Advantages Typical candidates for state-based rules
6/26/2018 4:57 PM
State rules
Advantages
State is always current
“What is the server status now?”
Problem taxonomy
What aspect of my server is having the problem?
Role (Exchange, DNS, etc.)
Component (Services, Queues, Mail Flow, Databases)
Typical candidates for state-based rules
Numeric thresholds (e.g., perf counters)
Service State
Problem State: property on Alerts indicating the state corresponding to that alert
Active = R/Y
Inactive = Green
Investigate = non-state
© Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

14. State Terminology 6/26/2018 4:57 PM
© Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

15. Why use state monitoring
Show users the real-time state of their MOM managed computer base for the multiple roles a computer can play (eg. Exchange & IIS).
Better escalations
Show users the state of the critical components of a computer role, at a glance.
Show users measurement information critical to a computer role.
Intelligent rollup state values (where a computer is red, specifically because one of its constituent applications is red) and navigation to root causes (of state information)

16. Performance Monitoring
Query and threshold Windows Performance counters as part of your management pack
Specify counter specifics to query
Object
Counter
Instance
Excellent targets for easy state monitoring

17. Internal Service Monitoring
Monitors for service changes and status
Scripts no longer required for service monitoring in MOM
Interrogates the Service Control Manager (SCM) to determine service state
Internal MOM events contain details of service changes and state

18. Internal Service Monitoring
6/26/2018 4:57 PM
Internal Service Monitoring
MOM Event Details
Event ID 21207
Source ”Microsoft Operations Manager”
Parameter 5 is Internal Service Name
Parameter 9 is New State
Supported parameters
1- Number of seconds from last sample
2 - Display Name
3 - Old State
4 - New State
5 - Service Name
6 - Start Up Type
7 - Service Context
8 - Old State (numeric)
9 - New State (numeric, e.g., 1= stopped)
10 - Start Up Type (numeric, e.g., 2 = automatic start)
The following values are available for Service State
Stopped 1
Start Pending 2
Stop Pending 3
Running 4
Continue Pending 5
Pause Pending 6
Paused 7
The following values are available for Service startup Type
Auto Start 2
Manual 3
Disabled 4
Unknown state/startup type -1
© Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

19. Tasks
Tasks provide the ability to execute on demand diagnostics, corrective actions, and automation processes
Tasks are executed by the administrator from the Management Server
Task scenarios
Automate a complex set of steps required to solve a common problem
Provide additional information required to diagnose a problem
Run administrative tools in context direct from the MOM server

20. Task Types Command-line Script Managed Code File Transfer
Execute Windows or Application command line tools
Operator Console: The tasks command line is predefined
Management Server or Agent Managed computer: Command line parameters are modifiable
Script
Executes custom scripts that are available inside MOM
Task scripts can use MOM Scripting Objects
Managed Code
Execute managed code methods
File Transfer
Leverage the file transfer response to transfer a file through a task

21. Task Output And Security
6/26/2018 4:57 PM
Task Output And Security
Tasks Output
Console task output available in task dialog
Agent or Management Server task output is available as MOM internal events
Leverage events 9897, 9898, and 9899 in your management packs to display task results
Security
“MOM Users” can not execute Agent or Management Server tasks
Task audit events provide details on how the task was executed
Must be Administrator or higher.
© Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

22. Responses
Responses run on timed basis or when a given condition is observed
Investigate/Resolve issue
Perform advanced monitoring
Response types
Script
Execute a command
Update a state variable
File Transfer
Managed Code Response
Note: Responses can now be run before alert suppression
Send notifications or perform responses even if the MOM database is not available

23. Response Execution
Script and Managed Code responses execute under the dedicated Action Account
Processes are hosted in the MOMHost process
Dedicated Host process per management group
Multiple instances of the same script can run at the same time
The MOMHost process is monitored by MOM
Script
Action Account

24. Script Responses
Script responses are significantly improved and more reliable with the MOMHost process
Response timeout is now specified per script

25. Managed Code Response
Managed code responses execute predefined managed code assemblies
A response may be executed by a rule or task
MOM does not distribute assemblies
Responses can leverage any .NET language
Visual Basic .NET, C#, C++ .NET
Response execute any publicly exposed method in your assembly

26. File Transfer Response
6/26/2018 4:57 PM
File Transfer Response
The file transfer response leverages BITS to transfer files between computers via port 80
File Transfer responses may
Download files to the agent
Upload files from the agent
File transfer responses may be called from either rules or tasks
Downloads are limited to the MOM \downloadedfiles\<configgroup> folder
© Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

27. File Transfer Scenarios
Upload transaction log files to a central location
Archiving data as required by law
Upload a file to assist with troubleshooting
Have a task upload data on demand from the agent
Download a file to the MOM Agent required by a Management Pack

28. 6/26/2018 4:57 PM
© Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

29. Management Pack Tools Convert management packs to XML
MOM 2005 management packs can be converted to XML to enable scenarios such as differencing and documentation
XML can be compared, queried and displayed
Conversion is one way only
The XML format is not supported by Microsoft and will change in future releases of MOM

30. Management Pack Tools Management Pack Diff
Compare two management pack file to understand differences and changes
Updated, Deleted and Moved objects
Logical and Physical changes
Useful during upgrade and deployment scenarios

31. Resources
Management Pack Catalog managementpacks/
Microsoft Management Alliance (MMA) (Management Pack Authoring)
Development Guide
Development Tools
Development Samples
MOM 2005 Management Pack Development Guide Feedback and Questions

32. Questions?

33. © 2003-2004 Microsoft Corporation. All rights reserved.
6/26/2018 4:57 PM
© Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.
© Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

34. MOM 2005 Built-in Reports TOTAL 13 193 Management Pack No. of Reports
6/26/2018 4:57 PM
MOM 2005 Built-in Reports
Management Pack
No. of Reports
Comment
Exchange 2000 & 2003 Server 34
RTM
Internet Information Services 6
WEB
MOM 2005 33
Security (MBSA) 2
SMS 2003 44
SQL Server 2000 12
Terminal Server 4
Virtual Server 2005
Web Services
Windows Active Directory 14
Windows Server Cluster
Windows DNS 3
Windows Server (2000, 2003, NT4) 27
TOTAL 13
193
We have made significant investment in reporting in MOM Not only have all the MOM 2000 reports been upgraded for MOM 2005, we also have many more reports available.
© Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.