Microsoft System Center

Guide for Windows Server 2016 Distributed

Transaction Coordinator Management Pack
for System Center 2016 Operations Manager
Microsoft Corporation
Published: September 2016

Copyright
This document is provided "as-is". Information and views expressed in this document, including
URL and other Internet Web site references, may change without notice.
Some examples depicted herein are provided for illustration only and are fictitious. No real
association or connection is intended or should be inferred.
This document does not provide you with any legal rights to any intellectual property in any
Microsoft product. You may copy and use this document for your internal, reference purposes.
You may modify this document for your internal, reference purposes.
© 2016 Microsoft Corporation. All rights reserved.
Microsoft, Active Directory, Bing, BizTalk, Forefront, Hyper-V, Internet Explorer, JScript,
SharePoint, Silverlight, SQL Database, SQL Server, Visio, Visual Basic, Visual Studio, Win32,
Windows, Windows Azure, Windows Intune, Windows PowerShell, Windows Server, and
Windows Vista are trademarks of the Microsoft group of companies. All other trademarks are
property of their respective owners.
Contents
Guide for Windows Server 2016 Distributed Transaction Coordinator Management Pack for
System Center 2016 Operations Manager..................................................................................4
Management Pack Purpose........................................................................................................ 5
Monitoring Scenarios............................................................................................................... 5
How Health Rolls Up................................................................................................................ 7
Configuring the Management Pack for Windows Server 2016 Distributed Transaction
Coordinator Management Pack for System Center 2016 Operations Manager.......................8
Links............................................................................................................................................ 8
Appendix: Management Pack Contents......................................................................................9

Appendix: Rules............................................................................................................................ 12
Rules...................................................................................................................................... 12
Guide for Windows Server 2016 Distributed
Transaction Coordinator Management Pack
for System Center 2016 Operations Manager
This guide was written based on version 10.0.0.0 of the Windows Server 2016 Distributed
Transaction Coordinator Management Pack for System Center 2016 Operations Manager.

Guide History

Release Date Changes

January 2015 Original release of this guide

Supported Configurations
This management pack requires System Center Operations Manager 2012 or later. A dedicated
Operations Manager management group is not required.
The following table details the supported configurations for the Windows Server 2016 Distributed
Transaction Coordinator Management Pack for System Center 2016 Operations Manager:

Configuration Support

Windows Server 2016 Windows Server 2016

Clustered servers Yes

Agentless monitoring Not supported/not tested

Virtual environment Yes

Management Pack Scope

This management pack supports up to Windows Server 2016.

Prerequisites
The following requirements must be met to run this management pack:

4
The following management packs must be installed prior to installing the Windows Server 2016
Distributed Transaction Coordinator Management Pack for System Center 2016 Operations
Manager:

 Windows Server Library Management Pack

 Microsoft Windows Server Cluster Management Pack

Files in this Management Pack

The Windows Server 2016 Distributed Transaction Coordinator Management Pack for System
Center 2016 Operations Manager includes the following files:
 Microsoft.Windows.MSDTC.2016.mp 10.0.0.0
 Microsoft.Windows.MSDTC.library.mp 10.0.0.0

Management Pack Purpose

In this section:
 Monitoring Scenarios
 How Health Rolls Up
For details on the discoveries, rules, monitors, views, and reports contained in this Management
pack, see Appendix: Management Pack Contents.

Monitoring Scenarios
The Windows Server 2016 Distributed Transaction Coordinator Management Pack for System
Center 2016 Operations Manager manages MSDTC service that an operator or administrator is
interested in monitoring, configuring, or reporting on.

The following component events are captured in this management pack:

 Windows Server 2016 Distributed Transaction Coordinator (MSDTC)

Objects the Windows Server 2016 Distributed Transaction Coordinator

Management Pack for System Center 2016 Operations Manager Discovers
The Windows Server 2016 Distributed Transaction Coordinator Management Pack for System
Center 2016 Operations Manager discovers the object types described in the following table.

Discovered
Object type Description
automatically

Servers with MSDTC

MSDTC Service Discovery Yes
installed

MSDTC Clustered MSDTC Role Yes Clustered MSDTC roles

5
Discovery

Not all of the objects are automatically discovered. Use overrides to discover those that are not
discovered automatically. For information about discovering objects, see the "Object Discoveries
in Operations Manager 2016" topic in Operations Manager 2016 Help
Use the following procedure to modify automatic discovery parameters.

To use an override to change the parameters for automatic discovery

1. In the Authoring pane, expand Management Pack Objects, and then click Object
Discoveries.
2. On the Operations Manager toolbar, click Scope, and then filter the objects that appear in
the details pane.
3. In the Operations Manager toolbar, use the Scope button to filter the list of objects, and
then click MSDTC DTC Role Discovery.
4. On the Operations Manager toolbar, click Overrides, click Override the Object
Discovery, and then click For all objects of type: Windows Server, For a group.
5. In the Overrides Properties dialog box, click the Override box for the parameter(s) you
wish to modify.
6. Under Management Pack, click New to create an unsealed version of the management
pack, and then click OK.

Classes
The following diagram shows the classes defined in this management pack.

Windows!Microsoft.Windows.ComputerRole

Microsoft.MSDTC.10.0.ServerRole Microsoft.MSDTC.10.0.ClusteredRoles

Legend

Microsoft.MSDTC.10.0.Servers ComputerRole Derived from Built in Class

Server with MSDTC

