Windows Server Operating System Management Pack for Operations Manager 2007

The Windows Server Operating System management pack provides the fundamental monitoring basics for computers running the Windows 2000 Server and Windows Server 2003, 2003 R2, 2008 and 2008 R2 Operating System.

Quick details
Version : 6.0.6794.0

Files in this download

The links in this section correspond to files available for this download. Download the files appropriate for you.

File Name	Size
OM2007_MP_WinSerBas.doc	390 KB	Download
Windows Server Base OS System Center Operations Manager 2007 MP.MSI	1.0 MB	Download

Overview

The Windows Server Operating System management pack consists of the following five management packs: Microsoft Windows Server Library, Microsoft Windows Server 2008 Discovery, Microsoft Windows Server 2008 Monitoring, Microsoft Windows Server 2003, and Microsoft Windows 2000 Server. The Microsoft Windows Server management packs monitor the performance, health, and availability of Windows Server 2008, 2008 R2, 2003, 2003 R2 and Windows 2000 Server.

By detecting, alerting on, and automatically responding to critical events and performance indicators, these management packs reduce resolution times for issues and increase the overall availability and performance of your systems running the Windows Server operating systems, thereby helping to reduce the total cost of ownership.

Feature Summary

• Availability
• Key Operating System Services: Required services are checked for status (for example, running, not running, or paused)
• Storage: Logical hard drives are checked for availability, sufficient free space, and integrity of the NTFS partition.
• Network: Network adapters are checked for connection health, name and IP address conflicts.
• Performance
• Processor: System processor(s) performance is checked system-wide. Processors can optionally be monitored on a per processor basis.
• Memory: Memory consisting of physical memory and virtual memory (also known as page files) is monitored using the following performance indicators:
• Available memory (in MB)
• Pages per second
• Page file percent usage
• Disks and Partitions: Logical disks/partitions and physical disks are monitored, and performance data is collected for average disk seconds per read, disk seconds per write, and disk seconds per transfer. Monitoring is also provided for fragmentation of logical disks. Depending on which version of the operating system is being monitored, either logical or physical monitoring is enabled by default. Refer to the MP guide for more detail.
• • Network Adapter: Network adapters are monitored for the number of bytes received per second, the number of bytes sent per second, and the total bytes per second. In addition, the health state of the network adapter is evaluated and is set to Healthy if connected and Critical if disconnected.

Management Pack Release History:

• 3/23/2007 - Initial Release, version 6.0.5000.0
• 9/28/2007 - Updated release, version 6.0.5000.25
• 10/23/2007 - Updated MP Guide - Software Version still 6.0.5000.25
• 11/8/2007 - Updated MP Guide - Software version still 6.0.5000.25
• 1/15/2008 - Updated MP Guide - same version
• 2/22/2008 - Updated release, version 6.0.6278.0, and released on SP1 media
• 5/27/2008 – Same version as released on SP1 media, version 6.0.6278.0, and released on Microsoft Download Center.
• 7/27/2008 - Updated version, 6.0.6278.22: Introduced support for the Windows Server 2008 Operating System and addressed some issues from the previous release. Refer to the MP guide for further details.
• 10/20/2008 – Updated release, version 6.0.6321.35. Refer to the MP guide for further details.
• 9/18/2009 - Updated release, version 6.0.6667.0, introduced support for the Windows Server 2008 R2 Operating System and made a series of updates. Refer to the MP guide for further details.
• 3/19/2010 - Updated release, version 6.0.6794.0, to resolve an issue with discoveries failing to query the Win32_PowerPlan WMI class.

System requirements

Supported Operating Systems: Windows 2000 Server, Windows Server 2003, Windows Server 2008, Windows Server 2008 R2

• Other Requirements: All management packs (MPs) included in this download are supported on System Center Operations Manager (OpsMgr) with Service Pack (SP) 1 and later.
  
  The following should be considered when importing the management packs into a management group which does not have OpsMgr SP1 installed:
  
  • The Library, Windows 2000 Server and Windows Server 2003 specific management packs can be imported into a management group that does not have OpsMgr 2007 SP1.
  • The Windows Server 2008 specific management packs are not supported, and will not import, into a management that does not have OpsMgr 2007 Service Pack 1 installed. This is due to the fact that monitoring of Windows Server 2008 is not supported without Service Pack 1.
  
  The Windows Server Operating System Management Pack for Operations Manager 2007 is designed to monitor the following versions of the base Operating System:
  
  • Microsoft Windows Server 2008
  • Microsoft Windows Server 2008 R2
  • Microsoft Windows Server 2003
  • Microsoft Windows Server 2003 R2
  • Microsoft Windows 2000 Server
  
  
