Pavleck.NET Operations Manager Wiki > OpsMgr R2 Beta 1 Highlights

OpsMgr R2 Beta 1 Highlights

Table of contents
  1. 1. What's New In Operations Manager 2007 R2
    1. 1.1. New Features
      1. 1.1.1. Import Management Packs Wizard
      2. 1.1.2. Process Monitoring Management Pack Template
      3. 1.1.3. Improved Windows Service Management Pack Template
      4. 1.1.4. Support for Custom queries in OLE DB Data Source Management Pack Template
      5. 1.1.5. Support for Discovery and Monitoring of UNIX and LINUX based computers
      6. 1.1.6. Service Level Monitoring
      7. 1.1.7. Health Explorer
    2. 1.2. Setup and Recovery
      1. 1.2.1. Support for SQL Server 2008
    3. 1.3. User Interface and Experience
      1. 1.3.1. XPath Support in Alert Description Customization
      2. 1.3.2. Improved Dashboard View Search and Selection Criteria
      3. 1.3.3. Overrides Summary view
      4. 1.3.4. Maintenance Mode
      5. 1.3.5. UI Performance andUsability
      6. 1.3.6. Notifications
    4. 1.4. Core Product
      1. 1.4.1. Support for Monitoring IIS7
      2. 1.4.2. Support for large scale monitoring of URL’s
    5. 1.5. Management Pack Authoring
    6. 1.6. Reporting
      1. 1.6.1. Object Picker for Report Parameters
  2. 2. Operations Manager 2007 R2 Beta Higlights Step by Step's
  3. 3. Step by step guide to monitoring UNIX and Linux computers using operations manager 2007 R2
    1. 3.1.  
      1. 3.1.1. System Architecture
  4. 4. Requirements for monitoring cross-platform computers
  5. 5. Steps for monitoring cross-platform computers
    1. 5.1.  
  6. 6. Configuring a Run As account
    1. 6.1. Procedures
  7. 7. Importing the cross-platform management packs
    1. 7.1. Procedures
  8. 8. Using the Discovery Wizard to discover systems and deploy agents
    1. 8.1. Procedures
  9. 9. Manually installing agents
    1. 9.1.  
    2. 9.2.  
    3. 9.3.  
    4. 9.4.  
  10. 10. Viewing system monitors
    1. 10.1. Procedures
  11. 11. Using the UNIX\Linux Management Pack Templates
    1. 11.1. Procedures
  12. 12. Step by Step Guide to Tracking Service Level Objectives
  13. 13. Requirements for Tracking Service Levels
  14. 14. Steps for Tracking Service Levels
  15. 15. Defining a service level objective against an application
    1. 15.1. Procedures
  16. 16. Defining a service level objective against a group
    1. 16.1. Procedures
  17. 17. Generating an SLM Report
    1. 17.1. Procedures
  18. 18. Step by Step Guide for Configuring and Using Notifications
  19. 19. Requirements for Configuring and Using Notifications
  20. 20. Steps for Configuring and Using Notifications
  21. 21. Configuring notifications
    1. 21.1. Procedures
  22. 22. Creating a notification subscription
    1. 22.1. Procedures
  23. 23. Creating a notification subscription from an alert
    1. 23.1. Procedures
  24. 24. Step by Step Guide to Using Run As
    1. 24.1. Run As Scenario Overview
  25. 25. Requirements for Using Run As
  26. 26. Steps For Using Run As
    1. 26.1. Procedures
  27. 27. Using Run As Additional Note
    1. 27.1.  
      1. 27.1.1. Multiple Associations in a Profile
  28. 28. Step by Step Guide to Using the Process Monitoring Management Pack Templage
    1. 28.1. Process Monitoring Scenario Overview
      1. 28.1.1. Requirements for Using Process Monitor
  29. 29. Operations Manager 2007 R2 Beta Highlights Appendixes
    1. 29.1. Summary of Appendixes
  30. 30. Appendix A – Table of Available Cross-Platform Reports
  31. 31. Appendix B - Cross Platform Operating System Package Dependencies
    1. 31.1. IBM AIX 5L 5.3
    2. 31.2. IBM AIX 6.1
    3. 31.3. HP-UX 11i v2 IA 64
    4. 31.4. HP-UX 11i v2 PA-RISC
    5. 31.5. HP-UX 11i v3 PA-RISC
    6. 31.6. HP-UX 11i v3 IA64
    7. 31.7. HP-UX 11i v2 IA/PA
    8. 31.8. Red Hat Enterprise Linux ES Release 4
    9. 31.9. Red Hat Enterprise Linux Server release 5.1 (Tikanga)
    10. 31.10. Solaris 8 SPARC
    11. 31.11. Solaris 9 SPARC
    12. 31.12. Solaris 10 SPARC
    13. 31.13. Solaris 10 x86
    14. 31.14. SUSE Linux Enterprise Server 9 (i586)
    15. 31.15. SUSE Linux Enterprise Server 10 SP1 (i586)
  32. 32. Appendix C - Cross-Platform Management Packs
    1. 32.1. Cross Platform Management Packs
  33. 33. Appendix D - Uninstalling the Cross Platform Management Packs and Agents
  34. 34. Operations Manager 2007 SP1 to R2 Upgrade
    1. 34.1. Upgrade Paths
    2. 34.2. Upgrading System Center Desktop Error Monitoring to System Center Operations Manager 2007 R2
    3. 34.3. Upgrade Evaluation Copies
    4. 34.4. Order of Operations
    5. 34.5. How to Prepare a Management Group for Upgrading to Operations Manager 2007 R2
    6. 34.6. How to Improve Upgrade Performance in Environments Where a Large Number of Agents Are Installed
    7. 34.7. How to Upgrade the Root Management Server to Operations Manager 2007 R2
    8. 34.8. How to Upgrade Reporting to Operations Manager 2007 R2
    9. 34.9. How to Upgrade a Stand-Alone Operations Console to Operations Manager 2007 R2
    10. 34.10. How to Upgrade a Management Server to Operations Manager 2007 R2
    11. 34.11. How to Upgrade a Gateway Server to R2
    12. 34.12. How to Upgrade an Agent to R2
    13. 34.13. How to Upgrade a Web Console Server to Operations Manager 2007 R2
    14. 34.14. How to Upgrade the ACS Collector to R2
    15. 34.15. How to Enable Subscriptions

- From the download off of the Connect site.
- Document Name: OM2007R2Beta_Hilites.docx
- I'm really not abiding by the user agreement, but this is just a test.

 

 

<meta content="text/html; charset=utf-8" http-equiv="Content-Type"/><meta content="Word.Document" name="ProgId"/><meta content="Microsoft Word 11" name="Generator"/><meta content="Microsoft Word 11" name="Originator"/>

Operations Manager 2007 R2 Beta Highlights

Microsoft Corporation

Published, November, 2008

Author

Liza Poggemeyer, Chris Fox, Scott Butler

Applies To

Operations Manager 2007 R2 Beta Release


This document supports a preliminary release of a software product that may be changed substantially prior to final commercial release.This document is provided for informational purposes only and Microsoft makes no warranties, either express or implied, in this document.Information in this document, including URL and other Internet Web site references, is subject to change without notice.The entire risk of the use or the results from the use of this document remains with the user.Unless otherwise noted, the companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted in examples herein are fictitious.No association with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred.Complying with all applicable copyright laws is the responsibility of the user.Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document.Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.2008 Microsoft Corporation.All rights reserved.Microsoft System Center Operations Manager 2007 R2 Beta trademarks of the Microsoft group of companies.All other trademarks are property of their respective owners.

Caution

Microsoft recommends that you do not install Operations Manager 2007 R2 Beta in a production environment. Because this software is offered on an “as is” basis, support may not be provided for it.

 


Contents

What's New In Operations Manager 2007 R2............................................................................. 3  

New Features...................................................................................................................... 3  

Import Management Packs Wizard..................................................................................... 3  

Process Monitoring Management Pack Template................................................................ 3  

Improved Windows Service Management Pack Template...................................................... 3  

Support for Custom queries in OLE DB Data Source Management Pack Template................. 3  

Support for Discovery and Monitoring of UNIX and LINUX based computers............................ 3  

Service Level Monitoring.................................................................................................... 3  

Health Explorer................................................................................................................. 3  

Setup and Recovery............................................................................................................. 3  

Support for SQL Server 2008.............................................................................................. 3  

User Interface and Experience............................................................................................... 3  

XPath Support in Alert Description Customization................................................................ 3  

Improved Dashboard View Search and Selection Criteria...................................................... 3  

Overrides Summary view................................................................................................... 3  

Maintenance Mode........................................................................................................... 3  

UI Performance andUsability............................................................................................ 3  

Notifications..................................................................................................................... 3  

Core Product....................................................................................................................... 3  

Support for Monitoring IIS7................................................................................................. 3  

Support for large scale monitoring of URL’s......................................................................... 3  

Management Pack Authoring................................................................................................ 3  

Reporting............................................................................................................................ 3  

Object Picker for Report Parameters.................................................................................. 3  

Operations Manager 2007 R2 Beta Higlights Step by Step's....................................................... 3  

Step by step guide to monitoring UNIX and Linux computers using operations manager 2007 R2.... 3  

System Architecture......................................................................................................... 3  

Requirements for monitoring cross-platform computers............................................................... 3  

Steps for monitoring cross-platform computers.......................................................................... 3  

Configuring a Run As account.................................................................................................. 3  

Procedures.......................................................................................................................... 3  

Importing the cross-platform management packs....................................................................... 3  

Procedures.......................................................................................................................... 3  

Using the Discovery Wizard to discover systems and deploy agents............................................ 3  

Procedures.......................................................................................................................... 3  

Manually installing agents........................................................................................................ 3  

Viewing system monitors......................................................................................................... 3  

Procedures.......................................................................................................................... 3  

Using the UNIX\Linux Management Pack Templates.................................................................. 3  

Procedures.......................................................................................................................... 3  

Step by Step Guide to Tracking Service Level Objectives............................................................ 3  

Requirements for Tracking Service Levels.................................................................................. 3  

Steps for Tracking Service Levels............................................................................................. 3  

Defining a service level objective against an application............................................................... 3  

Procedures.......................................................................................................................... 3  

Defining a service level objective against a group........................................................................ 3  

Procedures.......................................................................................................................... 3  

Generating an SLM Report....................................................................................................... 3  

Procedures.......................................................................................................................... 3  

Step by Step Guide for Configuring and Using Notifications......................................................... 3  

Requirements for Configuring and Using Notifications................................................................. 3  

Steps for Configuring and Using Notifications............................................................................. 3  

Configuring notifications........................................................................................................... 3  

Procedures.......................................................................................................................... 3  

Creating a notification subscription........................................................................................... 3  

Procedures.......................................................................................................................... 3  

Creating a notification subscription from an alert........................................................................ 3  

Procedures.......................................................................................................................... 3  

Step by Step Guide to Using Run As........................................................................................ 3  

Run As Scenario Overview.................................................................................................... 3  

Requirements for Using Run As................................................................................................ 3  

Steps For Using Run As.......................................................................................................... 3  

Procedures.......................................................................................................................... 3  

Using Run As Additional Note.................................................................................................. 3  

Multiple Associations in a Profile........................................................................................ 3  

Step by Step Guide to Using the Process Monitoring Management Pack Templage...................... 3  

Process Monitoring Scenario Overview................................................................................... 3  

Requirements for Using Process Monitor............................................................................ 3  

Operations Manager 2007 R2 Beta Highlights Appendixes.......................................................... 3  

Summary of Appendixes....................................................................................................... 3  

Appendix A – Table of Available Cross-Platform Reports............................................................. 3  

Appendix B - Cross Platform Operating System Package Dependencies..................................... 3  

IBM AIX 5L 5.3..................................................................................................................... 3  

IBM AIX 6.1......................................................................................................................... 3  

HP-UX 11i v2 IA 64............................................................................................................... 3  

HP-UX 11i v2 PA-RISC......................................................................................................... 3  

HP-UX 11i v3 PA-RISC......................................................................................................... 3  

HP-UX 11i v3 IA64................................................................................................................ 3  

HP-UX 11i v2 IA/PA.............................................................................................................. 3  

Red Hat Enterprise Linux ES Release 4................................................................................. 3  

Red Hat Enterprise Linux Server release 5.1 (Tikanga)............................................................. 3  

Solaris 8 SPARC................................................................................................................. 3  

Solaris 9 SPARC................................................................................................................. 3  

Solaris 10 SPARC............................................................................................................... 3  

Solaris 10 x86..................................................................................................................... 3  

SUSE Linux Enterprise Server 9 (i586)................................................................................... 3  

SUSE Linux Enterprise Server 10 SP1 (i586).......................................................................... 3  

Appendix C - Cross-Platform Management Packs...................................................................... 3  

Cross Platform Management Packs....................................................................................... 3  

Appendix D - Uninstalling the Cross Platform Management Packs and Agents............................. 3  

Operations Manager 2007 SP1 to R2 Upgrade........................................................................... 3  

Upgrade Paths..................................................................................................................... 3  

Upgrading System Center Desktop Error Monitoring to System Center Operations Manager 2007 R23  

Upgrade Evaluation Copies................................................................................................... 3  

Order of Operations.............................................................................................................. 3  

How to Prepare a Management Group for Upgrading to Operations Manager 2007 R2................. 3  

How to Improve Upgrade Performance in Environments Where a Large Number of Agents Are Installed3  

How to Upgrade the Root Management Server to Operations Manager 2007 R2......................... 3  

How to Upgrade Reporting to Operations Manager 2007 R2..................................................... 3  

