Getting Started

適用於: Operations Manager 2007

Before You Import the Management Pack

Before you import the Windows Server Internet Information Services 2000 or 2003 Management Packs, you should evaluate your organization's monitoring requirements for IIS. The planning phase will let you clarify your monitoring expectations, define your escalation procedures, and optimize importing and configuring the Management Packs.

Configure IIS Servers as Operations Manager 2007 Managed Objects

To manage servers running IIS with Operations Manager 2007, they must be configured as managed objects of an Operations Manager 2007 Management Group. Windows-based managed objects are either agent-managed or agentless managed computers. For more information about agent-managed and agentless managed computers, see the Configuring Objects to Be Managed by Operations Manager 2007 topic in the Operations Manager 2007 Help.

Agent-Managed

The Windows Server Internet Information Services 2000 and 2003 Management Packs for Operations Manager 2007 provide complete monitoring functionality for agent-managed servers running IIS 2000 and 2003. An agent-managed computer is a Windows-based computer that has the Operations Manager 2007 agent installed.

Agentless Managed

The Windows Server Internet Information Services 2000 and 2003 Management Packs for Operations Manager 2007 do not support agentless monitoring.

Files to Download

To monitor IIS 2000 or 2003, you must download the Windows Server Internet Information Services 2000 or 2003 Management Packs, which contain the following files:

For the IIS 2000 Management Pack:

  • Microsoft.Windows.InternetInformationServices.CommonLibrary.mp (Windows Server Internet Information Services Library)

  • Microsoft.Windows.InternetInformationServices.2000.mp (Windows Server Internet Information Services 2000)

For the IIS 2003 Management Pack:

  • Microsoft.Windows.InternetInformationServices.CommonLibrary.mp (Windows Server Internet Information Services Library)

  • Microsoft.Windows.InternetInformationServices.2003.mp (Windows Server Internet Information Services 2003)

note附註
You can find the latest Management Pack files at http://go.microsoft.com/fwlink/?LinkId=82105. The Management Pack files that ship with Operations Manager 2007 are in the ManagementPacks directory of the installation media.

Other Requirements

The Management Packs for IIS 2000 and 2003 have dependencies on the Management Packs that are installed by default with an Operations Manager 2007 Management Server.

Important重要事項
Almost all optional Management Packs have dependencies on some of the default Management Packs. Therefore, the default Management Packs should not be removed from an Operations Manager 2007 Management Group. If this removal does occur, the default Management Packs can be imported from the System Center Operations Manager 2007 installation directory, c:\System Center Operations Manager 2007 installation directory, for example.

Optional Management Packs

To keep your IIS servers running smoothly and with high availability, you must maintain the overall health of your Information Technology (IT) environment. The overall health includes components that are specific to IIS, along with components for the network, computer hardware, operating systems, and applications.

It is a best practice to import the Management Packs for the operating systems that provide the versions of IIS you are monitoring. Some of the views provided with the Windows Server Internet Information Services 2000 and 2003 Management Packs require the Management Packs for the appropriate operating systems to have data to display. Consider also deploying Management Packs for the following:

  • The databases of the Web sites

  • Clients of IIS, such as Information Worker Windows Internet Explorer

  • Network hardware, such as routers

    note附註
    Management Packs for hardware devices can be provided by the manufacturer or third parties or can be created within your organization. For information about creating Management Packs, see http://go.microsoft.com/fwlink/?LinkId=82637.

How to Import the Internet Information Services 2003 and 2000 Management Packs

Dependencies exist between the IIS Management Pack files; therefore, the files must be imported together or individually in the following order:

For IIS 2000 Management Pack Files

  1. Microsoft.Windows.InternetInformationServices.CommonLibrary.mp (Windows Server Internet Information Services Library)

  2. Microsoft.Windows.InternetInformationServices.2003.mp (Windows Server Internet Information Services 2000)

note附註
These Management Pack files are in the ManagementPacks directory of the Operations Manager 2007 installation media.

For IIS 2003 Management Pack Files

  1. Microsoft.Windows.InternetInformationServices.CommonLibrary.mp (Windows Server Internet Information Services Library)

  2. Microsoft.Windows.InternetInformationServices.2003.mp (Windows Server Internet Information Services 2003)

For information about importing Management Packs, see the "About the Management Packs Node in Operations Manager 2007" topic in the Operations Manager 2007 Help.

Create a New Management Pack for Customizations

Most vendor Management Packs are sealed so that you cannot change any of the original settings in the Management Pack file. However, you can create customizations, such as overrides or new monitoring objects, and save them to a different Management Pack. By default, Operations Manager saves all customizations to the Default Management Pack. As a best practice, you should instead create a separate Management Pack for each sealed Management Pack you want to customize.

Creating a new Management Pack for storing overrides has the following advantages:

  • It simplifies the process of exporting customizations that were created in your test and pre-production environments to your production environment. For example, instead of exporting a Default Management Pack that contains customizations from multiple Management Packs, you can export just the Management Pack that contains customizations of a single Management Pack.

  • It allows you to delete the original Management Pack without first needing to delete the Default Management Pack. A Management Pack that contains customizations is dependent on the original Management Pack. This dependency requires you to delete the Management Pack with customizations before you can delete the original Management Pack. If all of your customizations are saved to the Default Management Pack, you must delete the Default Management Pack before you can delete an original Management Pack.

  • It is easier to track and update customizations to individual Management Packs.

For more information about sealed and unsealed Management Packs, see Management Pack Formats. For more information about Management Pack customizations and the Default Management Pack, see About Management Packs.

To Create a New Management Pack for Customizations

  1. Open the Operations Console, and then click the Administration button.

  2. Right-click Management Packs, and then click Create New Management Pack.

  3. Enter a name (for example, ADMP Customizations), and then click Next.

  4. Click Create.

社群新增項目

顯示: