OpsMgr, SCE And MOM Blog : Technical Info

Operations manager 2007 Sp1 / Essentials 2007 SP1 support for windows server 2008 announced

CliveEastwood — Sat, 26 Jul 2008 03:19:37 GMT

Windows Server 2008 support has been announced. Please see the following resources for more information

The Knowledgebase article KB953141 announces our support of OpsMgr SP1 and SCE SP1 running on Windows Server 2008

The above article discusses 4 required Windows Server 2008 hotfixes which may have to be installed depending on the OpsMgr/SCE role installed on Windows Server 2008

The above article also provide a link to a required OpsMgrSP1/SCESP1 hotfix rollup which is described in Knowledgebase article KB954049

The hotfixes referenced are all available from the Microsoft download center.

The Support Configurations details for Operations Manager 2007 SP1 have been updated to reflect supported Windows Server 2008 roles http://tnstage.dns.microsoft.com/en-us/library/bb309428.aspx

Management Pack Releases for Windows Server 2008 will take place shortly.

The hotfix provided in KB954049 can be installed on localized OpsMgrSP1/SCESP1 installations as it does not provide any localized fixes. The hotfix MSI installer is currently provided in English, localized versions will be provided in the coming weeks.

NOTES:

Please take careful consideration of the OpsMgrSP1/SCESP1 installation notes within KB954049 , particularly:

The OpsMgrSP1/SCESP1 hotfix must be applied after installation of OpsMgr/SCE on Windows Server 2008 or after in-place upgrade of the OS to Windows Server 2008 of an affected OpsMgr/SCE role. This will ensure correct performance counter registration on RMS, SCE Server, Management Server, Gateway server roles.
If User Account Control (UAC) is enabled on Windows Server 2008 when you apply the OpsMgrSP1/SCESP1 hotfix, you MUST execute SystemCenterOperationsManager2007-SP1-KB954049-X86-X64-ENU.MSI from an elevated command prompt. Failure to do so will not allow the display of the hotfix applicaton dialog once the MSI has completed installation of the staging bits on the server.
Read carefully the Known issues section of KB954049. There are a number of requirements and known issues, several still under investigation (Issues 6/7). As more information on Issues 6/7 becomes available and hotfixes developed the KB article will be updated and details provided.

Some more Command Notification Tricks and Tips

CliveEastwood — Thu, 17 Apr 2008 03:17:00 GMT

Here are a couple a tidbits on command notification with Operations Manager 2007 I’ve seen people asking about recently.

1) I’m getting Alerts “Script or Executable was Dropped” when command notifications execute. How do I prevent it?

What you’ll typically see in the Alert description is the following:

“The process could not be created because the maximum number of asynchronous responses (5) has been reached, and it will be dropped. Command executed: ………”

What is happening here is that notification command execution in response to alerts is attempting to fire more than 5 (default) notification command processes asynchronously. By default the number of command processes executed defaults to 5 to protect the RMS from alert storms potentially overwelming the system with runaway processes.

The default of 5 async notification processes allowed can be overridden. The following solution comes with a warning “Increasing the default number of concurrent command notification processes could cause RMS performance issues”. For those running somewhat lengthy batch files, scripts, executables via command notification the following may allow such to scale out if your RMS has the horsepower to cope:)

It’s worth noting that it is the RMS that runs notifications. The follow registry modification on the RMS and subsequent stop and restart of the HealthService service will trigger the new maximum responses allowed:

One the RMS use RegEdit to navigate to HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft Operations Manager\3.0\Modules

Under this key create a new subkey called Global

Under the new Global subkey create another subkey called Command Executer

Under the Command Executer subkey create a new DWORD value AsyncProcessLimit

For the value of AsyncProcessLimit you can set a minimum of 0x00000001 (Strongly not recommended) and a maximum of 0x00000064 (100) (again definitely not recommended).

So, if you wanted to increase the number of async command notifications from 5 to 10 the key would look like:

HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft Operations Manager\3.0\Modules\Global\Command Executer\AsyncProcessLimit REG_DWORD:0x0000000a

2) When using some notification properties (e.g. $Data/Context…) with command notification the command process never executes and I get the rather annoying alert “Script or Executable Failed to run”

In the alert description you would see “The process could not be started because some of the data items could not be resolved…”

What you are seeing here is that one or more notification properties used in the notification command channel command line doesn’t actually contain anything. A common example is $Data/Context/DataItem/TicketId$ for example (will contain nothing unless you have a connector which sets it). When a notification property contains nothing the command executer will not execute the command since the process being executed may be expecting something as a parameter.

If you’ve hit this here’s a solution I became aware of recently that will most certainly help.

For command notifications (I’ve personally not tried this in other notification methods) you can provide a default value for the notification parameter if no value exists. For example

$Data[Default=’No Ticket ID’]/Context/DataItem/TicketID$

NOTE: Single quotes surround the default value. This then allows properties containing spaces to be easily supplied as parameters to batch, scripts or executables.

For example, in the Notification Command Channel dialog you could enter:

Full path to file: %COMSPEC%

Command line parameters: /C c:\notificationcmds\execsms.cmd “$Data/Context/DataItem/AlertName$” “$Data[Default=’No Description’]/Context/DataItem/AlertDescription$” “$Data[Default=’No TicketID’]/Context/DataItem/TicketID$”

This would allow the notification command to execute and output the defaults No Description and No TicketID if the Alert Description or TicketID did not contain a value.

More info on Notification properties:

http://blogs.technet.com/cliveeastwood/archive/2007/10/12/a.aspx

http://blogs.technet.com/kevinholman/archive/2007/12/12/adding-custom-information-to-alert-descriptions-and-notifications.aspx

System Center Essentials 2007 SP1 - Release Notes

CliveEastwood — Mon, 10 Mar 2008 20:40:32 GMT

I thought I'd post the release notes for SP1 here. They will be available online (publication pending), but are also available with the ProductDocumentation folder of the 90-day eval version.

The following Release Notes describe important information and known issues in the release of System Center Essentials 2007 Service Pack 1. For additional useful information, please see the WSUS 3.0 Release Notes on the Web.

What's New in System Center Essentials 2007 Service Pack 1

System Center Essentials 2007 Service Pack 1 (SP1) incorporates the following the improvements and major changes in functionality. For a complete list of fixes and changes that are included in Essentials 2007 SP1 please see: http://go.microsoft.com/fwlink/?LinkID=110536.

Support for managing workgroup-joined computers.
Support for monitoring SNMPv1 network devices.
Support for using multiple auto-approval rules in update management.
Support for using a remote SQL Server 2005 instance on a computer with a different architecture (x86 or x64) than that of the computer running the Essentials 2007 management server.
Support for running the Essentials 2007 management server, console and agent on computers running Windows Server 2008. Management packs for Windows Server 2008 and its role will be available shortly after the release of Windows Server 2008.
Improved backup and disaster recovery guidance.
Improvements in management pack quality.
Improvements in performance, usability, and supportability.

Supported Platforms and Requirements

When running Setup, a prerequisites checker runs to ensure that the computer on which you are installing Essentials 2007 complies with requirements. If a requirement is not met, the prerequisites checker flags the item as failed and provides a link for further assistance. The supported platforms for installing Essentials 2007 are as follows:

Hardware Requirements

The following table describes the hardware requirements for running System Center Essentials 2007.

Supported Database Platforms

The following list describes the Microsoft SQL Server versions and editions that are supported in System Center Essentials 2007.

SQL Server 2005 Express Edition SP1 or later (32-bit only)
SQL Server 2005 Workgroup Edition SP1 or later (32-bit only)
SQL Server 2005 Standard Edition SP1 or later (32-bit and 64-bit)
SQL Server 2005 Enterprise Edition SP1 or later (32-bit and 64-bit)

Operating System Requirements

The following table describes the operating system requirements for running Essentials 2007.

Software Dependencies

The following lists detail the software required for many of the Essentials 2007 components to operate properly.

Essentials 2007 Health Service required services and dependencies:

Windows Installer (required for Essentials 2007 setup)
Remote Procedure Call

Essentials 2007 Health Service optional services and dependencies:

IIS
.NET Framework 3.0
BITS
.NET Framework 2.0 (for managed response)
SNMPv1 and v2C
NT Event Log (Essentials 2007 uses NT Event Log but does not depend on it to start the Health Service)
WMI (Essentials 2007 uses WMI but does not depend on it to start the Health Service)
Performance Counter Infrastructure (registry API) (Essentials 2007 uses Performance Counter but does not depend on it to start the Health Service). Counters are made available through the remote registry service.
RPC

Essentials 2007 Configuration Service:

.NET Framework 2.0

Essentials 2007 management server\SDK Service required services and dependencies:

.NET Framework 2.0
.NET Framework 3.0
Windows Server 2003 SP1
Windows Installer 3.1

Essentials 2007 management server\SDK Service optional services and dependencies:

Active Directory

Essentials 2007 User Interface\SDK Client required services and dependencies:

.NET Framework 3.0
Windows Server 2003 SP1 or Windows XP SP2 or later

Services and dependencies to accept a push install of the agent:

Netlogon Service (not on workgroup)
NetBIOS Service
Server Service
Remote Registry
DCOM enabled
Windows Installer 3.1 or above

Agentless Exception Monitoring required services and dependencies:

Agentless exception monitoring requires the source of instrumentation that Essentials 2007 monitors to be running, so for example, a remote registry which gives service status and performance counters (and the event log) should definitely be running, but Windows Installer is not required.

Essentials 2007 Database required services and dependencies:

SQL Server 2005 SP1
Windows Server 2003 SP1

Other Application Dependencies:

SMTP Mail Server for notifications (Exchange 200x & SMTP)

Known Issues

The following are known issues with System Center Essentials 2007.

Issue: Upgrading to System Center Essentials 2007 Service Pack 1 from System Center Essentials 2007 RC1, Beta 2, or any other pre-release version of Essentials 2007 is not supported.

Workaround: Uninstall any pre-release Essentials 2007 software and install Essentials 2007 RTM before attempting to upgrade to the SP1 version of Essentials 2007.

_

Issue : Computers running Windows 2000 SP4 that have never connected to Windows Update and updated the local client (the operating system ships with a client of version 5.4.3630.2554) do not redirect to WSUS after Group Policy is applied. The Windows Update client that ships with this operating system version cannot process the Group Policy changes.

Workaround: Connect the computer to Windows Update and upgrade to the latest Windows Update client.

_

Issue: The Essentials 2007 Daily Health Report loads without graphics.

Cause: The computer running the report has no Internet access.

Workaround: Ensure that the computer running the daily health report has Internet access configured.

_

Issue: The Essentials 2007 SP1 upgrade requires 1 GB of free disk space on the system drive for the Update Services component to successfully upgrade.

Workaround: Ensure that 1 GB of free disk space is available on the system drive of the Essentials 2007 management server before attempting the upgrade.

_

Issue: Essentials 2007 will not be able to import a third party update catalog if your Internet connections require a proxy server setting with integrated Windows authentication and you have not explicitly defined a proxy server in your Internet Explorer connection settings. Specifically, Essentials 2007 does not support the Automatically detect settings proxy server connection setting in Internet Explorer for this purpose.

Workaround: Explicitly configure a proxy server in your Internet Explorer connection settings.

_

Issue: If you change the default port value for Agentless Exception Monitoring when running the Feature Configuration Wizard to anything other than the default value of 51906, the Windows Firewall on the Essentials 2007 management server will still be configured with the default port (51906) in the Agentless Exception firewall exception.

Workaround: Open the Windows Firewall Control Panel on the Essentials 2007 management server. Manually change the Operations Manager Application Error Monitoring entry to use the port you specified in the Feature Configuration Wizard.