How to Upgrade a Stand-Alone Operations Console to Operations Manager 2007 R2................. 3  

How to Upgrade a Management Server to Operations Manager 2007 R2.................................... 3  

How to Upgrade a Gateway Server to R2................................................................................ 3  

How to Upgrade an Agent to R2............................................................................................ 3  

How to Upgrade a Web Console Server to Operations Manager 2007 R2................................... 3  

How to Upgrade the ACS Collector to R2............................................................................... 3  

How to Enable Subscriptions................................................................................................ 3  


This topic describes some of the major improvements and major changes in functionality that are included in Operations Manager 2007 R2. R2 is a new version of Operations Manager 2007 and it is not a free upgrade; you can obtain it as part of your Software Assurance benefit, or you can purchase it. With appropriate licensing, you can upgrade from Operations Manager 2007 SP1 to Operations Manager 2007 R2. You can also run a clean install of Operations Manager 2007 R2.Operations Manager 2007 R2 is available for both x86-based and x-64 based computers.

New Features

 

Import Management Packs Wizard

You can use the Import Management Packs wizard to import management packs either from a local or network disk or directly from the management pack catalog on the Web. You can browse the management pack catalog directly from the wizard. The wizard has views for all management packs in the catalog, updates for management packs that you have installed, all management packs that have been released in the past three months, or all management packs that have been released in the past six months. After you select the management packs that you want to import from the Web, the wizard downloads, unpacks, and imports the management packs for you. If you do not want to import them directly from the catalog, you can download them manually and then import them later.

Process Monitoring Management Pack Template

Operations Manager 2007 R2 provides a template you can use to easily create process monitors. The monitor watches the running-processes list on a given computer or on groups that you define. This template creates a monitor that you can use to watch groups for processes that you do not want to be running and to gather performance and status data for processes that you expect to be running. The following are some examples of the different ways that monitoring can occur:

· A minimum number of wanted processes are running. For example, an IIS Web site has at least one w3wp.exe process that is running.

·The number of identified processes that are concurrently running does not exceed a limit. For example, you might not want more than four instances of w3wp.exe running in a given IIS Web site.

·Performance and status data are collected on a running process, either as a group or individually. For example, you might want to measure the load on an IIS Web site. To make this measurement, you might want the SUM Memory\Private Working Set performance counter from IISAdmin.exe and all w3wp.exe processes to be on a given computer.

Improved Windows Service Management Pack Template

In the Windows Service management pack template, you can use wildcards when you specify the service name that you want to monitor. For example, if you want to monitor multiple instances of SQL Server in a targeted group, you can enter *SQL* for the service name to monitor.

Support for Custom queries in OLE DB Data Source Management Pack Template

The OLE DB management pack template gives you a way to type or paste a custom query to be run against the remote OLE DB data source.

Support for Discovery and Monitoring of UNIX and LINUX based computers

In Operations Manager 2007 R2 you can discover, monitor, and manage UNIX-based and Linux-based computers by using the same interface and tools that you use to manage your Windows-based computers. Some of the components are:

·The Computer and Device Management Wizard (the discovery wizard), which performs UNIX and Linux discovery in addition to Windows discovery and Network Device discovery

·Management packs for monitoring:

·SUSE Linux Enterprise Server 9 and 10, SP1

·Red Hat Enterprise Server 4 and 5

·Solaris 8 for SPARC, 9 for SPARC and 10 for SPARC and x86

·HP-UX 11iv2 for PA-RISC and IA64 and 11iv3 for PA-RISC and IA64

·and AIX 5.3 for PowerPC and 6.1 for PowerPC

·The capability to provide different sets of credentials for remote monitoring of UNIX-basedand LINUX-based computers

·A single Unix/Linux Server State view for monitoring all your UNIX-based and LINUX based-computers

Service Level Monitoring

Operations Manager 2007 R2 provides Service Level Tracking for distributed applications. This tracking is done by defining Service Level Objectives (SLOs) in the Authoring space. These objectives allow you to classify monitors and rules that affect the availability and performance of Distributed Applications.

Health Explorer

The Health Explorer has been added to the Web console.

Setup and Recovery

The following items are new or improved in setup and recovery.

Support for SQL Server 2008

You can install the Operations Manager 2007 R2 databases on SQL Server 2008.

User Interface and Experience

The following items are new or improved in the user interface and user experience.

XPath Support in Alert Description Customization

When you create a new monitor that will generate an alert, you can dynamically choose the XPath elements that are required to customize the Alert Description field with context-sensitive data. For example you can choose XPath elements, such as $Data/Context… or $Target/Property .

Improved Dashboard View Search and Selection Criteria

When you create a dashboard view, you add other views to the dashboard view in each pane of the dashboard view. Operations Manager 2007 R2 provides a search tool that you can use to find the views you want quickly. In addition, the search also includes views that you have created in your My Workspace.

Overrides Summary view

You can view all rule and monitor overrides in the overrides summary view. The overrides summary view can be used for both sealed and unsealed management packs. You can customize this view by grouping items by multiple column headers.

Maintenance Mode

The process of placing a computer and all its related objects into maintenance mode has been streamlined in the following ways:

·Management pack authors can specify in the management pack what should be included in an alert and how it is formed when a monitor comes out of maintenance mode.

·Alerts are generated on HealthService heartbeat failures after exiting out of maintenance mode.

·You can put a whole computer into Maintenance mode. This automatically puts the Health Service and the associated Health Service watcher into maintenance mode, which suppresses all alerts on that computer.

UI Performance andUsability

In Operations Manager 2007 R2, the Operations console performance has been greatly improved. These improvements are most evident in:

·Opening new views in the monitoring space

·Pivoting between views

·Selecting multiple items in the results view and rendering the details pane more quickly

·Indicating that a view is in the progress of loading

Notifications

In Operations Manager 2007 R2, the notification feature has been restructured to make it easier to configure. The Notifications folder contains folders for Channels, Subscribers, and Subscriptions. A notification is sent by channels, such as SMTP mail or command. Subscribers are the entities that receive a notification, for example user@smtpaddress.com. Subscriptions describe what the subscriber will be notified of and on what schedule notifications will be sent.You can create new channels and subscribers prior to the configuration of a subscription. However, the New Subscription wizard provides the ability to create new channels and subscribers if the one you want to use does not already exist.In addition, Operations Manager 2007 R2 provides the capability to create a new subscription directly from an alert and to add the parameters from the selected alert to an existing subscription.

Core Product

The following are new features or improved features in the core product:

Support for Monitoring IIS7

Support has been added to natively monitor IIS 7 without having to enable the backward compatibility APIs or legacy management features.

Support for large scale monitoring of URL’s

Operations Manager 2007 R2 supports monitoring as many as 2,000 URL monitors per management server. The overall capacity of URL monitors has increased commensurately for the whole management group.

Management Pack Authoring

 

The Operations Manager Authoring Console now ships on the CD with Operations Manager . The new version of the authoring console adds several user interface enhancements, and now includes the ability to edit any element in a management pack.

The Authoring Console can be installed from the Authoring Console directory on the installation disc. Once installed, the Authoring Console can be run by selecting the Start menu, and then selecting the Authoring Console item from the System Center Operations Manager 2007 R2 menu.

Reporting

The following are new items or improved items for the Reporting feature:

Object Picker for Report Parameters

In Operations Manager 2007 R2 Reporting, it is easier to find the objects that you need to customize a report. The object picker has been enhanced to enable search and filtering by name or class of object, which makes it easier to find the objects you must have.

This section of the Operations Manager 2007 R2 Beta Highlights document contains Step by Step procedures that you can use to evaluate new or updated features in this beta release. This does not provide comprehensive coverage of all new features, but it does focus on some of the major new features like cross-platform monitoring.

Systems Center Operations Manager 2007 R2 allows IT professionals to monitor system health and events on computers running UNIX and Linux operating systems, including the following:

·File systems and network interfaces

·Critical system processes (for example, syslog, cron, and others)

·Key configurations (for example, resolution of host name, or the correct configuration of Web Services Management components)

·Core system attributes (for example, the health of system memory and processors)

·Detailed monitoring of physical and logical disk space, swap space, and system memory

·Degradation of performance caused by applications or processes



Systems Center Operations Manager 2007 R2 supports monitoring for the following UNIX and Linux operating systems:

·AIX 5.3 (Power), 6.1 (Power)

·HP-UX 11iv2 (PA-RISC _ IA64), and 11iv3 (PA-RISC, and IA64)

·Red Hat Enterprise Server 4 and 5

·Solaris 8 (SPARC), 9 (SPARC), and 10 (SPARC _ x86 versions later than 120012-14)

·SUSE Linux Enterprise Server 9 and 10 SP1

·Linux 64-bit is not supported in this release.

 

System Architecture

Operations Manager 2007 Cross-Platform uses Web Services Management (WS-Man) 1.1, a Web services-based protocol that enables remote computer management over HTTP and HTTPS, including hardware management and policy-based event forwarding. WS-Man enables secure and efficient data transfers by requiring authentication and using HTTPS as the transport and is required for all communication between Operations Manager 2007 and UNIX or Linux systems.

This guide demonstrates how to import management packs, discover non-Windows servers, install the suitable operating system agents on them, deploy monitors, and generate reports based on the data collected from the cross-platform systems.

Before you can complete the cross-platform scenario, you must complete the following:

·Install Operations Manager 2007 R2

·InstallWS-Management (WS-Man) 1.1

Important

·WS-Man must be installed prior to installing Operations Manager 2007 R2. Upgrading Operations Manager 2007 Cross Platform Extensions to Operations Manager 2007 R2 is not supported in this release. You must uninstall previous versions of Operations Manager 2007 Cross Platform.

· Required package dependencies for each operating system are shown in Appendix B - Cross Platform Operating System Package Dependencies.

Monitoring cross-platform computers involves the following steps:

 

 

Step  

Reference  

Configuring a Run As account

Create Run-As accounts and profiles to monitor systems.

Importing the cross-platform management packs

Import the management packs that are used to install monitoring agents on monitored computers.

Using the Discovery Wizard to discover systems and deploy agents

Use the Discovery Wizard to allow Operations Manager to detect non-Windows-based computers and to install agents that enable monitoring of these computers.

Manually installing agents

Install the agents manually when the computers are not detected by the Discovery Wizard.

Viewing system monitors

Create system monitors to view and troubleshoot alerts, state changes, and other significant issues on non-Windows-based computers.

Using the UNIX\Linux Management Pack Templates

Use the Management Pack Templates to create custom monitoring tasks for UNIX and Linux-based computers.

 

In Operations Manager 2007 R2, Run As profiles and Run As accounts are used to provide credentials that have the necessary privileges for running rules, tasks, and monitors that the default Action Account may not have. To monitor UNIX and Linux computers, you must configure both the UNIX Action account profile and the UNIX Privileged account profile. You must go through the “To configure run as for cross platform” procedure below once for each profile.

Procedures

To configure run as for cross platform

1.Open the Operations console with an account that is a member of the Operations Manager 2007 R2 Administrators profile.

2.Select the Administration view.

3.In the Run As Configuration container, select the Profiles folder.

4.In the results pane, double-click the Unix Account, or Unix Privileged Account profile to open the Run As Profile Properties – Unix Action Account or Run As Profile Properties – Unix Privileged Account window.

5.Select the Associations tab. Notice that the Selected Targets box is empty. Click Cancel to close the window.

6.In the Run As Configuration container, select the Accounts folder.

7.Right-click in the results pane, select Create Run As Account from the context menu to start the Create Run As Account Wizard, and then click Next.

8.On the General page, click the Run As Account type arrow.

9.From the Run As Account type list, select Basic Authentication. Notice that there are other options to choose from. The option you select depends on the type of account and authentication that is required. Refer to the management pack guide for the management pack that contains the profile that you are configuring for information on which account type to select.

10.In the Display Name field, enter a name you want to use to represent the UNIX Action Account or UNIX Privileged Account credentials. In this case, enter Step by Step Run As UNIX Action Account or Step by Step Run As UNIX Privileged Account, and click Next.

11.On the Basic Run As Account page, enter the appropriate values in the Account Name, Password, and Confirm Password fields, and then click Create. This creates the Step by Step Run As UNIX Action Account or Step by Step Run As UNIX Privileged Account object and maps it to the actual UNIX account credentials that will be used for nonprivileged or privileged interaction with the UNIX-based computers that you will be monitoring.

12.Double-click on the account you just created.

13.Select the Distribution tab.

14.Click the Add button.

15.From the Option drop down list, choose Show management servers and click the Search button.

16.In the Available items list, choose the management server that is to have these credentials distributed to them and click the Add Button.

17.Click the OK button to close the Computer Search dialog box.

18.Click the OK button to close the Run As Account Properties dialog box.

19.In the Run As Configuration container, select the Profiles folder.

20.Right click to open the properties for the UNIX Action Account or UNIX Privileged Account profile, and select the Associations tab.

21.Click Add, and select Object from Run As Profile Propertieslist. The Object Search window opens.

22.In the Look for box, select Management Server, and click Search. All the available management servers in your management group appear in the Available items box.

23.Select the management server that you will use to monitor the UNIX or Linux computer that the Run As account credentials are for. Click Add, and click OK. The management server appears in the Selected targets box.

24.In the Account column, click the Select box, and select the Step by Step Run As UNIX Action Account or Step by Step Run As UNIX Privileged Account from the list. Click OK to complete the creation of the association.

 

For a complete list of management packs provided with Operations Manager 2007 R2 Cross-Platform, see Appendix C - Cross-Platform Management Packs. Use the following steps to import the cross-platform management packs:

