This blog entry is another in a series of Operations Manager related items that review the steps that we performed to install, configure and tune management packs in real-world environments. With this entry we focus on the IIS MP.
- Download the IIS management pack (http://www.microsoft.com/downloads/details.aspx?FamilyId=D351BCA8-182B-4223-8C9E-627E184BA02B&displaylang=en), and the IIS Management Pack Guide (http://download.microsoft.com/download/7/4/d/74deff5e-449f-4a6b-91dd-ffbc117869a2/OM2007_MP_IIS.doc).
- Read the Management Pack guide from cover to cover. There are important pieces to know that the document spells out in detail.
- Import the IIS management pack. This consists of the Windows Server Internet Information Services Library, and individual management packs for IIS 5 (Internet Information Services 2000 with Windows 2000) and IIS 6 (Internet Information Services 2003 with Windows Server 2003). Import the Library (which is a prerequisite), plus the appropriate management pack for the version of IIS that you will be monitoring.
- We recommend you also import the appropriate version of the Windows Server management pack (Windows 2000 or 2003). Some of the views provided with the IIS MP require the MPs for the appropriate level of operating systems to have data to display.
- Even if you do not have any custom web applications using IIS, remember that Exchange, SQL Server Reporting Services, and Operations Manager itself have components that use IIS; you will want to implement the IIS MP as part of rolling out and monitoring those applications.
- The IIS management pack does not support agentless monitoring. Verify that the OpsMgr agent is installed on your IIS servers.
- The IIS MP collects data from the IIS logs. If logging is not enabled, the MP will only collect and analyze service data. The IIS logs must be set to the W3C Extended Log File format. Enable logging for each type of site and virtual server that you want to collect monitoring data for. This can include FTP sites, Web sites, SMTP virtual servers, and NNTP virtual servers. (Enable logging for a virtual server in the IIS Services Manager by double-clicking the local computer, right-click the SMTP or NNTP Virtual Server folder you want to enable logging for, select Properties, then on the General tab, select Enable logging. Be sure to select W3C Extended Log File format on the Active log format drop-down list.)
Rolling up Health
If you have used the IIS MP in MOM 2005, the Health rollup is a new feature. Use the Health Explorer to examine Health:
- The IIS MP for OpsMgr 2007 has the abiilty to tell you whether a specific Web site is health, in addition to being able to know if the Web server is healthy.
- The health of the IIS Sever is dependent on the health of the objects at the next lower level – the IIS Web, FTP, NNTP, and SMTP Servers. If any of these servers is in a critical health state, the IIS Server will display in a critical health state.
- By default, the health of the IIS FTP, NNTP, SMTP, and Web Servers are not dependent on the health of the objects at the next lower level. If one or more Web Sites is in a critical state, the Web Server object will not change state.
Tuning/Alerts to Look for: The following are alerts found and resolved while tuning the IIS management pack.
Alert: An unknown token name (s-event) was encountered.
Issue: IIS logging is configured by default on Windows Server 2000 to include Process Accounting extensions for Web sites.
Resolution: Disable logging Process Accounting Extensions. (In IIS Service Manager, select the Default Web Site, Properties, select Enable logging on the Web Site tab, from the Active log format drop-down list, select W3C Extended Log File Format, select properties, choose Extended Properties, and clear Process Accounting from the Extended Logging Options list box.)
Issue: IISReset causes a ton of alerts.
Resolution: Put the IIS object in maintenance mode before doing the IISReset. You could use PowerShell (use the command New-MaintenanceWindow to put the server into maintenance mode and then start the IISReset cmd operation) to automate this.
Issue: IIS MP does not work well with clusters. This can be a real issue when monitoring Exchange.
Resolution: None currently available. This may be addressed in Service Pack 1 / the next release of the IIS MP.
Issue: If you are using the Exchange management pack, you will encounter a number of IIS-related issues with Exchange.
Resolution: Check our "OpsMgr by Example: the Exchange Management Pack" entry (http://ops-mgr.spaces.live.com/blog/cns!3D3B8489FCAA9B51!220.entry) for a detailed list.