Sample Status Filter Rules

  • Article

Earlier in this chapter, you were introduced to five example status filter rules. This section provides instructions for creating each of these filter rules. Some of these examples might be directly applicable to a problem you face, and others might be less useful to you. By reading each of them, you gain a better understanding of how to use status filter rules for your organization.

If you decide to use some of these example rules at one of your sites, ensure that you examine the existing rules to see the status messages they match, the actions they perform, and their priority relative to your new rules. If your new rules are lower priority than existing ones, then the existing rules are processed before your new rules and might interfere with what you are trying to accomplish with the new rules. However, you can change the priority order.

To configure status filter rules, navigate to Status Filter Rules in the SMS Administrator console.

Where?

Systems Management Server > Site Database (site code - site name) >Site Hierarchy>site code - site name >Site Settings>Status Filter Rules

Right-click Status Filter Rules, point to New, and click Status Filter Rule. Each of the examples below assumes that you know how to access the Status Filter Rule Properties dialog box.

To discard status messages from a component that is flooding the system with the same status message multiple times

  1. Create a new status filter rule.

  2. On the General tab, in the Name box, enter Throw away status message X from component Y on system < computer name >, where X is the Message ID of the message you want to discard, and Y is the name of the component that is generating it.

  3. Click Site system. Type the name of the computer the component is running on.

  4. Click Component and enter the name of the component, Y. Click Message ID and enter in the Message ID of the status message, X.

  5. Verify that no other items are selected. Click the Actions tab.

  6. Click Do not forward to status summarizers. Click Do not process lower-priority status filter rules. Verify that no other items are selected, and then click OK.

  7. In the Status Filter Rules results pane, right-click the new rule and select Increment Priority until the new rule is the first one in the list.

    This step ensures that Status Manager processes each status message against this filter rule first. Because the rule specifies Do not process lower-priority status filter rules, none of the other rules have the opportunity to write the message to the SMS site database, or replicate it to the parent site.

To replicate error status messages to the parent site at high replication priority and replicate all other status messages at low replication priority

  1. Create a new status filter rule. On the General tab, in the Name box, type Replicate Error status messages at High priority.

  2. Click Message Type and select Error. Verify that no other items are selected.

  3. Select the Actions tab. Click Replicate to the parent site and set the priority to High. Verify that no other items are selected.

  4. Create a second new status filter rule. On the General tab, in the Name box, enter Replicate all status messages at low priority. Verify that no other items are selected.

  5. Click the Actions tab. Click Replicate to the parent site and set the replication priority to Low. Verify that no other items are selected.

  6. In the Status Filter Rules results pane, use the Increment Priority or Decrement Priority options until Replicate Error status messages at High priority is listed above Replicate all status messages at Low priority.

The first rule matches all Error status messages and causes Status Manager to replicate them at high priority. The second rule matches all status messages and causes the Status Manager to replicate the messages at low priority. Because the first rule is higher priority than the second, it overrides the second rule and causes Status Manager to replicate the status messages at high priority instead of low priority.

To not replicate status messages from the SMS Client to the parent site, but replicate all other status messages

  1. Create a new status filter rule.

  2. On the General tab, in the Name box, type Do not replicate SMS Client status messages. Click Source and select SMS Client. Verify that no other items are selected.

  3. Click the Actions tab. Click Do not process lower-priority status filter rules. Click any other options as appropriate, but do not select Replicate to parent site.

  4. Create a second new status filter rule.

  5. On the General tab, in the Name box, type Replicate all other status messages. Verify that no other items are selected.

  6. Click the Actions tab. Click Replicate to the parent site and select a replication priority. Choose any other options as appropriate. Click OK.

  7. In the Status Filter Rules results pane, use the Increment Priority or Decrement Priority options until the first new rule is above the second new rule.

The first rule matches all status messages from the SMS client and prevents Status Manager from replicating them. The second rule matches all status messages and causes Status Manager to replicate them at the priority you chose. Because the first rule is higher priority than the second, it overrides the second rule in the case of status messages from the SMS client computer and prevents Status Manager from replicating them.

If you had not specified Do not process lower-priority status filter rules in the first rule, the second rule would cause Status Manager to replicate SMS Client status messages. This nuance might not appeal to you, or it might complicate the other rules you want to define. An alternative way to express what this example seeks to accomplish is "Replicate status messages from the SMS server and SMS Provider, but do not replicate SMS client status messages."