Procedures

To import the cross-platform management packs from the local system

1.In the Operations console, select Administration.

2.Right-click Management Packs node, and click Import Management Packs. The Import Management Packs wizard opens.

3.Click Add, and then click Add from disk.

4.In the list of management packs, select the management pack for the operating system that you want to monitor, click Select, and then click Add.

5.On the Select Management Packs page, the management packs that you selected for import are listed. An icon next to each management pack in the list indicates the status of the selection, as follows:

·A green check indicates that the management pack can be imported.

·A red error icon indicates that the management pack is dependent on other management packs that are not in the Import list and not available from the catalog. Click Import

6.The Import Management Packs page shows the progress for each management pack. Each management pack is downloaded to a temporary directory, imported to Operations Manager, and then deleted from the temporary directory. If there is a problem at any stage of the import process, select the management pack in the list to view the status details. Click Close.

 

After the management packs have been imported, follow the steps in this section to launch the Discovery Wizard to discover available UNIX and Linux-based computers and deploy the agents.

Procedures

To discover and deploy agents:

1.In the Operations Manager console, click Start, select Programs, select Systems Center Operations Manager 2007 R2, and then click Operations Console.

2.Select Administration.

3.Select the Discovery Wizard link.

4.In the Computer and Device Management Wizard, select the Discovery Type, and choose Unix/Linux Discovery Wizard.

5.Click Next.

6.Select the Discovery Method link.

7.From the Management Server list, click Add to add discovery criteria

8.In the Define discovery criteria dialog box, type the necessary information and credentials to locate the computer to discover, and click OK.

9.Click OK

10.In the Define discovery criteria dialog box, click Add to add more computers to discover, or Edit, or Remove existing ones from the Discovery Scope list. Select the discovered computer that you want in the Discovery Scope column, and Click Discover.

11.In the Discovery results dialog box, in the Select the systems you want to manage: list, select the check box or click Select All for the system or systems that you want to manage.

12.Click Next.

13.The Computer and Device Management Wizard displays the agent deployment status on the Status menu.

14.Click Done.

 

Automatic System Discovery might not detect some Linux and UNIX systems due to firewalls or security concerns. For example, if the UNIX or Linux root password is not available to the Operations Manager administrator, an error might result. Use the following procedures to manually install agents to UNIX and Linux systems.

 

To install the agent on Red Hat Enterprise Linux 5 and SUSE Linux Enterprise Server 10

1.Transfer the agent (scx-<version>-<os>-<arch>.rpm) to the Linux Server.

2.To install the package, type:

rpm -i scx-<version>-<os>-<arch>.rpm

3.To verify that the package is installed, type:

rpm -qa | grep scx

4.To verify that the Microsoft SCX WS-Management Daemon and the Microsoft SCX CIM Server are running, type:

ps –ef|grep scx

Look for the following processes in the list:

scxwsmand

scxcimserver

 

To install the agent on Solaris

1.Transfer the agent (scx-<version>-<os>-<arch>.rpm) to the Solaris Server.

(scx-<version>-<os>-<arch>.pkg.Z)

2.Run the following command:

Uncompress scx-<version>-<os>-<arch>.pkg.Z

3.To install the package, type:

pkgadd -d scx-<version>.pkg scx

4.To verify that the package is installed, type:

rpm -qa | grep scx

5.To verify that the Microsoft SCX WS-Management Daemon and the Microsoft SCX CIM Server are running, type:

ps –ef|grep scx

Look for the following processes:

scxwsmand

scxwsmand

 

To install the agent on HP-UX 11i

1.Transfer the agent (scx-<version>-<os>-<arch>.rpm) to the HP server:

cp scx-<version>.gz

2.To unzip the package, type:

gzip -d scx-<version>.gz

3.To install the package, type:

swinstall -s /path/scx-<version> scx

4.To verify that the Microsoft SCX WS-Management Daemon and the Microsoft SCX CIM Server are running, type:

ps –ef|grep scx

Look for the following processes in the list:

scxwsmand

scxcimserver

 

To install the agent on AIX

1.Transfer the agent (scx-<version>-<os>-<arch>.rpm) to the AIX server:

cp scx-<version>.gz

2.To unzip the package, type:

gzip -d scx-<version>.gz

3.To install the package, type:

/usr/sbin/installp -a -d scx-<version> scx

4.To verify that the Microsoft SCX WS-Management Daemon and the Microsoft SCX CIM Server are running, type:

ps –ef|grep scx

Look for the following processes in the list:

scxwsmand

scxcimserver

 

You can use the Health Explorer in Operations Manager 2007 to view and troubleshoot alerts, state changes, and other significant issues when you are monitoring computers on your network. Health Explorer organizes information in the following categories:

·Availability

·Configuration

·Performance

·Security

Procedures

To view system monitors

1.To open the Operations Manager console, click Start, point to Programs, point to Systems Center Operations Manager 2007, and then click Operations Console.

2.Select Monitoring from the directory.

3.Expand the Cross Platform Servers folder.

4.Expand the folder for the server type that you want.

5.Click the Server State icon for the server type that you want.

6.Double-click the green or red icon in the State column to open the Health Explorer.

7.Expand the monitoring category that you want, and view the health states of the monitors shown.

 

You can use Management Pack Templates to add custom monitoring tasks to management packs. The following templates are available:

·UNIX\Linux LogFile – This template allows the user to create ormonitor a log file for a specific log entry.

·UNIX\Linux Service – This template allows the user to create or monitor a log file for a specific log entry.

Procedures

To use the UNIX\Linux LogFile management pack template

1.To open the Operations Manager 2007 console, click Start, point to Programs, point to Systems Center Operations Manager 2007, and then click Operations Console.

2.Select Authoring from the directory and select the Add Monitoring Wizard link.

3.Select the UNIX\Linux LogFile monitoring type from the Select monitoring type list, and click Next.

4.Type the name of the monitor and its description.

5.Select the destination management pack from the Management Pack list, or select New and fill in the general properties text boxes, click Next.

6.Select the Server name or Computer group name option, and click the browse icon.

7.Select the server or computer group name that you want from the list.

8.Click OK.

9.Under Define Log file, type the Log file path and the Expression that you want.

10.Perform an Expression Test by typing an expression for which you want to search in theSample entry box. For example, type Failure to search for the word, failure, in the monitored log files.

11.Click Test, and ensure that “Found match within sample entry” appears in Result. Click Next.

12.Review the Summary list to ensure that the information is correct.

13.Click Create. The name of the LogFile template and the date and time it was created appears.

To use the UNIX\Linux Service management pack template

1.To open the Operations Manager 2007 console, click Start, point to Programs, point to Systems Center Operations Manager 2007, and click Operations Console.

2.Select Authoring from the directory, and select the Add Monitoring Wizard link.

3.In the Select Monitoring Type dialogue box, select Unix\Linux Service from the list. Click Next.

4.In the Unix Service Name and Description dialogue box type the name of the monitor and its description.

5.Select the destination management pack from the Management Pack list, or select New and fill in the general properties text boxes. Click Next.

6.In the Service Details dialogue box, browse for the Server name or Computer group name option you want to monitor.

7.In the Select service list, select the service that you want to monitor.

8.If you want to apply the service monitor to a group of computers, select the Apply to computer group check box.

9.Click the browse icon.

10.Select a group from the Select computer group list. Click OK.

11.On the Service Name page, click Create. The UNIX\Linux Service template displays the name, creation date, and creation time of the service template.

 

One of the challenges facing businesses is ensuring that resources, such as applications and systems, are available and performing at acceptable levels. To assure this, companies set goals for their service availability and response times. Operations Manager 2007 R2 provides the capability to monitor these service goals through the use of service level tracking.

In Operations Manager 2007 R2, you define your service goals (referred to as, service level objectives) and then generate reports that show how your resources have performed against those goals. Using the information from these reports, you can identify any shortfalls between your service goals and your actual performance. This means that you are not only aware of problems but also can track the relative business effect of these problems.

For example, if you have a group of servers running instances of Microsoft Exchange Server, which are critical to your internal e-mail network, you can define a service level objective that states that 95% of the servers must be available at all times. Then you can generate a report that compares the actual availability of those servers against the service level objective.

This guide demonstrates the process of configuring and using service level tracking in Operations Manager 2007 R2.

Before you can complete the Service Level monitoring scenario, you must do the following:

·Deploy Operations Manager 2007 R2, including the Reporting component.

·Define the metrics that you want to track against.

·Ensure that the health model is correct.

Tracking service level objectives involves the following steps.

 

Step  

Reference  

Define the objectives that you want to track for an application.

Defining a service level objective against an application

Define the objectives that you want to track for a group.

Defining a service level objective against a group

Run a report that reflects the status of the service level objectives.

Generating an SLM Report

 

You can configure a service level objective (SLO) to define the availability and performance goals for an application. In the following procedure, you create a new service level (LOB Application 1) against a distributed application, define a Monitor SLO that is based on availability (99.9% up-time), and define a Collection Rule SLO that is based on a performance rule (80% average processor time).

Procedures

To define a service level objective for an application

1.In the Operations console, from the Authoring view, click Management Pack Objects and then click Service Level Tracking in the Authoring navigation tree.

2.In the Actions pane, click Create.

3.Type a name for the service level that you are defining. For example, type LOB Application 1. Optionally, you can provide a description. Click Next.

4.Under Targeted class, click Select to specify the class for the service level, such as Distributed Application.

5.Click Next.

6.On the Service Level Objectives page, click Add, and then click Monitor state SLO to create a new monitor. This monitor will track the availability of the application.

7.Define the state monitor as follows:

a.Type a name for the service level objective. For this scenario, type Availability.

b.Under Monitor, choose the specific monitor that you want to use to measure the objective. For this scenario, choose Availability.

c.For the service level objective goal, provide the numerical measure for your objective. For example, select 99.990 to indicate that your goal is 99.99% availability.

d.You can refine what the monitor tracks as available by selecting or clearing any of the following state criteria:

·Unplanned maintenance

·Unmonitored

·Monitoring unavailable

·Monitor disabled

·Planned maintenance

·Warning

e.Click OK.

8.On the Service Level Objectives page, click Add, and then click Performance rule SLO to create a new collection rule. This rule will track the performance of the application

9.Define the performance collection rule as follows:

a.Type a name for the service level objective. For this scenario, type Performance.

b.Specify the target class for the rule. Note that this class must be contained in the distributed application. For this scenario, select Windows Operating System.

c.Specify the performance collection rule to use. For this scenario, choose Collect Processor\ % Processor Time performance counter.

d.Choose one of the following aggregation methods:

·Average

·Min

·Max

e.Define the service level object goal by choosing either Less than or More than and entering a value. For this scenario, choose Less Than and 80. This indicates that the performance goal is to never exceed 80% processor time.

f.Click OK.

10.On the Service Level Objectives page, click Next.

11.Review the summary, and click Finish.

12.When the Completion page appears, click Close.

To validate the creation of the service level objective

·In the Service Level Tracking pane, select the new service level, and click Properties in the Action pane.

 

You can configure a service level objective (SLO) against a group of computers to ensure their availability. In the following scenario, you create a service level that consists of a group of servers (Exchange Servers) and then define a service level objective of 99.99% availability.

Procedures

To define a service level objective against a group

1.In the Operations console, from the Authoring view, click Management Pack Objects, and then click Service Level Tracking in the Authoring navigation tree.

2.In the Actions pane, click Create.

3.Type a name for the service level that you are defining. For example, type Exchange Servers. Optionally, you can provide a description. Click Next.

4.Under Targeted class, click Select to specify the class for the service level, such as Operations Manager Management Group.

5.You can narrow the service level by using the Scope option. The default value is to use all objects of the targeted class.

6.Select the management pack in which this service level will be saved. You can use an existing management pack or create a new one.

7.Click Next.

8.On the Service Level Objectives page, click Add, and then click Monitor state SLO to create a new monitor. This monitor will track the availability of the application.

9.Define the state monitor as follows:

a.Type a name for the service level objective. For this scenario, type Availability.

b.Under Monitor, choose the specific monitor that you want to use to measure the objective. For this scenario, choose Availability.

c.For the service level objective goal, provide the numerical measure for your objective. For example, select 99.990 to indicate that your goal is 99.99% availability.

d.You can refine what the monitor tracks as available by selecting or clearing any of the following state criteria:

·Unplanned maintenance

·Unmonitored

·Monitoring unavailable

·Monitor disabled

·Planned maintenance

·Warning

e.Click OK.

10.On the Service Level Objectives page, click Next.

11.Review the summary, and click Finish.

12.When the Completion page appears, click Close.

To validate the service level objective

·In the Service Level Tracking pane, select the new service level, and click Properties in the Action pane.

 

You can create a report that shows how your application or group is performing the defined service level objectives. The report that is generated provides both high-level information (to give you a picture of the overall status at a glance) and detailed low-level information (to provide specific information on availability and performance metrics).

The Service Level Tracking Summary report shows the results for one or more service levels in comparison to the defined target objectives. From this report, you can examine a more detailed report, the State view, or the Service Level Agreement view.

Use the following steps to generate a Service Level Tracking Summary report.

Procedures

To generate a Service Level Tracking Summary report

1.In the Reporting view of the Operations console, click Microsoft Service Level Report Library.

2.Right-click the Service Level Tracking Summary report, and click Open.

3.Click Add SLA.

4.In SLA Name, type the name of the defined service level (following the example in the previous procedures, LOB 1 Application), and click Search.

5.Select the service level, and click Add.

6.Click OK to close the Add SLA window.