_

Issue: Essentials 2007 Setup might fail and roll back with the following error message: "An installation package for the product Microsoft SQL Native Client cannot be found. Try the installation again using a valid copy of the installation package 'sqlncli.msi'."

Workaround: Remove the SQL Native Client using Add or Remove Programs. Then run the Essentials 2007 Setup program again.

_

Issue: On a computer with SQL Server Workgroup Edition installed, Essentials 2007 Setup might fail with the following error code:

ExecuteSqlScripts: ExecuteSqlScriptFileFromMsi returned error. Error Code: 0x80040E14.

MSI (s) (28!9C) [11:14:42:006]: Product: System Center Essentials 2007 -- Error 25154.Failed to execute SQL script. Error Code: -2147217900 (Address Windowing Extensions (AWE) is not supported in this edition of SQL Server.).

Error 25154.Failed to execute SQL script. Error Code: -2147217900 (Address Windowing Extensions (AWE) is not supported in this edition of SQL Server.).

Workaround: In SQL Server 2005 Workgroup Edition, turn off Address Windowing Extensions (AWE), and then run the Essentials 2007 Setup program again.

_

Issue: If IIS was installed on the computer after .NET 2.0 was installed, you must re-register ASP.NET 2.0 before installing Essentials 2007.

Workaround: Perform the following steps:

Open a command prompt.
On the command line, navigate to %WINDIR%\Microsoft.net\framework\V2.0.50727
Type aspnet_regiis.exe –i to re-register ASP.Net 2.0

_

Issue: Installing the Essentials 2007 management server may fail while upgrading WSUS 2.0 if the WSUS server is synchronizing from Microsoft Update.

Workaround: Ensure that WSUS is not synching from Microsoft Update before attempting Essentials server installation.

_

Issue: When installing the last licensed Windows client computer, the computer may be displayed in the Pending Management view with a "License Limit Exceeded" status.

Workaround: Reject the computer in the Pending Management view. The computer will then be displayed in the Agent Managed view.

_

Issue: SQL Server 2005 cannot create or upgrade databases on compressed drives.

Workaround: Select an uncompressed drive on which to install the Essentials databases.

_

Issue: In some cases, the domain controller of a trusted domain fails to pick up the Essentials 2007 managed computers policy. The following is an example of the scenario:

Create domain A and child domain B with a domain functional level of Windows Server 2003.
Install Essentials 2007 on a computer in domain A and deploy policy.
On domain B, link the System Center Essentials All Computers and System Center Essentials Managed Computers policies.
Deploy agents to all machines in domain A and B.
Result: Domain B's domain controller does not pick up the managed computers policy.

Workaround: Configure local policy on the DC to point to the Essentials 2007 management server.

_

Issue: After running the Feature Configuration Wizard it may take 2 hours or more for Group Policy to configure the Windows Firewall on computers in your domain. Depending on your site's configuration it may take longer than that for the policy to replicate throughout your domain. This can lead to a delay of up to 24 hours before all computers in the domain have their firewalls properly configured. If you run the Computer and Device Management Wizard to discover computers before that time, it may not successfully discover some computers because they do not yet have the proper policies applied via Group Policy.

Workaround: After running the Feature Configuration Wizard, you can log onto a target computer and run the following command from the command line to force the application of Group Policy:

gpupdate /force

_

Issue: The Essentials 2007 management server may not submit inventory immediately after submitting Group Policy.

Workaround: If Essentials 2007 management server local machine displays Unknown for status in the Computers pane after deploying Group Policy, restart the Essentials 2007 management server so that is will configure itself to properly submit inventory.

_

Issue: You cannot choose an SQL Server Reporting Services (SRS) instance that is configured to use SSL during Essentials 2007 setup.

Workaround: Remove all certificates from the SRS instance and ensure that it is operational before selecting it in Essentials 2007 setup.

_

Issue: You may be unable to create a software package which contains one or more files that are larger than 500 MB each.

Cause: This is caused by a known issue with the operating system when attempting to validate large files which have been digitally signed.

Workaround: Install the update detailed in the Knowledge Base article Windows Server Update Services cannot download large Windows update files in Windows Server 2003 - http://go.microsoft.com/fwlink/?LinkID=103458.

_

Issue: Disabling the printer spooler service on a managed computer may inadvertently disable inventory collection on that computer.

Cause: Inventory is collected via WMI queries, and if the Printer Spooler Service is not running, these WMI queries may fail.

Workaround: Do not disable the printer spooler service on managed computers.

_

Issue: In System Center Essentials 2007 installations where Microsoft SQL Server 2005 Express Edition has been installed to house Essentials 2007 data and host reporting, charts cannot be displayed in any reports that use Dundas chart control. Reports display everything but the charts (for example, the report header and footer, tabular data, and so on are displayed correctly). Charts in these reports are rendered as blank white space. The affected reports are:

Alert Logging Latency
Downtime Periods
Most Common Alerts
Most Common Events
Performance
Performance Detail
Performance Top Instances
Performance Top Objects

In addition, if you import Management Packs containing any other reports that use the Dundas chart control, such as some Operations Manager 2007 reports, the reports are similarly affected.

Workaround: None. To generate charts, you must uninstall Essentials 2007, install a different version of SQL Server 2005 (Workgroup Edition, Standard Edition, or Enterprise Edition) on the Essentials 2007 management server computer, and then reinstall Essentials 2007.

_

Issue: The Essentials 2007 management server cannot be installed on a server that has a self-signed certificate assigned to the default Web site.

Workaround: Remove the self-signed certificate from the default Web site before installing the Essentials 2007 management server. After setup has completed successfully, re-assign the self-signed certificate to the default Web site.

_

Issue: Computers added to a computer group may not appear as members of the group for up to 1 hour.

Causes:

When you restart the SDK service, any new members added to any existing groups will not be synchronized to WSUS until the next sync interval because the notification subscription to the SDK service is lost.
Any members that are removed from a group will not be synchronized to WSUS until the next sync interval because the membership notification mechanism does not work when a relationship is removed.

Workaround: Restart the OpsMgr Health Service on the Essentials 2007 management server to cause all group membership to be synchronized to WSUS or override the Interval property of the System.SCE.MP.GroupSynchronizationRule to a more frequent interval.

_

Issue: When installing the Essentials 2007 management server, setup may fail with the following event logged in the Application event log:

Event Type:       Error
Event Source:    .NET Runtime
Event Category: None
Event ID:           0
Date:                2007-07-31
Time:                03:10:28
User:                N/A
Computer:         TEMPO31D
Description:  .NET Runtime version : 2.0.50727.42 - Application ErrorApplication has generated an exception that could not be handled.

Workaround: Install .NET Framework 3.5 before installing Essentials 2007. You can obtain .NET Framework 3.5 from http://go.microsoft.com/fwlink/?LinkID=106379.

_

Issue: On computers on which you have installed an agent, you may see events in the event log with the IDs 2011 and 20012. These events are generated because the agent tries to connect to a service connection point (SCP) in Active Directory. These event IDs are created because the agent includes capabilities that are not used in this release of Essentials 2007 and the events have no effect on its functionality.

Workaround: None.

_

Issue: When you are running the Essentials 2007 console on Windows Server 2008, either on the Essentials 2007 management server or on a remote console, and you try to view a video from one of the Key Concepts and How-to Videos links in the console, the video may fail to open.

Workaround: Windows Media Player is part of the Desktop Experience feature in Windows Server 2008, but it may not be installed by default. You can install this feature from Server Manager.

_

Issue: A management pack is now available that replaces the "Windows Client Vista Operating Systems Essentials" management pack that shipped with Essentials 2007.

Workaround: Delete the "Windows Client Vista Operating Systems Essentials" management pack in the Essentials 2007 console Administration space. Download the Windows Vista Client Monitoring management pack from http://go.microsoft.com/fwlink/?LinkID=111117 and import the management pack into System Center Essentials 2007.

_

Issue: You may encounter one or more symptoms such as:

Failure to install the System Center Essentials 2007 management server or reporting components. The Setup program may return a message saying, "The setup wizard was interrupted before System Center Essentials 2007 could be installed."
In the case where the reporting feature does not install successfully, you may receive alerts indicating the report deployment failed, such as
- "Report deployment process failed to request management pack list from SQL Server 2005 Reporting Services. The operation will be retried."
- "Exception 'ServerDisconnectedException': The client has been disconnected from the server. Please call ManagementGroup.Reconnect() to reestablish the connection."

This is caused by the issue discussed in the following KB article: http://go.microsoft.com/fwlink/?LinkID=111142.

Workaround: Install the Windows Server 2003 hotfix that is available for Windows Server 2003 Service Pack 1 and Service Pack 2 from the location mentioned in the KB article: http://go.microsoft.com/fwlink/?LinkID=111142.

_

Issue: Windows Server 2008 support. At the time of the release of Essentials 2007 Service Pack 1, it is not supported to be installed on or to manage computers running Windows Server 2008 for production use. Windows Server 2008 will be added to Essentials 2007 supported configurations shortly after both Windows Server 2008 and Essentials 2007 Service Pack 1 are released. Please check the Essentials 2007 Web site at http://go.microsoft.com/fwlink/?LinkId=87292 to see if support for Windows Server 2008 has been added.

_

Issue: Upgrading the remote Essentials 2007 console on a computer that also has the Essentials 2007 agent installed requires that both the agent and user interface must be uninstalled before the remote console can be upgraded.

Workaround: If an agent and a remote Essentials 2007 console user interface are installed on the same computer, use this procedure to upgrade both to Service Pack 1.

Upgrade the Essentials 2007 management server to Service Pack 1.
Click the Administration button in the Essentials 2007 console on the management server.
In the Administration pane, expand Administration and then expand Device Management.
Select Agent Managed.
In the Views pane, right-click the computer whose agent you want to uninstall and click Delete.
On the computer running the remote Essentials 2007 console, uninstall the remote Essentials 2007 console using the Add/Remove Programs control panel.
Install RTM version of the remote Essentials 2007 console using Essentials 2007 RTM installation media.
Upgrade the remote console using Essentials 2007 Service Pack 1 upgrade package as described in the Upgrade Guide in Essentials 2007 Help.
Re-install agent on computer running the remote console using the Computer and Device Management Wizard on the Essentials 2007 management server.

_

Issue: Any views created in Essentials 2007 RTM that are intended to filter out update or software packages that are 'Approved for Uninstall' are not supported in Essentials 2007 SP1. Any such views will show all update packages or software packages when this option is selected. This property is no longer supported and there is no workaround.

_

Issue: Essentials 2007 updates will be available on Microsoft Update after the release of System Center Essentials 2007 Service Pack 1. When this category on Microsoft Update becomes available, you can create an automatic approval rule so that Essentials 2007 updates can be downloaded and installed. The relevant categories for the auto-approval rule are:

Product: System Center Essentials
Classification: Critical or Security updates
Computer group: Servers

If you manually create this rule you can ensure that service packages for Essentials 2007 itself will be downloaded and installed.

_

Issue: An alert stating "Managed Computer is not configured to use the Essentials update server" may continue to display after the computer has been correctly configured. Due to a timing issue, this alert may also appear on a correctly configured managed computer directly after agent install.

Workaround: Close the alert in Essentials 2007 manually to rescan the health state of the agent:

In the Essentials 2007 Console, click the Computers button.
In the Computers pane, click Computer Groups.
On the Overview page, under Monitoring Status, click n computers with active alerts.
In the Active Alerts window, right-click the alert and click Close Alert.

_

MP Released: Windows Server 2003 Cluster Management Pack for Operations Manager 2007 (6.0.6277.0)

CliveEastwood — Thu, 06 Mar 2008 21:34:00 GMT