Service/ClusteredRole service or Clustered role
6
Hosting

Derived from
How Health Rolls Up
The following diagram shows how the health states of MSDTC service roll up in this management
pack.

Microsoft.MSDTC.10.0.ServerRole

Microsoft.MSDTC.10.0.Servers

Configuring the Management Pack for Windows

Server 2016 Distributed Transaction Coordinator
Management Pack for System Center 2016
Operations Manager
This section provides guidance on configuring and tuning this management pack.
 Best Practice: Create a Management Pack for Customizations

Best Practice: Create a Management Pack for Customizations

By default, Operations Manager saves all customizations such as overrides to the Default
Management Pack. As a best practice, you should instead create a separate management pack
for each sealed management pack you want to customize.
When you create a management pack for the purpose of storing customized settings for a sealed
management pack, it is helpful to base the name of the new management pack on the name of
the management pack that it is customizing.
Creating a new management pack for storing customizations of each sealed management pack
makes it easier to export the customizations from a test environment to a production environment.
7
It also makes it easier to delete a management pack, because you must delete any dependencies
before you can delete a management pack. If customizations for all management packs are
saved in the Default Management Pack and you need to delete a single management pack, you
must first delete the Default Management Pack, which also deletes customizations to other
management packs.

Links
The following links connect you to information about common tasks that are associated with
System Center management packs:

System Center 2016 - Operations Manager

 Management Pack Life Cycle

 How to Import a Management Pack
 Tuning Monitoring by Using Targeting and Overrides
 How to Create a Run As Account
 How to Export a Management Pack
 How to Remove a Management Pack

Operations Manager 2007 R2

 Administering the Management Pack Life Cycle

 How to Import a Management Pack in Operations Manager 2007
 How to Monitor Using Overrides
 How to Create a Run As Account in Operations Manager 2007
 How to Modify an Existing Run As Profile
 How to Export Management Pack Customizations
 How to Remove a Management Pack
For questions about Operations Manager and management packs, see the System Center
Operations Manager community forum.
A useful resource is the System Center Operations Manager Unleashed blog, which contains “By
Example” posts for specific management packs.
For additional information about Operations Manager, see the System Center 2016 - Operations
Manager Survival Guide and Operations Manager 2007 Management Pack and Report Authoring
Resources

8
 Important
All information and content on non-Microsoft sites is provided by the owner or the users
of the website. Microsoft makes no warranties, express, implied, or statutory, as to the
information at this website.

Appendix: Management Pack Contents

The Windows Server 2016 Distributed Transaction Coordinator Management Pack for System
Center 2016 Operations Manager discovers the object types described in the following sections.
Not all of the objects are automatically discovered. Use overrides to discover those objects that
are not discovered automatically.

Microsoft.MSDTC.10.0.Discovery
Discovery Information

Interval Enabled When to Enable

43200 seconds True not applicable

Related Monitors

Monitor Data source Interval Alert Reset Cor Enabl When to

Behavior res ed Enable
pon
din
g
Rul
e
Microsoft.MSD
Service Interval True Automatic True “not
TC.10.0.Monit
or.Service name = period Alert priority: applicabl
MSDTC Normal e”

Alert severity:
Error

Note
If you are using connectors, you can disable the monitor and enable its corresponding
rule to enable alerts without changing health status.

Note

9
 Disable the rule and enable its corresponding monitor to enable alerts, state changes,
and health rollup.

Related Views

View Description Rules and

Monitors that
Populate the
View
Microsoft.MSDTC.10.0.State.View 
Show the MSDTC services
Microsoft.MSDT
C.10.0.Monitor
.Service

Microsoft.MSDTC.10.0.ClusteredRoleDiscovery
Discovery Information

Interval Enabled When to Enable

43200 seconds True not applicable

Related Monitors

Monitor Data source Interval Alert Reset Cor Enabl When to

Behavior res ed Enable
pon
din
g
Rul
e
Microsoft.MSD
MSCLUST Interval False Automatic True “not
TC.10.0.Monit
or.ClusteredR ER_Resour period applicabl
ole ce e”

10
 Note
If you are using connectors, you can disable the monitor and enable its corresponding
rule to enable alerts without changing health status.

Note
Disable the rule and enable its corresponding monitor to enable alerts, state changes,
and health rollup.

Related Views

View Description Rules and

Monitors that
Populate the
View
Microsoft.MSDTC.10.0.ClusteredRole
Show the clustered MSDTC roles 
s.State.View
Microsoft.MSDT
C.10.0.Monitor
.ClusteredRole

Appendix: Rules
The following tables list the rules from the Management Pack.

Note
Be aware that some of these rules may create noise in your environment.

Rules
Event Based Rules

Name Type Event Id Enabled?

Required file is missing from the Event 4143,4212,4213,4214,4129 Yes

System32 folder in Windows Collection
directory.

11
Name Type Event Id Enabled?

Confirm network connectivity Event 4358,4359 Yes

and firewall setting. Collection

System reported an unexpected Event 4418 Yes

error condition. Reinstall Collection
MSDTC to resolve it.

The service must be restarted or Event 4424,4228 Yes

missing files. Collection

Check low-resource condition. Event 4425 Yes

Collection
4363,4367,4368,4370,4155,4168
Restart MSDTC Event Yes
,
Collection 4169,4170,4209,4229,4230,4233
,
4355,4356,4433,4434,4435,4436
,
4441,4455,4456,53321

12