Rule and Monitor Targeting

Best Practices

Targeting All Managed Computers Targeting a Server Role Application Models

EXAMPLE: You want to monitor failed logon attempts on Windows Computers EXAMPLE: You want to monitor file cache hits on Web Servers
IIS
DO DO
• Use Windows Operating System to target all Windows managed nodes (desktop and servers). • Use IIS Server Role 2003 to target all IIS 2003 Web Servers.
• Use Windows Server Operating System to target all Windows server managed nodes • Use IIS Server Role to target all IIS Web Servers. Currently this would apply to Windows Windows
Server SQL
(all versions). 2000 and 2003 IIS servers. With the release of Windows Server 2008 MP, this would also
• Use Windows Server 2003 Operating System to target all Windows Server 2003 managed nodes. apply to Windows Server 2008 IIS Web Servers. IIS 2003 IIS 2003
NNTP Virtual SQL 2005
NNTP Server
Server Windows Server Reporting
Services
DON’T DON’T
• Use Agent: • Use Windows Server 2003 Operating System IIS 2003 IIS 2003
SQL 2005
Analysis
SMTP Server SMTP Virtual Service
- The monitor will not work for agent-less managed computers. - The monitor will apply to all Windows 2003 Operating Systems regardless of whether IIS is installed Server

- The monitor will affect the health state of the Agent which is not what you want. or not. IIS 2003 SQL 2005
Server Role SQL 2005 Engine Integration
• Use Computer: • Use Windows Server IIS 2003 IIS 2003 Service
FTP Server FTP Site
- Management packs for non-Windows management are likely to use computer as the base type for types - The monitor will apply to all Windows Servers regardless of whether IIS is installed or not.
AspNet Web
such as Unix computer. The monitor that you just created will not work against non-Windows computers. • Use Windows Computer Service
End Point SQL 2005 SQL 2005
- The monitor will execute against all Windows computers – both clients and servers that are managed - The monitor will apply to all Windows computers (both desktops and servers) regardless of whether IIS 2003
Web Server
IIS 2003
Web Site
Database DB File Group

by Operations Manager. IIS is installed or not . AspNet Web

Application
• Use Windows Computer: • Use Computer End Point SQL 2005
SQL 2005
DB File
Distributor
- The monitor will execute against all Windows computers – both clients and servers that are managed by - If management packs for other operating systems are installed, the monitor will apply to non-
Operations Manager. Windows computers as well. However, the monitor will not function correctly.
IIS 2003 SQL 2005 SQL 2005
Application Pool Publisher Publication

Operating System Model Computer Role Model Logical Disk

SQL 2005 SQL 2005

Subscriber Subscription

Operating System INHERITANCE Computer Role SQL 2005 SQL 2005

INHERITANCE Agent Agent Job

Other OS
Active Directory
Other
Operating System Computer Role

Windows Windows Active Directory

Operating System Computer Role

Exchange
Active Directory Active Directory
Forest Domain
Exchange Service

Windows 2003
Global Catalog
Active Directory Role
Windows Server Windows Client IIS Server Role SQL Role
Site
Exchange
Operating System Operating System Organization
File
Replication
Service

Windows 2003 Exchange

Domain Admin Group
Netlogon
Controller Service

Key Distribution Exchange

Center Routing Group
Windows Server 2003 Windows Server 2003 Windows XP Windows Vista IIS 2000 IIS 2003 SQL Reporting Service
SQL DB Engine Windows 2003
Operating System Operating System Operating System Operating System Server Role Server Role Services Domain
Controller Role Windows Windows Exchange
Time Service Computer 2003 Role

ExBPA
Component

Targeting Targeting Some Targeting Some

Exchange Exchange
IS Service OMA

Exchange Exchange

Multi-Instanced Managed Computers Components

Windows Server SA Service EAS

Exchange
Windows Server Management Exchange

Components
2003 Computer Service SMTP

EXAMPLE: You want to monitor failed logon attempts on Windows Computers in Redmond EXAMPLE: You want to monitor connection
Exchange

DO attempts per second on Web Sites that are Windows Server

Replication
Service
Exchange
MAPI logon
2003 Operating
• Use Windows Operating System to target all Windows managed nodes (desktop and servers). part of the HRWeb distributed application System
EXAMPLE: You want to monitor connection Exchange
• Use Windows Server Operating System to target all Windows server managed nodes (all versions). DO Database Exchange
Mail Flow
attempts per second on Web Sites Storage
• Use Windows Server 2003 Operating System to target all Windows Server 2003 managed nodes. • If the distributed app contains only IIS 2003 Windows 2003
Network Adapter
DO • Once you have picked the right type for the situation, create a disabled monitor. Add all web sites use IIS 2003 Web Site type. Exchange
IMAP4 Service
Exchange
Routing Engine
• Use IIS Web Site to monitor all IIS Web Sites. Redmond computers to a group. Create an override to enable the monitor for the group. • If the distributed app contains both IIS 2003
Service

Currently this would be both IIS 2000 and IIS and IIS 2000 web sites, use IIS Web Site type.
Windows 2003
Processor Exchange Exchange
2003 Web Sites. When the Windows Server DON’T • Create the monitor as disabled. Create an POP3 Service MTA

2008 MP ships, this would include Windows • Use Agent: override to enable the monitor and use the
Server 2008 Web Sites. - The monitor will not work for agent-less managed computers. distributed application as the context of the
Windows 2003
Physical Disk
Exchange
OWA
Exchange
Queue
• Use IIS 2003 Web Site to monitor all IIS 2003 - The monitor will affect the health state of the Agent, which is not what you want. override.
Web Sites. • Use Computer:
- Management packs for non-Windows management are likely to use computer as the base type for
DON’T Windows 2003
Disk Partition
DON’T • Use the distributed app type
types such as Unix computer. The monitor that you just created will not work against non-Windows
Use Web Site. - The monitor will not run against the right com-
computers. Legend
- In case you have management packs for web sites ponent as the distributed app instance actually
Windows 2003
Logical Disk
- The monitor will execute against all Windows computers – both clients and servers that are managed Hosting Relationship
other than IIS web sites, the monitor will likely not runs on the RMS.
by Operations Manager. Containment Relationship
work.
• Use Windows Computer: Health Rollup

- The monitor will execute against all Windows computers – both clients and servers that are managed
by Operations Manager. Failed logons is actually an attribute of the operating system rather than the
computer.

MCS 1019_BestPractices_SC2_REV.indd 1 11/6/07 9:25:43 AM