The much awaited Cluster monitoring MP for OpsMgr07 has released to the Web (MP catalog update may take a little longer)

Here's the download center link http://www.microsoft.com/downloads/details.aspx?FamilyID=ac7f42f5-33e9-453d-a923-171c8e1e8e55&DisplayLang=en

Special installation notes (see the download page) for this release

REQUIRED if importing this MP on Operations Manager 20007 original release product

I have a Management Group running Operations Manager 2007 RTM installation

Install the hotfix KB945312 from the folder KB9435312RTM ONLY QFE on each Management server before installing the cluster MP. This hotfix provides a fix for the WMI provider where events may be incorrectly interpreted when generated within a short space of time of one another. When the hotfix installation wrapper SystemCenterOperationsManager2007-RTM-KB945312-X86-X64-ENU.msi is executed it will (by default) create the %programfiles%\System Center 2007 Hotfix Utility\Q945312 folder and automatically launch the update dialog. I would suggest reading the Q945312.rtf document before proceeding with application of the hotfix. Once the hotfix is installed you will need to approve agents upgrades from Pending Management, and for manually installed agents apply the hotfix directly.
Import the Microsoft.Windows.Cluster.Library.mp (6.0.6277.0) included with the hotfix (%programfiles%\System Center 2007 Hotfix Utility\Q945312)
Install all MP files included in the MP release

I have a Management Group running Operations Manager 2007 SP1

DO NOT install the hotfix, this is already included in Service Pack 1
There is also no requirement to install Microsoft.Windows.Cluster.Library.mp (6.0.6277.0) included with the hotfix above.

More details still on Marius' blog here http://blogs.msdn.com/mariussutara/archive/2008/03/04/mp-for-monitoring-cluster-services-mscs-finally-web-released.aspx

System Center Team blog on the Release of OpsMgr SP1 and additional SP1 Resources

CliveEastwood — Sat, 23 Feb 2008 04:34:59 GMT

Worth while keeping your feeds updated with info on http://blogs.technet.com/systemcenter/archive/2008/02/23/system-center-operations-manager-2007-service-pack-1-sp1-now-available.aspx

