Best Practices for System Center 2012 Monitoring Pack for Microsoft Windows Server 2012 Internet Information Service 8

Troubleshooting the System Center Operations Manager (SCOM) 2012 Management Pack for IIS 8 on Windows Server 2012 focuses on fixing common integration bugs, script timeouts, discovery failures, and account permissions. Common Known Bugs & Updates

False IIS Admin Service Alerts: Early versions of the management pack contained a known bug that triggered false critical alerts for the IIS Admin Service. If you encounter these, verify your Management Pack version and upgrade to the finalized release (version 7.0.10249.2 or later) via the Microsoft Download Center.

Uninstall False Alerts: Older builds generated false active alerts when IIS was completely uninstalled from a server. Ensure the latest update is applied to fix the underlying workflows.

Exit Code 87 Error: The “List FTP Sites” task in the IIS 8 FTP Server Class historically returned an exit code “87” instead of a successful “0”. This requires the final October 2020 hotfix update to resolve. Missing Prerequisite Discoveries

Operating System MP Requirement: The IIS 8 Management Pack relies entirely on the underlying Windows Server 2012 Operating System Management Pack. If the OS Discovery Management Pack is missing, corrupted, or not imported beforehand, SCOM will fail to discover your IIS 8 Web Sites, Application Pools, and FTP servers. Permissions and Run As Accounts

Local Administrator Rights: The SCOM action account running on the monitored Windows Server 2012 agent must have local administrative rights to read the IIS configuration (applicationHost.config) and query the IIS WMI provider.

WMI Namespace Access: If discoveries fail silently, verify that the SCOM agent account has appropriate permissions to query the Root\WebAdministration WMI namespace. Run Get-CimInstance -Namespace Root\WebAdministration -ClassName WorkerProcess from a local PowerShell console to verify functionality. Performance & Script Churn

Frequent Configuration Churn: IIS environments with thousands of dynamic application pools can trigger continuous SCOM discovery changes, causing high CPU on management servers and excessive database usage. You can troubleshoot this by checking the Management Server event logs or data warehouse reports to identify “configuration churn”, then override the discovery interval from the default to a less frequent schedule (e.g., every 24 hours).

Script Timeouts: Monitoring scripts running against complex IIS sites might time out under load. Check the Operations Manager event log on the agent machine for Event ID 21405 or Event ID 4507, which indicate that an IIS monitoring script was terminated due to a timeout. You can resolve this by configuring a SCOM management pack override to increase the “Timeout Seconds” parameter for the failing rule or monitor.