The IIS management pack raises alerts if application pools or web applications are non-functional. In many environments it is common to have both default application pools and default web applications which are often not used but have not been removed from the environment. The best practice approach to these is to back the system up, and remove both the default application pool and the default web applications if they are truly not in use. So this article isn’t necessarily best practice but if you have a large number of servers which you want to ignore either the default application pools or default web applications this may be helpful.

So how do we ignore the default application pools and / or default web applications? AKA: How to ignore default application pools (or websites, etc.) using a dynamic group and overrides.

To do this we start we can create a group for “default application pools” and a group for “default web applications” for tuning.

The screenshot below shows a dynamic group for the Default Application Pools which is based upon the Display Name of “DefaultAppPool” for either IIS 7 Application Pools or IIS 2003 Application Pools.


The screenshot below shows a dynamic group for the Default Web Sites contains the name “Default”  for either IIS 7 Web Sites or IIS 2003 Web Sites.


After we have created these groups we can use these to disable the following monitors for these groups:

“Application Pool availability”

“A Windows Internet Information Service Application Pool is Unavailable”

“Web Site Availability”

“A Windows Internet Information Service Web Site is Unavailable”

Summary: Looking for a way to ignore alerts related to the default application pools and web sites? Consider making dynamic groups and disabling the monitors for those groups.