The TechCenter is already in the process of updates related to the SP1 release (http://technet.microsoft.com/en-us/opsmgr/cc280350.aspx) with major pointers to key topics in the process of publication now through Monday.

So lookout for updates to the Deployment and Operations Guides and the release of the SP1 Management Packs (SP1 is versioned at 06.0.6278.0000 by the way)

Operations Manager 2007 Service Pack 1 Debug Tracing

CliveEastwood — Sat, 23 Feb 2008 04:21:13 GMT

As Marius discussed (http://blogs.msdn.com/mariussutara/archive/2008/01/21/operations-manager-2007-sp1-tracing.aspx) SP1 introduces some changes in SP1 to debug level tracing sometimes required when working with Customer Support Services (CSS) on issues "under the hood". The KB article discussing tracing in the original release product (http://support.microsoft.com/kb/942864) will undergo a change shortly to reflect these changes.

I would still not expect tracing to be used without CSS interaction simply because of the detailed nature of the trace output which in MANY cases isn't meaningful without access to source code and the developers that wrote it:)

Below are my raw (warts and all) recommendations for the KB article update (should be prettier in the final KB release):

INTRODUCTION

This article describes how to use diagnostic tracing in Microsoft System Center Operations Manager 2007 and in Microsoft System Center Essentials 2007.

Important: We recommend that you perform diagnostic tracing only in association with a Microsoft Customer Support Services (CSS) representative. In Operations Manager and Essentials original release products we recommend this because the generated traces contain no human-readable text. After the traces are converted by a Microsoft CSS representative, human-readable text is available. However, this text contains only low-level information such as source-code file names, locations, source-code functions, and return codes. This information may be helpful if you have to troubleshoot a complex issue.

Within the Service Pack 1 release and above, Trace Message Files (TMF) are supplied which allow conversion of binary trace files to text. However it is still strongly recommended diagnostic tracing only be performed when required, and with the consultation of a Microsoft representative.

MORE INFORMATION

System Center Operations Manager 2007 and System Center Essentials 2007 implement a diagnostic tracing method that differs from earlier versions of Microsoft Operations Manager. This new tracing method creates binary files in which to store tracing information. Because this new tracing method is implemented at the Windows kernel level, it is highly efficient, and it can log tens of thousands of trace messages per second.

Trace information contains information about the context of a text-based trace message. However, within the original release products this trace information is not in a human-readable format. The traces must be sent to Microsoft CSS for conversion. With the Service pack 1 releases of Operations Manager and Essentials this is no longer a requirement as the files required to convert traces to human-readable format are supplied.

This article discusses the tools that are available to start and to stop tracing if you are asked to do this by a Microsoft CSS representative together with new functionality provided within Service Pack 1 and above.

Tracing tools location

The installation folder for each role, such as the Agent role, the Management Server role, or the Gateway role, contains a folder that is named Tools. The following files are located in the Tools folder:

StartTracing.cmd

StopTracing.cmd

TracelogSM.exe

TracingGuidsBid.txt

TracingGuidsUI.txt

TracingGuidsNative.txt

TracingReadMe.txt

Service Pack 1 introduces the following additions:

FormatTracing.cmd

ViewRealtimeTracing.cmd

TraceFmtSM.EXE

OpsMgrTraceTMF.cab

Default.TMF

System.TMF

To start tracing

NOTE: Within Service Pack 1 and above tracing is automatically started on both agent and management server roles. Tracing will default to error output only with binary trace files being written to the %WINDIR%\Temp\OpsMgrTrace folder. Before the tracing level for trace output can be changed, tracing must first be stopped.

To start diagnostic tracing, follow these steps:

1. On the computer on which you want to start tracing, click Start, click Run, type cmd , and then click OK.

2. At the command prompt, use the cd command to change to the Tools directory. For example, type the following command, and then press ENTER:

cd\Program Files\System Center Operations Manager 2007\Tools

3. Type StartTracing LEVEL , and then press ENTER. In this command, replace LEVEL with the tracing level that you want. You must use uppercase characters to specify the tracing level. The following levels are available :

ERR

WRN

INF

VER

For example, type StartTracing WRN .

When you start tracing, the trace output is written to the following binary files:

MOMTraceNative.etl

MOMTraceBID.etl

MOMTraceUI.etl

These files are located in the %WINDIR%\Temp folder.

NOTE: In Service Pack 1 and above trace files (.etl) are located in the %WINDIR%\Temp\OpsMgrTrace folder.

To stop tracing

To stop diagnostic tracing, follow these steps:

1. Click Start, click Run, type cmd , and then click OK.

2. At the command prompt, use the cd command to change to the Tools directory. For example, type the following command, and then press ENTER:

cd\Program Files\System Center Operations Manager 2007\Tools

3. Type StopTracing.cmd , and then press ENTER.

After you stop diagnostic tracing, you can send the .etl files from the %WINDIR%\Temp folder to the Microsoft CSS representative with whom you are working.

NOTE: In Service Pack 1 and above trace files (.etl) are located in the %WINDIR%\Temp\OpsMgrTrace folder.

To Convert Existing Traces to Text Format (Available with Service Pack 1 and above only)

To convert existing trace files to text tracing should first be stopped via the StopTracing,cmd command. Information within the converted traces is of an extremely low level detail (debug level) and will not be of use to the

1. Click Start, click Run, type cmd , and then click OK.

2. At the command prompt, use the cd command to change to the Tools directory. For example, type the following command, and then press ENTER:

3. cd\Program Files\System Center Operations Manager 2007\Tools

4. Type FormatTracing.cmd , and then press ENTER.

The first time FormatTracing.cmd is executed the Trace Message File (TMF) required to convert traces is extracted to the TMF subfolder.

The FormatTracing.cmd batch file then enumerates each trace file (*.etl) in the %WINDIR%\Temp\OpsMgrTrace folder, executing the TraceFMTSM.exe utility to convert it to text. The text output will be written to a file of the same name with the extension .log in the %WINDIR%\Temp\OpsMgrTrace folder. A summary (.sum) file will also be written to the same location for each file converted detailing each trace message event converted.

Viewing Converted Trace Files (Available with Service Pack 1 and above only)

Trace files converted to text (%WINDIR%\Temp\OpsMgrTrace) using the FormatTracing.cmd batch file can be viewed with Notepad or another suitable text editor.

Boot Time Tracing is Enabled by Default (Available with Service Pack 1 and above only)

On a typical Root Management Server (RMS) installation three trace sessions will begin when the HealthService service is started. By default only error tracing is performed, which will typically write little or no information to the trace files. The default trace file location and names created are:

%WINDIR%\Temp\OpsMgrTrace TracingGuidsBID.etl - Trace output for Managed Code Components

%WINDIR%\Temp\OpsMgrTrace TracingGuidsNative.etl - Trace output for Native Code Components

%WINDIR%\Temp\OpsMgrTrace TracingGuidsUI.etl - Trace output for Managed code User Interface (OpsMgr UI)

Each session is enabled with circular tracing at a maximum files size of 100Mb. The typical etl file size for a newly created etl file is 16Kb.

NOTE: Although an Operations Manager Role such as an Agent role does not contain Managed or UI tracing messages, the three default trace ETL files will be created by default when the HealthService service is started. On a User Interface only role no trace sessions are started by default.

How to disable boot time tracing (Available with Service Pack 1 and above only)

Three trace providers are automatically started on any role which contains the HealthService service with their trace files written to %WINDIR%\Temp\OpsmgrTrace. Typically the etl files in this folder will be small, especially on the agent role. However on the RMS role, if the operations manager installation becomes unhealthy one or more of these files could potentially grow to their maximum configured size of 100Mb each (TracingGuidsBid.etl, TracingGuidsNative.etl & TracingGuidsUI.etl, together with Previous.<filenames>.etl) even when error tracing only is enabled.

If it becomes necessary to disable tracing, due to small boot partition size this can be accomplished by adding a registry value on the computer. Note: If tracing is disabled this may affect future troubleshooting of Operations Manager because any low level tracing information will be lost. Future hotfixes, service packs or product updates may remove the registry entry therefore enabling tracing once more.

To disable debug level tracing add the following registry key to the Management Server or Agent you wish to disable tracing on:

HKLM\Software\Microsoft\Microsoft Operations Manager\3.0\Tracing\DisableAutoTracing:REG_DWORD:0x1

This registry key will not exist be default. Removing the registry key or changing its value to 0 will enable default tracing.

If you execute the StopTracing.cmd batch file from the Tools folder the Operations Manager trace sessions will be stopped. The etl files in the %WINDIR%\Temp\OpsmgrTrace can be deleted if they are no longer required to regain disk space.

How to move the default location of trace file output (Applies to Service Pack 1 and above only)

If, due to boot partition space limitations (typically the Management Server Role only) it is necessary to move the default location of trace files (*.etl) the following procedure can be used:

· Create a new folder on a local disk with sufficient capacity to house the files (three default trace files at maximum 100Mb, three previously used trace files at maximum 100Mb = Total potential trace file capacity of 600Mb).

· Set at least the following NTFS permissions on the folder, SYSTEM = Full Control, Administrators = Full Control.

· Locate the StartTracing.cmd batch file in the Tools folder beneath the Operations Manager/Essentials installation folder and opening it in a text editor such as Notepad.

· Within the StartTracing.cmd batch file locate the SET OpsMgrTracePath statement and replace the default value %windir%\temp\OpsMgrTrace with the path to the new location (delimit the path with speechmarks (“) if the path contains a space character)

· Save the changes to StartTracing.cmd

· To begin tracing to the new folder execute the StopTracing.cmd batch file and then execute the StartTracing.cmd batch file. Shortly after executing the StartTracing.cmd batch file the TracingGuidsBid.etl, TracingGuidsNative.etl & TracingGuidsUI.etl files will be written to the new folder.

· Before using the FormatTracing.cmd command to convert traces to text, this file much be edited too to change the OpsMgrTracePath variable to point to the new trace file folder.

Future hotfixes, service packs or product updates may change the files in the Tools folder changing the functionality back to the defaults. It is advised that you check the changes remain in place after performing updates.

How to view real time tracing (Available with Service Pack 1 and above only)

The use of the ViewRealTimeTracing.cmd batch file to view real time traces is strongly discouraged in a production environment without advice of Microsoft Customer Support Services. Viewing traces in real time especially at Information or Verbose trace level settings can incur large performance penalties.

The first time ViewRealTimeTracing.cmd is executed the Trace Message File (TMF) required to convert traces is extracted to the TMF subfolder. The ViewRealTimeTracing.cmd batch file then enumerates each trace session definition file (Tools\TracingGuids*.txt) in the Tools folder, launching a separate instance of TraceFmtSM within a command window. Output of trace sessions for Managed, Native and UI Managed traces is output to each window.

The ViewRealTimeTracing.cmd batch file accepts a single, optional command line parameter (-ods). Supplying this parameter will additionally output trace data to a debugger.

Operations Manager 2007 Service Pack 1 RTM - Upgrade Guide

CliveEastwood — Sat, 23 Feb 2008 02:03:41 GMT

I thought it may be a good idea to drop a copy of the Opsmgr SP1 Upgrade guide here for those planning deployments. Lots of information to take in and a few caveats besides. This can be found on the SP1 RTM CD image in the ProductDocumentation folder. RTM is imminent:)

And don't forget to import the SP1 Management Packs after upgrade.

Operations Manager 2007 SP1 Upgrade Guide

Upgrading from Microsoft Operations Manager 2007 to Microsoft Operations Manager 2007 Service Pack 1 is a multi-step 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 hosting the component being upgraded.

Before upgrading, please read Known Issues with the Operations Manager 2007 SP1 Upgrade at the end of this document where you will find topics such as considerations for agents that are multi-homed between upgraded and non-upgraded management groups.

Note

If you attempt to run SP1Upgrade.exe on a computer that is not hosting an Operations Manager 2007 component, the setup application will close and no warning will be displayed.

Upgrade Paths

To upgrade Operations Manager 2007 to SP1, run SP1Upgrade.exe from either the CD or from the downloaded update.

The following diagram provides an outline of the supported and unsupported upgrade paths.

Upgrade Evaluation Copies

When upgrading from an evaluation copy of the SP1 Release Candidate (RC) to the licensed version of Operations Manager 2007 SP1, double-click SetupOM.exe to both upgrade the license and perform an upgrade to Operations Manager 2007 SP1. Perform this step on only the Root Management Server. For all other computers hosting other Operations Manager components, double-click SP1Upgrade.exe to perform an upgrade.

To upgrade an evaluation copy of Operations Manager 2007 SP1 to the licensed version of Operations Manager 2007 SP1, double-click SetupOM.exe to upgrade the license. Perform this step on only the Root Management Server. No other upgrade actions are necessary.

Order of Operations

Upgrading to Operations Manager 2007 SP1 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

How to Prepare a Management Group for Upgrading to Operations Manager 2007 Service Pack 1
How to Upgrade the Root Management Server (RMS) to Service Pack 1
How to Upgrade Reporting to Service Pack 1
How to Upgrade a Standalone Operations Console to Service Pack 1
How to Upgrade a Management Server to Service Pack 1
How to Upgrade a Gateway Server to Service Pack 1
How to Upgrade an Agent to Service Pack 1
How to Upgrade a Web Console Server to Service Pack 1
How to Upgrade the ACS Collector to Service Pack 1
How to Enable Subscriptions
Known Issues with the Operations Manager 2007 SP1 Upgrade

How to Prepare a Management Group for Upgrading to Operations Manager 2007 Service Pack 1

Prepare for upgrading the Operations Manager 2007 management group by completing the procedures in this topic first. These procedures include removing agents from standalone Operations Consoles, backing up the databases in Operations Manager, 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.

Remove agents from computers that have standalone Operations Consoles

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.
In the Operations Console, click Administration.
In the Administration pane, expand Administration, expand Device Management, and then click Agent Managed.
In the Agent Managed pane, right-click the computers for which you want to uninstall the agent, and then select Uninstall.
In the Uninstall Agents dialog box, either leave Use selected Management Server Action Account selected, or do the following:
1. Select Other user account.
2. 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.
3. Click Uninstall.
In the Agent Management Task Status dialog box, the Status for each selected computer changes from Queued to Success.
Click Close.

Back up all Operations Manager 2007 databases

For the Root Management Server, backup the Operations Manager Database.
For Reporting, back up the Reporting Data Warehouse.
For Audit Collection Services (ACS), back up the ACS Database.

Note

For more information about backing up and restoring the Operations Manager Database, see http://go.microsoft.com/fwlink/?LinkId=96638.

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

On the computer hosting the Operations Manager database, on the Windows desktop, click Start, point to Programs, point to Microsoft SQL Server 2005, and then click SQL Server Management Studio.
In the Connect to Server dialog box, in the Server Type list, select Database Engine.
In the Server Name list, select the server and instance for your Operations Manager database (for example, computer\INSTANCE1).
In the Authentication list, select Windows Authentication, and then click Connect.
In the Object Explorer pane, expand Databases, right-click OperationsManager, and then click Properties.
In the Database Properties - OperationsManager dialog box, under Select a page, click Files.
In the results pane, increase the Initial Size value for the MOM_DATA database by 50%.
Increase the Initial Size value for the MOM_LOG database by 50%, and then click OK.

Increase space available for data and log files on the Reporting Data Warehouse

On the computer hosting the Reporting Data Warehouse, on the Windows desktop, click Start, point to Programs, point to Microsoft SQL Server 2005, and then click SQL Server Management Studio.
In the Connect to Server dialog box, in the Server Type list, select Database Engine.
In the Server Name list, select the server and instance for your Operations Manager database (for example, computer\INSTANCE1).
In the Authentication list, select Windows Authentication, and then click Connect.
In the Object Explorer pane, expand Databases, right-click OperationsManagerDW, and then click Properties.
In the Database Properties - OperationsManager dialog box, under Select a page, click Files.
In the results pane, increase the Initial Size value for the MOM_DATA database file by 50%.
Increase the Initial Size value for the MOM_LOG database by 50%, and then click OK.

Disable Subscriptions

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.
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.
In the Administration pane, expand Administration, expand Notifications, and then click Subscriptions.
In the Subscriptions pane, right-click each subscription, and then click Disable.

Note

Multi-select does not work when disabling subscriptions.

Remove agents that are pending management

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.
In the Administration pane, expand Device Management, and then click Pending Management.
Right-click each agent, and then click Approve or Reject.

Caution

When connecting remotely to a server, use the command mstsc.exe /console, otherwise log files that are collected during Setup will be lost when your system restarts. These log files might be critical to troubleshooting should the upgrade fail.

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.

To improve upgrade performance

On the computer hosting the Operations Manager database, on the Windows desktop, click Start, point to Programs, point to Microsoft SQL Server 2005, and then click SQL Server Management Studio.
In the Connect to Server dialog box, in the Server Type list, select Database Engine.
In the Server Name list, select the server and instance for your Operations Manager database (for example, computer\INSTANCE1).
In the Authentication list, select Windows Authentication, and then click Connect.
In the Object Explorer pane, right-click the computer\instance name at the top of the explorer tree, and then click New Query.
In the New Query results pane, type the following three SQL commands
```
use OperationsManager
exec sp_updatestats
DBCC FREEPROCCACHE
```
Click the Query menu, and then click Execute.
Click the File menu, and then click Exit.

How to Upgrade the Root Management Server to Service Pack 1

There are two ways to upgrade the Root Management Server (RMS). 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 to Operations Manager 2007 Service Pack 1 is performed locally on the RMS or locally on the nodes of the cluster that contains the RMS. For either procedure, the Operations Database is also upgraded with no additional steps. The additional procedures that verify whether the upgrade is successful are optional.

Note

Close all Operations Manager consoles before proceeding with the upgrade.

To upgrade the Root Management Server and Operations Manager Database

Log on to the computer hosting an RMS with an account that is a member of the Operations Manager Administrators role for your Operations Manager 2007 management group and a local administrator on the computer.
Insert the Operations Manager 2007 Service Pack 1 media.
At the root of the media, double-click SP1Upgrade.exe.
In the Apply Service Pack 1 section, click Operations Manager 2007. The System Center Operations Manager 2007 Setup Upgrade Wizard starts.

Note

You might be prompted with a System Center Operations Manager 2007 SP1 Setup dialog box indicating that a software update must be installed before the upgrade can proceed. Click Yes to proceed with the upgrade.
On the Welcome to the System Center Operations Manager 2007 Server Setup Upgrade Wizard page, click to select the Upgrade to Operations Manager 2007 SP1 check box, and then click Next.
On the End-User License Agreement page, read the licensing terms, click I accept the terms in the license agreement, and then click Next.
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.
When the Completing the System Center Operations Manager 2007 Setup Wizard page appears, click Finish.
If prompted, restart the server.

To upgrade the Root Management Server using a command prompt

Log on to a computer hosting the Root Management Server with an Operations Manager Administrators role account for your Operations Manager 2007 management group.
Insert the Operations Manager 2007 Service Pack 1 media.
Open the command window.
For example, at the command prompt, type the following:

%WinDir%\System32\msiexec.exe /p \\ path \MOM2007QFEPreSP1.msp /qn /l*v D:\logs\QFERollup.log REINSTALLMODE=omus REINSTALL=ALL
After step 4 completes, type the following at the command prompt:

%WinDir%\System32\msiexec.exe /i \\ path \MOM2007SP1.msi /qn /l*v D:\logs\SP1Upgrade.log SP1UPGRADE=1 REINSTALLMODE=omus REINSTALL=ALL

To upgrade Root Management Server on a cluster and Operations Manager Database

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 management group.
In the navigation pane, expand the cluster name, expand Groups, and then click the Operations Manager group.
In the results pane, examine the cluster resources listed in Name column and ensure they are online.
In the results pane, in the Owner column, note which node is the owner node.
Ensure that you have logged on to the owner 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.
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.
1. In the Cluster Administrator pane, right-click the service you want to change (for example, OpsMgr Health Service), and then click Properties.
2. In the Properties dialog box, click Modify.
3. 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 of the nodes have been upgraded, configure your Operations Manager 2007 group to failover to the original primary node.
Insert the Operations Manager 2007 Service Pack 1 media.
At the root of the media, double-click SP1Upgrade.exe.
In the Apply Service Pack 1 section, click Operations Manager 2007. The System Center Operations Manager 2007 Setup Upgrade Wizard starts.

Note

You might be prompted with a System Center Operations Manager 2007 SP1 Setup dialog box indicating that a software update must be installed before the upgrade can proceed. Click Yes to proceed with the upgrade.
On the Welcome to the System Center Operations Manager 2007 Server Setup Upgrade Wizard page, select the Upgrade to Operations Manager 2007 SP1 check box, and then click Next.
On the End-User License Agreement page, read the licensing terms, click I accept the terms in the license agreement, and then click Next.
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.

Important

During installation, a warning message will display stating that Setup failed to clean up the service state folder. Click OK to proceed. When Setup completes, see the topic "Health Service State Directory Error" in the Known Issues with the Operations Manager 2007 SP1 Upgrade section later in this guide.

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.
When the Completing the System Center Operations Manager 2007 Setup Wizard page appears, click Finish.

Note

If prompted, restart the server.
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 verify the Operations Manager Database upgrade

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.
In the Connect to Server dialog box, in the Server Type list, select Database Engine.
In the Server Name list, select or type the server and instance for your operations database (for example, computer\INSTANCE1).
In Authentication list, select Windows Authentication, and then click Connect.
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.0.627x.x, where x is any positive integer, your operations database upgraded successfully.

To verify the Root Management Server upgrade

On the Windows desktop, click Start, and then click Run.
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.
Navigate to the HKey_Local_Machine\Software\Microsoft\Microsoft Operations Manager\3.0\Setup key. If the value of the ServerVersion entry is 6.0.627x.x, where x is any positive integer, your RMS upgraded successfully.
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

For every node in the cluster, click Start, and then click Run.
1. 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.
2. Navigate to the HKey_Local_Machine\Software\Microsoft\Microsoft Operations Manager\3.0\Setup key. If the value of the ServerVersion entry is 6.0.627x.x, where x is any positive integer, your RMS upgraded successfully.
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 Service Pack 1

The procedure to upgrade the Reporting Server from Operations Manager 2007 to Operations Manager 2007 Service Pack 1 is performed on the computer hosting 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

Log on to the computer hosting the Reporting Server with an account that is a member of the Operations Manager Administrators role for your Operations Manager 2007 management group.
Insert the Operations Manager 2007 Service Pack 1 media.
At the root of the media, double-click SP1Upgrade.exe.
In the Apply Service Pack 1 section, click Operations Manager 2007 Reporting. The Operations Manager 2007 Reporting Setup wizard starts.
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.
On the End-User License Agreement page, read the licensing terms, click I accept the terms in the license agreement, and then click Next.
On the Ready to Install the Program page, click Install.
When the Completing the Operations Manager Reporting Components Setup Wizard page appears, click Finish.

To upgrade the Reporting Server using a command prompt

Log on to a computer hosting the Reporting Server with an Operations Manager Administrators role account for your Operations Manager 2007 management group.
Insert the Operations Manager 2007 Service Pack 1 media.
Open the command window.
For example, at the command prompt, type the following:

%WinDir%\System32\msiexec.exe /i \\ path \Directory\Reporting2007.msi /qn /l*v D:\logs\ReportingUpdate.log SP1UPGRADE=1 SET_ACTIONS_ACCOUNT=0 REINSTALLMODE=vomus REINSTALL=ALL

To verify the Reporting Server upgrade

On the computer hosting the Reporting Server, click Start, and then click Run.
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.
Navigate to the HKLM\Software\Microsoft\Microsoft Operations Manager\3.0\Setup key. If the value of the CurrentVersion entry is 6.0.627x.x, where x is any positive integer, your Reporting Server upgraded successfully.

How to Upgrade a Standalone Operations Console to Service Pack 1

This procedure upgrades a standalone Operations Console from Operations Manager 2007 to Operations Manager 2007 Service Pack 1. 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 Service Pack 1 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 standalone Operations Console

Log on to the computer hosting the Operations Console with an Operations Manager Administrators role account for your Operations Manager 2007 management group.
Insert the Operations Manager 2007 Service Pack 1 media.
At the root of the media, double-click SP1Upgrade.exe.
In the Apply Service Pack 1 section, click Operations Manager 2007.
In the System Center Operations Manager 2007 SP1 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.
On the Welcome page, click to select the Upgrade to Operations Manager 2007 SP1 check box, and then click Next.
On the End-User License Agreement page, read the licensing terms, click I accept the terms in the license agreement, and then click Next.
On the Ready to Install the Program page, click Install. The Installing System Center Operations Manager 2007 page displays the progress of the upgrade.
When the Completing the System Center Operations Manager 2007 Setup Wizard page appears, click Finish.

To upgrade a standalone Operations Console using a command prompt

Log on to the computer hosting the Operations Console with an Operations Manager Administrators role account for your Operations Manager 2007 management group.
Insert the Operations Manager 2007 Service Pack 1 media.
Open the command window.
For example, at the command prompt, type the following:

%WinDir%\System32\msiexec.exe /p \\ path \MOM2007QFEPreSP1.msp /qn /l*v D:\logs\QFERollup.log REINSTALLMODE=omus REINSTALL=ALL
After step 4 completes, type the following at the command prompt:

%WinDir%\System32\msiexec.exe /i \\ path \MOM2007SP1.msi /qn /l*v D:\logs\SP1Upgrade.log REINSTALLMODE=omus REINSTALL=ALL

To verify the Operations Console upgrade

On the Windows desktop, click Start, and then click Run.
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.
Navigate to the HKey_Local_Machine\Software\Microsoft\Microsoft Operations Manager\3.0\Setup key. If the value of the UIVersion entry is 6.0.627x.x, where x 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 Service Pack 1

Perform the procedure to upgrade a management server from Operations Manager 2007 to Operations Manager 2007 SP1 locally on each management server. You must upgrade the Root Management Server (RMS) of a management group before upgrading any of the management servers.

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

To upgrade a management server

Log on to the computer hosting the management server with an Operations Manager Administrators role account for your Operations Manager 2007 management group.
Insert the Operations Manager 2007 Service Pack 1 media.
At the root of the media, double-click SP1Upgrade.exe.
In the Apply Service Pack 1 section, click Operations Manager 2007. The System Center Operations Manager 2007 Server Setup Upgrade Wizard starts.

Note

You might be prompted with a System Center Operations Manager 2007 SP1 Setup dialog box indicating that a software update must be installed before the upgrade can proceed. Click Yes to proceed with the upgrade.
On the Welcome to the System Center Operations Manager 2007 Server Setup Upgrade Wizard page, click to select the Upgrade to Operations Manager 2007 SP1 check box, and then click Next.
On the End-User License Agreement page, read the licensing terms, click I accept the terms in the license agreement, and then click Next.
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.
When the Completing the System Center Operations Manager 2007 Setup Wizard page appears, click Finish.

To upgrade a management server using a command prompt

Log on to the computer hosting the Operations Console with an Operations Manager Administrators role account for your Operations Manager 2007 management group.
Insert the Operations Manager 2007 Service Pack 1 media.
Open the command window.
For example, at the command prompt, type the following:

%WinDir%\System32\msiexec.exe /p \\ path \MOM2007QFEPreSP1.msp /qn /l*v D:\logs\QFERollup.log REINSTALLMODE=omus REINSTALL=ALL
After step 4 completes, type the following at the command prompt:

%WinDir%\System32\msiexec.exe /i \\ path \MOM2007SP1.msi /qn /l*v D:\logs\SP1Upgrade.log SP1UPGRADE=1 REINSTALLMODE=omus REINSTALL=ALL

To verify the management server upgrade

On the computer hosting the management server, click Start, and then click Run.
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.
Navigate to the HKey_Local_Machine\Software\Microsoft\Microsoft Operations Manager\3.0\Setup key. If the value of the ServerVersion entry is 6.0.627x.x, where x is any positive integer, your management server upgraded successfully.

How to Upgrade a Gateway Server to Service Pack 1

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

To upgrade the gateway server

Log on to the computer hosting the gateway server with an Operations Manager Administrators role account for your Operations Manager 2007 management group.
Insert the Operations Manager 2007 Service Pack 1 media.
At the root of the media, double-click SP1Upgrade.exe.
In the Apply Service Pack 1 section, click Operations Manager 2007 Gateway. When the Resuming the setup wizard for System Center Operations Manager Gateway page opens, click Next.
In the Welcome to the System Center Operations Manager Gateway Setup wizard page, click Next.
The status page displays the progress of the upgrade.
When the Completing the System Center Operations Manager Gateway Setup wizard page appears, click Finish.
If prompted, restart the server.

To upgrade the gateway server using a command prompt

Log on to a computer hosting the gateway server with an Operations Manager Administrators role account for your Operations Manager 2007 management group.
Insert the Operations Manager 2007 Service Pack 1 media.
Open the command window.
For example, at the command prompt, type the following:

%WinDir%\System32\msiexec.exe /i \\ path \MOMGateway.msi /qn /l*v D:\logs\GatewayUpdate.log SP1UPGRADE=1 SET_ACTIONS_ACCOUNT=0 REINSTALLMODE=vomus REINSTALL=ALL

To verify the gateway server upgrade

On the computer hosting the gateway server, click Start, and then click Run.
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.
Navigate to the HKey_Local_Machine\Software\Microsoft\Microsoft Operations Manager\3.0\Setup key. If the value of the MOMGatewayVersion entry is 6.0.627x.x, where x is any positive integer, your gateway server upgraded successfully.

How to Upgrade an Agent to Service Pack 1

There are four procedures available for upgrading agents from Operations Manager 2007 to Operations Manager 2007 SP1: 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 using the Operations Console

Log on to the computer hosting the Operations Console with an account that is a member of the Operations Manager Administrators role for the Operations Manager 2007 management group.
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.
In the Administration pane, expand Device Management, and then click Pending Management.
In the Pending Management pane, expand Type: Agent Requires Update, right-click each agent-managed computer listed, and then click Approve.
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.
When the upgrade is complete, click Close.

Note

Agents deployed from a Root Management Server upon which HOTFIX Q937456 was applied will not be upgraded. To upgrade these agents, copy MomAgent.msi from the Operations Manager 2007 Service Pack 1 media to \Program Files\System Center Operations Manager 2007\AgentManagement\cpu type directory on the computer hosting the Root Management Server before using this procedure. Be sure to copy all three CPU types: x86, ia64, and amd64.

To manually upgrade an agent using the Setup Wizard

Log on to a computer hosting the agent with an Operations Manager Administrators role account for your Operations Manager 2007 management group.
Insert the Operations Manager 2007 Service Pack 1 media.
At the root of the media, double-click SP1Upgrade.exe.
In the Apply Service Pack 1 section, click Operations Manager 2007 Agent. The Welcome to the System Center Operations Manager Agent Upgrade Wizard page opens, and then click Next.
In the System Center Operations Manager Agent Setup dialog box, click Upgrade. The status page displays the progress of the upgrade.
When the Completing the System Center Operations Manager Agent Setup wizard page appears, click Finish.

To manually upgrade an agent using the command prompt

Log on to a computer hosting the agent with an Operations Manager Administrators role account for your Operations Manager 2007 management group.
Insert the Operations Manager 2007 Service Pack 1 media.
Open the command window.
For example, at the command prompt, type the following: %WinDir%\System32\msiexec.exe /i \\path\Directory\MOMAgent.msi /qn /l*v c:\opsmgr.log SP1UPGRADE=1 SET_ACTIONS_ACCOUNT=0 REINSTALLMODE=vomus REINSTALL=ALL

Note

If the agent was deployed using Active Directory Integration, type the following:
%WinDir%\System32\msiexec.exe /i \\path\Directory\MOMAgent.msi /qn /l*v c:\opsmgr.log SP1UPGRADE=1 SET_ACTIONS_ACCOUNT=0 REINSTALLMODE=vomus REINSTALL=ALL USE_MANUALLY_SPECIFIED_ACCOUNT=0

To upgrade agents using Active Directory Integration

Log on to the computer with an Operations Manager Administrators role account for the Operations Manager 2007 management group.
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 displays. Type the name of the Operations Manager 2007 management server you want the Operations Console to connect to in the Server name text box.
In the Administration pane, expand Administration, expand Device Management, and then click Agent Managed.
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

On the computer hosting an agent, click Start, and then click Run.
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.
Navigate to the HKey_Local_Machine\Software\Microsoft\Microsoft Operations Manager\3.0\Setup key. If the value of the AgentVersion entry is 6.0.627x.x, where x is any positive integer, your agent upgraded successfully.

How to Upgrade a Web Console Server to Service Pack 1

Perform this procedure on the computer hosting the Web Console server to upgrade a Web Console from Operations Manager 2007 to Operations Manager 2007 SP1.

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

Log on to the computer hosting the Web Console server with an Operations Manager Administrators role account for your Operations Manager 2007 management group.
Insert the Operations Manager 2007 Service Pack 1 media.
At the root of the media, double-click SP1Upgrade.exe.
In the Apply Service Pack 1 section, click Operations Manager 2007. The System Center Operations Manager 2007 Server Setup Upgrade Wizard starts.

Note

You might be prompted with a System Center Operations Manager 2007 SP1 Setup dialog box indicating that a software update must be installed before the upgrade can proceed. Click Yes to proceed with the upgrade.
On the Welcome page, select the Upgrade to Operations Manager 2007 SP1 check box, and then click Next.
On the End-User License Agreement page, read the licensing terms, click I accept the terms in the license agreement, and then click Next.
On the Ready to Install the Program page, click Install. The Installing System Center Operations Manager 2007 page displays the progress of the upgrade.
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

Log on to the computer hosting the Operations Console with an Operations Manager Administrators role account for your Operations Manager 2007 management group.
Insert the Operations Manager 2007 Service Pack 1 media.
Open the command window.
For example, at the command prompt, type the following:

%WinDir%\System32\msiexec.exe /p \\ path \MOM2007QFEPreSP1.msp /qn /l*v D:\logs\QFERollup.log REINSTALLMODE=omus REINSTALL=ALL
After step 4 completes, type the following at the command prompt:

%WinDir%\System32\msiexec.exe /i \\ path \MOM2007SP1.msi /qn /l*v D:\logs\SP1Upgrade.log SP1UPGRADE=1 REINSTALLMODE=omus REINSTALL=ALL

To verify the Web Console server upgrade

On the computer hosting the Web Console server, click Start, and then click Run.
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.
Navigate to the HKey_Local_Machine\Software\Microsoft\Microsoft Operations Manager\3.0\Setup key. If the value of the CurrentVersion entry is 6.0.627x.x, where x is any positive integer, your Web Console Server upgraded successfully.

How to Upgrade the ACS Collector to Service Pack 1

Perform this procedure to upgrade the Audit Collection Services (ACS) Collector from Operations Manager 2007 to Operations Manager 2007 Service Pack 1 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. You must upgrade the management server components before you upgrade the ACS Collector component.

To upgrade an ACS Collector

Log on to the computer hosting the ACS Collector with an Operations Manager Administrators role account for your Operations Manager 2007 management group.
Insert the Operations Manager 2007 Service Pack 1 media.
On the root of the media, double-click SP1Upgrade.exe.
In the Apply Service Pack 1 section, click Audit Collection Server. The Audit Collection Services Collector Setup Wizard starts.
On the Welcome to the Audit Collection Services Collector Setup Wizard page, click Next.
On the Database Installation Options page, click Use an existing database, and then click Next.
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.
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.
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.
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.
When the upgrade is complete, click Finish.

To upgrade the ACS Collector using a command prompt

Log on to a computer hosting the gateway server with an Operations Manager Administrators role account for your Operations Manager 2007 management group.
Insert the Operations Manager 2007 Service Pack 1 media.
Open the command window.
For example, at the command prompt, type the following:

%WinDir%\System32\msiexec.exe /i \\ path \AdtServer.msi /qn /l*v D:\logs\ACSUpdate.log REINSTALLMODE=vamus REINSTALL=ALL

How to Enable Subscriptions

Once the upgrade has completed, use the following procedure to re-enable subscriptions.

Enable Subscriptions

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.
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.
In the Administration pane, expand Administration, expand Notifications, and then click Subscriptions.
In the Subscriptions pane, right-click each subscription, and then click Enable.

Known Issues with the Operations Manager 2007 SP1 Upgrade

The following items are known issues with the Operations Manager 2007 SP1 release.

An "Audit Collection Services update failed" Error Might Occur when Upgrading to Audit Collection Services SP1

An "Audit Collection Services update failed" error might be displayed after performing an upgrade of the ACS Collector. The error ID that will be displayed is 0x00000BC2. This error incorrectly states that the upgrade failed.

Workaround: Restart the computer. The error code of 0x00000BC2 means that changes have been made but will not be effective until the computer has been restarted.

Additional Upgrade Steps Must Be Performed when Installing or Re-Installing Reporting in an Environment Where the RMS Was Upgraded from SP1 RC to SP1

If your environment contains a Root Management Server that was at one time at the SP1 RC level, and was later upgraded to SP1, you must follow the steps below after Reporting has been installed.

Workaround: Add the credentials you specified for the Data Reader account to the Operations Manager Report Operators User Role. See the topic "How to Add Users or Groups to the Report Operator User Role in Operations Manager 2007" in the Operations Manager help.

Agents That Are Not Upgraded Can Consume Excessive System Resources

Agents that are not upgraded in an environment where the management server has been upgraded can cause the computer hosting the agent to consume excessive system resources.

Workaround: Upgrade the agent, or if this is not possible, install hotfix Q941811. This hotfix is available on the Operations Manager 2007 SP1 installation media.

Cluster may failover to another node while performing the upgrade

If an upgrade on a clustered node fails, examine the Operations Manager Event log for the following event:

Event Type: Error

Event Source: OpsMgr SDK Service

Event Category: None

Event ID: 23680

Description:

The System Center Operations Manager SDK Service failed due to an unhandled exception.

The service will attempt to restart.

Exception:

System.TypeLoadException: Method 'SetupEventsByManagedEntityIdAndCriteriaAndClassReader' in type 'Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.SdkDataAccess' from assembly 'Microsoft.Mom.Sdk.ServiceDataLayer, Version=6.0.4900.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' does not have an implementation.

at Microsoft.EnterpriseManagement.Mom.Sdk.Service.SdkSubService.AsyncStartCallback(Object notUsed)

at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)

