In my blog post, Does a Status Filter Rule Stop the Component Status from Entering a Warning or Error State? I talked about how I used a status filter rule to prevent the Component Status from entering a warning or error state. I needed to put a rule in place because a client of mine had Windows Firewall disabled on all servers, and needed their system status to be healthy all of the time. With Windows Firewall turned off you get the following warning message every hour and Component Status is immediately thrown into a warning state:
SMS_HIERARCHY_MANAGER reports (Message ID=3353): “Hierarchy Monitoring detected that the ConfigMgr SQL Server <fqdn> ports 1433, 4022, are not active on Firewall exception.” This blog post will show you the steps that I took to stop the Component Status from entering a warning state.
1. In the Configuration Manager 2012 (CM12) console in the Administration | Overview | Site Configuration | Sites node, click on the Status Filter Rules.
Note: The procedures are similar in the CM07 console. In the CM07 console, however, you must click on the New Status Filter Rule link to start the Wizard. See the screenshot below.
2. Click Create…
3. Provide a name for the rule, select the Component and the Message ID check box. Enter the appropriate details, and then click Next.
4. Check Do not forward to status summarizers, and then click Next.
5. Click Next.
6. Click Close.
7. Click OK.
From this point forward Component Status will not enter a warning or error state due to this status message:
SMS_HIERARCHY_MANAGER reports (Message ID=3353): “Hierarchy Monitoring detected that the ConfigMgr SQL Server <fqdn> ports 1433, 4022, are not active on Firewall exception.” Keep in mind that these status messages will still exist and can be viewed when reviewing the component status. Several months from now you may forget that you created a status filter rule, or that these messages exist, so it may undoubtedly cause confusion.
I encourage you to vote up the Connect item (see link below) to solve this particular status message issue permanently.
Thank you, again, to Rob Marshall @RobMVP for his suggestion about setting up a status filter rule.