7.Define the data period for the report. You can select the following options:

·Data aggregation

·Day range

·Time range

8.Under Report Fields, select the fields that you want to include in the report. The fields that are available depend on the day and time range selection. For example, if you have specified a day range of Thursday to Wednesday, you do not have the option to include the Last 30 Days field.

9.Click Run to generate the report.

To validate your service level report

·When you run the Service Level Tracking Summary report, you should see a report that resembles the following:

 

Notifications generate messages or run commands automatically when an alert is raised on a monitored system. By default, notifications for alerts are not configured. If you want users to be notified immediately when an alert is generated you need to configure notifications and let the users know the steps they need to take to receive them.

To configure notifications, an Operations Manager administrator must perform the following steps:

·Configure the Notification action account

·Configure notification channels

Once the above steps are complete, an administrator, operator, or advanced operator can do the following:

·Configure notification subscribers

·Create notification subscriptions

Operations Manager 2007 R2 Beta introduces both terminology and procedural changes to configuring and using notifications. The R2 Beta release also provides enhanced notification functionality – you can now create a notification subscription directly from an alert.

If this is the first time you have used notifications, this guide walks you through the process for configuring and using notifications. If you have previously used notifications, you can compare your experience to the procedures outlined in this guide.

Before you configure and use notifications, do the following:

·Install Operations Manager 2007 R2.

·Gather information for the account that will be used to send notifications. If you are will be sending notifications through e-mail, you will need an e-mail address.

·Gather information about any users who will receive notifications. For example, if you want to use e-mail to send notifications to a user, you will need the user’s e-mail address.

Configuring and using notifications involves the following steps.

 

Step  

Reference  

Create a user account for sending notifications, define the method for notifications, and define the user who will receive the notifications.

Configuring notifications

Define when and why a notification should be sent.

Creating a notification subscription

Create a new notification subscription for a specific alert.

Creating a notification subscription from an alert

 

Before you can use notifications, you need to create the user account (Notification action account) that will be used to send notifications, configure the method (or channel) for sending notifications, and define the recipient (or subscriber) for the notifications.

Note

The procedure below configures an e-mail notification channel. You can additionally configure notification channels that use instant messages, SMS, or commands. For information on those channels, see the Operations Guide.

Procedures

To create and configure the Notification action account

1.In the Operations console, click Administration.

2.In the Administration pane, right-click Security, and then click Create Run As Account. Use the Create Run As Account Wizard to create an account to use as the Notification action account, which is used to send the notifications.

·On the General page, select Windows from the Run As Account type drop-down list, and then in Display name, type Notification action account.

·On the Account page, type in the information for the user name, password and domain of the user account that you are creating.

3.In the navigation pane, click Accounts under Run As Configuration.

4.In the details pane, right-click Notification action account, and then click Properties.

5.On the Distribution tab, click Add to add the root management server.

6.Select the server and click OK. Click OK again to close the properties window.

7.In the navigation pane, click Profiles under Run As Configuration.

8.Right-click Notification Account and click Properties.

9.On the Associations tab, click Add and then click Class.

10.Type Alert Notification Subscription Server and click Search.

11.Double-click Alert Notification Subscription Server in the resulting list and click OK.

12.On the Associations tab, click Select next to Alert Notification Subscription Server.

13.Select Notification action account in the drop-down list and then click OK.

To enable an e-mail notification channel

1.In the Operations console, click the Administration button.

2.In the navigation pane, right-click Notifications and click New channel and then click E-Mail (SMTP).

3.Type a name for the notification channel and optionally provide a description. Click OK.

4.Click Add to display the Add SMTP server dialog box.

5.Type the fully qualified domain name (FQDN) of a Simple Mail Transfer Protocol (SMTP) server, type the port number, select the authentication method used by the SMTP server, and then click OK.

6.Type the Return Address that should appear on e-mail notifications, and then in the Retry primary after list, select the number of minutes to wait before trying to resend a notification to the primary SMTP server.

7.Click Next.

8.In the E-mail subject and E-mail message fields, specify the wildcard parameters you want to use to populate these fields in the e-mail. You can click the arrow to display available wildcards.

9.Select the importance of the e-mail message. You can choose Normal, High, or Low.

10.Select the encoding to use for the message and click Save.

To create a notification subscriber

1.In the Operations Console, click the Administration button.

2.In the navigation pane, right-click Notifications and click New subscriber.

3.Type a name for this recipient and click Next.

4.Set the schedule for when this subscriber should receive notifications. The default is to always send notifications.

5.Define the addresses for the subscriber. Click Add.

6.Type a name for the subscriber address, such as Work E-mail, and click Next.

7.In Channel Type, select E-Mail (SMTP), type the e-mail address for where to send notifications, and click Next.

8.You can set the schedule for when this address will get notifications. The default is to always send notifications.

9.Click Finish.

10.In the Notification Subscriber wizard, click Save and then click Close.

 

A notification subscription defines what a user is notified about and how they receive notifications.

Note

Both administrators and operators can create notification subscriptions. The following procedure documents how the administrator creates the subscription. For information on how the operator creates the subscription, see the Operations Guide.

Procedures

To create a notification subscription

1.In the Operations Console, click the Administration button.

2.In the navigation pane, right-click Notifications and click New subscription.

3.Type a name for the subscription, type a short description, and then click Next.

4.Define the criteria for sending notifications. Select a condition and then provide the criteria by double-clicking the underlined text displayed in the Criteria description box.

5.Click Next.

6.Click Add or Remove to select the notification subscriber to whom the notifications should be sent.

7.Click Search to display all available subscribers.

8.Double-click the subscriber you want to use and click OK.

9.Click Next.

10.Click Add or Remove to select the notification channel to use.

11.Click Search to display all available channels.

12.Double-click the channel you want to use and click OK.

13.Click Next and then Finish.

14.Click Close.

 

You can create a notification subscription from an alert to ensure that you are notified if this alert is triggered again. You can either create a new subscription or add the alert to an existing subscription. In the following procedure, you create a new subscription.

Procedures

To create a notification subscription from an alert

1.In the Alerts view, right-click the alert, click Notification subscription and then click Create.

2.The name and description for the subscription are pre-populated with information from the alert. Click Next.

3.The conditions and criteria for when the notification is sent are pre-populated with default values from the alert. Click Next.

4.Click Add or Remove to select the notification subscriber to whom the notifications should be sent.

5.Click Search to display all available subscribers.

6.Double-click the subscriber you want to use and click OK.

7.Click Next.

8.Click Add or Remove to select the notification channel to use.

9.Click Search to display all available channels.

10.Double-click the channel you want to use and click OK.

11.Click Next and then Finish.

12.Click Close.

 

Every agent carries out duties, as defined in the applied management packs, by using the Agent Action Account. By default this is the Local System Account, although the administrator can choose to define a different account at installation time. Some management packs include actions that cannot be successfully completed by using the default Agent Action Account. In this case, the management pack author can define a Run As profile that is used to carry-out those actions that require the elevated privileges.

Run As profiles are created in Operations Manager 2007 R2 when the management pack that contains them is imported. They are in the Operations console, Administration view, Run As Configurations, Profiles folder. To configure a Run As profile, you need one or more Run As accounts and any number of the Groups, Objects or Classes that the profile will be applied to.

In this scenario, you learn how to configure a Run As profile using the UNIX Action account profile as an example.

Run As Scenario Overview

·This scenario occurs in the Run As Configuration container in the Operations console.

·First, you examine the UNIX Action Account profile.

·Second, you create a Run As account object in the Accounts container.

·Third, you edit the UNIX Action Account profile and create associations between the Run As account and one or more Groups, Objects and Classes

To complete the Run As scenario, you must have the following environment:

·Operations Manager 2007 R2 installed

·Operations Manager 2007 R2 Administrator Role access to the Operations console

·User accounts on the UNIX-based computers that will be monitored; you must have both the username and the password.

This procedure shows you how to configure a Run As account and Run As profile for the Unix Action Account Profile.

Procedures

how to configure Run as using a cross platform example

1.Open the Operations console with an account that is a member of the Operations Manager 2007 R2 Administrators profile.

2.Select the Administration view.

3.In the Run As Configuration container, select the Profiles folder.

4.In the results pane, double-click the Unix Action Account profile to open the Run As Profile Properties – Unix Action Account window.

5.Select the Associations tab. Notice that the Selected Targets box is empty. Click Cancel to close the window.

6.In the Run As Configuration container, select the Accounts folder.

7.Right-click in the results pane, select Create Run As Account from the context menu to start the Create Run As Account Wizard, and then click Next.

8.On the General page, click the Run As Account type arrow next to the Run As Account type box.

9.From the Run As Account type list, select Basic Authentication. Notice that there are other options to choose from. The option you select depends on the type of account and authentication that is required. Refer to the management pack guide for the management pack that contains the profile that you are configuring for information on which account type to select.

10.In the Display Name field, enter a name you want to use to represent the Unix Action Account credentials. In this case, enter Step by Step Run As Unix Action Account, and then click Next.

11.On the Basic Run As Account page, enter the appropriate values in the Account Name, Password, and Confirm Password fields, and then click Create. This creates the Step by Step Run As Unix Action Account object and maps it to the actual UNIX account credentials that will be used for nonprivileged interaction with the UNIX-based computers that you will be monitoring.

12.Open the properties of the account that you just created and select the Distribution tab.

13.On the Distribution tab, click on Add….

14.In the Options: drop down list select Show management servers and click search.

15.Select the management server that you want these credentials distributed to from the list of management servers displayed in the Available items box and click Add.

16.Click, OK to close the Computer Search box.

17.Click, OK to close the Run As Account Properties box.

18.In the Run As Configuration container, select the Profiles folder.

19.Open the properties for the UNIX Action Account profile, and select the Associations tab.

20.Click Add, and select Group… from thelist. The Group Search window opens.

21.In the Filter: box, enter Unix, and then click Search. The Unix Computer Groupappears in theAvailable items box.

22.Select the Unix Computer Group , click Add, The Unix Computer Group appears in the Selected targets box. Click,OK.

23.In the Account column, click on the Select… box, and select the Step by Step Run As Unix Action Account from the list. Click OK to complete the creation of the association.

 

 

 

Multiple Associations in a Profile

Every profile can contain multiple associations. Each association can consist of a different pairing of Run As Accounts and Groups, Objects or Classes. This gives Operations Manager 2007 R2 great flexibility in the configuration of Run As profiles. When an agent must run an action that requires a Run As account, it consults the associations that have been defined in the profile to find one that is applicable. If it does not find one, it attempts to use the default action account, which is usually the Local System account.

Each management pack guide contains information for configuring the required credentials, Run As Account, and associations if the management pack calls for them.

The Windows Process Monitoring Management Pack template is used to create process monitors.The monitor watches the running-processes list on a given computer or groups of computers that you define.

Process Monitoring Scenario Overview

·This scenario occurs in the Process Monitoring container in the Authoring view of the Operations console

·You will create a process monitor for SQLserver.exe

 

Requirements for Using Process Monitor

·Operations Manager 2007 R2 installed.

·Operations Manager 2007 R2 Adminsitrator Role access to the Operations console.

Steps For Using the Monitor a Windows Process Template

1.Launch the Add monitoring wizard from the Authoring space and pick the process monitoring template.

2.Specify a name for the template such as “Monitoring SQL process” and save it in a new management pack called “SQL Overrides.”.

3.Click Next and choose to Monitor whether and how a process is running (for processes you want). Specify “sqlservr.exe” in the process name text box. Scope the monitor to target the All Computers group.

4.Specify your own custom alert criteria for the SQL process and click Next.

5.Specify the performance counter data collection settings you would like to set. For example select Generate an alert if CPU usage exceeds the specified thresholds and set the value to “70”. Also select Generate an alert if memory usage exceeds the specified threshold and set the value to “20”.

 

Summary of Appendixes

This appendixes section includes:

·Appendix A – Table of Available Cross-Platform Reports

·Appendix B – Cross Platform Operation System Package Dependencies

·Appendix C – Cross-Platform Management Packs

·Appendix D – Uninstalling the Cross Platform Management Packs and Agents

·Operations Manager 2007SP1 to R2 Upgrade procedures

The following is a list of available reports that can be produced in Systems Center Operations Manager 2007 R2 Cross-Platform. All the reports can be run for any of the computers running UNIX and Linux operating systems.

 

Report Type  

Description  

Disk Performance Analysis

The Disk Performance Analysis report displays historical charts and data tables of disk performance for logical disks on discovered UNIX and Linux computers. The report displays information for several performance counters.

Memory Performance History (Available MB)

Memory Performance History Reports display historical charts and data tales of memory performance.

Memory Performance History (Page Reads per Sec)

Memory Performance History Reports display historical charts and data tales of memory performance.

Memory Performance History (Page Writes per Sec)

Memory Performance History Reports display historical charts and data tales of memory performance.

Memory Performance History (Pages per Sec)

Memory Performance History Reports display historical charts and data tales of memory performance.

Operating System Configuration

Operating system Configuration reports display the following properties of discovered UNIX and Linux computers:

·Physical Memory

·Build Number

·Service Pack Version

·Install Date

·CSD Version

·OS Version

·Serial Number

·System Drive

Operating System Performance

The Operating System Performance report displays historical charts that show the processor and memory performance of UNIX and Linux computers.

Operating System Storage Configuration

The Operating System Storage Configuration report displays the following properties of logical disks on discovered UNIX and Linux computers:

·Device Name

·File System

·Device Description

·Size (Bytes)

Performance History