at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback(Object state)

This issue might occur when a service is stopped during the upgrade. The cluster interprets this as a failure and then performs a failover to another node.

Workaround: To prevent this issue, use the following procedure to limit the nodes that a service can run on to the specific node you are upgrading.

To limit nodes that a service can run on

In the Cluster Administrator pane, right-click the service you want to change (for example, OpsMgr Health Service), and then click Properties.
In the OpsMgr Health Service Properties dialog box, click Modify.
In the Modify Preferred Owner dialog box, under Available nodes, select the node you are performing the upgrade on, ensure it is the only node listed under Preferred owners, and then click OK.

Health Service State Directory Error

An error regarding the deletion of the Health Service State directory during upgrade of the Root Management Server, management server, gateway server, or agent might occur during the upgrade.

The error contains the following information:

Event Type: Error

Event Source: Service Control Manager

Event Category: None

Event ID: 7023

Description:

The OpsMgr Health Service service terminated with the following error:

%%2164195332

Workaround: Use the following procedure to manually delete the directory and then restart the Ops Mgr Health Service.

To delete the Health Service State directory and restart the Health Service

Click Start, point to Programs, point to Administrative Tools, and then click Services (on a client operating system, the Services application is accessed through Control Panel).
In the Name column, right-click OpsMgr Health Service, and then click Stop.
Start Windows Explorer, and then navigate to %Program Files%\System Center Operations Manager 2007.
Right-click the Health Service State folder, and then click Delete.
Exit Windows Explorer.
Click Start, point to Programs, point to Administrative Tools, and then click Services (on a client operating system, the Services application is accessed through Control Panel).
In the Name column, right-click OpsMgr Health Service, and then click Start.

