Optional Configuration

適用於: Microsoft Office, Operations Manager 2007, Operations Manager 2007 R2

This section contains information about optional configurations you can set for features of the Information Worker Management Pack. You use the overrides feature of Operations Manager 2007 to change configuration settings.

Every version of every monitored application is automatically discovered, bust you can disable monitoring of the applications and versions that you do not use. For example you might want to disable monitoring of Microsoft Excel 2003. You can change the setting in the Authoring pane of the Operations console.

To use an override to change the setting for automatic discovery

  1. In the Authoring pane of the Operations Console, expand Management Pack Objects, and then click Object Discoveries.

  2. In the Find box, enter Office 2003 Excel, and then click Find Now.

  3. Under Discovered Type: Microsoft Office 2003 Excel (n), click Microsoft.Office.2003.Discovery.

  4. On the Operations Manager toolbar, click Overrides, click Override the Object Discovery, and then click For all objects of type: Windows Client.

  5. In the OverridesProperties dialog box, click the Override box for the DiscoverExcel parameter, in the Override Setting column, change the value to False, and then click Apply.

The override settings you created is defined in the Default Management Pack.

For more information about setting overrides, see the Object Discoveries in Operations Manager 2007 topic in Operations Manager 2007 Help.

The following monitoring scenarios require manual configuration:

  • Designation as business-critical

  • The Web Site Access feature

  • Client Data Source Access feature

Populating the All Business Critical Windows Clients Group

Computer groups for this Management Pack are differentiated by the extent to which they are critical to your business. Rules for the business critical groups generate alerts for specific health states of the applications you monitor. Rules for the groups that are not business-critical (collective clients) aggregate data collected by the rules. This data can be used in reports to track trends, identify problems that occur throughout the collective clients, and so on. For information about using business-critical clients, see the "Key Monitoring Scenarios" section later in this document.

To designate a client group as business-critical

  1. In the Authoring pane of the Operations Console, click Groups. The following three business-critical groups, along with others, appear in the results pane: All Business Critical Windows Clients, All Business Critical Windows 2000 Clients, and All Business Critical Windows XP Clients.

  2. Add client individual clients to these business-critical groups. Right-click the group name, and then click Properties.

  3. On the Explicit Members tab, click Add/Remove Object.

  4. Add the Windows-based client computers to the group: From the Search for drop-down list select Windows Client 2000 Computer and Windows Client XP Computer.

When this process is complete, the affected computers are added to the All Business Critical Windows Clients group and the Business Critical monitoring policy is applied to each of these computers. With your business-critical computers configured in this way, Operations Manager 2007 will update the configuration of the Management Pack rules to generate alerts for issues you define.

Configuring the Client Web Site Access Feature

The Client Web Site Access feature of Information Worker enables you to create a service that identifies the inability of client computers to access a specified web application. The State view and the Diagram view in the Operations Console shows an unhealthy state when this occurs.

To enable the Client Web Site Access feature, you first add monitoring that will detect a failure to connect to the specified Web site. Then you use the Distributed Application Designer to create a service that enables the Client Web Site Access feature. Then you use the Distributed Application Designer to create a service whose health represents a client's ability to access a specific web site.

To add monitoring for the Client Web Site Access feature

  1. In the Authoring pane of the Operations Console, under Management Pack Templates, right-click Web Application, and then click Add monitoring wizard.

  2. On the Select Monitoring Type page, click Web Application, and then click Next.

  3. On the Web Application Name and Description page, enter a name and description for your application.

  4. Under Management Pack, use the drop-down list to select an existing Management Pack or click New to create a new one, and then click Next.

  5. On the Enter and Test Web Address page, enter the URL for your Web site, and then click Next.

  6. On the Choose Watcher Nodes page, under Watcher node, select the computers that will function as watcher nodes.

  7. In the Run this query every boxes, designate the frequency with which you want this query to run, and then click Next.

  8. If you want to configure your web application further, in Web Application Monitoring Settings Summary page, click Configure Advanced Monitoring or Record a browser session, and then click Create. If you application is complete, leave that option disabled and simply click Create.

In you selected the Configure Advanced Monitoring option, when you click Create, the Web Application editor opens with three panes visible.

To configure advanced settings

  • To request that a web site be added to the sites for which activity will be monitored, click Insert request in the actions pane. The Create New Request dialog box appears in which you can set options for site monitoring.

  • To delete a web site from the list of web requests, select it in the list and click Delete in the actions pane.

  • To change settings that define monitoring of the web site selected in the Web Site - Requests list and make your changes in the details pane.