The Performance History report displays the performance of processors on discovered UNIX and Linux computers, showing the percentage value of time a processor was busy during the sampling interval.

Performance History (Percent Processor Time)

A Performance History (Percent Processor Time) report shows the percentage value of total processor time utilization system-wide during the sample interval.

Total Percent IO Wait Time (percentage Usage)

The Total Percent IO Wait Time (percentage Usage) report displays the percentage of interrupt time between IO operations.

 

The following tables describe the required UNIX and Linux operating systems and package dependencies.

IBM AIX 5L 5.3

 

Required Package  

Description  

Minimum Version  

xLC RTE

xLC runtime

9.0.0.6

OpenSSL/openssl.base

OpenSSL Libraries

0.9.8.4

bos.rte.security

On AIX, PAM is part of the core operating system components. More specifically it is contained in the bos.rte.sequrity package.

5.3.0.65

Libxml2

 

RPM Package Manager

2.6.21-3

 

IBM AIX 6.1

 

Required Package  

Description  

Minimum Version  

oslevel

 

6100-00-01-0748

OpenSSL/openssl.base

OpenSSL Libraries

0.9.8.4

PAM

objrepos bos.rte.security;On AIX, PAM is part of the core operating system components. More specifically it is contained in the bos.rte.sequrity package.

6.1.1.1

objrepos rpm.rte

OpenWSMan is dependent on libxml2. On AIX 5, libxml2 is only available as an RPM package. This means that RPM also needs to be installed. Both these are available on the AIX installation media.

3.0.5.42 RPM Package Manager

Libxml2

 

2.6.21-3

 

HP-UX 11i v2 IA 64

 

Required Package  

Description  

Minimum Version  

HPUXBaseAux

HP-UX Base OS Auxiliary

B.11.23.0706

HPUXBaseOS

Base OS

B.11.23

HPUXBaseAux

Base OS Auxiliary

B.11.23.0706

HPUXBaseAux.openssl

Secure Network Communications Protocol

A.00.09.07l.003

OS-Core.MinimumRuntime.UX2-CORE IA64-specific

Pluggable Authentication Modules

B.11.23

OS-Core.Runtime.UX2-CORE IA64-specific

Pluggable Authentication Modules

B.11.23

libxml2, zlib

OpenWSMan is dependent on libxml2 which in turn is dependent on zlib. These are provided by HP-UX Internet Express.

libxml2-A.11.00-2.6.31.001,zlib-A.11.00-1.2.3.001

 

HP-UX 11i v2 PA-RISC

 

Required Package  

Description  

Minimum Version  

HPUX11i-OE

HP-UX Foundation Operating

B.11.23.0706

HPUXBaseAux.openssl

OpenSSL Libraries

A.00.09.07l.003

PAM

Pluggable Authentication Modules

On HP-UX, PAM is part of the core operating system components. No specific dependencies are needed for this.

libxml2, zlib

OpenWSMan is dependent on libxml2 which in turn is dependent on zlib. These are provided by HP-UX Internet Express.

libxml2-A.11.00-2.6.31.001,zlib-A.11.00-1.2.3.001

 

HP-UX 11i v3 PA-RISC

 

Required Package  

Description  

Minimum Version  

HPUX11i-OE

HP-UX Foundation Operating Environment

B.11.31

openssl/OPENSSL-LIB

OpenSSL Libraries

A.00.09.08d.002

Libxml2/LIBXML2-LIB

The XML Library; package name ixLibxml2

A.09.00-2.6.28.002

 

HP-UX 11i v3 IA64

 

Required Package  

Description  

Minimum Version  

HPUX11i-OE

HP-UX Foundation Operating Environment

B.11.31.0709

SysMgmtMin

Minimum Software Deployment Tools

B.11.31.0709

SysMgmtMin.openssl

Secure Network Communications Protocol

A.00.09.08d.002

Libxml2/LIBXML2-LIB

The XML Library; package name ixLibxml2

A.09.00-2.6.28.002

PAM

Pluggable Authentication Modules

On HP-UX, PAM is part of the core operating system components. No extra dependencies are needed for this.

ixLibxml2

Libxml2 Library, OpenWSMan is dependent on libxml2. This is provided by HP-UX Internet Express. This version of libxml2 is not dependent on zlib.

A.10.00-2.6.30.002

ixLibxml2

ixLibxml2.Libxml2

A.10.00-2.6.30.002

 

HP-UX 11i v2 IA/PA

 

Required Package  

Description  

Minimum Version  

HPUX11i-OE

HP-UX Foundation Operating Environment

B.11.31.0709

openssl/OPENSSL-LIB

OpenSSL Libraries

A.00.09.08d.002

Libxml2/LIBXML2-LIB

The XML Library; package name ixLibxml2

A.09.00-2.6.28.002

 

Red Hat Enterprise Linux ES Release 4

 

Required Package  

Description  

Minimum Version  

Unpatched compiler version

 

3.4.3-9.EL4

Openssl

OpenSSL Libraries

0.9.7a-43.1

PAM

Pluggable Authentication Modules

0.77-65.1

libxml2, zlib

ZIP Compression Library

libxml2-2.6.16-6, zlib-1.2.1.2-1

 

Red Hat Enterprise Linux Server release 5.1 (Tikanga)

 

Required Package  

Description  

Minimum Version  

Unpatched compiler version

 

4.1.1-52.el5

glibc

OpenSSL Libraries

2.5-12

Openssl

OpenSSL Libraries

0.9.8b-8.3.el5

PAM

Pluggable Authentication Modules

0.99.6.2-3.14.el5

libxml2, zlib

ZIP Compression Library

libxml 2-2.6.26-2.1.2,zlib-1.2.3-3

 

Solaris 8 SPARC

 

Required Package  

Description  

Minimum Version  

Required OS patch

PAM memory leak

108434-22

SUNWlibC

Sun Workshop Compilers Bundled libC(sparc)

5.8,REV=99.06.09

OpenSSL

SMCossl from Sunfreeware

openssl(sparc) 0.9.8h

PAM

SUNWcsl, Core Solaris, (Shared Libs)(sparc)

11.8.0,REV=2000.01.08.18.12

zlib, libiconv, libgcc, libintl

ZIP Compression Library, OpenWSMan is dependent on libxml2 which is not supplied by Sun. The version we depend on is from Sunfreeware. This version is in turn dependent on zlib and libiconv. Libiconv is also dependent on libgcc and libintl. All these packages are found on sunfreeware.

SMClxml2, libxml2, (sparc) 2.6.31; SMCzlib, zlib, (sparc) 1.2.3; SMCliconv, libiconv,sparc) 1.11; SMClgcc, libgcc, (sparc) 3.4.6; SMClintl, libintl, (sparc) 3.4.0

 

Solaris 9 SPARC

 

Required Package  

Description  

Minimum Version  

Required OS patch

PAM memory leak

112960-48

SUNWlibC

Sun Workshop Compilers Bundled libC(sparc)

5.9,REV=2002.03.18

OpenSSL

SMCosslg from Sunfreeware. Sun does not provide any version of OpenSSL for Solaris 9 SPARC. There is a version available from Sunfreeware.

openssl (sparc) 0.9.8h

PAM

SUNWcsl, Core Solaris, (Shared Libs)(sparc)

11.9.0,REV=2002.04.06.15.27

zlib, libiconv, libgcc, libintl

ZIP Compression Library, OpenWSMan is dependent on libxml2, which is not supplied by Sun. There is a version from Sunfreeware. This version is dependent on zlib and libiconv. Libiconv is also dependent on libgcc and libintl.

SMClxml2, libxml2, (sparc) 2.6.31; SMCzlib, zlib, (sparc) 11.9.0, REV=2002.03.02.00.35; SMCliconv, libiconv,sparc) 1.11

 

Solaris 10 SPARC

 

Required Package  

Description  

Minimum Version  

Required OS patch

PAM memory leak

117463-05

SUNWlibC

Sun Workshop Compilers Bundled libC (sparc)

5.10, REV=2004.12.22

SUNWlibms

Math _ Microtasking Libraries (Usr) (sparc)

5.10, REV=2004.11.23

SUNWlibmsr

Math _ Microtasking Libraries (Root) (sparc)

5.10, REV=2004.11.23

SUNWcslr

Core Solaris Libraries (Root)(sparc)

11.10.0, REV=2005.01.21.15.53

PAM

SUNWcsr, Core Solaris, (Root) (SPARC)

11.10.0, REV=2005.01.21.15.53

libxml2, zlib

OpenWSMan is dependent on libxml2 which in turn is dependent on zlib. Both are provided as bundled packages by SUN.

 

SUNWlxml The XML library (sparc), SUNWzlib The Zip compression library

11.10.0, REV=2005.01.08.05.16, 11.10.0, REV=2005.01.08.05.16

 

 

Solaris 10 x86

 

Required Package  

Description  

Minimum Version  

Required OS patch

PAM memory leak

117464-04

SUNWlibC

Sun Workshop Compilers Bundled libC(i386)

5.10,REV=2004.12.20

SUNWlibmsr

Math _ Microtasking Libraries (Usr) (i386)

5.10, REV=2004.12.18

SUNWcsl

Core Solaris, (Shared Libs) (i386)

11.10.0,REV=2005.01.21.16.34

SUNWcslr

Core Solaris Libraries (Root) (i386)

11.10.0, REV=2005.01.21.16.34

OpenSSL

SUNWopenssl-libraries

OpenSSL Libraries (Usr) (i386) 11.10.0, REV=2005.01.21.16.34

PAM

SUNWcsr

Core Solaris, (Root)(i386) 11.10.0,REV=2005.01.21.16.34

libxml2, zlib

OpenWSMan is dependent on libxml2 which in turn is dependent on zlib. Both are provided as bundled packages by SUN.

 

SUNWlxml The XML library (i386) 11.10.0, REV=2005.01.08.01.09, SUNWzlib The Zip compression library (i386)

11.10.0, REV=2005.01.08.01.09

 

 

SUSE Linux Enterprise Server 9 (i586)

 

Required Package  

Description  

Minimum Version  

OS Patch Libstdc++-41.rpm

Standard shared library

41-4.1.2_20070115-0.6

OS Patch libgcc-41.rpm

 

Prereq of the above - customer must install this.

Openssl

OpenSSL Libraries

0.9.7d-15.10

PAM

Pluggable Authentication Modules

0.77-221.1

libxml2, zlib

ZIP Compression Library

libxml2-2.6.7-28.1,zlib-1.2.1-70.1

 

SUSE Linux Enterprise Server 10 SP1 (i586)

 

Required Package  

Description  

Minimum Version  

glibc-2.4-31.30

Standard shared library

2.4-31.30

OpenSSl

OpenSSL Libraries

0.9.8a-18.15

PAM

Pluggable Authentication Modules

0.99.6.3-28.8

libxml2, zlib

ZIP Compression Library

libxml2 2.6.23-15.2, zlib 1.2.3-15.2

 

Cross Platform Management Packs

The following cross platform management packs are included with the installation of Operations Manager 2007 Cross Platform Extensions.

 

Management Pack Name  

File Name  

Description  

Microsoft IBM AIX 5L 5.3 Technology Level 6, SP5, Operating System Management Pack

Microsoft.AIX.5.3.mp

This management pack discovers and monitors IBM AIX 5L 5.3 computers.

Microsoft IBM AIX 6.1, Operating System Management Pack

Microsoft.AIX.6.1.mp

This management pack discovers and monitors IBM AIX 6.1 computers.

Microsoft AIX Core Library

Microsoft.AIX.Library.mp

This management pack contains the definitions that are specific to the AIX platform.

Microsoft HPUX 11i v2 Operating System Management Pack

Microsoft.HPUX.11iv2.Library.mp

This management pack discovers and monitors HPUX 11i v2 computers.

Microsoft HPUX 11i v3 Operating System Management Pack

Microsoft.HPUX.11iv3.Library.mp

This management pack discovers and monitors HPUX 11i v3 computers.

Microsoft HPUX Core Library

Microsoft.HPUX.Library.mp

This management pack contains the definitions that are specific to the HPUX platform.

Microsoft Linux Core Library

Microsoft.Linux.Library.mp

This management pack contains the definitions that are specific to the Linux platform.

Microsoft Linux Red Hat Core Library

Microsoft.Linux.RedHat.Library.mp

This management pack contains the definitions that are specific to the Red Hat platform.

Microsoft Red Hat Enterprise Linux 4 Operating System Management Pack

Microsoft.Linux.RHEL.4.mp

This management pack discovers and monitors Red Hat Enterprise Linux 4 computers.

Microsoft Red Hat Enterprise Linux 5 Operating System Management Pack

Microsoft.Linux.RHEL.5.mp

This management pack discovers and monitors Red Hat Enterprise Linux 5 computers.

Microsoft Linux SUSE Enterprise 9 Operating System Management Pack

Microsoft.Linux.SLES.9.mp

This management pack discovers and monitors SUSE Enterprise 9 computers.

Microsoft Linux SUSE Enterprise 10 Operating System Management Pack

Microsoft.Linux.SLES.10.mp

This management pack discovers and monitors SUSE Enterprise 10 computers.

Microsoft Linux SUSE Core Library

Microsoft.Linux.SUSE.Library.mp

This management pack contains the definitions that are specific to the SUSE platform.

Microsoft Solaris 8 Operating System Management Pack

Microsoft.Solaris.8.mp

This management pack discovers and monitors Solaris 8 computers.

Microsoft Solaris 9 Operating System Management Pack

Microsoft.Solaris.9.mp

This management pack discovers and monitors Solaris 9 computers.

Microsoft Solaris 10 Operating System Management Pack