To delete the Health Service State directory on a cluster and restart the Health Service

Log on to the active node of the cluster.
Using the Cluster Administrator, set the OpsMgr Health Service to offline.
Start Windows Explorer and navigate to %Program Files%\System Center Operations Manager 2007.
Right-click the Health Service State folder, and then click Delete.
Exit Windows Explorer.
Using the Cluster Administrator, set the OpsMgr Health Service to online.
Repeat these steps on every node of the cluster.

Unable to Start the Operations Console After Upgrading from Operations Manager 2007 SP1 RC to Operations Manager 2007 SP1 when Hotfixes Q945313 or Q946528 Have Been Installed

If you are upgrading from Operations Manager 2007 SP1 RC to Operations Manager 2007 SP1 and you had hotfixes Q945313 or Q946528 installed, you might be unable to start the Operations Console. Moreover, the Operations Manager database version number in the dbo__MOMManagementGroupInfo__ table will not have been updated.

Workaround: Using SQL Server Management Studio, open the OperationsManager database, locate the dbo__MOMManagementGroupInfo__ table and change the DBVersion entry from 6.0.6246.0 to 6.0.627x.0 where X is the last digit of the version number for Operations Manager 2007 SP1.

A Multi-homed Agent Stops Sending Events to Management Groups That Are Not Updated

If an agent is multi-homed to two management groups where one management group has been upgraded to SP1 and the other management group has not, the agent will stop sending events to the non-upgraded management group.

Workaround: If possible, upgrade the remaining management group to SP1. If that is not possible, install hotfix Q941557 on the computer hosting the management server that the agent is connecting to in the non-upgraded management group. This hotfix is available on the Operations Manager 2007 SP1 installation media.

An Error Event With an ID of 4511 Might Occur when Upgrading to SP1

An event of type error with an Event ID of 4511 might occur after upgrading a management server when the associated agents are monitoring cluster-aware applications; for example, Microsoft SQL Server or Microsoft Exchange. This issue will occur only when upgrading from Operations Manager 2007 to Operations Manager 2007 SP1. This issue will not occur when upgrading from an RC version of Operations Manager 2007 SP1 to Operations Manager 2007 SP1. This issue might occur after the management server is updated and before the agent is updated.

Workaround: This issue will be resolved once the agent has been updated to Operations Manager 2007 SP1. We recommend that agents are updated as soon as possible.

Uninstalling the Operations Console Permanently Removes the Command Shell

Removing the Operations Console from a computer that is also hosting either a Root Management Server or management server will result in the permanent loss of the Command Shell on that computer. This issue does not occur if the Operations Console is on a standalone computer.

Once the Operations Console is removed, you can re-install the Operations Console, but not the Command Shell.

Upgrading Microsoft System Center Desktop Error Monitoring 2007 Might Fail to Upgrade if Hotfixes Have Been Installed

Attempting to upgrade System Center Desktop Error Monitoring 2007 to System Center Desktop Error Monitoring 2007 SP1 or attempting to upgrade System Center Desktop Error Monitoring 2007, which has been licensed (Select version) to Select SP1, might fail if hotfixes have been installed.

Workaround: Customers using System Center Desktop Error Monitoring 2007 should not use the Operations Manager 2007 SP1 upgrade and instead wait for the System Center Desktop Error Monitoring 2007 SP1 Upgrade to be released. Customers who have licensed their copy of System Center Desktop Error Monitoring 2007 to the Select version should contact Microsoft for upgrade instructions before attempting an upgrade.

Error Messages

When you use Add or Remove Programs to remove the Operations Console, the following issues might occur.

Warning 25453. Setup failed to cleanup the service stat folder at <path to Operations Manager>\Health Service State. Please remove it manually
Error 1334. The file F_Microsoft.Mom.Sdk.OperationsManager.ClientShell.Startup.ps1.E1C3A829_C8F3_443F_B5FEE_0CE01DB47829 cannot be installed because the file cannot be found in cabinet file Data.Cab.

Click OK on any error message that displays. These errors can be ignored.

Dialog Boxes Indicate an Upgrade when Uninstalling the Operations Console

