Reference
Published : January 1, 2005
On This Page
Additional Resources
Sites and Components
Computer Groups
Rule Groups
Providers
Scripts
Public Views for MOM 2005
Views for Microsoft SMS 2003
Diagrams
Reports
Tasks
Additional Resources
Microsoft Operations Manager 2005
For the latest information about Microsoft® Operations Manager (MOM) 2005, see the product Web site..
To access the MOM 2005 core product documentation on the Web, see the Product Documentation section of the product Web site. These technical papers describe issues and procedures involved in deploying and administering MOM in an enterprise computing environment.
The Microsoft Operations Manager 2005 Deployment Guide provides a high-level overview of MOM 2005 components and features, management products and processes, deployment topologies, Management Pack modules and step-by-step instructions to deploy MOM 2005 in your organization.
The Microsoft Operations Manager 2005 Operations Guide outlines deployment, maintenance, and recommended best practices to maintain and run MOM 2005 in an existing IT infrastructure.
The Microsoft Operations Manager 2005 Security Guide provides information about security-related issues and requirements for deploying MOM 2005 in your environment.
The Technical Resources sections of the product Web site provides detailed technical information about MOM 2005, including planning and deployment papers, product documentation, training information, and other technical guidance.
To access additional MOM 2005 technical papers, see Microsoft Operations Manager on the Microsoft TechNet Web site.
SMS 2003
All of the information that you need for deploying and using SMS 2003 is provided in the core product documentation, the SMS Administrator console Help, the SMS glossary, and the SMS Online Library. The SMS Online Library and SMS Administrator console Help are accessible from the SMS Administrator console.
SMS Online Library
The SMS Online Library provides pointers to all the information that you need for deploying and using SMS. There are two ways to run the SMS Online Library after you install SMS 2003:
From the Start menu, click Programs, click Systems Management Server, and then select SMS Online Library.
Right-click SMS Online Library in the SMS Administrator console tree, and then click Run Online Library.
The Online Library includes the following:
SMS 2003 Release Notes, which contain critical information about SMS.
What’s New in this Version of SMS, which describes the differences between this version of SMS 2003 and earlier versions.
A link to the SMS Product Documentation Web page.
Links to download pages for the SMS 2003 Device Management Feature Pack and the SMS 2003 Operating System Deployment Feature Pack.
SMS on the Web
To locate technical papers and information about related products, see the Microsoft Systems Management Server 2003 product Web site. The SMS Web site also provides specific information about how to use SMS with other Microsoft products, such as Microsoft Windows® XP and Microsoft Office XP.
For links to browseable and downloadable versions of SMS 2003 core product documentation, see the Systems Management Server 2003 Product Documentation Web page.
Microsoft maintains many free newsgroups where you can post your questions and obtain free support from your peers and often, from members of the SMS product team. Visit the Systems Management Server Community Web page for more information about free newsgroups.
For technical how-to articles, FAQs, Web casts, newsgroups, and more, see the Support for Systems Management Server Web page.
To search the Microsoft Knowledge Base and other technical resources for fast, accurate answers to SMS questions, visit the Microsoft Help and Support Web site. You can query the Knowledge Base to find an article about a specific issue by using the Qxxxxxx number or the xxxxxx number that is assigned to the issue.
Providing Feedback
If you have comments or suggestions about SMS, send them to SMS Wish. We greatly value your feedback.
Help the SMS documentation team ship the kind of product information that you need most by giving us your feedback and comments. Send your feedback about our documentation to SMS Documentation.
Sites and Components
SMS 2003 components include the SMS central site server, SMS site database, and SMS Administrator console. Typically, the SMS central site server, SMS site database, and SMS Administrator console reside on the same server and each site system role resides on a dedicated server. A central site server and database, together with any site system roles, make up a single SMS site. A single SMS site might include multiple duplicate site system roles. For example, a single site might include multiple client access points (CAPs). SMS 2003 sites can be tiered. A single SMS site might not include some site server roles, such as a server locator point.
The SMS 2003 Management Pack is designed to monitor SMS server components. This Management Pack is not designed to monitor SMS functionality on SMS client computers. However, MOM might be used to monitor other applications that reside on an SMS client computer.
For more information about SMS 2003 components, see the SMS 2003 Online Library. For links to SMS 2003 documentation, see the Reference section in this guide.
Key server roles and components include:
Client access point
Distribution point
Management point
Server locator point
Reporting point
Site server
Site database
Senders
Advanced Client
Legacy Client
SMS Provider
SMS Administrator console
Client Access Point
The CAP role is the point of contact between Legacy Clients and the SMS site server. The CAP passes all Legacy Client data to the site server. Legacy Client computers contact the CAP for management information from the SMS site server. A CAP serves only one SMS site and is installed by default on the site server. The CAP also:
Provides specific configuration instructions and files for the Legacy Client during client installation and when changes are made after client installation.
Serves as the location where Legacy Client computers check for advertisements.
Receives data from Legacy Clients, which it forwards to the SMS site server. For example, when a client completes either hardware or software inventory and has created an inventory data file, it sends this data to the CAP. Any status messages originating from the client are replicated to the CAP.
Distribution Point
The distribution point stores SMS package source files that SMS clients use when installing software programs distributed by SMS. When the SMS administrator advertises a program, the advertisement and program information are available to clients through a CAP for Legacy Clients or through a management point for Advanced Clients.
When SMS is set up, the site server is automatically assigned the distribution point role. The SMS administrator can enable the distribution point to use Background Intelligent Transfer Service (BITS), which enables incremental package file download to Advanced Clients.
Advanced Clients use BITS to automatically detect the client network connection capacity and adjust transfer rates efficiently. This is supported only on clients running Microsoft Windows 2000, Microsoft Windows XP Professional, and Microsoft Windows Server™ 2003 operating systems.
Management Point
The management point is the primary point of contact between Advanced Clients and the SMS site server. An SMS site has only one default management point, although multiple management points can be configured with Windows Network Load Balancing Service. Similar to the relationship between CAPs and Legacy Clients, a management point:
Provides specific client configuration details (also known as the Advanced Client policy) for the Advanced Client after client installation.
Serves as the location where Advanced Client computers check for advertisements.
Locates distribution points for Advanced Clients.
Receives inventory, software metering, and status information from Advanced Clients and forwards it to the SMS site server.
Server Locator Point
The server locator point locates CAPs for Legacy Clients and management points for Advanced Clients. The server locator point is mostly used in client installation. The server locator point:
Locates a management point for the Advanced Client if the Advanced Client is configured for automatic SMS site assignment.
Provides Advanced Clients with the location of the management point during Logon Script-initiated Client Installation and during an installation without sufficient credentials.
Provides SMS site assignment for the Legacy Client and locates CAPs during Logon Script-initiated Client Installation.
Reporting Point
A reporting point is a server running Internet Information Services (IIS) that hosts the code for Report Viewer and any supplemental reports. A reporting point communicates only with its SMS site database server.
Advanced Client
SMS 2003 addresses the need for mobile computing with the Advanced Client. The Advanced Client supports the full SMS feature set, including software distribution, asset management, and remote troubleshooting. You can manage mobile users and desktop users without differentiating between them. The Advanced Client uses a Windows technology called BITS to provide connectivity for all management operations.
Legacy Client
You can use the Legacy Client if your organization needs to manage computers that do not meet the requirements for supporting the Advanced Client. You can enable, configure, and control the following Legacy Client installation methods:
Logon Script-initiated Client Installation
Client Push Installation
Manual Client Installation
SMS Provider
The SMS Provider processes requests for data from the SMS site database. The SMS Provider role is installed on the same computer as the SMS site server or the SMS site database. It is recommended that you install both the SMS Provider and the SMS site database on the site server. The SMS Provider provides access to data for the SMS Administrator console installed on the site.
SMS Administrator Console
The SMS Administrator console is the graphical user interface used to administer SMS. This interface uses a Microsoft Management Console (MMC) snap-in that is provided with the SMS product software. The SMS Administrator console is installed by default when you install a primary site server. It can also be installed on other servers or workstations.
Computer Groups
The SMS 2003 Management Pack provides the following computer groups:
Microsoft SMS 2003 Administrator Consoles
Microsoft SMS 2003 Advanced Clients
Microsoft SMS 2003 Central Site Servers
Microsoft SMS 2003 Clients
Microsoft SMS 2003 Client Access Point Servers
Microsoft SMS 2003 Component Servers Based on IIS
Microsoft SMS 2003 Component Servers Based on SMS Executive
Microsoft SMS 2003 Distribution Point Servers
Microsoft SMS 2003 Management Point Servers
Microsoft SMS 2003 Primary Site Servers
Microsoft SMS 2003 Providers
Microsoft SMS 2003 Reporting Point Servers
Microsoft SMS 2003 Secondary Site Servers
Microsoft SMS 2003 Sender Servers
Microsoft SMS 2003 Server Locator Point Servers
Microsoft SMS 2003 Servers
Microsoft SMS 2003 Site Servers
Microsoft SMS 2003 Legacy Clients
Rule Groups
The SMS 2003 Management Pack contains the following rule groups:
SMS Administrator Consoles
SMS Clients
SMS Clients - Advanced
SMS Clients - Common
SMS Clients - Legacy
SMS Servers
SMS Client Access Points
SMS Distribution Points
SMS Management Points
SMS Providers
SMS Reporting Points
SMS Sender Servers
SMS Servers - Common
SMS Servers Based on IIS
SMS Servers Based on SMS Executive
SMS Server Locator Points
SMS Site Database Servers
SMS Site Servers - Central
SMS Site Servers - Common
SMS Site Servers - Primary
SMS Site Servers - Secondary
This section lists the rule groups and event rules within the SMS 2003 Management Pack that generate critical events and alerts. See the MOM Administrator console to review all rules under the Systems Management Server (SMS) 2003 rule group.
SMS Management Points
The SMS Management Point rule group contains rules for errors related to the SMS management points. These are found in the MOM Administrator console at the following location:
Management Packs\Microsoft Systems Management Server (SMS) 2003\SMS Servers\SMS Management Points
Table R.1 Rules in the SMS Management Points Rule Group
Rule |
Default alert severity |
|---|---|
SMS 2003 service failure: SMS Agent Host terminated unexpectedly |
Service Unavailable |
SMS 2003 service failure: SMS Agent Host hung on starting |
Service Unavailable |
SMS 2003 service failure: SMS Agent Host failed to start |
Service Unavailable |
SMS 2003 service failure: SMS Agent Host was unable to log on |
Service Unavailable |
SMS 2003 service failure: SMS Agent Host depends on another service which failed to start, or is nonexistent |
Service Unavailable |
SMS 2003 service stopped: SMS Agent Host (client) |
Service Unavailable |
SMS 2003 service running: SMS Agent Host |
Service Unavailable |
SMS 2003 dependent service running: IIS Admin Service |
Service Unavailable |
SMS 2003 dependent service running: World Wide Web Publishing Service |
Service Unavailable |
SMS 2003 Management Point Health: State |
Critical Error |
SMS 2003 Management Point Health: Script error |
Critical Error |
SMS Providers
The SMS Providers rule group contains rules for errors related to the SMS Providers component of SMS 2003. These are found in the MOM Administrator console at the following location:
Management Packs\Microsoft Systems Management Server (SMS) 2003\SMS Servers\SMS Providers
Table R.2 Rules in the SMS Providers Rule Group
Rule |
Default alert severity |
|---|---|
SMS 2003 Status: Script error |
Critical Error |
SMS 2003 Site System Summarizer: Script error |
Critical Error |
SMS Reporting Points
The SMS Reporting Point rule group contains rules for errors related to the SMS reporting points. These are found in the MOM Administrator console at the following location:
Management Packs\Microsoft Systems Management Server (SMS) 2003\SMS Servers\SMS Reporting Points
Table R.3 Rules in the SMS Reporting Points Rule Group
Rule |
Default alert severity |
|---|---|
SMS 2003 service failure: SMS_REPORTING_POINT terminated unexpectedly |
Service Unavailable |
SMS 2003 service failure: SMS_REPORTING_POINT hung on starting |
Service Unavailable |
SMS 2003 service failure: SMS_REPORTING_POINT failed to start |
Service Unavailable |
SMS 2003 service failure: SMS_REPORTING_POINT was unable to log on |
Service Unavailable |
SMS 2003 service failure: SMS_REPORTING_POINT depends on another service which failed to start, or is nonexistent |
Service Unavailable |
SMS 2003 service running: SMS_REPORTING_POINT |
Service Unavailable |
SMS 2003 dependent service running: IIS Admin Service |
Service Unavailable |
SMS 2003 dependent service running: World Wide Web Publishing Service |
Service Unavailable |
SMS Sender Servers
The SMS Sender Servers rule group contains rules for errors related to the SMS Sender Servers. These are found in the MOM Administrator console at the following location:
Management Packs\Microsoft Systems Management Server (SMS) 2003\SMS Servers\SMS Sender Servers
Table R.4 Rules in the SMS Sender Servers Rule Group
Rule |
Default alert severity |
|---|---|
SMS 2003 service running: SMS_EXECUTIVE |
Service Unavailable |
SMS Server Locator Points
The SMS Server Locator Point rule group contains rules for errors related to the SMS server locator points. These are found in the MOM Administrator console at the following location:
Management Packs\Microsoft Systems Management Server (SMS) 2003\SMS Servers\SMS Server Locator Points
Table R.5 Rules in the SMS Server Locator Points Rule Group
Rule |
Default alert severity |
|---|---|
SMS 2003 service failure: SMS_SERVER_LOCATOR_POINT terminated unexpectedly |
Service Unavailable |
SMS 2003 service failure: SMS_SERVER_LOCATOR_POINT hung on starting |
Service Unavailable |
SMS 2003 service failure: SMS_SERVER_LOCATOR_POINT failed to start |
Service Unavailable |
SMS 2003 service failure: SMS_SERVER_LOCATOR_POINT was unable to log on |
Service Unavailable |
SMS 2003 service failure: SMS_SERVER_LOCATOR_POINT depends on another service which failed to start, or is nonexistent |
Service Unavailable |
SMS 2003 service running: SMS_SERVER_LOCATOR_POINT |
Service Unavailable |
SMS 2003 dependent service running: IIS Admin Service |
Service Unavailable |
SMS 2003 dependent service running: World Wide Web Publishing Service |
Service Unavailable |
SMS Server - Common
The SMS Server - Common rule group contains rules for errors related to all SMS servers. These are found in the MOM Administrator console at the following location:
Management Packs\Microsoft Systems Management Server (SMS)\ SMS Servers\SMS Server - Common
Table R.6 Rules in the SMS Server - Common Rule Group
Rule |
Default Alert Severity |
|---|---|
SMS 2003 dependent service failure: Windows Management Instrumentation terminated unexpectedly |
Service Unavailable |
SMS 2003 dependent service failure: Windows Management Instrumentation hung on starting |
Service Unavailable |
SMS 2003 dependent service failure: Windows Management Instrumentation failed to start |
Service Unavailable |
SMS 2003 dependent service failure: Windows Management Instrumentation was unable to log on |
Service Unavailable |
SMS 2003 dependent service failure: Windows Management Instrumentation depends on another service which failed to start, or is nonexistent |
Service Unavailable |
SMS Servers Based on IIS
The SMS Servers Based on IIS rule group contains rules for errors related to all SMS site servers that require IIS. These are found in the MOM Administrator console at the following location:
Management Packs\Microsoft Systems Management Server (SMS) 2003\SMS Servers\SMS Servers based on IIS
Table R.7 Rules in the SMS Servers Based on IIS Rule Group
Rule |
Default alert severity |
|---|---|
SMS 2003 dependent service failure: The World Wide Web Publishing Service terminated unexpectedly |
Service Unavailable |
SMS 2003 dependent service failure: The World Wide Web Publishing Service hung on starting |
Service Unavailable |
SMS 2003 dependent service failure: The World Wide Web Publishing Service failed to start |
Service Unavailable |
SMS 2003 dependent service failure: The World Wide Web Publishing Service was unable to log on |
Service Unavailable |
SMS 2003 dependent service failure: The World Wide Web Publishing Service depends on another service which failed to start, or is nonexistent |
Service Unavailable |
SMS Servers Based on SMS Executive
SMS Servers Based on the SMS Executive rule group contains rules for errors generated on any site server that runs the SMS Executive service. These are found in the MOM Administrator console at the following location:
Management Packs\Microsoft Systems Management Server (SMS) 2003\SMS Servers\SMS Servers based on SMS Executive
Table R.8 Rules in the SMS Servers Based on SMS Executive Rule Group
Rule |
Default alert severity |
|---|---|
SMS 2003 service failure: SMS_EXECUTIVE terminated unexpectedly |
Service Unavailable |
SMS 2003 service failure: SMS_EXECUTIVE hung on starting |
Service Unavailable |
SMS 2003 service failure: SMS_EXECUTIVE failed to start |
Service Unavailable |
SMS 2003 service failure: SMS_EXECUTIVE was unable to log on |
Service Unavailable |
SMS 2003 service failure: SMS_EXECUTIVE depends on another service which failed to start, or is nonexistent |
Service Unavailable |
SMS Site Database Servers
The SMS Site Database Servers rule group contains rules for errors related to the SMS site database server. These are found in the MOM Administrator console at the following location:
Management Packs\Microsoft Systems Management Server (SMS) 2003\SMS Servers\SMS Site Database Servers
Table R.9 Rules in the SMS Site Database Servers Rule Group
Rule |
Default alert severity |
|---|---|
SMS 2003 service failure: SMS_SQL_MONITOR terminated unexpectedly |
Service Unavailable |
SMS 2003 service failure: SMS_SQL_MONITOR hung on starting |
Service Unavailable |
SMS 2003 service failure: SMS_SQL_MONITOR failed to start |
Service Unavailable |
SMS 2003 service failure: SMS_SQL_MONITOR was unable to log on |
Service Unavailable |
SMS 2003 service failure: SMS_SQL_MONITOR depends on another service which failed to start, or is nonexistent |
Service Unavailable |
SMS 2003 service running: SMS_SQL_MONITOR |
Service Unavailable |
SMS 2003 dependent service failure: MSSQLSERVER terminated unexpectedly |
Service Unavailable |
SMS 2003 dependent service failure: MSSQLSERVER hung on starting |
Service Unavailable |
SMS 2003 dependent service failure: MSSQLSERVER failed to start |
Service Unavailable |
SMS 2003 dependent service failure: MSSQLSERVER was unable to log on |
Service Unavailable |
SMS 2003 dependent service failure: MSSQLSERVER depends on another service which failed to start, or is nonexistent |
Service Unavailable |
SMS 2003 dependent service running: MSSQLSERVER |
Service Unavailable |
SMS Site Servers - Common
The SMS Site Servers - Common rule group contains rules for errors related to all SMS site servers. These are found in the MOM Administrator console at the following location:
Management Packs\Microsoft Systems Management Server (SMS) 2003\SMS Servers\SMS Site Servers - Common
Table R.10 Rules in the SMS Site Servers - Common Rule Group
Rule |
Default alert severity |
|---|---|
SMS 2003 service failure: SMS_SITE_COMPONENT_MANAGER terminated unexpectedly |
Service Unavailable |
SMS 2003 service failure: SMS_SITE_COMPONENT_MANAGER hung on starting |
Service Unavailable |
SMS 2003 service failure: SMS_SITE_COMPONENT_MANAGER failed to start |
Service Unavailable |
SMS 2003 service failure: SMS_SITE_COMPONENT_MANAGER was unable to log on |
Service Unavailable |
SMS 2003 service failure: SMS_SITE_COMPONENT_MANAGER depends on another service which failed to start, or is nonexistent |
Service Unavailable |
SMS 2003 service running: SMS_SITE_COMPONENT_MANAGER |
Service Unavailable |
SMS 2003 service running: SMS_EXECUTIVE |
Service Unavailable |
SMS 2003 Component: Distribution Manager failed to process a package |
Error |
SMS 2003 Component: The sender cannot connect to remote site over the LAN (Advanced Security) |
Error |
SMS 2003 Component: The sender cannot connect to remote site over the LAN (Standard Security) |
Error |
SMS 2003 Component: The sender cannot connect to remote site over the RAS connection |
Error |
SMS Site Database Servers - Primary
The SMS Site Servers - Primary rule group contains rules for errors related to all SMS primary site servers. These are found in the MOM Administrator console at the following location:
Management Packs\Microsoft Systems Management Server (SMS) 2003\SMS Servers\SMS Site Servers - Primary
Table R.11 Rules in the SMS Site Servers - Primary Rule Group
Rule |
Default alert severity |
|---|---|
SMS 2003 service failure: SMS_SITE_BACKUP terminated unexpectedly |
Service Unavailable |
SMS 2003 service failure: SMS_SITE_BACKUP hung on starting |
Service Unavailable |
SMS 2003 service failure: SMS_SITE_BACKUP failed to start |
Service Unavailable |
SMS 2003 service failure: SMS_SITE_BACKUP was unable to log on |
Service Unavailable |
SMS 2003 service failure: SMS_SITE_BACKUP depends on another service which failed to start, or is nonexistent |
Service Unavailable |
SMS 2003 service stopped running: SMS_SITE_BACKUP |
Information |
SMS 2003 service started running: SMS_SITE_BACKUP |
Information |
Providers
The data provider types used by the SMS 2003 Management Pack are as follows:
Application log
Timed Event
Windows NT Performance Counter
Scripts
The SMS 2003 Management Pack contains MOM scripts that run automatically on the agent and scripts that need to be run by an administrator. Additional information about some of these scripts follows in this section.
The following scripts are run by the MOM agent automatically:
SMS 2003 Monitor SMS Status Messages
SMS 2003 Monitor Site System Summarizer
SMS 2003 Service Discovery – Client
SMS 2003 Service Discovery – Server
SMS 2003 Site Backup Event Suppression
SMS 2003 Monitor Management Point Health
SMS 2003: Monitor Management Point Availability
SMS 2003 Server Topology: Discovery
SMS 2003 Monitor SMS Inbox
SMS 2003 Monitor SMS Executive Crash Dumps
The following scripts are run by the administrator:
SMS 2003 Manage Site Systems Operations Management Information - Manual
SMS 2003 Manage Site Systems Operations Management Information - Automatic
SMS 2003 Server Availability
For more information on the SMS 2003 Manage Site Systems Operations Management Information scripts, see the Running Configuration Script section in this guide.
SMS 2003 Monitor SMS Status Messages
Many problems in SMS are detected and reported internally through the SMS Status System. Status messages are raised by SMS components pertaining to conditions of interest to an SMS administrator.
The status messages flow into the database for an SMS site and also up the site hierarchy into the parent site’s database. It is possible to monitor the SMS status system on a per-site basis, simply by querying the SMS status message table of a specified site’s database.
A set of status messages have been chosen for monitoring that reflect the most critical events to SMS administrators. When one of these messages is found in the database, an alert is generated.
After installing the management pack, the SMS 2003 Monitor SMS Status Messages script can be found in the Scripts node of the MOM Administrator console. This script does the following:
Checks if it is running under agentless-managed mode. If so, the script will exit without taking any further action.
Initializes global variables.
Opens and reads the RecordID of the last status message processed for each SMS site database being monitored from the SMS 2003 Monitor SMS Status Messages.VarSet file.
Processes status messages found in each SMS Site Database on the local computer.
Writes the RecordID of the last status message processed, for each SMS Site Database being monitored, to the SMS 2003 Monitor SMS Status Messages.VarSet file and closes the file.
The SMS 2003 Monitor SMS Status Messages script raises events with an Event ID set to the SMS Status Message ID being reported on. Table S.1 describes the format of the raised event.
Table S.1 Format of Events Raised by SMS 2003 Monitor SMS Status Messages Script
Parameter |
Description |
|---|---|
EventType |
Success, Error, Warning, or Information, depending on the SMS status message severity |
EventNumber |
SMS Status Message ID |
Category |
SMS site code |
LoggingDomain |
Resource domain of computer |
LoggingComputer |
NetBIOS name of computer |
Parameter1 |
NetBIOS name of computer |
Parameter2 |
SMS module name—for example, SMS Server |
Parameter3 |
SMS component name |
Parameter4 |
SMS Message ID |
Parameter5 |
Win32 error code |
Parameter6 |
Parent or top-level site code |
Parameter7 |
RecordID of status message in the SMS Status Message Table |
Description |
"A new monitored SMS status message on machine <NetBIOS Name> from component <Component Name> with message ID <Message ID> was found in the site <Site Code> database.” |
The SMS 2003 Monitor SMS Status Messages script also reports script errors through Status Message ID number 1102:
EventType = Warning EventNumber = 1102 Description = The script SMS 2003 Monitor SMS Status Messages running under processing rule <ScriptProcessingRuleName> encountered a runtime error. The error message will contain the text “Failed to <ErrorDescription>.”
All SMS 2003 status message monitoring event rules begin with the phrase “SMS 2003 Status:” and are located in the SMS Site Database Servers rule group.
SMS 2003 Status: Message Monitoring
SMS 2003 Status: Message Monitoring launches the script using the SMS 2003 Schedule every 30 minutes synchronize at 00:02 timed event provider. Summary information is provided on the Knowledge property page of the rule.
SMS 2003 Status: Script error
SMS 2003 Status: Script error monitors for and alerts on any script error events that might be raised. There is only one script error event, number 1102, which reports all script errors. Information about resolution of the alert is provided on the Knowledge property page of the rule.
SMS 2003 Status: <status message name>
SMS 2003 Status: < status message name > monitors for and alerts on specific status message events. Information about resolution of the alert is provided on the Knowledge property page of the rule.
All alerts have a description of the event in the following format, where $Description$ is the event description:
$Logging Computer$ - "Rule Name". $Description$
The SMS 2003 Monitor SMS Status Messages VarSet file is used to persist the RecordID of the last status message processed, on a per-site-database basis. The VarSet file is located in the Windows\Temp directory. It is a tab-delimited file with the following format:
LastRecordID_DBName RecordID#
For example, LastRecordID_SMS_FLA, with a RecordID of 477860 would indicate that the last RecordID processed from the site database named SMS_FLA was number 477860.
When upgrading the management pack from a previous version, the following will be found in the SMS 2003 Monitor SMS Status Messages VarSet file:
LastRecordID 476743 LastRecordID_SMS_FLA 477860
The first line, which does not contain a database name, indicates the original version of status message monitoring that did not support multiple database monitoring. The second line, which does contain a database name, SMS_FLA, indicates that the current version of status message monitoring does support multiple database monitoring.
No action will be taken to utilize the first line of data, because in the multiple site database case it is difficult to determine to which database it would correspond. The first line of data is not removed from the VarSet file, because it can be of value in evaluating the new changes and insuring that status message monitoring begins with the correct RecordID after the upgrade.
SMS 2003 Monitor Site System Summarizer
Site System Summarizer
The Site System Status Summarizer is a component thread of the SMS Executive service that maintains status on all defined SMS site systems. By default, it polls once every hour, on the hour, for current status. This polling interval is defined in the SMS Site Control File. It is recommended that the polling interval not be changed. Status is maintained in a table in the SMS site database.
Site System DownSince Status
The Site System Status Summarizer assumes that a site system is down when it cannot contact the site system during one of its polling intervals. This can be due to one of the following factors:
The site system is not turned on, not connected to the network, or not functioning properly.
The SMS Site System Status Summarizer does not have a connection because no connections are available.
The SMS Site System Status Summarizer does not have sufficient access rights to connect to the site system.
Network problems are preventing the SMS Site System Status Summarizer from connecting to the site system.
The site system has been permanently taken out of service.
Site System Status Summarizer-Based Availability
Site System Status Summarizer status is used for availability reporting by the SMS 2003 Server Availability Script and SMS 2003 Server Availability Report. SMS Server availability measurements utilize the DownSince registry value for determining whether or not a server is available.
Limitations of Site System Status Summarizer-Based Availability
This section explains the limitations of using Site System Summarizer status for availability reporting by the SMS 2003 Server Availability Script and SMS 2003 Server Availability Report. SMS Server availability measurements utilize DownSince status for determining whether or not a server is available.
Site System Status Summarizer–based availability monitoring has the following limitations:
The Site System Summarizer polling interval is one hour. This interval allows sufficient time for the Site System Status Summarizer to poll all the site systems. For performance reasons, the interval cannot be changed. The summarizer’s time-out interval is controlled by the Startup Schedule property in the Site Control File, not by the Wakeup Interval property. This means that changing the Wakeup Interval property from its default value of 60 has no effect. In addition, changing the Startup Schedule has no effect. By default, it is set for every 15 minutes, and the Site System Status Summarizer polls site systems once per hour, on the hour, regardless of how the Startup Schedule is set.
The availability methodology considers a site unavailable only if two successive SMS 2003 Site System Summarizer: Site System is possibly down events occur over a period of two hours. This is designed to account for temporary network outages. This means your availability is assessed a two-hour service outage, even if the site has been unavailable for a small amount of time.
SMS can be unavailable in many ways that the Site System Status Summarizer does not monitor. For example, the Site System Status Summarizer does not consider SMS unavailable if SMS services are not running or the SMS site database is unavailable, as when the SQL Server service is stopped.
Availability data is impacted for computers hosting multiple SMS server roles. Downtime is calculated based on alerts generated for a site system being down. A single alert has a two-hour downtime weighting. The Site System Status Summarizer writes the current DownSince status for each site object and site system role hosted on a computer to the database, in the Site System Status Summarizer table.
The Site System Status Summarizer monitoring script examines each site system role in the Site System Status Summarizer table. If a site system is marked as down, it raises an event. An alert is subsequently generated based on that event. Multiple roles can generate multiple alerts, which will create extended downtime durations. This can be reflected as negative availability percentages, depending upon the interval of interest.
Each SMS server role, except for an SMS distribution point, establishes two SMS server roles by default, one for the specific role and the other for the SMS component server. For example, in the case of a site system hosting both a server locator point and a reporting point, if the server was offline for more than two hours (two Site System Status Summarizer polling intervals), the Site System Status Summarizer would mark both of these roles, and their SMS component server roles, as down.
However, only three alerts, one for each server role and one for the physical component server hosting two server roles, would be raised per polling interval for the two-hour period. This would produce a negative availability result because six hours would be marked as unavailable for the two-hour time period.
The 60-minute schedule, offset from the hour by 10 minutes, has been set as default so that the SMS 2003 Monitor Site System Summarizer script runs 10 minutes after the beginning of the Site System Status Summarizer polling interval of 1 hour. If the summarizer is taking longer than 10 minutes to complete its cycle, the timed event provider offset should be increased appropriately. Otherwise, the most current site system status messages will be missed.
SMS 2003: Monitor Management Point Availability
The SMS 2003 Monitor Management Point Availability script supports the Management Point Availability Report. This support is available only in SMS 2003 SP1. Management point availability is based on the health state of a management point and leverages the following health state value found in the registry:
DWORD value HKEY_LOCAL_MACHINE\Microsoft\SMS\MP\MPHealthState
Based on a configurable schedule and reporting interval, the script reads and then reports, through a MOM event, the duration that the state is unhealthy (registry value is 1, not 0).
These availability data events are stored first in the OnePoint database and are later transferred by the SystemCenterDTSPackageTask to the SystemCenterReporting database. A MOM report can then be run that displays the total time that the Management Point was down during a specified interval along with an availability percentage.
The MPHealthState registry value is maintained by the MP Control Manager. It is updated every six minutes.
This script performs the following actions:
Checks whether it is running under agentless managed mode. If so, the script exits without taking further action. The script uses a local VarSet file for persisting variables, so the MOM agent must be installed.
Initializes global variables.
Obtains the input parameters ScheduledInterval and ReportingInterval, in minutes.
Verifies that the input parameters are not empty, 0, or negative. If they are, a script error event is raised, indicating that a non-valid value was specified. The script also verifies that the ReportingInterval value is not less than the ScheduledInterval value. If it is, a script error event is raised indicating that ReportingInterval cannot be less than ScheduledInterval. Both values implement a Lng type and have a maximum value of 2147483647 (2G -1).
Opens and copies the contents of the SMS 2003 Monitor Management Point Availability.VarSet file into a local collection. If the file does not exist, no script error event is raised. If the file does exist but can’t be opened, a script error event is raised.
Checks the availability of the Management Point.
If the current SMS version is less than 2.50.3067.0000, the script exits with no error raised because the MPHealthState registry value is not present. The Agent Response log file, AgentResponses-Configuration Group Name.log, will contain the statement "Monitoring Management Point health is not supported on this SMS build." Logging is enabled by setting the EnableActiveDebugging DWORD value, under the HKEY_LOCAL_MACHINE\SOFTWARE\Mission Critical Software\OnePoint key, to 1.
Obtains the current Management Point Health State from registry DWORD value HKEY_LOCAL_MACHINE\Microsoft\SMS\MP\MPHealthState. If the value cannot be obtained, the script exits with no error raised because the MP Control Manager has not yet created it.
Obtains the Start Date and Time from the VarSet collection. If this is the first time the script has run and it is the start of a new reporting period, there is no entry. The script initializes the duration and the start date, in the VarSet collection, before exiting with no error raised. It sets the duration to 0 and the start date to the current date and time.
For the current reporting interval, if the MPHealthState registry value is 1, the script increments the unavailable duration in the VarSet collection, based on the specified schedule interval.
Reports, by creating an availability data event, if the reporting interval has elapsed and the management point has been unavailable. The script resets the duration to 0 and resets the start date in the VarSet collection to the current local time for the next reporting period.
If an error occurs while checking the availability of the Management Point, a script error is raised.
Event Number = 1102
Event Type = Warning
Message = "The script ‘SMS 2003 Monitor Management
Availability' running under processing rule
<ProcessingRuleName> encountered
a runtime error." CrLf "Failed to check Management
Point availability.” <ErrorString>
- Writes the contents of the VarSet collection to the local SMS 2003 Monitor Management Point Availability.VarSet file and closes the file. If the file does not exist, it is created. If no VarSet variables were set, no entries for them appear in the file. If an error occurs writing the file, the script raises a script error.
SMS 2003: Monitor SMS Inbox
SMS does most of its key server-side activities by reading from and writing to files in its inboxes. When SMS inboxes get unusually full, it’s a strong indication that SMS processing is falling behind. This could be for a variety of reasons, including but not limited to bad files, stopped processes, lack of disk space, or unusual software distribution activity level. Such problems are fairly rare, but serious for customers with a substantial number of sites.
A number of the performance counters for SMS inboxes measure the number of items queued by the service component and not the actual number of items waiting to be processed on disk. The SMS service component will update the performance counter after working through its current queue. This might cause the performance counters to update very infrequently, preventing timely detection of serious backlogs. The new SMS 2003: Monitor SMS Inbox script adds direct monitoring by counting files in critical SMS server inboxes and alerts the administrator through MOM 2005 when the number of files in a particular inbox exceeds a user configurable threshold value.
All rules are located in the SMS Site Servers – Common processing rule group, which targets these rules at central, primary, and secondary sites. You can copy these rules to other processing rule groups, such as SMS Site Servers – Primary, and disable the original rules if you choose to limit the application of the rules to a subset of your SMS site servers.
Due to performance considerations, these rules are not targeted at management points or any other SMS site system roles.
Schedule and Optional Configuration
To minimize the performance impact of inbox monitoring, the pertinent rules will be synchronized to run once per day. The rules are staggered at 15 minute intervals, beginning at 01:00 AM, so that only one rule runs at a time. For example, the first rule counts the files present in the first inbox at 01:00 AM. The next rule counts the files present in the second inbox at 01:15 AM, and so forth, until all inboxes have been counted.
You can modify this schedule following the usual steps you take in scheduling rule script execution in MOM 2005. No initial configuration is required to activate this feature. Following are optional configuration changes you can perform:
Change the default threshold value for each inbox.
Change the schedule for individual inbox rules.
Change the script’s targets to a subset of SMS servers by copying the inbox rules from the SMS Site Servers – Common rule group to other rule groups.
These optional configuration changes can be made by following the usual steps to configure threshold event rules in any management pack.
Threshold Alerts and Values
One alert is generated whenever the configured threshold value for a specific inbox rule is reached each time the monitoring rule is processed. A script error alert is generated whenever the script encounters a non-valid threshold value or an error attempting to monitor the count of files in each inbox.
The default threshold value for each inbox monitoring rule is set to 10,000. You should set threshold values for the FileCountThreshold parameter of the SMS 2003: Monitor SMS Inbox script as appropriate in your specific environment. Valid threshold values can be from 1 to 2147483647 (0x7FFFFFFF), inclusive. Invalid threshold values are zero (0) or numbers greater than 2147483647, as these will produce negative numbers in the 32-bit range.
For a description of inbox folders and how they are used in Systems Management Server, see the relevant topic at Microsoft Help and Support.
SMS 2003 Monitor SMS Executive Crash Dumps Script
This script is located in the Scripts folder of the SMS Administrator console and is named SMS 2003 Monitor SMS Executive Crash Dumps. The following actions are taken by this script:
Determines whether the target computer is running in agentless mode. If so, the script exits without further action. This script uses a local VarSet file for persisting variables, so the MOM agent must be installed on all target computers.
Opens and reads the contents of the local SMS 2003 Monitor SMS Executive Crash Dumps.VarSet file into a collection. If the file does not exist, no script error event is raised. If the file does exist but can’t be opened, a script error event is raised, with a message containing the following text:
Failed to load script variables.
Checks whether a new crash dump has occurred since the last time a check was performed. If so, the script raises an event to report the new crash dump. To raise the script error event, the script does the following:
Obtains the SMS Installation Directory from the registry under the SMS Identification key, registry value "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Identification\ Installation Directory". If the path cannot be obtained, the script raises a script error event message with the following text and exits:
Failed to read registry value.
- Constructs the full path for the CrashDumps directory by appending "\\Logs\\CrashDumps" to the retrieved SMS Installation Directory.
- Checks whether the CrashDumps directory exists. If it doesn’t, the script logs that the folder’s existence could not be verified and exits without further action. The Agent Response log file, AgentResponses-Configuration Group Name.log, will contain the statement:
<pre IsFakePre="true" xmlns="http://www.w3.org/1999/xhtml">
Failed to verify existence of crash dump
directory: <CrashDumpsPath>.
Logging is enabled by setting the EnableActiveDebugging DWORD value under the HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Mission Critical Software\\OnePoint key to a value of 1.
- Obtains the last crash dump folder creation date from the VarSet collection.
- Checks whether new crash dumps were created and acts only on the most recent one. To determine which is most recent, the saved folder creation date of the last crash dump is used, if available. Date and time comparison is based on folder creation to a resolution of one second.
- If a new crash dump occurred or if it is the first time that the script has run, the script logs and creates event 1710, specifying the new crash dump folder and path. The script saves the folder creation date of the crash dump in the VarSet collection. If a crash dump did not occur, that is logged.
- Writes the contents of the VarSet collection to the local SMS 2003 Monitor SMS Executive Crash Dumps.VarSet file and closes the file. If the file does not exist, it is created. If no VarSet variables were set, no entries for them appear in the file. If an error occurs writing the file, a script error event message with the following text is raised: Failed to save script variables.
SMS 2003 Monitoring SMS Executive Crash Dump Event
The SMS 2003 Monitor SMS Executive Crash Dumps script reports through event 1710 that a crash has occurred, as described below:
EventType = Error EventNumber = 1710 Category = SMS Site Code Description = SMS Executive in site “XXX” has crashed. For details, see crash dump information under <Drive> \SMS\Logs\CrashDumps\NewFolder.
SMS 2003 Monitoring SMS Executive Crash Dumps Script Error Event
The “SMS 2003 Monitor SMS Executive Crash Dumps” script reports runtime script errors through event 1102.
EventType = Warning EventNumber = 1102 Description = The script “SMS 2003 Monitor SMS Executive Crash Dumps” running under processing ruleSMS 2003 Crash Dumps: Monitoring SMS Executiveencountered a runtime error. CrLf “Failed to <Message>." ErrorString
SMS 2003 Server Availability Script
SMS is a critical enterprise application for desktop configuration management. Customers need to track its service availability. The Management Pack provides a sample Microsoft SQL Server™ script for computing SMS site system availability based on alerts that are raised in response to a down status from the SMS Site System Status Summarizer. Availability can be determined over any number of specified days. This metric can be used in support of established service level agreements (SLAs).
Limitations of the SMS 2003 Server Availability Script
The SMS 2003 Server Availability Script has the following limitations.
The displayed data is limited to the MOM database grooming interval. By default, the script returns data for the last seven days, and for the last 30 days. However, the OnePoint database has a grooming interval of 4 days, so executing the script with seven- and 30-day intervals returns the same results. If reports reflecting longer time periods are required it will be necessary to increase the grooming interval or use the SMS 2003 Server Availability Report which executes against the SystemCenterReporting database which is the long-term storage for operational data. For smaller periods of time the 7 and 30 day intervals in the script need to be changed.
Running the SMS 2003 Server Availability Script
The SMS 2003 server availability script is a SQL script that returns the availability of SMS site systems during a specified interval. A SQL administrator can run the script or create and schedule the stored procedure that runs against the MOM OnePoint database. Before running the SQL script, you must copy it from the MOM Administrator console and paste it into a text file with a .sql file name extension.
To create an executable version of the script
In the MOM Administrator console, navigate to Microsoft Operations Manager, Management Packs, Rule Groups, and then click Scripts.
In the Details pane, double-click the SMS 2003 Server Availability script.
In the Script Properties dialog box, click the Script tab.
To select all the text in the script, press CTRL+A.
To copy all the text to the Clipboard, press CTRL+C.
Paste the text into a text editor, such as Notepad, and save the script with a .sql file name extension.
.gif "note.gif")
Note
Some text editors automatically append a .txt file name extension to all documents. Verify that the file name extension is .sql.
After you have created the SQL script, the database administrator can run it on the server running MOM against the MOM (OnePoint) database. The database administrator must have read/write access to the MOM (OnePoint) database to create and drop (that is, remove) the stored procedure.
If the script is to be scheduled, the database administrator should create the stored procedure by commenting out the bottom sections that run and then drop the stored procedure. When the procedure exists, the database administrator can run it as many times as needed. To delete the procedure, run the script again and comment out all sections except dropping the procedure.
Script Algorithm
Once every hour, the site system summarizer attempts to contact each site system. If it is unable to contact a site system, it lists that computer as down in the Site System Status Summarizer table. To reduce the number of false reports for this condition, the Management Pack consolidates events and raises an alert only if there are two events in a two-hour period. When you run the stored procedure, it calculates the number of “Site System is possibly down” alerts that are raised during the specified number of days, subtracts the downtime from the total time available, and returns a percentage of availability for that period. If a computer has not logged any “Site System is possibly down” alerts during the specified interval, its calculated availability is 100%.
You do not need to run the script more frequently than every seven days, unless you want to see a daily trend.
By default, the script returns data for the last seven days and for the last 30 days. By specifying a longer data interval, a more accurate estimate of the server uptime is provided. Do not set the intervals to a time period longer than the MOM database grooming cycle.
The following examples show how the server availability goes up as the data is averaged over a longer time period:
If there are two events generated for a computer within two hours, one alert is generated. If one alert is generated within the last seven days, the calculations are as follows:
Total number of hours in seven days = 7 * 24 = 168
Total number of hours down = 1 * 2 = 2
Total number of hours up = (168 - 2) = 166
Percentage availability = (166 / 168) * 100 = 98.809%
If one alert is generated within the last 30 days, the calculations are as follows:
Total number of hours in 30 days = 30 * 24 = 720
Total number of hours down = 1 * 2 = 2
Total number of hours up = (720 - 2) = 718
Percentage availability = (718 / 720) * 100 = 99.72%
If one alert is generated within the last 84 days, the calculations are as follows:
Total number of hours in 84 days = 84 * 24 = 2016
Total number of hours down = 1 * 2 = 2
Total number of hours up = (2016 - 2) = 2014
Percentage availability = (2014 / 2016) * 100 = 99.9%
The following examples show how the server availability changes as more alerts are logged over the same time period:
If two alerts are generated within the last 30 days, the calculations are as follows:
Total number of hours in 30 days = 30 * 24 = 720
Total number of hours down = 2 * 2 = 4
Total number of hours up = (720 - 4) = 716
Percentage availability = (716 / 720) * 100 = 99.44%
If three alerts are generated within the last 30 days, the calculations are as follows:
Total number of hours in 30 days = 30 * 24 = 720
Total number of hours down = 3 * 2 = 6
Total number of hours up = (720 - 6) = 714
Percentage availability = (714 / 720) * 100 = 99.16%
The polling interval of the Site System Status Summarizer is fixed at one hour and cannot be changed through the SMS Administrator console. Modifying this interval does not improve the accuracy of this script. Changing the event consolidation interval is possible, but not recommended because it does not improve the accuracy of the result. In fact, reducing the consolidation interval makes the results less reliable because the two-hour consolidation interval reduces false results due to a momentary network outage.
Public Views for MOM 2005
Each view that MOM provides displays dynamic information in a results window. You can select a specific item in the results display and, depending on the view, additional details are displayed in a details window.
The views that MOM provides display dynamic information for each view in a results window. You can select a specific item in the results display, and depending on the view, additional details are displayed in a details window.
MOM 2005 provides the following views that you can use and customize when you’re working with the Operator console.
Alerts The Alerts view is divided into two categories, Alerts and Service Level Exceptions. These views display all the alerts in both categories. This view displays summary information in a results window and expanded information for a specific alert in a details window.
State The State view shows aggregated information about alerts and their associated entities, for example, computer groups, computers, and application instances. The State view uses the results, details window pair.
Events The Events view is divided into two categories: Events and Task status for the tasks that you run from the Operator console. This view shows all categories of events that are generated and uses the results, details windows pair.
Performance The Computer Performance view is generated in stages. First, you select the computer that you want to work with from a list of computers in the initial view window. Then, you select the performance counters that you want to graph. The final view displays the graph in the results windows for the view and the accompanying details windows displays information about each counter in the graph.
Computers and Groups The Computers and Groups view uses two categories, Computer Groups and Computers. This view uses the results, details windows pair to display information.
Diagram The Diagram view uses a single window to generate a topology diagram that is based on your management group and the Management Pack(s) that is selected.
My Views My Views displays any custom views that you create. You can nest your views and incorporate any of the views that we just described.
Public Views Public views provide another way of working with the views. All the views described here, excluding My Views, are displayed as a navigation tree.
Note
The performance measure rules associated with the views for MOM 2005 are disabled by default. You must enable the rules to have the associated view populated with data.
Views for Microsoft SMS 2003
The SMS 2003 Management Pack provides several categories of views.
For more information about working with views, see the Tuning the Management Pack, Performance Monitoring and Daily Tasks sections in this guide. In addition, you can refer to the MOM 2005 Management Pack documentation for more information about how to modify existing rules or create new views.
The SMS 2003 Management Pack provides the following common views:
Alerts
Computer Groups
Computers
Events
Performance
Service Level Exceptions
State
Task Status
The following views, customized for SMS 2003, are also provided:
Availability
- Computers with no heartbeat in the last three periods (15 minutes)
Diagram
- SMS 2003 Hierarchy
General
Advanced Client Versions detected in the last 24 hours
Alerts from the SMS Central Site Server in the last 72 hours
Alerts that are New in the last 72 hours
Events that generated Alerts in the last 72 hours
Legacy Client Versions detected in the last 24 hours
Site Server Site Codes detected in last 24 hours
Site Server Versions detected in last 24 hours
UI Versions detected in last 24 hours
Versions detected in last 24 hours
Performance Views
It is possible to configure Views to display data for particular computers on a per-view basis. To do this, it is recommended that you copy the view that you want to customize to My Views, rename the view, and begin customizing the view to your requirements. The complexity of the graph can be reduced by individually selecting the counter for the computers of interest.
Backlogs\Management Points
DDR Backlog in the last 48 hours
FileCollection Backlog in the last 48 hours
HINV Backlog in the last 48 hours
Relay Backlog in the last 48 hours
SINV Backlog in the last 48 hours
Status Backlog in the last 48 hours
Backlogs\Site Servers
DDR Backlog in the last 48 hours
HINV Backlog in the last 48 hours
Scheduler Jobs Backlog in the last 48 hours
Scheduler Send Requests Backlog in the last 48 hours
SINV Backlog in the last 48 hours
SWM Backlog in the last 48 hours
General\Management Point Servers
LogicalDisk in the last 48 hours
Memory in the last 48 hours
Processor in the last 48 hours
General\Site Servers
LogicalDisk in the last 48 hours
Memory in the last 48 hours
Processor in the last 48 hours
Note
The performance provider for the LogicalDisk in the last 48 hours view is installed with the Microsoft Windows Servers Base Operating System Management Pack.
Processing Rates\Management Point Servers
*All Message Processing Rates on an SMS 2003 Management Point Server in the last 24 hours
*All Report Processing Rates on an SMS 2003 Management Point Server in the last 24 hours
*All Report Processing Rates on an SMS 2003 Site Server in the last 24 hours
DDRs/sec. in the last 24 hours
DM Database Connection Attempts/sec. in the last 24 hours
DM DDRs/sec. in the last 24 hours
DM Discovery Translation Requests/sec. in the last 24 hours
DM DP Locations/sec. in the last 24 hours
DM Hardware Inventory Translation Requests/sec. in the last 24 hours
DM HINVs/sec. in the last 24 hours
DM ISAPI Requests/sec. in the last 24 hours
DM Machine Setting Requests/sec. in the last 24 hours
DM Package Version Requests/sec. in the last 24 hours
DM SINVs/sec. in the last 24 hours
DM Software Policy Body Requests/sec. in the last 24 hours
DM Software Policy ID Requests/sec. in the last 24 hours
DM Status/sec. in the last 24 hours
DM Total Setting Requests/sec. in the last 24 hours
DP Locations/sec. in the last 24 hours
GetAuth Requests/sec. in the last 24 hours
GetPolicy Requests/sec. in the last 24 hours
HINVs/sec. in the last 24 hours
ISAPI Requests/sec. in the last 24 hours
MP Locations/sec. in the last 24 hours
PA Requests/sec. in the last 24 hours
Relay Reports/sec. in the last 24 hours
SINVs/sec. in the last 24 hours
SPs Executed/sec. in the last 24 hours
Status/sec. in the last 24 hours
Total DDRs in the last 24 hours
Total DM DDRs in the last 24 hours
Total DM HINVs in the last 24 hours
Total DM ISAPI Requests Dispatched in the last 24 hours
Total DM ISAPI Requests Received in the last 24 hours
Total DM SINVs in the last 24 hours
Total DM Status in the last 24 hours
Total HINVs in the last 24 hours
Total Relay Reports in the last 24 hours
Total SINVs in the last 24 hours
Total Status in the last 24 hours
Processing Rates\Site Database Servers
- SMS 2003 Site Database Servers – SQL Server User connections in the last 24 hours
Processing Rates\Site Servers
DDRs/minute in the last 24 hours
HINVs/minute in the last 24 hours
SINVs/minute in the last 24 hours
Status/minute in the last 24 hours
SWMs/minute in the last 24 hours
Total DDRs in the last 24 hours
Total HINVs in the last 24 hours
Total SINVs in the last 24 hours
Total Status in the last 24 hours
Total SWMs in the last 24 hours
Diagrams
The SMS 2003 Management Pack provides a topology diagram for its SMS hierarchy. Site servers and site systems are displayed showing their relationships to each other with context-sensitive information. Since SMS 2003 hierarchies can be large, you can scope the view of your hierarchy to any SMS 2003 computer group by using the Group filter.
In order for the topology discovery to produce a diagram of your SMS 2003 hierarchy, SMS Provider computers must be managed, an agent must be installed on these computers, and agent proxying for other computers must be enabled. Also, for connectors to be displayed between site servers and site systems, the site systems must have been discovered by an SMS discovery process and must be members of the All Systems collection.
Discovery is performed on a per-site basis from primary sites, and secondary sites are discovered as part of parent primary discovery. The discovery data is provided through Tool Tips and server annotations. In addition, diagrams can be exported to a Microsoft Visio® file format.
Tool Tips provide summary computer information and status by pausing over a selected computer or connector. The information displayed for a computer Tool Tips includes:
IPAddress
Operating system version
Components, for instance CAP, database, distribution point, management point, provider, reporting point, sender, server locator point, and site server.
Site code
Version
Status
Tool information displayed for a connector between a site server and site system includes:
Connector name i.e. Domain\SiteServerNetbiosName - Domain\SiteSystemNetbiosName
Connector type
"Site Server to Site Server“
"Site Server to Site System"
SMS Server Topology Image Annotations
Icons for Server Types
Database Server Type: site database
Site System Type: management point
Server Type: central site, primary site, secondary site and site system
Connector Lines
Connector line color and style denote the type of relationship two computers have:
The Site Server to Site Server connector is a black solid line.
The Site Server to Site System connector is a blue dashed line.
Reports
MOM 2005 features a completely redesigned reporting infrastructure based on SQL Server Reporting Services. MOM 2005 provides the ability to include reports as part of Management Packs.
MOM Reporting Architecture
The key highlights of the MOM 2005 reporting infrastructure include:
Dedicated data warehouse: In addition to providing long-term data storage capability, the dedicated data warehouse also provides performance improvements produced by a normalized schema optimized for reporting, and isolation from the production database.
SQL Server Reporting Services for reporting: The use of SQL Server Reporting provides a number of features, including easier extensibility and customizability, report-level security, report scheduling and Web-based reporting.
Data Transformation Services (DTS): The DTS job runs once per day, at 0:100 by default, to transfer operational data from the MOM database to the data warehouse. Displayed report data can be up to 24 hours old, unless the DTS job schedule is changed or runs immediately prior to the report.
Web-based Reporting Console: To access the console, in the MOM Administrator console, click Operations, and then click Reporting Console. The Reporting console displays the Microsoft Operations Manager Reporting Web page, which contains the report folders for all installed Management Packs.
SMS Reporting
Reports are organized under the Systems Management Server (SMS) 2003 folder in two subfolders, Availability and Performance. Performance reports are grouped by the following SMS components, or SMS server roles: SMS site servers, SMS management points and SMS site database servers.
The list of available computers for a given report belongs to the corresponding computer group.
The list of available computers for a given report will belong to the corresponding computer group. Each report can be customized by selecting a Computer Name where applicable, and a date range, by completing the Begin Date and End Date fields.
Each report can be customized by selecting a Computer Name where applicable, and a date range, by completing the Begin Date and End Date fields.
You can choose among seven exportable formats for your reports.
Availability
Two reports are available in the Availability subfolder.
Server Availability Report
The Server Availability Report implements the algorithm of the SMS 2003 Server Availability script for a user-specified time period. Its availability calculation includes all SMS 2003 Site System Summarizer: Site System is possibly down alerts raised during the specified time period. You should use care when specifying the time period because a single alert will have a 2 hour weighting on the availability calculation for that time span.
The following limitations exist for the Server Availability Report:
Each alert is based on Alert Raised Time. The alert represents that the site system has been down for the previous 2 hours. It is therefore possible to specify a period less than two hours in which the alert was raised and have a negative availability percentage displayed.
The report runs against the SystemCenterReporting database. Data from the OnePoint database is transferred to the SystemCenterReporting database once per day at 01:00 AM by default. The report is capable of reflecting long term availability but not short term availability, for example, daily availability.
Management Point Availability Report
The Management Point Availability Report is based upon the health state of a management point. The report leverages the health status of the management point which the SMS 2003 Monitor Management Point Availability script monitors. Status is reported through Availability Data Event 1701. These availability data events are first stored in the OnePoint database and then transferred by the SystemCenterDTSPackageTask * *to the SystemCenterReporting database. The default setting for this task is once every day at 01:00 AM. Once the data is transferred, the report is run, and displays the total time that the management point was down during a user-specified interval along with an availability percentage.
The Management Point Health State is maintained by the MP Control Manager. It is updated every six minutes. This support is only available in SMS 2003 SP1.
The following limitations exist for the Management Point Availability report:
The report is capable of reflecting long term availability but not short term, daily availability.
The report displays data based upon the selected Begin and End dates and times. These dates are the time filter for the event data in the database. All event data with dates and times between the Begin and End dates and times, inclusively, will be used in calculating the downtime duration and availability. Therefore, if an event has a start and end date and time that overlaps either the Begin or End dates, it will not be included in the report results. Consequently, selection of begin and end dates should be done based upon the configured reporting interval and the number of possible sample points with the duration.
The MP Control Manager Health state monitoring interval is once every six minutes, and is not configurable.
The report can be disabled by changing the rule ID for SMS 2003 Management Point Availability: Monitoring by copying the rule or creating a new rule and deleting or disabling the shipped rule. The rule ID of the SMS 2003 Management Point Availability: Monitoring rule, not the script name, identifies the source of the event 1701. Therefore, this rule ID cannot be changed.
Management point availability monitoring can be stopped by disabling either of these rules:
SMS 2003 Management Point Availability: Monitoring
SMS 2003 Management Point Availability: Collect event data
Consideration must be taken when choosing the values for the ReportingInterval and ScheduledInterval script input parameters for the SMS 2003 Monitor Management Point Availability script. Their default values are set to thirty and to five minutes, respectively.
If the ScheduledInterval value is changed, the timed provider for the SMS 2003 Management Point Availability: Monitoring rule must be changed to match. In addition, the provider must be synchronous so that predictable script execution is guaranteed, because the script uses the ScheduledInterval value to increment the total duration that the management point was found to be unavailable.
Timeliness of the availability data is dictated by the ReportingInterval value. It must be equal to, or greater than, the ScheduledInterval value. The ReportingInterval should be set to satisfy the timeliness requirement of the reporting, while minimizing the number of events created.
Performance
SMS 2003 Management Point Servers
Discovery Data Record (DDR) Backlog
Discovery Data Records (DDRs) Processed per Second
Distribution Point Locations Provided per Second
File Collection Backlog
GetAuth Requests Processed per Second
GetPolicy Requests Processed per Second
Hardware Inventory Backlog
Hardware Inventory Records Processed per Second
ISAPI Requests Processed per Second
Management Point Locations Provided per Second
Policy Assignment Requests Processed per Second
Relay Manager Report Backlog
Relay Manager Reports Processed per Second
Software Inventory Backlog
Software Inventory Records Processed per Second
Status Message Backlog
Status Messages Processed per Second
Stored Procedures Executed per Second
Total Discovery Data Records Processed
Total Hardware Inventory Records Processed
Total Relay Manager Reports Processed
Total Software Inventory Records Processed
Total Status Messages Processed
SMS 2003 Site Database Servers
- SQL Server User Connections
SMS 2003 Site Servers
Discovery Data Record (DDR) Backlog
Discovery Data Records (DDRs) Processed per Minute
Hardware Inventory Backlog
Hardware Inventory Records Processed per Minute
Scheduler Job Backlog
Scheduler Send Request Backlog
Software Inventory Backlog
Software Inventory Records Processed per Minute
Software Metering Backlog
Software Metering Reports Processed per Minute
Status Messages Processed per Second
Total Discovery Data Records Processed
Total Hardware Inventory Records Processed
Total Software Inventory Records Processed
Total Software Metering Reports Processed
Total Status Messages Processed
Tasks
SMS Administrator console tasks require installation of the Microsoft Systems Management Server (SMS) 2003 SP1 or later Administrator console on the same computer as the Microsoft Operations Manager(MOM) 2005 Operations console. After installation of the SMS Administrator console, you must log off and log on again to Windows to enable task functionality.
Table T.1 Management Pack Tasks
Task |
Description |
|---|---|
SMS Administrator console |
Opens the SMS Administrator console directed at the currently selected computer. This applies to computers hosting the SMS site server role. |
All SMS status messages |
Prompts for the computer’s site server, opens a MMC window, and executes a status message query to return all status messages associated with the currently selected computer. This applies to all systems. |
SMS Service Manager |
Opens the SMS Service Manager directed to the currently selected computer. This applies to computers hosting the SMS site server role. |
SMS Resource Explorer |
Prompts for the computer’s site server, opens a MMC window with the SMS Resource Explorer displaying the data for the currently selected computer. This applies to all systems. |