Does a Status Filter Rule Stop the Component Status from Entering a Warning or Error State?

Recently I published a blog post called Turning Off the Windows Firewall Warning Message in Configuration Manager 2012. In that blog post I noted that my client’s Component Status was always unhealthy because of the firewall being turned off. Rob Marshall @RobMVP, a fellow Enterprise Client Management MVP, sent me an email asking why I didn’t use a status filter rule to stop the status messages.

To be honest I hadn’t thought about doing that, so I tested it out. After putting a status filter rule in place, I discovered that it was only partially successful because it didn’t stop the status messages from occurring. It did, however, stop Component Status from entering a warning or error state.

Does a Status Filter Rule Stop the Component Status from Entering a Warning or Error State

Thanks to Rob’s advice, I was able to achieve my client’s goal of always keeping their system status healthy! Now, what to do about those pesky status messages? If you want this problem to be fixed permanently, like I do, make sure to vote up my Connect feedback item. https://connect.microsoft.com/ConfigurationManagervnext/feedback/details/1045929

As I discovered, status filter rules can be very helpful, so in tomorrow’s blog post, How to Create a Status Filter Rule to Prevent Component Status from Entering a Warning or Error State, I’ll tell you how I set-up this particular rule. In the meantime, if you have any questions, please leave me a note in the comment section below.

Comments
pingbacks / trackbacks

Leave a Comment

Share via
Copy link