Microsoft.Solaris.10.mp

This management pack discovers and monitors Solaris 10 computers.

Microsoft Solaris Core Library

Microsoft.Solaris.Library.mp

This management pack contains the definitions that are specific to the Solaris platform.

UNIX Service Image Library

Microsoft.Unix.Image.Library.mp

This management pack contains icons for UNIX types.

Microsoft UNIX Core Library

Microsoft. Unix.Library.mp

This management pack contains the definitions that are specific to the UNIX platform.

Microsoft UNIX LogFile Library

Microsoft. Unix LogFile.mp

This management pack contains the LogFiles that are specific to the UNIX platform.

Microsoft UNIX Service Library

Microsoft. Unix.Service.mp

This management pack contains the views that are specific to the UNIX platform.

Microsoft UNIX Views Library

Microsoft. Unix.Views.mp

This management pack contains the views that are specific to the UNIX platform.

 

If you decide to stop monitoring UNIX or Linux computers, there are three ways you can uninstall the management packs and agents:

1.Delete selected UNIX or Linux system management packs from the Operations Manager 2007 R2 console.

When you no longer need a management pack, you can delete it by using the Operations console. When you delete a management pack, all the settings and thresholds that are associated with it are removed from Operations Manager 2007 R2. The associated .mp or .xml file is also deleted from the hard disk of the Management Server. You can delete a management pack only if you have first deleted dependent management packs.

2. Delete an agent from Operations Manager 2007 R2 and uninstall the agent from the monitored computer. It will be uninstalled first from the UNIX or Linux computer.

3.Delete the agent from Operations Manager without uninstalling it on the UNIX or Linux host.

Use the following procedures to manually uninstall agents.

To delete a UNIX or Linux system management pack from the Operations Console

1.In the Operations Manager 2007 R2 console, click Administration.

2.Click Management Packs.

3.In the Management Packs pane, right-click the pack you want to remove.

4.Click Delete.

To delete a UNIX or Linux system agent from Operations Manager 2007 R2 and the monitored computer

1.In the Operations Manager 2007 R2 console, click Administration.

2.Click Unix/Linux Servers.

3.In the Unix/Linux Servers pane, right-click the monitored computer agent you want to delete.

4.Select Uninstall.

Delete an agent from Operations Manager without uninstalling it on the UNIX or Linux host

1.In the Operations Manager 2007 R2 console, click Administration.

2.Click Unix/Linux Servers.

3.In the Unix/Linux Servers pane, right-click the monitored computer agent you want to remove.

4.Select Delete .

After the UNIX or Linux computer has been deleted from the list of monitored computers, you must log in to the computer and manually uninstall the agent. Use the following procedures to manually uninstall agents from UNIX and Linux computers.

To uninstall the agent from Red Hat Enterprise Linux Servers:

1.Log in as the root user, and uninstall the agent by typing:

rpm –e scx

2.To verify that the package is uninstalled, type:

rpm –q scx

To uninstall the agent from SUSE Linux Enterprise Server

1.Log in as the root user, and uninstall the agent by typing:

rpm –e scx

2.To verify that the package is uninstalled, type:

rpm –q scx

To uninstall the agent from Solaris computers

1.Log in as the root user, and uninstall the agent by typing:

pkgrm MSFTscx

2.To verify that the package is uninstalled, type:

pkginfo –I MSFTscx

To uninstall the agent from HP-UX 11i

1.Log in as the root user, and uninstall the agent by typing:

swremove scx

2.To verify that the package is uninstalled, type:

swlist scx

To uninstall the agent from IBM AIX

1.Log in as the root user, and uninstall the agent by typing:

installp –u scx

2.To verify that the package is uninstalled, type:

lslpp –L scx.rte

 

Upgrading from Microsoft Operations Manager 2007 SP1 to Microsoft Operations Manager 2007 R2 is a multistep process. The procedures listed in this section are presented in the order in which they must be completed. Most procedures must be completed on the computer that hosts the component being upgraded.

Upgrade Paths

To upgrade Operations Manager 2007 SP1 to Operations Manager 2007 R2, run SetupOM.exe from your source media.

Here is an outline of the supported and unsupported upgrade paths.

 

Upgrading System Center Desktop Error Monitoring to System Center Operations Manager 2007 R2

Start with System Center Desktop Error Monitoring SP1 (build 6278). Upgrade to System Center Desktop Error Monitoring R2 by using the System Center Desktop Error Monitoring SetupOM.exe and following the instructions in this guide. After you upgrade to System Center Desktop Error Monitoring R2, you can convert to System Center Operations Manager 2007 R2 by starting Operations Manager 2007 R2 SetupOM.exe.

Upgrade Evaluation Copies

To upgrade to the licensed version of Operations Manager 2007 R2, you must run the setup wizard by double-clicking SetupOM.exe on the root management server.

Order of Operations

Upgrading to Operations Manager 2007 R2 requires a specific order of operations outlined in this section.

In an environment comprised of connected management groups, first upgrade the Operations Manager 2007 components in the top tier and then upgrade the components in bottom tier.

Order of Operations

1.How to Prepare a Management Group for Upgrading to Operations Manager 2007 R2

2.How to Upgrade the Root Management Server (RMS) to R2

3.How to Upgrade Reporting to R2

4.How to Upgrade a Stand-Alone Operations Console to R2

5.How to Upgrade a Management Server to R2

6.How to Upgrade a Gateway Server to R2

7.How to Upgrade an Agent to R2

8.How to Upgrade a Web Console Server to R2

9.How to Upgrade the ACS Collector to R2

10.How to Enable Subscriptions

How to Prepare a Management Group for Upgrading to Operations Manager 2007 R2

Prepare for upgrading the Operations Manager 2007 SP1 management group by first completing the procedures in this topic. These procedures include removing agents from stand-alone Operations consoles, backing up the databases in Operations Manager, backing up the encryption key, exporting unsealed management packs, increasing the size of the database and log files for both the Operations Manager database and the Reporting data warehouse, disabling subscriptions, and removing agents that are in pending management.

To remove agents from computers that have stand-alone Operations consoles

1.Log on to the Operations console with an account that is a member of the Operations Manager Administrators role for the Operations Manager 2007 management group.

2.In the Operations console, click Administration.

3.In the Administration pane, expand Administration, expand Device Management, and then click Agent Managed.

4.In the Agent Managed pane, right-click the computers for which you want to uninstall the agent, and then select Uninstall.

5.In the Uninstall Agents dialog box, either leave Use selected Management Server Action Account selected, or do the following:

a.Select Other user account.

b.Type the User name and Password, and type or select the Domain from the list. Select This is a local computer account, not a domain account if the account is a local computer account.

Note

The account must have administrative rights on the computer or the uninstall fails.

c.Click Uninstall.

6.In the Agent Management Task Status dialog box, the Status for each selected computer changes from Queued to Success.

7.Click Close.

To back up all Operations Manager 2007 SP1 databases

1.For the root management server, back up the Operations Manager database.

2.For Reporting, back up the Reporting data warehouse.

3.For Audit Collection Services (ACS), back up the ACS Database.

Note

For more information about backing up and restoring the Operations Manager database, see “How to Schedule Back Ups of Operations Manager Databases” at http://go.microsoft.com/fwlink/?LinkId=96638.

To back up the encryption key

1.Log on to the computer that hosts the root management server with an account that is a member of the Administrators group.

2.On the Windows desktop, click Start, and then click Run.

3.In the Run dialog box, type cmd, and then click OK.

4.At the command prompt, type cd\<path to Operations Manager>, and then press ENTER.

5.To back up the encryption key, do the following:

a.Type SecureStorageBackup Backup <BackupFile>, and then press ENTER.

b.At the Please enter the password to use for storage/retrieval prompt, type a password that is at least eight characters long, and then press ENTER.

c.At the Please re-enter your password prompt, type the same password, and then press ENTER.

For more information about backing up the encryption key, see the topic “How to Back Up the Encryption Key” topic in Operations Manager 2007 Help.

To export unsealed management packs

1.Log on to the Operations console with an account that is a member of the Operations Manager Administrators role for the Operations Manager 2007 management group.

2.In the Operations console, click Administration.

Note

When you run the Operations console on a computer that is not a management server, the Connect To Server dialog box appears. In the Server name text box, type the name of the Operations Manager 2007 management server that you want the Operations console to connect to.

3.In the Administration pane, click Management Packs to display the list of imported management packs.

4.In the Management Packs pane, right-click the management pack you want to export, and then click Export Management Pack.

5.In the Browse For Folder dialog box, expand the path for the location to save the file, and then click OK.

To increase space available for data and log files on the Operations Manager database

1.On the computer that hosts the Operations Manager database, click Start, point to Programs, point to Microsoft SQL Server 2005, and then click SQL Server Management Studio.

2.In the Connect to Server dialog box, in the Server Type list, select Database Engine.

3.In theServer Name list, select the server and instance for your Operations Manager database (for example, computer\INSTANCE1).

4.In the Authentication list, select WindowsAuthentication, and then click Connect.

5.In the Object Explorer pane, expand Databases, right-click OperationsManager, and then click Properties.

6.In the Database Properties - OperationsManager dialog box, under Select a page, click Files.

7.In the results pane, increase the Initial Size value for the MOM_DATA database by 50%.

Note

This step is not required if free space already exceeds 50%.

8.Increase the Initial Size value for the MOM_LOG database by 50%, and then click OK.

To increase space available for data and log files on the reporting data warehouse

1.On the computer that hosts the Reporting data warehouse, click Start, point to Programs, point to Microsoft SQL Server 2005, and then click SQL Server Management Studio.

2.In theConnect to Server dialog box, in the Server Type list, select Database Engine.

3.In the Server Name list, select the server and instance for your Operations Manager database (for example, computer\INSTANCE1).

4.In the Authentication list, select Windows Authentication, and then click Connect.

5.In the Object Explorer pane, expand Databases, right-click OperationsManagerDW, and then click Properties.

6.In the Database Properties - OperationsManagerDW dialog box, under Select a page, click Files.

7.In the results pane, increase the Initial Size value for the MOM_DATA database file by 50%.

Note

This step is not required if free space already exceeds 50%.

8.Increase the Initial Size value for the MOM_LOG database by 50%, and then click OK.

To disable subscriptions

1.Log on to the Operations console account that is a member of the Operations Manager Administrators role for the Operations Manager 2007 SP1 management group.

2.In the Operations console, click Administration.

Note

When you run the Operations console on a computer that is not a management server, the Connect To Server dialog box appears. In the Server name box, type the name of the Operations Manager 2007 management server to which you want to connect.

3.In the Administration pane, expand Administration, expand Notifications, and then click Subscriptions.

4.In the Subscriptions pane, right-click each subscription, and then click Disable.

Note

Multiselect does not work when you are disabling subscriptions.

To remove agents that are in the pending management container

1.Log on to Operations console with an account that is a member of the Operations Manager Administrators role for the Operations Manager 2007 SP1 management group.

2.In the Administration pane, expand Device Management, and then click Pending Management.

3.Right-click each agent, and then click Approve or Reject.

Caution

When you are using an RDP connection to access a server remotely, use the command mstsc.exe /console to launch the connection. Otherwise, the log files that are collected during setup will be lost when your system restarts. These log files might be critical to troubleshooting if the upgrade fails.

How to Improve Upgrade Performance in Environments Where a Large Number of Agents Are Installed

The upgrade of a root management server (RMS) or management server that hosts more than 800 agents might take more than one hour. You can significantly reduce the amount of time required to perform an upgrade by running several SQL commands. For each RMS or management server that hosts 800 or more agents, or if the upgrade of a particular RMS or management server is taking over an hour, use the following procedure. You can implement this procedure while the upgrade is in progress or prior to initiating the upgrade.

To improve upgrade performance

1.On the computer that hosts the Operations Manager database,click Start, point to Programs, point to Microsoft SQL Server 2005, and then click SQL Server Management.

2.In the Connect to Serverdialog box, in the Server Typelist, select Database Engine.

3.In the Server Namelist, select the server and instance for your Operations Manager database (for example, computer\INSTANCE1).

4.In the Authentication list, select Windows Authentication, and then click Connect.

5.In the Object Explorer pane, right-click the computer\instance name at the top of the explorer tree, and then click New Query.

6.In the New Query results pane, type the following three SQL commands

use OperationsManager

exec sp_updatestats

DBCC FREEPROCCACHE

Note

The use command assumes that the name of the Operations Manager database was not changed and the default value of OperationsManager is used.

7.Click the Query menu, and then click Execute.

8.Click the File menu, and then click Exit.

How to Upgrade the Root Management Server to Operations Manager 2007 R2

You can upgrade the root management server (RMS) by using either the standard setup interface or by using the command line tool. Procedures for upgrading an RMS that is installed on a single server and for an RMS that is a located on a cluster are provided.

The procedure to upgrade the RMS from Operations Manager 2007 SP1 to Operations Manager 2007 R2 is performed locally on the RMS or locally on the nodes of the cluster that contains the RMS. In both procedures, the Operations Manager database is also upgraded, even when the Operations Manager database is on a server that is separate from the server that hosts the RMS. If you intend to install an agent on the server that hosts the stand-alone Operations Manager database, you must run SetupOM.exe on the server before you install the agent. See the topic “To upgrade the stand-alone Operations Manager database prior to installing an agent” later in this guide. The additional procedures that verify whether the upgrade is successful are optional.

Note

Prior to upgrading to Operations Manager R2, it is necessary to install WS-Management v1.1, Cross-Platform Extensions. The Operations Manager 2007 WS-Management module depends on WS-Management protocol. This is required for all server and gateway components

