Monitoring IIS on Server 2000/2003: Internet Information Services Management Pack Overview

How to Install and Configure the Server ⁄₂₀₀₃ IIS Management Pack

Overview

This guide explains how to install and configure the Internet Information Services (IIS) Management Pack for Windows Server ⁄₂₀₀₃ so you can monitor IIS performance, availability, and key events from System Center (or similar monitoring tools). Assumes a working Operations Manager environment (or compatible monitoring system) and administrative access to the IIS servers.

Prerequisites

• Administrative access to the monitoring server and target IIS servers.
• IIS installed and running on the target Server ⁄₂₀₀₃ machines.
• Windows Server ⁄₂₀₀₃ updates and service packs applied (recommended).
• .NET Framework and Windows Management Instrumentation (WMI) functional on both monitoring and target servers.
• Management console (e.g., System Center Operations Manager) installed and communicating with the agents on target servers.
• The IIS Management Pack file (usually an MP or MPZ package) downloaded and available.

Step 1 — Obtain the Management Pack

1. Locate and download the IIS Management Pack compatible with IIS versions on Server ⁄₂₀₀₃ (look for “IIS ⁄₆ Management Pack” or legacy IIS pack).
2. Verify the file integrity and note any included README or release notes for version-specific instructions.

Step 2 — Prepare Target Servers

1. Ensure the monitoring agent is installed and online on each Server ⁄₂₀₀₃ machine.
2. Verify WMI is responsive:
   • From the monitoring server, run a WMI query or use WBEMTest to connect to the target server.
3. Confirm firewall settings allow communications between monitoring server and agents (RPC, appropriate ports for your monitoring system).
4. If present, configure necessary permissions so the monitoring account can query performance counters, event logs, and IIS configuration (local Administrators group membership is safest).

Step 3 — Import the Management Pack into the Monitoring Console

1. Open your monitoring console (Operations Manager or compatible).
2. Navigate to Management Packs or Administration → Management Packs.
3. Choose “Import” and browse to the downloaded MP/MPZ file.
4. Review any dependencies listed during import; import required dependent packs if prompted.
5. Complete the import and confirm the Management Pack appears in the list.

Step 4 — Configure Discovery and Targeting

1. Open the Management Pack’s configuration or rules views.
2. Ensure the discovery rules target the correct operating system and IIS versions (Server 2000 maps to IIS 5; Server 2003 maps to IIS 6).
3. If discovery is disabled by default, enable the discovery rule and run discovery manually on selected agent-managed groups.
4. Verify that discovered IIS instances appear under the monitored objects in the console.

Step 5 — Configure Credentials and Run-As Profiles

1. Open the Run As Accounts/Profiles section of the console.
2. Create or verify a Run As Account with sufficient permissions to read performance counters, event logs, and IIS metabase (local admin or delegated account).
3. Map the Run As Account to the Management Pack’s Run As Profile(s) used by discovery and collection rules.
4. Test the Run As application to ensure data collection works.

Step 6 — Enable and Tune Monitoring Rules and Alerts

1. Review default monitors, rules, and thresholds included with the pack (HTTP response, request queues, worker process crashes, event-based alerts, etc.).
2. Enable or adjust rules to match your environment’s expected load and noise levels.
3. Set alert severity and notifications (email, SMS, ticketing integrations) as appropriate.
4. Consider excluding or tuning counters that generate false positives (e.g., short-lived spikes).

Step 7 — Validate Data Collection and Dashboards

1. After discovery, verify that performance counters, availability checks, and event-based alerts are populating in the console.
2. Open the IIS object dashboards or views to confirm charts and health states are displayed.
3. Trigger a known condition (for example, stop an IIS service) to confirm alerts fire and are actionable.

Step 8 — Troubleshooting Common Issues

• Discovery fails or IIS not listed:
  • Verify agent online status and WMI connectivity.
  • Check that IIS metabase access is permitted for the Run As account.
• No performance data:
  • Confirm the performance counters are enabled on the target server.
  • Verify firewall and RPC connectivity.
• Excessive alerts/noise:
  • Tune thresholds, set suppression windows, or disable noisy rules.
• Management Pack import errors:
  • Verify dependencies are imported first and the MP file is not corrupted.

Maintenance and Best Practices

• Keep the Management Pack and monitoring software updated; apply vendor-released updates.
• Use descriptive naming for Run As accounts and document their permissions.
• Periodically review alert noise and adjust thresholds.
• Back up custom Management Pack configurations and export them for recovery or migration.
• For large environments, use resource pools or distributed collectors to reduce load on a single monitoring server.

Summary

Installing and configuring the Server ⁄₂₀₀₃ IIS Management Pack involves obtaining the correct pack, preparing target servers (agents, WMI, permissions), importing and enabling discovery, mapping Run