• NOTE: You need to install the English MP before you import localized language packs.
All support is subject to Microsoft’s overall support lifecycle (http://go.microsoft.com/fwlink/?Linkid=26134) and the Operations Manager 2007 SP1 Supported Configurations (http://go.microsoft.com/fwlink/?Linkid=90676) document.

Windows Server Internet Information Services 7 Management Pack for System Center Operations Manager 2007

The Internet Information Services Management Pack provides proactive and reactive monitoring of your Internet Information Services (IIS) environment.

Quick details
Version : 6.0.7600.0

Files in this download

The links in this section correspond to files available for this download. Download the files appropriate for you.

File Name	Size
IIS 7 Management Pack Guide.doc	514 KB	Download
Internet Information Services MP.msi	873 KB	Download
OM2007_MP_IIS.doc	323 KB	Download

Overview

This management pack provides an early warning to administrators on issues that could affect services so that administrators can investigate and take corrective action, if necessary. The management pack helps to simplify the administrative environment by providing a single console for the administrator to perform a number of useful management tasks. To help troubleshoot common issues, the management pack contains helpful product knowledge and a way to extend this knowledge through adding your own company or organization knowledge related to an issue.

Note: For System Center Operations Manager 2007 SP1 environment, hotfix K971541 or later is required in order to manage IIS 7 by using this management pack.

Feature Summary:
The IIS MP provides monitoring of the following objects:

• Web Sites
• Application Pools
• FTP Servers
• NNTP Servers
• SMTP Servers

Management Pack Release History:

• 3/23/2007 - Initial release, version 6.0.5000.0
• 1/15/2008 - Updated Guide, same version
• 2/22/2008 - Updated release, version 6.0.6278.0, released on SP1 media
• 5/27/2008 - Same version release, version 6.0.6278.0, released on Microsoft Download Center
• 2/23/2009 - Updated the IIS management pack to support monitoring Windows Server 2008, version 6.0.6539.0
• 2/8/2010 - Updated IIS managment pack to support monitoring Windows Server 2008 SP2 and Windows Server 2008 R2, version 6.0.7600.0
• 4/27/2011 - Updated management pack guide

System requirements

Supported Operating Systems: Windows 2000 Server, Windows Server 2003, Windows Server 2003 R2 Standard Edition (32-bit x86), Windows Server 2003 R2 Standard x64 Edition , Windows Server 2008, Windows Server 2008 R2, Windows Server 2008 Service Pack 2

• Other Software: System Center Operations Manager 2007

Note: For System Center Operations Manager 2007 SP1 environment, hotfix K971541 or later is required in order to manage IIS 7 by using this management pack.

All management packs (MPs) included in this download are supported on System Center Operations Manager (OpsMgr) with Service Pack (SP) 1 and higher. The Windows Server 2008 specific management packs require that portions of the Windows Microsoft Windows Server Operating System Management Pack be imported as well. If the necessary MP’s are not present in the management group at the time of import then the import wizard will indicate which MPs are required. A link to download the Microsoft Windows Server Operating System Management Pack is available on the System Center Operations Manager 2007 Catalog (http://www.microsoft.com/technet/prodtechnol/scp/opsmgr07.aspx) .

Exchange Server 2010 Monitoring Management Pack

This management pack includes scripts and rules to effectively monitor Exchange 2010 and report on performance, availability, and reliability of its server roles.

Quick details

Version:

14.02.0071.0

Date Published:

4/6/2011

Files in this download

The links in this section correspond to files available for this download. Download the files appropriate for you.

File Name	Size
Exchange Server 2010 Management Pack Guide.doc	1.0 MB	DOWNLOAD
Exchange2010ManagementPackForOpsMgr2007-EN-i386.msi	6.0 MB	DOWNLOAD
Exchange2010ManagementPackForOpsMgr2007-EN-x64.msi	6.0 MB	DOWNLOAD

Overview

The Microsoft Exchange Server 2010 monitoring management pack is designed to be used for monitoring Exchange 2010 events, collecting Exchange component-specific performance counters in one central location, and for raising alerts for operator intervention as necessary. By detecting, sending alerts, and automatically correlating critical events, this management pack helps indicate, correct, and prevent possible service outages or configuration problems, allowing you to proactively manage Exchange servers and identify issues before they become critical. The management pack monitors and provides alerts for automatic notification of events indicating service outages, performance degradation, and health monitoring.

Feature SummaryThe Exchange Server 2010 Monitoring Management Pack includes rules and scripts to monitor and report on performance, availability, and reliability of all Exchange 2010 server roles including. 

• Mailbox Server Role
• Client Access Server Role
• Hub Transport Server Role
• Edge Transport Server Role
• Unified Messaging Server Role

Release History

• 4/6/2011 - Updated release, version 14.02.0071.0
• 11/9/2009 - Original release of the English version and language packs, version 14.0.650.7.

System requirements

Supported Operating Systems: Windows Server 2003 x64 editions, Windows Server 2008

• Other Software: System Center Operations Manager 2007 or later.

Instructions

To use the English version of the Exchange Server 2010 Monitoring Management Pack, you only need to download and install the English (EN) version of the Exchange Server 2010 SP1 Management Pack. The English version of the management pack includes the Exchange Server 2010 SP1 Management Pack application and the required files to use the management pack in English.

If you want to use a localized version of the management pack, you must first download and install the English version of the management pack. Then, you must download and install the language pack for your respective language. The English version of the management pack includes the Exchange Server 2010 Service Pack 1 Management Pack application that is a prerequisite for all localized versions of the management pack.

For detailed information about installing and using this management pack, download and read the Exchange Server 2010 Service Pack 1 Management Pack Guide. That guide is available for download on this Web page.

Changes in This Update:

The Exchange 2010 SP1 version of the Exchange 2010 Management Pack includes significant improvements beyond those included in the RTM version of the Exchange 2010 Management Pack. The following list includes some of the new features and updates:
· Capacity planning and performance reports   New reports dig deep into the performance of individual servers and provide detailed information about how much capacity is used in each site.
· SMTP and remote PowerShell availability report   The management pack now includes two new availability reports for SMTP client connections and management end points.
· New Test-SMTPConnectivity synthetic transaction   In addition to the inbound mail connectivity tasks for protocols such as Outlook Web App, Outlook, IMAP, POP, and Exchange ActiveSync, the Management Pack now includes SMTP-connectivity monitoring for outbound mail from IMAP and POP clients. For information about how to enable this feature, see Optional Configurations.
· New Test-ECPConnectivity view   Views for the Exchange Control Panel test task are now included in the monitoring tree.
· Cross-premises mail flow monitoring and reporting   The Management Pack includes new mail flow monitoring and reporting capabilities for customers who use our hosted service.
· Improved Content Indexing and Mailbox Disk Space monitoring   New scripts have been created to better monitor context indexing and mailbox disk space. These new scripts enable automatic repair of indexes and more accurately report of disk space issues.
· The ability to disable Automatic Alert Resolution in environments that include OpsMgr connectors   When you disable Automatic Alert Resolution, the Correlation Engine won't automatically resolve alerts. This lets you use your support ticketing system to manage your environment. For information about how to disable this feature, seeOptional Configurations.
· Several other updates and improvements were also added to this version of the Management Pack, including the following.
· Suppression of alerts when the alerts only occur occasionally was added to many monitors.
· Most of the event monitors in the Exchange 2010 Management Pack are automatically reset by the Correlation Engine. Automatic reset was added to those event monitors so that issues aren't missed the next time they occur. For a list of the event monitors that are not reset automatically, see Understanding Alert Correlation.
· Monitoring was added for processes that crash repeatedly.
· Additional performance monitoring was added for Outlook Web App.
· Monitoring of Active Directory access was improved.
· Monitoring of anonymous calendar sharing was added.
· Reliability of database offline alerts was improved.
· Monitoring for the database engine (ESE) was added.


Installation Notes:

• When you install the MSI download – this is not like all our other MP’s.  This MSI actually installs the Exchange Correlation engine with no prompts or warnings.  Keep that in mind… so it is best to extract/install this MSI where you want the correlation engine to be installed!
• My first attempts to install this on my RMS kept failing.  The problem was UAC…. this MSI doesn’t seem to invoke UAC…. so you get an “installation was interrupted” error when you try to install it.  When I opened a CMD prompt as an Administrator (elevated) and then called the MSI – it installed just fine. 
• When you install the MP/Correlation engine – you may get an error that the correlation files cannot be updated, and a restart will be required.  Even if you stop the correlation engine service – you will be prompted for a reboot.  Therefore – plan for this update to require an outage/downtime of your RMS for a reboot (or wherever the server hosting the Exchange Correlation engine is located)

How to monitor SQL Agent jobs using the SQL Management Pack and OpsMgr

When you use Operations Manager to monitor your SQL servers using the SQL Server Management Pack, there are some options that you will need to think about up front.   
One of those areas is the SQL Agent, and SQL Agent jobs.



I will cover three conceptual areas:

• Out of the box experience and defaults
• SQL Agent only monitoring (monitoring all jobs at the agent level)
• SQL Agent Job monitoring (optionally discovering and monitoring agent jobs on an individual level)

Out of the box, we don’t discover or monitor individual SQL agent jobs by default.  What we do is discover the SQL Agent object: 

By default – all we are monitoring with regard to the SQL Agent, is the SQL Agent service availability:


Keep in mind – on SQL clusters, we don’t monitor manual services by default.  The assumption is that if the service is clustered, and is down, the cluster MP will alert that a clustered resource is partially offline.  This keeps from having duplicate alerts about the same service availability issue.  However, if you WANT the SQL MP to alert when a clustered SQL Agent service is down – you will need to override this monitor:


There are also several rules that target the “SQL Agent” object, that primarily look in the Application event log for issues/errors related to the SQL Agent:

Notice that the “An SQL job failed to complete successfully” is disabled out of the box.   This was done to reduce out of the box noise…. as many customers have terribly monitored/maintained SQL environments and have so many jobs failing that this was almost un-actionable.  If you want to be alerted to ANY sql agent job failure of any kind – then you might consider enabling this rule via override.  I would recommend this if you aren't going to discover and monitor individual SQL agent jobs (covered later in this article)

Lastly – at the SQL Agent level – there is a monitor for alerting when SQL Agent jobs run too long.  To reduce noise, this is also disabled out of the box.

If you want to monitor ALL jobs run under a specific SQL Agent with the same thresholds, you should consider enabling and adjusting this monitor.  By default – the warning threshold is 60 minutes, and critical is 120 minutes.  If you want to be able to control and override individual agent jobs that need longer run-times than others, leave this disabled and configure the SQL MP to discover and monitor individual SQL agent jobs (covered later in this article) Ok – that covers the out of the box defaults, and SQL Agent only monitoring.  Now, what if I need to go deeper, and have the ability to override settings for individual SQL Agent jobs?  You will notice that in the view for SQL Agent Job State – there are no objects:

This is by design, because we don’t discover SQL Agent jobs individually out of the box.  Perhaps I have some SQL Agent jobs that I don’t want to monitor at all, and others have especially long run-times that need unique thresholds (like SQL backups or maintenance on VERY large DB’s?)  In this case – we will want to enable the discovery to discover SQL Agent jobs as discovered objects.
To enable the object discovery, go to Authoring Pane, select Object Discoveries.  In the upper right corner, select Change Scope, and clear everything, selecting on “SQL 2008 Agent Job” and “SQL Server 2005 Agent Job”:

These are disabled by default.  Create an override for each, “For all objects of class" and set Enabled = true.  Save these overrides to your custom “SQL Overrides” management pack.
This discovery runs every 4 hours by default, so within 4 hours you should see your SQL Agent job state view populated with your individual SQL Agent jobs.  (**Hint – to speed this process up, bounce the System Center Management service on your agents – as this will force a discovery to run on service startup)


Now – lets talk about what we monitor by default for discovered SQL Agent jobs.  There are a total of two monitors.  Last Run Status, and Job Duration:


“Last Run Status” monitor checks every 10 minutes, and will remain Yellow (Warning state) for any job whose last run was not a success.  This gives you a nice “real time” view of the unhealthy jobs that need some attention.
“Job Duration” monitor runs every 10 minutes, and looks for jobs that have exceeded a run-time threshold.  The default is 60 minutes (warning) and 120 minutes (critical).  This monitor also does not generate alerts by default.  If you want this monitor to generate alerts you must override that setting.
In the following example – I am creating an override for my SQL agent job that performs full backups, setting the thresholds higher and enabling alerting….. and saving it to my SQL Overrides management pack:



As you can see, this gives you SQL Agent job by job granularity.
You could easily also create groups of SQL agent jobs based on group name…. if you wanted to treat all jobs with the same or similar names the same from an override perspective.  This will additionally ease the burden of maintaining overrides using a dynamic group based on criteria of the job:



Kevin Holman

System Center Operations Manager 2007 R2 Cross Platform Monitoring Management Packs

The System Center Operations Manager 2007 R2 Cross Platform Monitoring Management Packs enable discovering, monitoring, and managing UNIX-based and Linux-based computers by using the same interface and tools that you use to manage your Windows-based computers.

Download

OM2007xpMP_RedHat.docx

SCOM 2007 R2 Cross Platform MPs.msi

Overview

The System Center Operations Manager 2007 R2 Cross Platform Monitoring Management Packs enable discovering, monitoring, and managing UNIX-based and Linux-based computers by using the same interface and tools that you use to manage your Windows-based computers. They provide both proactive and reactive monitoring of the UNIX and Linux operating systems. The management packs monitor components such as processes, resources, and server agents. The monitoring provided by the management packs includes availability and configuration monitoring, performance data collection, and default thresholds. You can integrate the monitoring of UNIX and Linux components into your service-oriented monitoring scenarios. In addition to health monitoring capabilities, the management packs include reports, diagnostics, tasks, and views that enable near real-time diagnosis and resolution of detected issues. The management packs also enable the installation of the Cross Platform Audit Collection Services Management Packs.

Feature Summary

• Provides monitoring of the AIX 5.3 and 6.1 operating systems.
• Provides monitoring of the HP-UX 11iv2 PA-RISC, HP-UX 11iv2 IA64, HP-UX 11iv3 PA-RISC, and HP-UX 11iv3 IA64 operating systems.
• Provides monitoring of the Red Hat Enterprise Linux Server 4 (x64), Red Hat Enterprise Linux Server 5 (x64) and Red Hat Enterprise Linux Server 6 (x64) operating systems.
• Provides monitoring of Solaris 8, Solaris 9, and Solaris 10 operating systems.
• Provides monitoring of SUSE Linux Enterprise Server 9, SUSE Linux Enterprise Server 10 SP1, and SUSE Linux Enterprise Server 11 operating systems.
• Enables the installation of the Cross Platform Audit Collection Services Management Packs.

Release History

• 5/28/2009 - Original release of the English version, version 6.1.7000.256, with System Center Operations Manager 2007 R2
• 10/15/2009 - Updated release, version 6.1.7000.262, to support SUSE Linux Enterprise Server 11
• 12/17/2009 - Updated release, version 6.1.7000.269, enable the installation of the Cross Platform Audit Collection Service management pack
• 2/15/2010 - Updated release, version 6.1.7000.273, with bug fixes
• 10/1/2010 - Updated release, version 6.1.7000.277, with bug fixes
• 8/2/2011 - Updated release, version 6.1.7000.294 to support Red Hat Enterprise Linux Server 6

System requirements

Supported Operating Systems: Windows Server 2003, Windows Server 2008, Windows Vista, Windows XP

• Other Software: System Center Operations Manager 2007 R2

Instructions

1. Download and install Operations Manager Cross Platform Cumulative Update 5
2. Use the Operations Manager 2007 R2 Discovery Wizard to re-discover the UNIX and Linux computers and upgrade the agents on those computers.
3. Download the management packs to each computer that meets the following criteria:
   
   Hosts a Microsoft Operations Manager 2007 R2 Management Server
   or
   Hosts a Microsoft Operations Manager 2007 R2 Gateway Server
4. Import the management packs for all monitored server types.

Cumulative Update 5 for System Center Operations Manager 2007 R2 (KB 2495674)

Cumulative Update 5 contains a number of fixes for Operations Manager 2007 R2 and adds support for Red Hat 6. A number of fixes require manual steps to install. See Knowledgebase article KB 2495674

Download

File NameSizeSystemCenterOperationsManager2007-R2CU5-KB2495674-X86-X64-IA64-ENU.MSI

Overview

This update contains a collection of new fixes, as well as all of the fixes from System Center Operations Manager 2007 R2 CU4. A number of fixes require manual steps to install. See Knowledgebase article KB 2495674

System requirements

Supported Operating Systems: Windows Server 2008

• Other Software: System Center Operations Manager 2007 R2

Cumulative Update 5 for System Center Operations Manager 2007 R2 is available

Summary

This article contains a complete description of all changes that are contained in Cumulative Update 5 for Microsoft System Center Operations Manager 2007 R2.

Cumulative Update 5 for Operations Manager 2007 R2 includes all previous cumulative updates for Operations Manager 2007 R2 and includes all cross-platform updates.

To download Cumulative Update 5 for Operations Manager 2007 R2, visit the following Microsoft Download Center webpage:

Download Cumulative Update 5 for System Center Operations Manager 2007 R2

Cumulative Update 5 for Operations Manager 2007 R2 resolves the following issues:

• Restart of non-Operations Manager services when the agent is updated.
• Updated ACS reports.
• TCP Port Probe incorrectly reports negative ping latency.
• MissingEvent Manual Reset Monitor does not work as expected.
• Drillthrough fails because of rsParameterTypeMismatch in the EnterpriseManagementChartControl.
• ACS - Event log message is truncated or corrupted in SCDW.
• UI hang caused by SDK locking.
• ACS Filter fails for certain wildcard queries.
• Edit Schedule button is disabled with SQL 2008 R2.
• Web console times out when you open the left navigation tree.
• Scheduled Reports view for Windows Server 2003 and for Microsoft SQL Server 2005 Reporting Services SP3 CU9 returns "System.IndexOutOfRangeException: Index was outside the bounds of the array."
• Signed MPs cannot be imported when new attributes are added to existing classes.

Cross Platform Cumulative Update 5 for Operations Manager 2007 R2 resolves the following issues:

• Performance data for LVM managed partitions is not available.
• Process monitor does not keep name if run by using symbolic link.
• AIX with large number of processes crashes with bad alloc.

Cross Platform Cumulative Update 5 for Operations Manager 2007 R2 adds the following feature:

• Support for Red Hat 6

Note The new agent for Red Hat 6 is included in Cumulative Update 5. You can download the management pack for Red Hat 6 by visiting the following Microsoft website:

System Center Operations Manager 2007 R2 Cross Platform Monitoring Management Packs

More Information

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require you to reinstall the operating system. Microsoft cannot guarantee that these problems can be resolved. Modify the registry at your own risk.

SQL Server 2008 R2 database upgrade support

The feature for SQL Server 2008 database update support lets you upgrade a database for Operations Manager 2007 R2 to SQL Server 2008 R2. The tools for this feature are in the SupportTools folder of the update package. For more information about how to upgrade SQL Server 2005 to SQL Server 2008, visit the following Microsoft TechNet website:

Upgrading SQL Server 2005 to SQL Server 2008

In the following upgrade scenarios, follow the steps that are described on the "Upgrading SQL Server 2005 to SQL Server 2008" TechNet website:

• SQL Reporting Services 2005 to SQL Reporting Services 2008 Service Pack 1 (SP1)
• SQL Reporting Services 2008 Service Pack 1 (SP1) to SQL Reporting Services 2008 R2

Important If you upgraded from SQL Server 2005 to SQL Server 2008, a version of theSRSUpgradeHelper tool is already installed. To upgrade a database to SQL Server 2008 R2, uninstall this version of the SRSUpgradeHelper tool, and then install the updated version that is included in Cumulative Update 5 for Operations Manager 2007 R2. To uninstall the previous version of the SRSUpgradeHelper tool, follow these steps:

1. Delete the SRSUpgradeHelperInstalled registry key under the following registry key:
   HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft Operations Manager\3.0\Reporting
2. Uninstall the SRSUpgradeHelper tool by using the Add or Remove Programs feature.
3. Install the updated version that is included in Cumulative Update 5 for Operations Manager 2007 R2.

Automatic recovery of the System Center Management service in a SQL Server failure scenario

After SQL Server goes offline, the System Center Management service of the root management server (RMS) stops responding. For example, the System Center Management service stops responding after SQL Server disconnects, restarts, or fails. To recover from this issue when SQL Server is available again, you must restart the System Center Management service. 

By default, this automatic recovery feature is disabled. The DALInitiateClearPoolSecondssetting controls when RMS drops the current connection pool and when RMS tries to reestablish an SQL connection. We recommend that you set this setting to 60 seconds or more to avoid performance issues. To configure this recommended setting, set the following values for the following HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\DAL subkeys:

• "DALInitiateClearPoolSeconds" = dword:0000003c
• "DALInitiateClearPool"= dword:00000001

Note To apply the DALInitiateClearPoolSeconds setting, restart the System Center Management service of RMS.

Issues that are resolved by Cumulative Update 5 for Operations Manager 2007 R2

Symptoms	Scenario
Restart of non-Operations Manager services when the agent is updated.	When another application or service has inspected performance counters, that application or service may be restarted when the Operations Manager agent is updated to CU3 or to CU4.
Updated ACS reports.	ACS reports were updated.
TCP Port Probe incorrectly reports negative ping latency.	When you use the TCP Port Probe under certain circumstances, a negative ping latency can be reported.
MissingEvent Manual Reset Monitor does not work as expected.	The MissingEvent Manual Reset monitor can return an unhealthy state even when the monitored event is detected within the time window.
Drillthrough fails because of ParameterTypeMismatch in the EnterpriseManagementChartControl.	When you run Performance reporting on a localized operating system that is trying to drill through, you may receive the error "The value provided for the report parameter 'StartDate_BaseValue' is not valid for its type. (rsReportParameterTypeMisMatch)"
ACS - Event log message is truncated or corrupted in SCDW.	Importing a batch of security events sometimes reports error and failed because event description data is corrupted.
UI hang that is caused by SDK locking.	Occasionally the Operator console can seem to hang.
ACS Filter fails for certain wildcard queries.	When filtering for headers that contain "$," the events are not collected.
Edit Schedule button is disabled with SQL 2008 R2.	The Edit Schedule button in the action pane may be disabled even when the report has an associated schedule.
Web console is timing out while you open the left navigation tree.	When you open the console, the navigation tree can time out after the 110-second default time-out setting.
Scheduled Reports view for Windows Server 2003 and for SQL Server 2005 Reporting Services SP3 CU9 returns "System.IndexOutOfRangeException: Index was outside the bounds of the array."	When you use Windows Server 2003 after you upgrade to CU4, a System.IndexOutOfRangeException can occur when you open the Scheduled Reports view.
Signed MPs cannot be imported when new attributes are added to existing classes.	When a new attribute is added to an existing class in a new version of a sealed MP, the MP cannot be imported.
Performance data for LVM managed partitions is not available with RHEL 4.8 and later versions or with SLES 10 and later versions.	When you use performance view "Logical Disk\Disk Bytes/sec Performance," all the partitions except root "/" do not show any graph/data for the rule "Disk Bytes/sec."
On Solaris or HP-UX, the service name does not show the correct value if the program was started through a symbolic link.	In the Authoring workspace of the Operations console, the Add Monitoring Wizard displays an incorrect Service Name if the service was started through a symbolic link. The Service Name shows the underlying process name instead of the name of the symbolic link.
On AIX, the Operations Manager agent may crash when it is enumerating many processes.	On an AIX computer that is running many processes, the scxcimprovagt process (which is part of the Operations Manager agent) may run out of memory when it enumerates all the processes and may crash with a "bad_alloc" error.

The following released Operations Manager 2007 R2 hotfix is not included in this update because the hotfix includes SQL Server Transact-SQL scripts, SQL Stored Procedure updates, or cross-platform agent updates. For more information about how to obtain a hotfix for this issue, click the following article number to view the article in the Microsoft Knowledge Base : 

981740 System Center Operations Manager 2007 R2 does not display new properties in some views after you import a management pack

Known issues for this update

• CU4 update installation entry still exists in ARP after you upgrade to CU5
  
  We plann to resolve this issue in Cumulative Update 6.
• New management packs cannot be edited in the authoring console after the Cumulative Update is installed
  
  When a new management pack is created after CU4 or CU5 is installed and then an attempt is made to edit the management pack in the Authoring console, the Authoring console cannot edit the management pack because it cannot find the latest version of the Microsoft.SystemCenter.Library Management Pack (build .61 for CU4 and build .81 for CU5).
• Rollback / SDK start failure
  Cumulative Update 5 may roll back multiple times. Or, the System Center Data Access service or the System Center Management Configuration service does not restart after a rollback of Cumulative Update 5 for Operations Manager 2007 R2. Additionally, the "CAStartServices: StartService failed. Error Code: 0x8007041D" error message may be logged in the log file for the installation of the update. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 
  
  936707 FIX: A .NET Framework 2.0 managed application that has an Authenticode signature takes longer than usual to start 
  
  This issue occurs because of a known .NET Framework 2.0 issue in which a certificate revocation list (CRL) response delay affects a small percentage of computers. If you encounter this issue, apply one of the following workarounds:
  • Follow the steps that are described in the following Microsoft Knowledge Base article.
    
    Note You do not have to install hotfix 963707 if you have the .NET Framework 2.0 Service Pack 1 (SP1) or a later version of the .NET Framework installed. 
    
    936707 FIX: A .NET Framework 2.0 managed application that has an Authenticode signature takes longer than usual to start 
    
    After you install hotfix 963707, you should change the manifest file for the System Center Management Configuration service and for the System Center Data Access service on the affected computers. This solution disables CRL checking for the specified executables permanently. To do this, use the following tags to edit the section of the Microsoft.MOM.ConfigServiceHost.exe.config and Microsoft.MOM.Sdk.ServiceHost.exe.config files. These files are stored in the OM installation directory:
    

  • Follow these steps:
    1. Follow the steps that are described in the following Microsoft Knowledge Base article:
       
       922918 A service does not start, and events 7000 and 7011 are logged in Windows Server 2003
    2. Set the value of the ServicesPipeTimeout registry key to 120000.
    3. Restart the affected computer.
    4. Reapply Cumulative Update 5 for Operations Manager 2007 R2. 
       
       Note The Cumulative Update 5 installer may display an error or warning in the installation process. Ignore these warnings and errors by clicking to continue.
• Restart required after ACS update
  When you apply the Audit Collection Services (ACS) update, you may have to restart the computer if an affected file is being used. Additionally, you may receive an error message that resembles the following:
  
  Error 2803: Dialog View did not find a record for dialog
  
  To resolve this issue, restart the computer that has ACS installed after you apply the ACS update.
  
  The HealthServiceRuntime.dll file is not updated on some Windows 2000 Server-based agent computers. This means that the resolution for the following issue is not applied:
  • The monitoring host process does not start the workflows immediately when tasks are received.
  
  This hotfix is not supported on Windows 2000 Server-based computers and is not addressed in upcoming cumulative updates.
• Cumulative Update 5 agent patching failure
  If you apply Cumulative Update 3 for Operations Manager 2007 R2, the pushed agent may not display the update list correctly. This issue occurs because the agent updates in Cumulative Update 3 for Operations Manager 2007 R2 may require a restart operation and then a repair operation. If you do not restart these servers after you apply Cumulative Update 3 for Operations Manager 2007 R2, the agent updates in Cumulative Update 5 for Operations Manager 2007 R2 are not applied. However, the restart required state is set on these computers. Therefore, you have to restart these computers and then repair the agent to apply the updates in Cumulative Update 5 for Operations Manager 2007 R2.
• Microsoft Office might be unable to edit Company Knowledge
  
  This issue is not related to Operations Manager cumulative updates and is introduced by an Office security hotfix. To resolve this issue, apply the following hotfix: 
  
  2458608 Description of the Office Word 2007 hotfix package (wordconv-x-none.msp, word-x-none.msp): December 14, 2010 
  
  Note Operations Manager 2007 R2 supports only the x86-based version of Microsoft Office 2010.
• "Path" property of IIS website object might not be displayed correctly
  
  This issue is limited to state views. It does not affect inventory views, and it affects only those state views in which there is duplication of property names between the EnterpriseManagementObject and the class of the object that is being targeted in the state view. The issue is that the Path property of EnterpriseManagementObject collides with thePath property of the class that is being targeted (Microsoft.Windows.InternetInformationServices.WebSite). We are considering fixing this issue in a future cumulative update.

Installation information

This update must be applied to computers that host any of the following Microsoft Operations Manager servers or agents:

• Root management server (RMS)
• Management server
• Gateway server
• Operations console
• Web console server
• An agent that was manually installed
• Audit Collection Services (ACS) server

To apply this cumulative update, you must use an account that has the same user rights that were used during the installation of Operations Manager. When you update the Operation Manager database, use an account that has local administrator rights on the computer and that has system administrator (SA) credentials on the database. When you update RMS, use an account that has administrator rights and that is a member of the Operations Manager Administrators group. 

Note Before you apply this update, we recommend that you back up the OperationsManager database.

Recommended installation order

We recommend that you install this cumulative update in the following order:

1. Root management server (RMS).
2. Manually update the Operations Manager database by running the included stored procedure file that is discussed later in this article.
3. Manually import the management packs that are discussed later in this article.
4. Secondary management servers.
5. Gateway servers.
6. Deploy the agent update to agents that used a discovery-based installation.
7. Operations console role computers.
   
   Note When you update this role, select the Run Server Update option from theSoftware Update dialog box.
8. Web console server role computers.
9. Apply the agent update to manually installed agents.
10. Audit Collection Services (ACS) role computers. 
    
    Notes
• When you update a component by using the installer splash screen, you have to complete three update installers. When you update a component such as RMS, each installer starts and requires you to click Finish when the update is completed. The next installer starts automatically.
• Cumulative Update 5 for Operations Manager 2007 R2 consists of the following three updates:
• Operations Manager 2007 R2 updates
• Localized updates
• Cross-platform updates

Installation steps

To extract the files that are contained in this update, follow these steps:

1. Copy the following file to either a local folder or an available network share: 
   
   SystemCenterOperationsManager2007-R2CU5-KB2495674-X86-X64-IA64-ENU.MSI
2. Run this file locally on each applicable computer. For example, run this file on the root management server (RMS).
   
   Notes
   • Run this file by using either Windows Explorer or a command prompt.
   • To run this file on a computer that is running Windows Server 2008, you must use an elevated command prompt. An elevated command prompt is a command prompt that was started by using the Run as Administrator option. If you do not run this Windows-based installer file under an elevated command prompt, the System Center Operations Manager 2007 Software Update splash screen does not let the hotfix be installed.
3. In the System Center Operations Manager 2007 Software Update window, select the update option for the role that will be updated.

Recommended steps for applying this cumulative update to a clustered root management server

For more information about the recommended instructions for applying this cumulative update to a clustered root management server, visit the following Microsoft website:

How to apply a SCOM hotfix to a clustered RMS

Manual operations that must be performed after you update the root management server and Data Warehouse

Run the SQL scripts

This update contains fixes that must be manually applied. These fixes are applied by running the \SQLUpdate\CU5_DataWarehouse.sql file against the Operations Manager data warehouse (OperationsManagerDW) and by running the \SQLUpdate\CU5_Database.sql file against the Operations Manager database (OperationsManager). 

To do this, follow these steps:

1. Log on to the computer that hosts the Operations Manager 2007 database by using a user account that has database system administrator (SA) rights to the Operations Manager 2007 database instance. To perform the database update remotely, log on to a computer that hosts SQL Server Management Studio by using a user account that has the appropriate SA rights to the Operations Manager 2007 database.
2. Run SQL Server Management Studio.
3. In the Connect to Server dialog box, connect to the instance of SQL Server that hosts the Operations Manager database. The default database name is OperationsManager.
4. Click New Query on the toolbar.
5. From the SQL Editor toolbar, use the Available databases option to select the Operations Manager database.
6. On the File menu, click Open, select the \SQLUpdate\CU5_Database.sql file that was extracted by the Windows installer (.msi file), and then click Open.
7. When the file is loaded, click Execute in the SQL Editor toolbar.
8. View the Messages pane to check whether the Transact-SQL commands ran successfully.
9. Exit SQL Server Management Studio.
10. For the Operations Manager data warehouse, repeat steps 1 through 8. However, connect to the instance of SQL Server that hosts the Operations Manager data warehouse, and then run the \SQLUpdate\CU5_DataWarehouse.sql file.

Import the management packs

The management packs that are supplied in the ManagementPacks folder must be manually imported by using the Import Management Packs Wizard in the Operations console. The Windows Installer packages that are released for each localized version of Operations Manager contain the appropriate localized version of the management pack. For example, the following file contains the localized version of the management pack for the Japanese localized version of Operations Manager: 

SystemCenterOperationsManager2007-R2CU5-KB2495674-X86-X64-IA64-JPN.MSI

The following updated management packs are located in the ManagementPacks folder of the package installation:

• Microsoft.SystemCenter.DatawareHouse.Report.Library.mp
• Microsoft.SystemCenter.WebApplication.Library.mp
• Microsoft.SystemCenter.WSManagement.Library.mp

Update the Web.Config file on the Web Console server role computers

To make sure that all cookies that are created by the web console cannot be accessed by the client cscript, add the following configuration to the Web.Config file on the web console server: 

If the web console is configured to run under SSL, add the following configuration to make sure that all cookies are encrypted: 

Install Linux/UNIX management packs, and update Linux/UNIX agents

Cumulative Update 5 for Operations Manager 2007 R2 contains the same Linux/UNIX updates that are included in Cumulative Update 3 for Operations Manager 2007 R2. Therefore, you do not have to install the Linux/UNIX management packs and agents if you have already updated your monitored Linux/UNIX computers by using Cumulative Update 3 for Operations Manager 2007 R2. If you do not upgrade from Cumulative Update 3 for Operations Manager 2007 R2, follow these steps to monitor Linux/UNIX computers:

1. Download and then install the updated management packs from the following Microsoft website:
   
   System Center Operations Manager 2007 R2 Cross Platform Monitoring Management Packs
2. Import the updated management pack for each version of Linux or UNIX that you are monitoring in your environment.
3. Use the Operations Manager 2007 R2 Discovery Wizard to rediscover the Linux and UNIX computers that you monitor. After you rediscover the computers, the agents on those computers upgrade automatically.

Updated support tools that are included in this cumulative update

The following updated file in the SupportTools folder supports the upgrade from SQL Reporting Services 2005 to SQL Reporting Services 2008 and from SQL Reporting Services 2008 to SQL Reporting Services 2008 R2:

SRSUpgradeTool.exe 

Note Use the appropriate platform version of this file instead of the file that is supplied in the SupportTools folder of the Operations Manager 2008 R2 distribution media.

Advanced installation instructions at a command prompt

The installer (hotfix utility) that is downloaded from this site unpacks the bootstrapping application and necessary MSP files to install Cumulative Update 5 for Operations Manager 2007 R2. It is better to run the hotfix utility on each computer and to deploy Cumulative Update 5 for Operations Manager 2007 R2 by using the GUI interface that is invoked after you run the hotfix utility. However, you can avoid multiple installations of the hotfix utility by copying the unpacked directory and files to the appropriate computers. These files are unpacked to the following location by the hotfix utility:

\Program Files (x86)\System Center 2007 R2 Hotfix Utility\KB2495674\

If you decide to install Cumulative Update 5 for Operations Manager 2007 R2 at a command prompt, use the following command:

SetupUpdateOM.exe /x86msp:KB<#>-x86.msp /amd64msp:KB<#>-x64.msp /ia64msp:KB<#>-ia64.msp /x86locmsp:KB<#>-x86-.msp /amd64locmsp:KB<#>-x64-.msp /ia64locmsp:KB<#>-ia64-.msp /Agent /Silent /noreboot

Note The /Silent flag is not necessary if you want to install Cumulative Update 5 for Operations Manager 2007 R2 by using the GUI interface. Replace the  parameter with the appropriate language code for the update that you have downloaded. Replace the <#> parameter with the Microsoft Knowledge Base article number for this cumulative update. 

For example, run the following command for the English version of Cumulative Update 5 for Operations Manager 2007 R2:

SetupUpdateOM.exe /x86msp:KB2495674-x86.msp /amd64msp:KB2495674-x64.msp /ia64msp:KB2495674-ia64.msp /x86locmsp:KB2495674-x86-ENU.msp /amd64locmsp:KB2495674-x64-ENU.msp /ia64locmsp:KB2495674-ia64-ENU.msp /Agent /Silent /noreboot

Advanced installation instruction to manually update agents

With Cumulative Update 5 for Operations Manager 2007 R2, you can manually update agents without copying the full contents of the package. To deploy updates to an agent, follow these steps:

1. Install the hotfix utility by using the instructions in the "Advanced installation instructions at a command prompt" section. By default, the files that you have to have to update the agent are found at the following location:
   C:\Program Files (x86)\System Center 2007 R2 Hotfix Utility\KB2495674
2. Copy the appropriate MSP files to a folder of your choosing (for example, C:\temp\CU5_Agent) on each computer on which you want to manually update the agent.
3. Run the following commands at a command prompt from the folder that contains the update files (C:\temp\CU5_Agent if you follow the suggestion here) (ex: x64 architecture and English language):
   msiexec.exe /p "C:\temp\CU5_Agent\KB2495674-x64-Agent.msp" REBOOT="ReallySuppress" 
   
   msiexec.exe /p "C:\temp\CU5_Agent\KB2495674-x64-ENU-Agent.msp" REBOOT="ReallySuppress"
   
   Note Replace ENU with the language code of the Cumulative Update 5 for Operations Manager 2007 R2 package that you downloaded. Also, if you want to do a silent install, add the /qn switch to the command line.

File list and roles

Expand this table

File name	Version	Roles
		Server	Agent	Gateway	ACS	X-Plat
Access_Violation_-_Unsuccessful_Logon_Attempts.rdl	Not applicable	X
ActionsPane.ascx	Not applicable	X
AdtAgent.exe	6.1.7221.81	X	X
AdtServer.exe	6.1.7221.81				X
AdtSrvDll.dll	6.1.7221.81				X
AlertPropertypage5.ascx	Not applicable	X
AuditingMessages.dll	6.1.7221.81	X
Blank.aspx	Not applicable	X
CACore.dll	6.1.7221.81	X	X	X
DataViews.js	Not applicable	X
DetailsTypeAlert.aspx	Not applicable	X
DetailsTypePerformance.aspx	Not applicable	X
DetailsTypeTaskStatus.aspx	Not applicable	X
DisableForwarding.ps1	Not applicable				X
EnableForwarding.ps1	Not applicable				X
EventCommon.dll	6.1.7221.81	X	X	X
Forensic_-_All_Events_For_Specified_User.rdl	Not applicable	X
FormatTracing.cmd	Not applicable	X	X	X
HeaderControl.ascx	Not applicable	X
HealthExplorer.css	Not applicable	X
HealthExplorerView.ascx	Not applicable	X
HealthService.dll	6.1.7221.81	X	X	X
HealthServiceMessages.dll	6.1.7221.81	X	X	X
HealthServicePerformance.dll	6.1.7221.81	X	X	X
HealthServiceRuntime.dll	6.1.7221.81	X	X	X
HSLockdown.exe	6.1.7221.81	X	X	X
Login.aspx	Not applicable	X
MainStyles.css	Not applicable	X
Microsoft.EnterpriseManagement.DataWarehouse.DataAccess.dll	6.1.7221.81	X
Microsoft.EnterpriseManagement.HealthService.Modules.DataWarehouse.dll	6.1.7221.81	X
Microsoft.EnterpriseManagement.HealthService.Modules.Notification.dll	6.1.7221.81	X
Microsoft.EnterpriseManagement.HealthService.Modules.WorkflowFoundation.dll	6.1.7221.81	X	X	X
Microsoft.EnterpriseManagement.Modules.Azure.dll	6.1.7221.81	X	X	X
Microsoft.EnterpriseManagement.OperationsManager.ClientShell.Console.psc1	Not applicable	X
Microsoft.EnterpriseManagement.OperationsManager.ClientShell.dll	6.1.7221.81	X
Microsoft.EnterpriseManagement.OperationsManager.ClientShell.dll-help.xml	Not applicable	X
Microsoft.EnterpriseManagement.OperationsManager.ClientShell.Format.ps1xml	Not applicable	X
Microsoft.EnterpriseManagement.OperationsManager.ClientShell.Functions.ps1	Not applicable	X
Microsoft.EnterpriseManagement.OperationsManager.ClientShell.NonInteractiveStartup.ps1	Not applicable	X
Microsoft.EnterpriseManagement.OperationsManager.ClientShell.Startup.ps1	Not applicable	X
Microsoft.EnterpriseManagement.OperationsManager.ClientShell.Types.ps1xml	Not applicable	X
Microsoft.EnterpriseManagement.OperationsManager.Common.dll	6.1.7221.81	X
Microsoft.EnterpriseManagement.OperationsManager.DataAbstractionLayer.CommonSetup.dll	6.1.7221.81	X
Microsoft.EnterpriseManagement.OperationsManager.DataAbstractionLayer.dll	6.1.7221.81	X
Microsoft.EnterpriseManagement.OperationsManager.dll	6.1.7221.81	X
Microsoft.EnterpriseManagement.OperationsManager.Web.ConsoleFramework.dll	6.1.7221.81	X
Microsoft.EnterpriseManagement.UI.Administration.dll	6.1.7221.81	X
Microsoft.EnterpriseManagement.UI.Authoring.dll	6.1.7221.81	X
Microsoft.EnterpriseManagement.UI.Authoring.resources.dll	6.1.7221.81	X
Microsoft.EnterpriseManagement.UI.Reporting.dll	6.1.7221.81	X
Microsoft.Mom.Common.dll	6.1.7221.81	X	X	X
Microsoft.Mom.ConfigServiceHost.exe	6.1.7221.81	X
Microsoft.Mom.DataAccessLayer.dll	6.1.7221.81	X
Microsoft.Mom.DiscoveryDatabaseAccess.dll	6.1.7221.81	X
Microsoft.Mom.Modules.ClientMonitoring.dll	6.1.7221.81	X
Microsoft.Mom.Modules.DataTypes.dll	6.1.7221.81	X	X	X
Microsoft.Mom.RecorderBarBHO.dll	1.0.0.2	X
Microsoft.Mom.Sdk.ServiceDataLayer.dll	6.1.7221.81	X
Microsoft.Mom.Sdk.ServiceHost.exe	6.1.7221.81	X
Microsoft.Mom.ServiceCommon.dll	6.1.7221.81	X
Microsoft.MOM.UI.Common.dll	6.1.7221.81	X
Microsoft.MOM.UI.Components.dll	6.1.7221.81	X
Microsoft.MOM.UI.Console.exe	6.1.7221.81	X
Microsoft.Mom.UI.Wrappers.dll	6.1.7221.81	X
MicrosoftRSChart.dll	2.0.0.175	X
MicrosoftRSChartDesigner.dll	2.0.0.175	X
MobileWebConsole.dll	6.1.7221.81	X
MomADAdmin.exe	6.1.7221.81	X
MOMAgentInstaller.exe	6.1.7221.81	X		X
MOMAgentInstallerPS.dll	6.1.7221.81	X		X
MOMAgentManagement.dll	6.1.7221.81	X		X
MomBidLdr.dll	5.2.3790.1290	X	X	X
MOMConnector.dll	6.1.7221.81	X	X	X
MomConnectorMessages.dll	6.1.7221.81	X	X	X
MOMConnectorPerformance.dll	6.1.7221.81	X	X	X
MomIISModules.dll	6.1.7221.81	X	X	X
MOMModuleMsgs.dll	6.1.7221.81	X	X	X
MOMModules.dll	6.1.7221.81	X	X	X
mommodules2.dll	6.1.7221.81	X	X	X
MOMMsgs.dll	6.1.7221.81	X
MOMNetworkModules.dll	6.1.7221.81	X	X	X
MOMPerfSnapshotHelper.exe	6.1.7221.81	X	X	X
MOMScriptAPI.dll	6.1.7221.81	X	X	X
MOMSCXLogModules.dll	6.1.7000.277					X
MOMV3.SP2_7221_signed.cab	Not applicable	X	X	X
MomWsManModules.dll	6.1.7221.81	X	X	X
MonitoringHost.exe	6.1.7221.81	X	X	X
MPConvert.exe	6.1.7221.81	X
MPExport.exe	6.1.7221.81	X
MPImport.exe	6.1.7221.81	X
MPVerify.exe	6.1.7221.81	X
OperationalDataReporting.exe	6.1.7221.81	X
OpsMgrVssWriterService.exe	6.1.7221.81	X
Planning_-_Logon_Counts_of_Privileged_Users.rdl	Not applicable	X
PrereqResource.dll	6.1.7221.0	X
RootWebConsole.dll	6.1.7221.81	X
RSSWebConsole.dll	6.1.7221.81	X
Operations ManagerMaintenanceMode.dll	6.1.7221.81	X	X	X
ScopingForm.aspx	Not applicable	X
SCXAgents.dll	6.1.7000.295					X
scxcertconfig.exe	6.1.7000.277					X
SecureStorageBackup.exe	6.1.7221.81	X
SecureStorageSDK.dll	6.1.7221.81	X
StateSummary.ascx	Not applicable	X
TitleBar.js	Not applicable	X
TraceConfig.exe	6.1.7221.81	X	X	X
tracefmtsm.exe	6.1.7221.81	X	X	X
TraceLogSM.exe	6.1.7221.81	X	X	X
Usage_-_Privileged_logon.rdl	Not applicable	X
Usage_-_User_Logon.rdl	Not applicable	X
ViewTypeFavoritesOverview.aspx	Not applicable	X
ViewTypeOverview.aspx	Not applicable	X
Web.Config	Not applicable	X
WSSDiscovery.exe	6.1.7221.81	X	X	X

This update installs updated UNIX and Linux agents, and this update removes older UNIX and Linux agents in the following folder:

Program Files\System Center Operations Manager 2007\AgentManagement\UnixAgents

The updated agents have file names that use the following format and a version number of 265:

scx-1.0.4-265-server type.server version.architecture.package type

Notes

• The placeholder server type represents the name of the UNIX or Linux server product.
• The placeholder server version represents the version number of the server type.
• The placeholder architecture represents the processor architecture of the destination computer.
• The placeholder package type represents the kind of installation file.

For example, the following is the file name format for the agent for SUSE Linux Enterprise Server 10 (x86):

scx-1.0.4-265-sles.10.x86.rpm

The agents that are included with Systems Center Operations Manager 2007 R2 Cross Platform Cumulative Update 2 (hotfix 979490) have a version number of 258. All agent files for this version number are removed during the installation of this update.

The agents that are included with System Center Operations Manager 2007 R2 Cross Platform Agent Update (hotfix 973583) have a version number of 252. All agent files for this version number are removed during the installation of this update.

The agents that are included with the original release of System Center Operations Manager 2007 R2 have a version number of 248. These files are not removed during installation. However, these files are replaced with 1-kilobyte (KB) files. You have the option of removing these 1-KB files. These files are as follows:

• scx-1.0.4-248.aix.5.ppc.lpp.gz
• scx-1.0.4-248.aix.6.ppc.lpp.gz
• scx-1.0.4-248.hpux.11iv2.ia64.depot.Z
• scx-1.0.4-248.hpux.11iv2.parisc.depot.Z
• scx-1.0.4-248.hpux.11iv3.ia64.depot.Z
• scx-1.0.4-248.hpux.11iv3.parisc.depot.Z
• scx-1.0.4-248.rhel.4.x64.rpm
• scx-1.0.4-248.rhel.4.x86.rpm
• scx-1.0.4-248.rhel.5.x64.rpm
• scx-1.0.4-248.rhel.5.x86.rpm
• scx-1.0.4-248.sles.10.x64.rpm
• scx-1.0.4-248.sles.10.x86.rpm
• scx-1.0.4-248.sles.9.x86.rpm
• scx-1.0.4-248.solaris.10.sparc.pkg.Z
• scx-1.0.4-248.solaris.10.x86.pkg.Z
• scx-1.0.4-248.solaris.8.sparc.pkg.Z
• scx-1.0.4-248.solaris.9.sparc.pkg.Z