Note

Close all Operations Manager consoles before proceeding with the upgrade.

To upgrade the root management server and Operations Manager database

1.Log on to the computer that hosts an RMS with an account that is a member of the Operations Manager Administrators role for your Operations Manager 2007 SP1 management group and a local administrator on the computer.

2.Insert the Operations Manager 2007 R2 media.

3.At the root of the media, double-click SetupOM.exe.

4.In the Install section, click Install Operations Manager 2007 R2. The System Center Operations Manager 2007 Setup Upgrade Wizard starts.

5.On the Welcome to the System Center Operations Manager 2007 Server Setup Upgrade Wizard page, click to select the Upgrade to Operations Manager 2007 R2 check box, and then click Next.

6.On the End-User License Agreementpage, read the licensing terms, click I accept the terms in the license agreement, and then click Next.

7.On the Ready to Install the Program page, click Install. The Installing System Center Operations Manager 2007 page displays the progress of the upgrade.

Note

You might be presented with a Warning dialog box indicating that a service has failed to start. If a warning is displayed, click OK.

8.When the Completing the System Center Operations Manager 2007 Setup Wizard page appears, click Finish.

9.If prompted, restart the server.

To upgrade the root management server using a command line tool

1.Log on to a computer that hosts the root management server with an Operations Manager Administrators role account for your Operations Manager 2007 SP1 management group.

2.Open the command window.

3.Type the following at the command prompt where you substitute PATH\TO with the actual path to the MOM.msi file:

msiexec /i PATH\TO\MOM.msi SPUPGRADE=1 REBOOT=ReallySuppress /qn /l*v D:\logs\MOMUpgrade.log

To upgrade root management server on a cluster and Operations Manager database

1.Using Cluster Administrator, log on to the first node of the cluster with an account that is a member of the Operations Manager Administrators role for your Operations Manager 2007 SP1 management group.

2.In the navigation pane, expand the cluster name, expand Groups, and then click the Operations Manager group.

3.In the results pane, examine the cluster resources listed in Name column, and ensure they are online.

4.In the results pane, in the Owner column, note which node is the owner node.

5.Ensure that you have logged on to the owning node. If not, in the navigation pane, right-click the Operations Manager cluster group, click Move Group, and then select the node from the list representing the node you have logged onto.

6.During the upgrade of a multiple-node cluster, if a service is stopped during the upgrade, the cluster might interpret this as a failure and failover to another node. To prevent this issue, use steps 6a through 6c to limit the nodes that a service can run on to the specific node you are upgrading.

a.In the Cluster Administrator pane, right-click the service you want to change (for example, OpsMgr Health Service), and then click Properties.

b.In the Properties dialog box, click Modify.

c.In the Modify Preferred Owner dialog box, under Available nodes, select the node you are performing the upgrade on, make sure it is the only node listed under Preferred owners, and then click OK.

Note

Step 6 needs to be followed on every node that is being upgraded. After the upgrade of a particular node is complete, users should re-add failover nodes to the Available Nodes list. After all the nodes have been upgraded, configure your Operations Manager 2007 group to failover to the original primary node.

Warning

When running the upgrade on a cluster, you will be presented with a check box that is used to indicate if this is the first node that you are upgrading or a subsequent node. You must check this box during the upgrade process for all subsequent nodes, but not for the first node.

7.Open your Operations Manager 2007 R2 source media.

8.At the root of the media, double-click SetupOM.exe.

9.In the Install section, click Install Operations Manager 2007 R2. The System Center Operations Manager 2007 Setup Upgrade Wizard starts.

10.On the Welcome to the System Center Operations Manager 2007 Server Setup Upgrade Wizard page, select the Upgrade to Operations Manager 2007 R2 check box, and then click Next.

11.On the End-User License Agreementpage, read the licensing terms, click I accept the terms in the license agreement, and then click Next.

12.On the Ready to Install the Program page, click Install. The Installing System Center Operations Manager 2007 page displays the progress of the upgrade. This process might take up to 20 minutes for the first node. Remaining nodes will take 5 to 10 minutes.

Note

You might be presented with a Warning dialog box indicating that a service has failed to start. If a warning is displayed, click OK.

13.When the Completing the System Center Operations Manager 2007 Setup Wizard page appears, click Finish. If prompted, restart the server.

14.Repeat the upgrade steps of this procedure on all nodes of the cluster. For each additional node, ensure that you log into the node you are upgrading and that all cluster groups have failed over to the node.

To upgrade the stand-alone Operations Manager database prior to installing an agent

1.Log on to the computer that hosts an Operations Manager database with an account that is a member of the Operations Manager Administrators role for your Operations Manager 2007 SP1 management group and a local administrator on the computer.

2.Open the Operations Manager 2007 R2 source media.

3.At the root of the media, double-click SetupOM.exe.

4.In the Install section, click Install Operations Manager 2007. The System Center Operations Manager 2007 Setup Upgrade Wizard starts.

5.On the Welcome to the System Center Operations Manager 2007 Server Setup Upgrade Wizard page, click to select the Upgrade to Operations Manager 2007 R2 check box, and then click Next.

6.On the End-User License Agreement page, read the licensing terms, click I accept the terms in the license agreement, and then click Next.

7.On the Ready to Install the Program page, click Install. The Installing System Center Operations Manager 2007 page displays the progress of the upgrade.

Note

You might be presented with a Warning dialog box indicating that a service has failed to start. If a warning is displayed, click OK.

8.When the Completing the System Center Operations Manager 2007 Setup Wizard page appears, click Finish.

9.If prompted, restart the server.

To verify the Operations Manager database upgrade

1.On the computer that hosts the Operations Manager database, click Start, point to Programs, point to Microsoft SQL Server 2005, and then click SQL Server Management Studio.

2.In the Connect to Server dialog box, in the Server Typelist, select DatabaseEngine

3.In the Server Namelist, select or type the server and instance for your operations database (for example, computer\INSTANCE1).

4.In Authentication list, select Windows Authentication, and then click Connect.

5.In the Object Explorer pane, expand Databases, expand OperationsManager, expand Tables, right-click dbo.__MOMManagementGroupInfo__, and then click Open Table. In the DBVersion column, if the version number is 6.1.####.#, where # is any positive integer, your operations database upgraded successfully.

To verify the root management server upgrade

1.Log on to the RMS with an account that has local administrator rights and on the Windows desktop, click Start, and then click Run.

2.Type regedit and then click OK. The Registry Editor starts.

Caution

Incorrectly editing the registry can severely damage your system. Before you make changes to the registry, you should back up any valued data that is on the computer.

3.Navigate to the HKey_Local_Machine\Software\Microsoft\Microsoft Operations Manager\3.0\Setup key. If the value of the ServerVersion entry is 6.1.####.#, where # is any positive integer, your RMS upgraded successfully.

4.In the Windows Services snap-in, ensure that the status is set as Started on the following services:

·OpsMgr Config Service

·OpsMgr Health Service

·OpsMgr SDK Service

To verify the root management server upgrade on a cluster

1.For every node in the cluster, click Start, and then click Run.

a.Type regedit and then click OK. The Registry Editor starts.

Caution

Incorrectly editing the registry can severely damage your system. Before you make changes to the registry, you should back up any valued data that is on the computer.

b.Navigate to the HKey_Local_Machine\Software\Microsoft\Microsoft Operations Manager\3.0\Setup key. If the value of the ServerVersion entry is 6.1.####.#, where # is any positive integer, your RMS upgraded successfully.

2.Using the Cluster Administrator, move the cluster group to each cluster node and verify that the following services are online.

·OpsMgr Config Service

·OpsMgr Health Service

·OpsMgr SDK Service

How to Upgrade Reporting to Operations Manager 2007 R2

The procedure to upgrade the Reporting Server from Operations Manager 2007 SP1 to Operations Manager 2007 R2 is performed on the computer that hosts the Reporting Server. During this procedure the Reporting data warehouse is also upgraded with no additional steps.

The additional procedure that verifies whether the upgrade is successful is optional.

To upgrade the Reporting Server and the Reporting data warehouse

1.Log on to the computer that hosts the Reporting Server with an account that is a member of the Operations Manager Administrators role for your Operations Manager 2007 SP1 management group.

2.Open the Operations Manager 2007 R2 source media.

3.At the root of the media, double-click SetupOM.exe.

4.In the Install section, click Install Operations Manager 2007 R2 Reporting. The Operations Manager 2007 Reporting Setup wizard starts.

5.On the Welcome to the Operations Manager 2007 Reporting Setup Upgrade Wizard page, select the Upgrade Operations Manager Reporting check box, and then click Next.

6.On the End-User License Agreementpage, read the licensing terms, click I accept the terms in the license agreement, and then click Next.

7.On the Ready to Install the Program page, click Install.

8.When the Completing the Operations Manager Reporting Components Setup Wizard page appears, click Finish.

To upgrade the Reporting Server using a command prompt

1.Log on to a computer that hosts the Reporting Server with an Operations Manager Administrators role account for your Operations Manager 2007 SP1 management group.

2.Open the Operations Manager 2007 R2 source media..

3.Open the command window.

4.For example, at the command prompt, type the following where you substitute PATH\TO with the path to the R2 source media:

msiexec /i \PATH\TO\Reporting2007.msi SPUPGRADE=1 SET_ACTIONS_ACCOUNT=0 REINSTALLMODE=vomus REINSTALL=ALL /qn /l*v D:\logs\ReportingUpgrade.log

To verify the Reporting Server upgrade

1.On the computer that hosts the Reporting Server, click Start, and then click Run.

2.Type regedit, and then click OK. The Registry Editor starts.

Caution

Incorrectly editing the registry can severely damage your system. Before you make changes to the registry, you should back up any valued data that is on the computer.

3.Navigate to the HKLM\Software\Microsoft\Microsoft Operations Manager\3.0\Setup key. If the value of the CurrentVersion entry is 6.1.####.#, where # is any positive integer, your Reporting Server upgraded successfully.

How to Upgrade a Stand-Alone Operations Console to Operations Manager 2007 R2

This procedure upgrades a standalone Operations console from Operations Manager 2007 SP1 to Operations Manager 2007 R2. Perform this procedure locally on the computer that has a standalone Operations console installed. You do not need to perform this procedure to upgrade Operations consoles that are installed locally on a management server. See How to Upgrade a Management Server to Operations Manager 2007 R2 later in this guide for instructions on upgrading your management servers.

The additional procedure that verifies whether the upgrade is successful is optional.

Note

If an agent is installed, you must uninstall it before beginning this procedure. You can re-install the agent after the Operations console is upgraded.

To upgrade a stand-alone Operations console

1.Log on to the computer that hosts the Operations console with an Operations Manager Administrators role account for your Operations Manager 2007 SP1 management group.

2.Open the Operations Manager 2007 R2 source media.

3.At the root of the media, double-click SetupOM.exe.

4.In the Install section, click Install Operations Manager 2007 R2.

5.In the System Center Operations Manager 2007 R2 Setup dialog box, click Yes.

Note

You might be presented with a Warning dialog box indicating that a service has failed to start. This behavior is expected. If a warning is displayed, click OK.

6.On the Welcome page, click to select the Upgrade to Operations Manager 2007 R2 check box, and then click Next.

7.On the End-User License Agreementpage, read the licensing terms, click I accept the terms in the license agreement, and then click Next.

8.On the Ready to Install the Program page, click Install. The Installing System Center Operations Manager 2007 page displays the progress of the upgrade.

9.When the Completing the System Center Operations Manager 2007 Setup Wizard page appears, click Finish.

To upgrade a stand-alone Operations console using the Command Line Tool

1.Log on to the computer that hosts the Operations console with an Operations Manager Administrators role account for your Operations Manager 2007 SP1 management group.

2.Open the Operations Manager 2007 R2 source media.

3.Open the command window.

4.For example, at the command prompt, type the following, substituting \PATH\TO with the path to the MOM.msi file:

msiexec /i \PATH\TO\MOM.msi SPUPGRADE=1 REBOOT=ReallySuppress /qn /l*v D:\logs\MOMUpgrade.log

To verify the Operations console upgrade

1.On the Windows desktop, click Start, and then click Run.

2.Type regedit, and then click OK. The Registry Editor starts.

Caution

Incorrectly editing the registry can severely damage your system. Before you make changes to the registry, you should back up any valued data that is on the computer.

3.Navigate to the HKey_Local_Machine\Software\Microsoft\Microsoft Operations Manager\3.0\Setup key. If the value of the UIVersion entry is 6.1.####.#, where # is any positive integer, the Operations console upgraded successfully.

Note

After a successful upgrade of a management server, it can take several minutes before the upgraded version numbers are displayed in Operations console.

How to Upgrade a Management Server to Operations Manager 2007 R2

Perform the procedure to upgrade a management server from Operations Manager 2007 SP1to Operations Manager 2007 R2 locally on each management server. You must upgrade the root management server (RMS) of a management group before you upgrade any of the management servers.

The additional procedure that verifies whether the upgrade is successful is optional.

Note

Prior to upgrading to Operations Manager R2, it is necessary to install WS-Management v1.1, Cross-Platform Extensions and the Operations Manager 2007 WS-Management module depends on WS-Management protocol. OpsMgr 2007 R2 setup pre-requisite recommends to install WS-Management v1.1 if not installed on the computer where OpsMgr 2007 R2 server or gateway is being installed. Setup pre-requisite explicitly checks for WS-Management v1.1 while installing OpsMgr server, but this check is not present on gateway, although it is also recommended for gateway.

To upgrade a management server