To replicate status messages from the SMS Server and SMS Provider, but not replicate SMS client status messages

  1. Create a new status filter rule.

  2. On the General tab, in the Name box type Replicate SMS Server status messages. Click Source and select SMS Server. Verify that no other items are selected.

  3. Click the Actions tab. Click Replicate to the parent site and select an appropriate replication priority. Verify that no other items are selected.

  4. Create a new status filter rule.

  5. On the General tab, in the Name box, type Replicate SMS Provider status messages. Click Source and select SMS Provider. Verify that no other items are selected.

  6. Click the Actions tab. Click Replicate to the parent site and select an appropriate replication priority. Verify that no other items are selected.

The first rule matches all status messages from the SMS Server and causes Status Manager to replicate them at the priority you chose. The second rule matches all status messages from the SMS Provider and causes Status Manager to replicate them at the priority you chose. It does not matter which rule is higher priority than the other, because they are mutually exclusive, as a status message cannot be from both the SMS Server and the SMS Provider. These two rules might appeal to you more than the first two example rules because these two do not involve the Do not process lower-priority status filter rules option.

To alert you via the "net send" command when a particular component reports an Error status message

  1. Create a new status filter rule.

  2. On the General tab, in the Name box, enter Alert me when the Inbox Manager component reports any Error status messages.

  3. Click Component and select Inbox Manager from the drop-down box. Click Severity and select Error. Verify that no other items are selected.

  4. Select the Actions tab.

  5. Click Run a program, and in the Program box, type the following:

    C:\Winnt\System32\Net.exe send % sitesvr Component %msgcomp running on computer % msgsys reported the following error: %msgdesc

    Replace C:\winnt\system32 with the appropriate path to the system32 directory on your site server.

  6. Verify that no other items are selected. Click OK.

  7. In the Status Filter Rules results pane, select the new rule and right-click Increment Priority until the new rule is the first one in the list. This ensures that Status Manager processes this rule first, which prevents any of the existing rules from interfering with it. This rule causes any Error status messages processed by Status Manager that come from Inbox Manager to pop up as messages on the site server console.

The criteria that you specified on the General tab do not include a site code or a system name. You are alerted when Status Manager processes a status message from Inbox Manager running on any computer at any site, including child sites. To restrict the alerting to components from a specific computer or site, check the System or Site Code boxes on the General tab as appropriate.

To keep status messages associated with a particular advertisement in the SMS site database for 30 days, but keep other status messages for only seven days

  1. Create a new status filter rule.

  2. On the General tab, in the Name box, enter Keep status messages for Advertisement X in the database for 30 days, where X is the Offer ID for the advertisement whose messages you would like stored for 30 days.

  3. Note

    • Offer ID and Advertisement ID are the same.

  1. Click Source and select SMS Client. Click Property name and select Offer ID. Click Property value and type in the Offer ID value. Verify that no other items are selected.

  2. Click the Actions tab. Click Write to the site database and select 30 in the Allow user to delete messages after: days dialog box. Verify that no other items are selected.

  3. Create a new status filter rule.

  4. On the General tab, in the Name box, enter Keep all other status messages in the database for 7 days. Verify that no other items are selected.

  5. Click the Actions tab. Click Write to the site database and select 7 in the Allow user to delete messages after: days dialog box.

  6. Verify that no other items are selected.

  7. In the Status Filter Rules details pane, use the Increment Priority or Decrement Priority options until the first new rule is above the second new rule.

The first rule matches all status messages from the SMS client that are associated with the advertisement you specified and causes Status Manager to keep them in the site database for 30 days. The second rule matches all status messages and causes Status Manager to keep them in the database for only seven days. Because the first rule has higher priority than the second, it overrides the second rule in the case of status messages from the SMS client that are associated with your advertisement and cause Status Manager to keep them in the database for 30 days instead of seven days.

In the previous example, you had to specify a source to be able to specify Property name and Property value. This means that to keep messages from the SMS Server or SMS Provider that are associated with your advertisement for 30 days instead of seven, you must create an additional rule for the SMS Server and another for the SMS Provider. If you want to keep status messages from the SMS client that are associated with any advertisement for 30 days, you would leave Property value cleared.

For More Information

Did you find this information useful? Please send your suggestions and comments about the documentation to smsdocs@microsoft.com