When you use Add or Remove Programs to remove the Operations Console, dialog boxes might display indicating that you are upgrading Operations Manager. Make the same choices you made when you performed the upgrade. The Operations Console is removed during this process.

Workaround: Install the Operations Console and Command Shell on a standalone computer from the Operations Manager 2007 installation media and then upgrade to SP1.

Attempting to Add Additional Components Might Fail

Attempting to add additional components to a computer that has been upgraded to Operations Manager 2007 SP1 might fail when double-clicking SetupOM.exe from the SP1 media.

Workaround: Use Add or Remove Programs and select Modify to add additional components after upgrading to SP1.

In the following example, an Operations Console will be installed on a computer that hosts a management server. The management server was previously upgraded to SP1.

To Add Additional Components to Operations Manager 2007 SP1

Click Start, point to Settings, and then click Control Panel.
In Control Panel, double-click Add or Remove Programs.
In Add or Remove Programs, click Change or Remove Programs.
In the list of Currently installed programs, click System Center Operations Manager 2007, and then click Change.
On the Welcome to the System Center Operations Manager 2007 Setup Wizard page, click Upgrade to Ops Mgr 2007, and then click Next.
On the End-User License Agreement page, read the licensing terms, click I accept the terms in the license agreement, and then click Next.
On the Ready to Install the Program page, click Install.

Note

No changes to your installation will be take place at this time.
On the Welcome to the System Center Operations Manager 2007 Setup Wizard page, click Next.
On the System Center Operations Manager 2007 Maintenance page, click Modify, and then click Next.
On the Custom Setup page, select the components you want to add. For example, click User Interfaces, click This component will be installed on local hard drive, and then click Next.
On the Customer Experience Improvement Program page, do one of the following:
- If you do not want your organization to participate in the program, leave the default option I don't want to join the program selected and then click Next.
- If you want your organization to participate in the program, select Join the Customer Experience Improvement Program, and then click Next.
On the Ready to Modify the Program page, click Install.

Note

Errors messages might be displayed. Press OK on any error dialog boxes that display.
On the Completing the System Center Operations Manager 2007 Setup Wizard page, click Finish.
Close the Add or Remove Programs dialog box.
Close the Control Panel dialog box

The SP1 Release Includes OpsMgr VSS Writer Service

A new OpsMgr VSS Writer Service has been added to computers that host either a Root Management Server or management server. The Volume Shadow Copy Service provides the means for creating consistent point-in-time copies of data known as shadow copies. Disabling this service will not impact any other Operations Manager 2007 functionality.

Server role installation issues (Sdk Service has not yet initialized),Or Please call ManagementGroup.Reconnect() to reestablish the connection, issues

CliveEastwood — Tue, 05 Feb 2008 22:55:54 GMT

I've come across a number of cases in the past where Opsmgr/SCE server role installation may fail, or even post installation processes such as report deployment can fail with no indication as to why. Some symptoms you may see which may indicate the need to install the hotfix detailed below are:

Installing an Opsmgr/SCE server roll results in an MSI installation failure and subsequent rollback with the error "The setup wizard was interrupted before System Center Operations Manager 2007 could be installed."
Then clicking the Finish button pops up an error dialogue the says "The setup failed. Do you want to open the setup log file (search for "value 3" in the file for locating failure)". Although this message can be displayed for a very wide variety of reasons, if you search the failed MSI log for " Sdk Service has not yet initialized. Please retry" and get a hit with a stack trace similar to below, it's quite likely this is your problem.