1.Log on to the computer that hosts the management server with an Operations Manager Administrators role account for your Operations Manager 2007 SP1 management group.

2.Open the Operations Manager 2007 R2 source media.

3.At the root of the media, double-click SetupOM.exe.

4.In the Install section, click Install Operations Manager 2007 R2. The System Center Operations Manager 2007 Server Setup Upgrade Wizard starts.

5.On the Welcome to the System Center Operations Manager 2007 Server Setup Upgrade Wizard page, click to select the Upgrade to Operations Manager 2007 R2 check box, and then click Next.

6.On the End-User License Agreementpage, read the licensing terms, click I accept the terms in the license agreement, and then click Next.

7.On the Ready to Install the Program page, click Install. The Installing System Center Operations Manager 2007 page displays the progress of the upgrade.

Note

You might be presented with a Warning dialog box indicating that a service has failed to start. This behavior is expected. If a warning is displayed, click OK.

8.When the Completing the System Center Operations Manager 2007 Setup Wizard page appears, click Finish.

To upgrade a management server using a command prompt

1.Log on to the computer that hosts the Operations console with an Operations Manager Administrators role account for your Operations Manager 2007 SP1 management group.

2.Open the Operations Manager 2007 R2 source media.

3.Open the command window.

4.For example, at the command prompt, type the following, where \PATH\TO\ is substituted with the path to the MOM.msi file:

msiexec /i \PATH\TO\MOM.msi SPUPGRADE=1 REBOOT=ReallySuppress /qn /l*v D:\logs\MOMUpgrade.log

To verify the management server upgrade

1.On the computer that hosts the management server, click Start, and then click Run.

2.Type regedit, and then click OK. The Registry Editor starts.

Caution

Incorrectly editing the registry can severely damage your system. Before you make changes to the registry, you should back up any valued data that is on the computer.

3.Navigate to the HKey_Local_Machine\Software\Microsoft\Microsoft Operations Manager\3.0\Setup key. If the value of the ServerVersion entry is 6.1.####.#, where # is any positive integer, your management server upgraded successfully.

How to Upgrade a Gateway Server to R2

The procedure to upgrade a gateway server from Operations Manager 2007 SP1 to Operations Manager 2007 R2 is performed locally on the gateway server. The additional procedure that verifies whether the upgrade is successful is optional.

Note

Prior to upgrading to Operations Manager R2, it is necessary to install WS-Management v1.1, Cross-Platform Extensions and the Operations Manager 2007 WS-Management module depends on WS-Management protocol. OpsMgr 2007 R2 setup pre-requisite recommends to install WS-Management v1.1 if not installed on the computer where OpsMgr 2007 R2 server or gateway is being installed. Setup pre-requisite explicitly checks for WS-Management v1.1 while installing OpsMgr server, but this check is not present on gateway, although it is also recommended for the gateway.

To upgrade the gateway server using a command prompt

1.Log on to a computer that hosts the gateway server with an Operations Manager Administrators role account for your Operations Manager 2007 management group.

2.Open the Operations Manager 2007 R2 source media.

3.Open the command window.

4.For example, at the command prompt, type the following, where \PATH\TO is substituted with the path to the MOMGateway.msi file:

msiexec /i PATH\TO\MOMGateway.msi SPUPGRADE=1 SET_ACTIONS_ACCOUNT=0 /qn /l*v D:\logs\GatewayUpgrade.log

To verify the gateway server upgrade

1.On the computer that hosts the gateway server, click Start, and then click Run.

2.Type regedit, and then click OK. The Registry Editor starts.

Caution

Incorrectly editing the registry can severely damage your system. Before you make changes to the registry, you should back up any valued data that is on the computer.

3.Navigate to the HKey_Local_Machine\Software\Microsoft\Microsoft Operations Manager\3.0\Setup key. If the value of the MOMGatewayVersion entry is 6.1.####.#, where # is any positive integer, your gateway server upgraded successfully.

How to Upgrade an Agent to R2

There are four procedures available for upgrading agents from Operations Manager 2007 SP1 to Operations Manager 2007 R2: by using the Operations console, manually using the Setup Wizard, manually using a command prompt, or by using Active Directory Integration.

Agents that were installed using Active Directory Integration can be upgraded manually, or through the Operations console. When the root management server, management servers, and gateway servers have been upgraded, follow the "To upgrade agents leveraging Active Directory Integration" procedure below.

The additional procedure that verifies whether the upgrade is successful is optional.

Note

Information about upgraded agents might not display in the Operations console for up to 30 minutes after performing the upgrade.

To upgrade agents from Operations Manager 2007 SP1 (build 6278) to Operations Manager 2007 R2using the Operations console

1.Log on to the computer that hosts the Operations console with an account that is a member of the Operations Manager Administrators role for the Operations Manager 2007 SP1 management group.

2.In the Operations console, click Administration.

Note

When you run the Operations console on a computer that is not a management server, the Connect To Server dialog box appears. In the Server name text box, type the name of the Operations Manager 2007 management server to which you want to connect.

3.In the Administration pane, expand Device Management, and then click Pending Management.

4.In the Pending Management pane, expand Type: Agent Requires Update, right-click each agent-managed computer listed, and then click Approve.

5.In the Update Agents dialog box, enter the administrator account credentials, and then click Update. The upgrade status is displayed in the Agent Management Task Status dialog box.

6.When the upgrade is complete, click Close.

To manually upgrade an agent using the Setup Wizard

1.Log on to a computer that hosts the agent with an Operations Manager Administrators role account for your Operations Manager 2007 SP1 management group.

2.Open the Operations Manager 2007 R2 source media.

3.At the root of the media, double-click SetupOM.exe.

4.In the Install section, click Install Operations Manager 2007 R2 Agent. The Welcome to the System Center Operations Manager Agent Upgrade Wizard page opens, and then click Next.

5.In the System Center Operations Manager Agent Setup dialog box, click Upgrade. The status page displays the progress of the upgrade.

6.When the Completing the System Center Operations Manager Agent Setup wizard page appears, click Finish.

To manually upgrade an agent using the command prompt

1.Log on to a computer that hosts the agent with an Operations Manager Administrators role account for your Operations Manager 2007 SP1 management group.

2.Open the Operations Manager 2007 R2 source media.

3.Open the command window.

4.At the command prompt, type the following, where \PATH\TO is substituted with the path to the MOMAgent.msi file and D:\ is the desired location for the upgrade log file: \PATH\TO\msiexec /i MOMAgent.msi SPUPGRADE=1 SET_ACTIONS_ACCOUNT=0 REINSTALLMODE=vomus REINSTALL=ALL /qn /l*v D:\logs\AgentUpgrade.log

To upgrade agents using Active Directory Integration

1.Log on to the computer with an Operations Manager Administrators role account for the Operations Manager 2007 SP1 management group.

2.In the Operations console, click the Administration button.

Note

When you run the Operations console on a computer that is not a management server the Connect To Server dialog box appears. Type the name of the Operations Manager 2007 management server you want the Operations console to connect to in the Server name text box.

3.In the Administration pane, expand Administration, expand Device Management, and then click Agent Managed.

4.In the Agent Managed pane, select the agents that were installed using Active Directory Integration, right-click them, and then select Repair.

Note

Agents leveraging Active Directory integration will not appear in the Pending Management view.

To verify the agent upgrade

1.On the computer that hosts an agent, click Start, and then click Run.

2.Type regedit and then click OK. The Registry Editor starts.

Caution

Incorrectly editing the registry can severely damage your system. Before you make changes to the registry, you should back up any valued data that is on the computer.

3.Navigate to the HKey_Local_Machine\Software\Microsoft\Microsoft Operations Manager\3.0\Setup key. If the value of the AgentVersion entry is 6.1.####.#, where # is any positive integer, your agent upgraded successfully.

How to Upgrade a Web Console Server to Operations Manager 2007 R2

Perform this procedure on the computer that hosts the Web console server to upgrade a Web console from Operations Manager 2007 SP1 to Operations Manager 2007 R2.

Note

Prior to upgrading the SP1 Web console you must install ASP.NET AJAX Extensions 1.0 (v 1.0.61025.0) for ASP.NET 2.0. The pre-requisite checker result details also point the Ajax installer web location. This is located at: http://go.microsoft.com/fwlink/?LinkId=132195

If your Web console server is on the same computer as a management server, the Web console server is upgraded when the management server is upgraded, rendering this upgrade procedure unnecessary. You can still run the verification procedure to ensure that the Web console server upgrade was successful.

To upgrade the Web console server

1.Log on to the computer that hosts the Web console server with an Operations Manager Administrators role account for your Operations Manager 2007 SP1 management group.

2.Open the Operations Manager 2007 R2 source media.

3.At the root of the media, double-click SetupOM.exe.

4.In the Install section, click Install Operations Manager 2007 R2. The System Center Operations Manager 2007 Server Setup Upgrade Wizard starts.

5.On the Welcome page, select the Upgrade to Operations Manager 2007 R2 check box, and then click Next.

6.On the End-User License Agreementpage, read the licensing terms, click I accept the terms in the license agreement, and then click Next.

7.On the Ready to Install the Program page, click Install. The Installing System Center Operations Manager 2007 page displays the progress of the upgrade.

8.When the Completing the System Center Operations Manager 2007 Setup Wizard page appears, click Finish.

To upgrade the Web console server using a command prompt

1.Log on to the computer that hosts the Operations console with an Operations Manager Administrators role account for your Operations Manager 2007 management group.

2.Open the Operations Manager 2007 R2 source media.

3.Open the command window.

4.For example, at the command prompt, type the following, where \PATH\TO is replaced with the path to the MOM.msi file :

msiexec /i \PATH\TO\MOM.msi SPUPGRADE=1 REBOOT=ReallySuppress /qn /l*v D:\logs\MOMUpgrade.log

To verify the Web console server upgrade

1.On the computer that hosts the Web console server, click Start, and then click Run.

2.Type regedit and then click OK. The Registry Editor starts.

Caution

Incorrectly editing the registry can severely damage your system. Before you make changes to the registry, you should back up any valued data that is on the computer.

3.Navigate to the HKey_Local_Machine\Software\Microsoft\Microsoft Operations Manager\3.0\Setup key. If the value of the CurrentVersion entry is 6.1.####.#, where # is any positive integer, your Web Console Server upgraded successfully.

How to Upgrade the ACS Collector to R2

Perform this procedure to upgrade the Audit Collection Services (ACS) Collector from Operations Manager 2007 SP1 to Operations Manager 2007 R2 locally on the ACS Collector. During this procedure the ACS Database is also upgraded with no additional steps.

Note

A computer that hosts an ACS Collector must also be an Operations Manager management server or gateway. You must upgrade the management server components before you upgrade the ACS Collector component.

To upgrade an ACS Collector

1.Log on to the computer that hosts the ACS Collector with an Operations Manager Administrators role account for your Operations Manager 2007 SP1 management group.

2.Open the Operations Manager 2007 R2 source media.

3.On the root of the media, double-click SetupOM.exe.

4.In the Install section, click Install Audit Collection Server. The Audit Collection Services Collector Setup Wizard starts.

5.On the Welcome to the Audit Collection Services Collector Setup Wizard page, click Next.

6.On the Database Installation Options page, click Use an existing database, and then click Next.

7.On the Data Source page, type the name that you used as the Open Database Connectivity (ODBC) data source name for your ACS database in the Data Source Name box. By default, this name is OpsMgrAC. Click Next.

8.On the Database page, if the database is on a separate server than the ACS collector, click Remote Database Server, and then type the computer name of the database server that will host the database for this installation of ACS. Otherwise, click Database server running locally, and then click Next.

9.On the Database Authentication page, select one authentication method. If the ACS collector and the ACS database are members of the same domain, you can select Windows authentication; otherwise, select SQL authentication, and then click Next.

Note

If you select SQL authentication and click Next, the Database Credentials page displays. Enter the name of the user account that has access to the SQL Server in the SQL login name box and the password for that account in the SQL password box, and then click Next.

10.The Summary page displays a list of actions that the installation program will perform to upgrade ACS. Review the list, and then click Next to begin the installation.

Note

If a SQL server login dialog box displays and the database authentication is set to Windows authentication, select the correct database and verify that the Use Trusted Connection check box is checked. Otherwise clear it, enter the SQL login name and password, and then click OK.

11.When the upgrade is complete, click Finish.

To upgrade the ACS Collector using a command prompt

1.Log on to a computer that hosts the ACS server with an Operations Manager Administrators role account for your Operations Manager 2007 management group.

2.Open the Operations Manager 2007 R2 source media.

3.Open the command window.

4.For example, at the command prompt, type the following, where \PATH\TO is substituted with the path to the ADTServer.msi file:

msiexec /i AdtServer.msi ADDLOCAL=ALL REINSTALLMODE=vamus REINSTALL=ALL /qn /l*v D:\logs\ACSUpgrade.log

How to Enable Subscriptions

After the upgrade has finished, use the following procedure to re-enable subscriptions.

Enable Subscriptions

1.Log on to the computer with an account that is a member of the Operations Manager Administrators role for the Operations Manager 2007 management group.

2.In the Operations console, click Administration.

Note

When you run the Operations console on a computer that is not a management server, the Connect To Server dialog box appears. In the Server name text box, type the name of the Operations Manager 2007 management server to which you want to connect.

3.In the Administration pane, expand Administration, expand Notifications, and then click Subscriptions.

4.In the Subscriptions pane, right-click each subscription, and then click Enable.

 

 

Tag page
You must login to post a comment.


Wik portal where you can upload your ideas and interests and educational mind set for a free website account please apply here