SMS components and site systems generate a
constant stream of status messages. Most of these messages will prove
to be extremely helpful in resolving issues or troubleshooting problems
you might be having with your SMS site. Some messages, however, might
simply be flooding the Status Message Viewer with interesting but not
particularly useful information, or too much information, or not the
kind of information you’re looking for.
1. Configuring Status Reporting Properties
To
configure the status reporting component properties, in the SMS
Administrator Console, expand the Site Settings node and then select
the Component Configuration node. Right-click Status Reporting and
choose Properties from the context menu to display the Status Reporting
Properties dialog box, as shown in Figure 1.
By default, reporting is enabled for both the site server and the client components for the following types of messages:
By
selecting the appropriate message types from the drop-down lists, you
can control how much data is reported. For example, to only show
milestone messages that are errors or warnings, select the Error And
Warning Milestones option from the drop-down list in the Server
Component Status Reporting frame of the dialog box.
Caution
The
default settings for message reporting are considered appropriate for
most SMS sites. Enabling too many messages or filtering out too much
information can make the status message system less effective as a
problem-solving tool. |
The
Report Details On Failure option is also selected by default. This
powerful feature ensures that when a failure occurs or an error is
reported, the affected component reports details as to the nature of
the failure as well as possible causes and remedies. You will probably
not want to disable this feature—unless, of course, you can
troubleshoot without knowing the details of a problem.
You
can also enable logging for the same message types to the Windows Event
Log and include failure details in the log by selecting those options.