AssociateSecureRefsForADWriterAndAlertSubscriptionModules: Error: Sdk Service has not yet initialized. Please retry,
Stack:    at Microsoft.EnterpriseManagement.DataAbstractionLayer.SdkDataAbstractionLayer.HandleIndigoExceptions(Exception ex)
   at Microsoft.EnterpriseManagement.DataAbstractionLayer.SdkDataAbstractionLayer.CreateChannel(TieredManagementGroupConnectionSettings managementGroupTier)
   at Microsoft.EnterpriseManagement.DataAbstractionLayer.SdkDataAbstractionLayer..ctor(DuplexChannelFactory`1 channelFactory, TieredManagementGroupConnectionSettings managementGroupTier, IClientDataAccess callback, CacheMode cacheMode)
   at Microsoft.EnterpriseManagement.DataAbstractionLayer.SdkDataAbstractionLayer.CreateEndpoint(ManagementGroupConnectionSettings connectionSettings, IClientDataAccess clientCallback)
   at Microsoft.EnterpriseManagement.DataAbstractionLayer.SdkDataAbstractionLayer.Connect(ManagementGroupConnectionSettings connectionSettings)
   at Microsoft.EnterpriseManagement.ManagementGroup..ctor(ManagementGroupConnectionSettings connectionSettings)
   at Microsoft.EnterpriseManagement.ManagementGroup.Connect(ManagementGroupConnectionSettings connectionSettings)
   at Microsoft.MOMv3.Setup.MOMv3ManagedCAs.AssociateSecureRefsForADWriterAndAlertSubscriptionModules(Session session)

Another possible post server roll installation problem which you may see is instances of "Please call ManagementGroup.Reconnect() to reestablish the connection" in events (opsmgr event log) or alerts, such as the following:

Report deployment process failed to request management pack list from SQL RS Server. The operation will be retried. Exception 'ServerDisconnectedException': The client has been disconnected from the server. Please call ManagementGroup.Reconnect() to reestablish the connection. One or more workflows were affected by this. Workflow name: Microsoft.SystemCenter.DataWarehouse.Deployment.Report

If you do see symptoms such as those described above, installation of the following Windows Server 2003 SP1 & SP2 hotfix may well solve the issue : http://support.microsoft.com/default.aspx/kb/931319/ (Error code when you run a network program that uses a Winsock connection on a computer that is running Windows Server 2003: "WSAECONNABORTED (10053)"). Details of how to obtain the hotfix are discussed in the article.

A KB article for OpsMGr/SCE will be available shortly. If I discover any more symptoms I'll be sure to include them.

Operations Manager 2007 Service Pack 1 Training Videos released to the TechNet TechCenter

CliveEastwood — Thu, 10 Jan 2008 02:46:42 GMT

The following series of training videos on some of the aspects of Opsmgr SP1 (Currently in Release Candidate stage of release) have been released to the Operations Manager TechNet TechCenter (http://technet.microsoft.com/en-us/opsmgr/bb986763.aspx)

Please be aware that some information in these presentations will not be applicable to the original release product and is specific to new or improved functionality in the Service Pack 1 release. For more information on the Service Pack 1 release visit http://www.microsoft.com/systemcenter/opsmgr/default.mspx or http://connect.microsoft.com/SystemCenter/content/content.aspx?ContentID=6859

Web page view type
Presenter: Scott Jackson, Microsoft
This video demonstrates using the new web page view type.
Running Time (minutes): 0:43
Date Posted: January 10, 2008
Web Console State View
Presenter: Scott Jackson, Microsoft
This video demonstrates parity between the web console and the Operations Manager console.
Running Time (minutes): 0:36
Date Posted: January 10, 2008
Change Agentless Proxy Agent
Presenter: Scott Jackson, Microsoft
This video demonstrates how to change the proxy agent for agentless managed computers.
Running Time (minutes): 0:34
Date Posted: January 10, 2008
Monitoring space performance enhancements
Presenter: Scott Jackson, Microsoft
This video demonstrates improved responsiveness of list-based views in the Monitoring space.
Running Time (minutes): 1:13
Date Posted: January 10, 2008
Targeting a monitor at a group
Presenter: Scott Jackson, Microsoft
This video demonstrates how to correctly target a monitor at a group.
Running Time (minutes): 1:19
Date Posted: January 10, 2008
Using the Microsoft Generic Report Library
Presenter: Eugene Bykov, Microsoft
This video demonstrates generic overrides report.
Running Time (minutes): 6:16
Date Posted: January 10, 2008
Using favorite reports and the report publishing feature
Presenter: Eugene Bykov, Microsoft
This video demonstrates favorite reports and report publishing features.
Running Time (minutes): 6:44
Date Posted: January 10, 2008
Using Reset or Recalculate on monitors
Presenter: Marius Sutara, Microsoft
This video demonstrates how to use tasks to reset or recalculate the state of a monitor.
Running Time (minutes): 7:59
Date Posted: January 10, 2008
Targeting Monitors
Presenter: Boris Yanushpolsky, Microsoft
This video demonstrates how to properly configure rules and monitors for multi-instance components.
Running Time (minutes): 3:53
Date Posted: January 10, 2008

List of Operations manager Cluster configurations supported

CliveEastwood — Sat, 01 Dec 2007 01:56:26 GMT

As an aid to clearing up some of the confusion around supported Cluster configurations the Product Group posted a list of supported and unsupported configurations here http://blogs.technet.com/momteam/archive/2007/11/30/supported-cluster-configurations-for-opsmgr-2007.aspx

Remote Agent PreReq check tool for OpsMgr07

CliveEastwood — Tue, 20 Nov 2007 20:14:26 GMT

The Operations Manager team have released a command line tool similar to the GUI tool within the MOM 2005 reskit for Operations Manager 2007. Check out the details and download here http://blogs.technet.com/momteam/archive/2007/11/20/remote-agent-prerequisite-checker-tool-for-opsmgr-2007.aspx

This MOMNetChkCMd.exe tool requires .Net Framework 2.0 but can be run independently of a Management Server.

The tool checks requirements for Agent push such as required discovery info via WMI, MSXML 6 requirement, Ports 445,139,137,135,5723 enabled, Windows Installer Service started, Remote Registry enabled, responds to ICMP ping.

Invoking MOMNetChkCMd.exe -Computername <nameofcomputer>

will perform a check against a single remote computer logging details to a .log file of the same name as the machine. The log header will contain a summary of the number of Errors, Warnings and Successes followed by details of each of the test performed and the results.

To be able to perform the check against large numbers of machines before agent deployment a text file and batch file are included. The text file to contain the list of computer NetBIOS names, and the batch file to read the list and call MOMNetChkCMd.exe against each. The log files can then be scanned for Errors as discussed in the Readme.txt file.

Exchange 2007 MP Release notes now available

CliveEastwood — Fri, 12 Oct 2007 22:35:13 GMT

The release notes for the Exchange MP have been released to the Web and are available via http://go.microsoft.com/fwlink/?LinkId=96219

Some Notification properties that may prove useful

CliveEastwood — Fri, 12 Oct 2007 22:31:00 GMT

These will end up being published in a KB article shortly. But since I have them, they are worth publishing here.

In addition to the notification properties you are able to add via Settings,Notification from the Administration space for Global notification settings or via the custom formats within your subscription, the list below list some other currently undocumented properties that may prove useful.

Excel sheet with the details below is also available to download here http://home.comcast.net/~the_eastwoods/MOMDownloads\NotificationProps.zip

$Data/Context/DataItem/AlertId$                                         The AlertID GUID
$Data/Context/DataItem/AlertName$                                   The Alert Name
$Data/Context/DataItem/Category$                                    The Alert category PerformanceHealth,PerformanceCollection,Operations,EventCollection,StateCollection,SoftwareAndUpdates,Alert,System,Custom,AvailabilityHealth,ConfigurationHealth,SecurityHealth,Discovery,NotificationCategory,Maintenance
$Data/Context/DataItem/CreatedByMonitor$                     True/False
$Data/Context/DataItem/Custom1$                                    CustomField1
$Data/Context/DataItem/Custom2$                                    CustomField2
$Data/Context/DataItem/Custom3$                                    CustomField3
$Data/Context/DataItem/Custom4$                                    CustomField4
$Data/Context/DataItem/Custom5$                                    CustomField5
$Data/Context/DataItem/Custom6$                                     CustomField6
$Data/Context/DataItem/Custom7$                                     CustomField7
$Data/Context/DataItem/Custom8$                                     CustomField8
$Data/Context/DataItem/Custom9$                                     CustomField9
$Data/Context/DataItem/Custom10$                                  CustomField10
$Data/Context/DataItem/DataItemCreateTime$                          UTC Date/Time of Dataitem created
$Data/Context/DataItem/DataItemCreateTimeLocal$                  LocalTime Date/Time of Dataitem created
$Data/Context/DataItem/LastModified$                                   UTC Date/Time DataItem was modified
$Data/Context/DataItem/LastModifiedLocal$                               Local Date/Time DataItem was modified
$Data/Context/DataItem/ManagedEntity$                                  ManagedEntity GUID
$Data/Context/DataItem/ManagedEntityDisplayName$                ManagedEntity Display name
$Data/Context/DataItem/ManagedEntityFullName$                     ManagedEntity Full name
$Data/Context/DataItem/ManagedEntityPath$                            Managed Entity Path
$Data/Context/DataItem/Priority$                                               The Alert Priority Number (High=1,Medium=2,Low=3)
$Data/Context/DataItem/Owner$                                                 The Alert Owner
$Data/Context/DataItem/RepeatCount$                                       The Alert Repeat Count
$Data/Context/DataItem/ResolutionState$                                   Resolution state ID (0=New, 255= Closed)
$Data/Context/DataItem/ResolutionStateLastModified$                        UTC Date/Time ResolutionState was last modified
$Data/Context/DataItem/ResolutionStateLastModifiedLocal$                Local Date/Time ResolutionState was last modified
$Data/Context/DataItem/ResolutionStateName$                                   The Resolution State Name (New, Closed)
$Data/Context/DataItem/ResolvedBy$                                   Person resolving the alert
$Data/Context/DataItem/Severity$                                       The Alert Severity ID
$Data/Context/DataItem/TicketId$                                        The TicketID
$Data/Context/DataItem/TimeAdded$                                  UTC Time Added
$Data/Context/DataItem/TimeAddedLocal$                           Local Time Added
$Data/Context/DataItem/TimeRaised$                                  UTC Time Raised
$Data/Context/DataItem/TimeRaisedLocal$                            Local Time Raised
$Data/Context/DataItem/TimeResolved$                                UTC Date/Time the Alert was resolved
$Data/Context/DataItem/WorkflowId$                                    The Workflow ID (GUID)
$Target/Property[Type="Notification!Microsoft.SystemCenter.AlertNotificationSubscriptionServer"/WebConsoleUrl$                                                  The Web Console URL
Target/Property[Type="Notification!Microsoft.SystemCenter.AlertNotificationSubscriptionServer"/PrincipalName$                                                     The principalname of the management server
$Data/Recipients/To/Address/Address$                                                                                                        The name of the recipient (e.g. the Email alias to which the notification is addressed)

System Center Essentials post RTM Hotfix Rollup released to the Web

CliveEastwood — Sat, 29 Sep 2007 01:14:00 GMT

In an aid to specifically resolve the issue http://support.microsoft.com/kb/936481/en-us (The installation of System Center Essentials 2007 fails during the Reporting part of Setup and the following information is logged: "The specified domain does not exist or cannot be contacted") in which the whole installation of System Center Essentials 2007 will roll back (fail), and to allow address several other top issues (see below), a hotfix rollup package has been released and is available here http://www.microsoft.com/downloads/details.aspx?FamilyID=c9f977e4-d26f-4038-88b7-b70b13aa8e3d&DisplayLang=en

What specifically this rollup package fixes:

936481 You cannot install the System Center Operations Manager 2007 Reporting feature in a disjointed namespace environment
936339 Windows-based computers are not displayed in the Network Topology diagram view in System Center Essentials 2007, and WSUS component parts fail on the Essentials 2007 agents after you deploy the agents
937467 Update files not getting downloaded to the Essentials 2007 server when importing updates from a partner catalog

More information on the rollup package will be available shortly in the form of a KB article which, when available (I'll post an update here), will be on http://support.microsoft.com/943111/en-us

Does the hotfix rollup apply to you?

If you already have Essentials installed this hotfix rollup does not apply to you.

If you already have Essentials installed and you experience the symptoms referred to in KB936339 or KB937467 please refer to those KB articles on how to obtain the hotfixes separately so that you can apply them in your environment.

If you currently don't have Essentials installed and believe you will be affected by symptoms referred to in KB936481, KB936339 or KB937467 then this rollup package can certainly help you.

Also for those users registering to download the 90-day evaluation version here http://technet.microsoft.com/en-us/bb738028.aspx , the English downloads (aka US English) include a download of the rollup.

Can this hotfix rollup be applied to a SCE localized version?

Yes it can. However, you will have to download the rollup package from http://www.microsoft.com/downloads/details.aspx?FamilyID=c9f977e4-d26f-4038-88b7-b70b13aa8e3d&DisplayLang=en if you intend using the 90-day trial version and my be affected. The hotfix rollup UI is also not supplied in a localized version.

How do I install the System Center Essentials 2007 Hotfix Rollup?

Firstly, as mentioned this applies to a fresh install of SCE. If you have SCE installed don't continue from here unless you plan on installing another SCE environment in a situation where you will need this rollup.

Requirements:

Have a copy of the original source SCE media available to you on the proposed SCE Management server computer (best to map a drive to a network resource where it is located or have it available on DVD. Do not have it located on a local hard drive which will be the same drive the rollup package will create a patched version to.)
Have a copy of the SCE hotfix rollup package available locally on the proposed SCE Management server computer.

What does the hotfix rollup do?

The hotfix rollup package SCE2007RTMHotfixRollup.exe when executed will unpack its hotfix payload to a folder beneath the current users Temp folder and then present the following UI.

When using the Browse buttons make sure you select a source and destination which are different drives. The utility will not allow the source and destination hard drive for example to contain C:.

The "Select Essentials 2007 RTM media location" is a mapped network drive or local DVD media location (or a local hard drive which will not be the same as the "Select local directory.... option"

The "Select local directory to copy Essentials RTM media" is a local hard drive directory (empty) where the entire source media will be copied. When "Apply QFEs and start setup" button is clicked the source folder and file structure is copied to the destination folder and then the first of the hotfixes KB936481is applied to the destination (required because this is a patch to the reporting msi in order to install SCE in a disjointed DNS namespace). System Center Essentials 2007 Setup is then executed and you can begin the installation of SCE. During the installation the other two hotfixes will be applied automatically by the Setup infrastructure.

Once installation has completed successfully the directory chosen as "Select local directory to copy Essentials RTM media" can be removed.

Can I use the new media folder created as a result of the rollup package be used to install other SCE servers?

Yes, and No :)

If the destination folder is copied to DVD, network, etc for use in installing other SCE servers, note that only the hotfix for KB936481 will apply when installing using the updated media (ie. you can install in a disjlointed DNS namespace). Due to the way the other hotfixes are applied during Setup if you need them installed at install time run the hotfix rollup on the indended Management server itself. You can of course install the other two hotfixes after install (you can obtain them separately, or on the machine that SCE2007RTMHotfixRollup.exe was run the installing users %TEMP%\IXP0000.TMP folder will contain the MSI's).

System Center Operations Manager 2007 Resource Kit tools released to the download center

CliveEastwood — Thu, 13 Sep 2007 02:40:59 GMT

The first set of resource kit tools for Operations Manager 2007 have been released to the download center. They will be soon referenced from the TechNet TechCenter for OpsMgr too (http://technet.microsoft.com/en-us/opsmgr/default.aspx)

All tools are subject to the license agreement published here http://technet.microsoft.com/en-us/opsmgr/bb743255.aspx. (awaiting publication last time I tried)

Here's the first line-up (8 in all):

1) Sample Vista Gadget (http://www.microsoft.com/downloads/details.aspx?FamilyID=0f5a060b-635d-4355-b0ac-32ee2943bfd9&DisplayLang=en)

A Vista Gadget that enables you to view the active alerts and health states for a specified set of objects from a computer running Windows Vista.

1. Allows selection of object types.
2. Displays alert counts for each severity level.
3. Color-coded alert levels.
4. Color-coded summary of health states.

2) Operations Manager Inventory (http://www.microsoft.com/downloads/details.aspx?FamilyID=10e79763-6906-4f44-86c6-fbabb0bf1b9f&DisplayLang=en)

A command-line utility that captures the configuration of your Operations Manager 2007 Management Servers and stores it in a .cab file that can be sent to Microsoft support to assist in problem analysis.

Feature Bullet Summary
1. Collects Windows Installer data for Ops Mgr installation.
2. Collects file information for Ops Mgr files.
3. Collects registry settings information for Ops Mgr installation.
4. Collects Ops Mgr server configuration data.
5. Collects data regarding running processes on Ops Mgr servers.
6. Collects Ops Mgr install logs.
7. Collects Windows event logs.

3) Operations Manager Cleanup Tool (http://www.microsoft.com/downloads/details.aspx?FamilyID=14ff7073-c71b-4ad0-805a-a8e458d2c9e0&DisplayLang=en)

A command-line utility that enables you to remove any or all of the components of Operations Manager from a local computer in cases where the normal method of uninstallation has failed.

1. Fast command line removal of agents.
2. Fast command line removal of server roles.
3. Removal of services associated with Ops Mgr.
4. Removal of registry keys.
5. Removal of Ops Mgr install directories and files.

4) AEM Validation (http://www.microsoft.com/downloads/details.aspx?FamilyID=db979eb5-b423-4b14-8664-b16dc8157e8d&DisplayLang=en)

A command line utility that will allow you to perform end-to-end validation of Agent-less Exception Monitoring to verify that AEM is properly configured and operational.

Feature Bullet Summary
1. Generates a test exception.
2. Allows end-to-end validation of AEM functionality.

5) AEM Management Pack (http://www.microsoft.com/downloads/details.aspx?FamilyID=6f0ba772-8521-4717-ab54-80ecd1f75aec&DisplayLang=en)

A Management Pack that enables you to identify generic errors sent by Windows Error Reporting (WER) clients to Management Servers that are AEM-enabled. Without this mapping function these errors appear in Operations Manager as "unknown application" and "unknown version".

1. Identifies application associated with generic exceptions.
2. Provides application version information for generic application exceptions.
3. Facilitates more precise application exception reporting.

6) Active Directory Integration Sample Script (http://www.microsoft.com/downloads/details.aspx?FamilyID=b3aa2d5a-b56c-40e8-8b63-139865a1749b&DisplayLang=en)

A sample script that enables you to extract a list of computer names from your custom SQL Server database and add them to an Active Directory security group. The security group can then be referenced in the Agent Assignment and Failover Wizard to automate agent assignments to Management Servers.

1. Queries customer SQL asset database.
2. Populates custom security group with computer accounts of computers returned by the SQL query.

7) Effective Configuration Viewer (http://www.microsoft.com/downloads/details.aspx?FamilyID=a9db4dca-6716-478d-89b9-42f27ebc76a8&DisplayLang=en)

A tool that displays the set of rules and monitors that are running on a computer, distributed application, or any other managed entity after any configured overrides have been applied.

Feature Bullet Summary
1. View effective monitoring of a managed object after overrides are applied.
2. View monitors and current state

8) Action Account Tool (http://www.microsoft.com/downloads/details.aspx?FamilyID=1d9a8d81-0e42-4076-88a9-8e6c08993054&DisplayLang=en)

A PowerShell script that allows you to set the action account on groups of computers.

Feature Bullet Summary
Modify action account settings for groups of computers with a single command.