You use the Distributed Application Designer to create your service.

To create a service with the Distributed Application Designer

  1. In the navigation pane right-click Distributed Applications, and then click Create a new distributed application.

  2. In the Distributed Application Designer, type a name and description for your distributed application.

  3. Under Template, click Windows Internet Explorer Service.

  4. Under Management Pack use the drop-down list to select an existing Management Pack or click New to create a new one, and then click OK.

  5. The Distributed Application Designer opens showing your service.

    • Under Organize Object Types, select the kinds of object types you want to access.

    • Under Objects, you can search for objects.

    • In the Component Group details pane, you can view the key details, views, and health roll-up information.

  6. To add components to your distributed application, drag them from the Objects pane to the diagram, where you can arrange the components any way you like and create relationships between them.

    Start with selecting the type Perspectives, and then select the perspectives you created in the "To add monitoring for the Client Web Site Access feature" procedure. Other components rely on the installation of additional Management Packs to discover the applicable instances.

To view the health of the service you created

  • In the Distributed Application details pane, under Views, click State View.

Or

  • In the navigation pane of the Monitoring pane, expand Microsoft Windows Client, expand Enterprise Health Monitoring, expand Internet Explorer, and then click Internet Explorer Services State.

Configuring the Client Data Source Access Feature

The Client Data Source Access feature enables you to create a service that displays, in the State view and the Diagram view, an unhealthy state when a client computer cannot access a specified OLE DB data source, such as an Excel spreadsheet that connects to a database.

To enable the Client Data Source Access feature, you first add monitoring that will detect a failure to connect to the specified OLE DB data source. Then you use the Distributed Application Designer to create a service that enables the Client Data Source Access feature. Then you use the Distributed Application Designer to create a service whose health represents a client's ability to access a specific data source.

To add Monitoring for the Client Data Source Access feature

  1. In the Authoring pane of the Operations Console, under Management Pack Templates, right-click OLE DB Data Source, and then click Add monitoring wizard.

  2. On the Select Monitoring Type page, click OLE DB Data Source, and then click Next.

  3. On the OLE DB Data Source Name and Description page, type a name and description for the data source.

  4. Under Management Pack, use the drop-down list to select an existing Management Pack or click New to create a new one, and then click Next.

  5. On the Enter and Test OLE DB Data Source Settings page, either select Simple Configuration and supply the requested information or select Advanced Configuration and supply a connection string, and then click Next.

  6. On the Choose Watcher Nodes page, under Watcher node, select the computers that will function as watcher nodes.

  7. In the Run this query every boxes, designate the frequency with which you want this query to run, and then click Next.

  8. On OLE DB data Source Monitoring Settings Summary page, click Create.

  9. In the navigation pane, click New distributed application.

  10. In the Distributed Application Designer, type a name and description for your distributed application.

  11. Under Template, click Windows Internet Explorer Data Source Service.

  12. Under Management Pack, use the drop-down list to select an existing Management Pack or click New to create a new one, and then click OK.

You use the Distributed Application Designer to create your service.

To create a service with the Distributed Application Designer

  1. In the navigation pane right-click Distributed Applications, and then click Create a new distributed application.

  2. In the Distributed Application Designer, type a name and description for your distributed application.

  3. Under Template, click Windows Explorer Data Source Service.

  4. Under Management Pack use the drop-down list to select an existing Management Pack or click New to create a new one, and then click OK.

  5. The Distributed Application Designer opens showing your service.

    • Under Organize Object Types, select the kinds of object types you want to access.

    • Under Objects, you can search for objects.

    • In the Component Group details pane, you can view the key details, views, and health roll-up information.

  6. To add components to your distributed application, drag them from the Objects pane to the diagram, where you can arrange the components any way you like and create relationships between them.

    Start with selecting the type Perspectives, and then select the perspectives you created in the "To add monitoring for the Client Data Source Access feature" procedure. Other components rely on the installation of additional Management Packs to discover the applicable instances.

To view the health of the service you created

  • In the Distributed Application details pane, under Views, click State View.

Or

  • In the navigation pane of the Monitoring pane, expand Microsoft Windows Client, expand Enterprise Health Monitoring, expand Internet Explorer, and then click Internet Explorer Services State.

社群新增項目

顯示: