- Support for Windows 7
- Support for Windows Server 2008 R2
- Support for SQL Server 2008 and SQL Reporting Services 2008 Upgrade
- Additional fixes and improvements
Download informationThe following file is available for download from the Microsoft Download Center:
Download the Download the Operations Manager 2007 Service Pack 1 Update package now.
For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:
List of released fixes that are included in this updateThe following fixes are included in this update:
|Knowledge Base article||Article title|
|949875||When you run a task in the System Center Operations Manager 2007 Operations Console on a Russian version of Windows Server 2003, the task outputs are displayed in corrupted text|
|950853||A memory leak occurs when you monitor Exchange Server 2007 by using the MOM 2007 agent in System Center Operations Manager 2007|
|951380||Some computer properties for a cluster node may not be collected by the discovery process in System Center Operations Manager 2007 Service Pack 1|
|951526||The Root Management Server (RMS) of System Center Operations Manager 2007 Service Pack 1 or Essentials 2007 Service Pack 1 becomes unstable or unusable if a management pack is imported|
|951527||Modifications that you try to make to a Web application that was created before you upgrade Microsoft System Center Operations Manager 2007 are not saved|
|951529||System Center Operations Manager 2007 runs scripts in the Rule Name field or in the Description field|
|951979||Problems occur on a management server that is running System Center Operations Manager 2007 Service Pack 1 when certain management packs are installed|
|952857||The Custom Event Report does not list the GenericLog-type events in System Center Operations Manager 2007 Service Pack 1|
|952937||The relative date picker returns wrong dates when you run a report in a month that has less days than the previous month in System Center Operations Manager 2007|
|953817||The Administrator Console exits when you try to use the "Set Resolution State" option for an alert that is generated in System Center Operations Manager 2007|
|954049||Description of the hotfix rollup package for System Center Operations Manager 2007 Service Pack 1 and for System Center Essentials 2007 Service Pack 1: July 25, 2008|
|954090||Objects that are displayed in a performance view are not scoped to the specified group when they are viewed in the Web Console of Operations Manager 2007 Service Pack 1|
|954329||An Audit Collection Service forwarder may be unable to retrieve the distinguished name for the ObjectGUID in the collected events in System Center Operations Manager 2007 Service Pack 1|
|954823||A custom event report does not display events that are generated by the generic CSV text log collection rules when Parameter 1 to Parameter 20 is included in the Report Field criteria in System Center Operations Manager 2007 Service Pack 1 (SP1)|
|954903||The Monitoringhost.exe process may consume all the CPU resources when a large amount of performance data is created by using a managed data source module in System Center Operations Manager 2007|
|955523||Web console hotfix package for System Center Operations Manager 2007|
|956172||The CcmExec.exe process crashes on a Windows 2000-based computer if both a System Center Operations Manager 2007 Service Pack 1 agent and a System Center Configuration Manager 2007 client are installed on this computer|
|956240||The SQL Server process may consume lots of CPU resources on the server that hosts the Operations Manager 2007 database after you make Operations Manager 2007 configuration changes|
|956423||The connection settings for connectors in tiered management groups are configured incorrectly after the OpsMgr SDK Service restarts in a System Center Operations Manager 2007 SP1 environment|
|956446||The e-mail notifications may contain garbled subject lines if you enable the "Generate subject line with no encoding" option in System Center Operations Manager 2007 Service Pack 1|
|956689||A Run As account that is configured for proxy authentication in a Web application monitor is not used in System Center Operations Manager 2007 Service Pack 1|
|957123||Hotfix for System Center Operations Manager 2007 SP1 enables monitoring support for IIS 7.0|
|957135||You cannot change the alert resolution state of any alert in the Active Alerts view in System Center Operations Manager 2007 Service Pack 1|
|957199||The System Center Operations Manager 2007 Service Pack 1 operations console cannot display English product knowledge when you open the properties dialog box of an alert: "No product knowledge was available for this Alert"|
|957511||Warning alerts and warning monitor state changes do not occur as expected for a Web application that is created by using the Web application template in System Center Operations Manager 2007 Service Pack 1|
|958253||When you try to view the Patch List property, the list of Operations Manager agent hotfixes may be truncated on System Center Operations Manager 2007 Service Pack 1 systems|
|958254||You receive multiple "WMI Probe Module Failed Execution" alerts from Windows 2000-based computers after you install System Center Operations Manager 2007 SP1|
|958490||Dependency monitors indicate an incorrect state on a System Center Operations Manager 2007 SP1-based computer|
|959497||The System Center Operations Manager 2007 Service Pack 1 SDK service may stop unexpectedly, and you may receive an error message: "Specified argument is out of the range of valid values"|
|959865||Issues that are resolved by the Operations Manager Module rollup update for System Center Operations Manager 2007 Service Pack 1: June 10, 2009|
|959867||You cannot specify a management pack to store a new override of a monitor or of a rule in the Operations console in System Center Operations Manager 2007 Service Pack 1|
|960363||Charts in a performance report are incorrectly scaled, or a report that contains multiple charts does not display the charts in the correct order in System Center Operations Manager 2007 SP1|
|961363||Operations Manager 2007 Service Pack 1 may stop monitoring SNMP devices|
|963005||The Add Object Wizard displays only 500 objects even if more objects exist in System Center Operations Manager 2007 Service Pack 1|
|967843||The <Server>_PrimarySG_<number> security group is repopulated every hour even though the group's membership has not changed in System Center Operations Manager 2007 SP1|
|968082||Error message when you add an agent assignment rule in the System Center Operations Manager 2007 if an Active Directory domain name begins with a numeric digit: "XSD verification failed for management pack"|
|969130||The size of the System Center Operations Manager 2007 Service Pack 1 Data Warehouse database may grow if many event collection rules exist within management packs|
|970533||The Product Knowledge tab is displayed as the Company Knowledge tab after you import a Language Pack for System Center Operations Manager 2007 Service Pack 1|
List of released fixes that are not included in this updateThe following released Operations Manager SP1 hotfixes are not included in this update because they include SQL Server TSQL scripts and SQL Stored Procedure updates or because they affect setup. Refer to the individual Microsoft Knowledge Base articles to obtain a fix for your specific issues.
|Knowledge Base article||Article title|
|951148||You cannot install Operations Manager 2007 Reporting if the SQL Server Reporting Services instance takes more than 60 seconds to start|
|954643||Event ID 31569 is logged after you install a management pack that includes reports on a System Center Operations Manager 2007 SP1 server or on a System Center Essentials 2007 SP1 server|
|956184||Alerts are issued from the MOM Active Directory Management Pack after you install an Operations Manager 2007 SP1 agent over a MOM 2005 agent on a domain controller that is running a 64-bit version of Windows|
|962967||Expected reports for installed management packs are not visible in the System Center Operations Manager 2007 Operations Console Reporting node|
List of fixes from Microsoft Knowledge Base article 974722 that are included in this updateThis update addresses the known issues that are described in Microsoft Knowledge Base article 974722
|Operations Manager services stop unexpectedly on a Root Management Server whose operating system was upgraded to Windows Server 2008 R2.||Apply update 971541 to the Root Management Server after you upgrade the operating system to Windows Server 2008 R2. If you have already applied update 971541 on the Root Management Server before the upgrade, you can safely reapply update 971541 to correct this issue.|
|The ACS Server (ADTServer) service does not start after you upgrade the operating system to Windows Server 2008 R2.||Apply update 971541 on the ACS Server after you upgrade the operating system to Windows Server 2008 R2. If you have already applied update 971541 on the ACS Server before the upgrade, you do not have to reapply the update.|
|"Backward Compatibility Script Error" alerts are generated with the description of "An error occurred on line 123 while executing script 'MOM Backward Compatibility Service State Monitoring Script'".||Apply update 971541 on the Root Management Server. This update automatically imports an updated Backward Compatibility management pack library that corrects this issue when agents Windows 7-based or Windows Server 2008 R2-based agents receive the updated management pack.|
|Event ID 26017 from source "Health Service Modules" is logged for Operations Manager 2007 SP1 agents. This event displays an "Event log Provider monitoring the <LogName> Event Log is # minutes behind" error and the number of minutes is in the hundreds of millions.||Apply update 971541 on the Root Management Server, secondary Management Servers and Gateway servers. Manually approve Pending agent updates in the Operations Console for agents that are deployed through Discovery-based installation. Apply update 971541 on each manually installed agent that was upgraded to Windows 7 or Windows Server 2008 R2.|
Additional fixes included in this updateThe following additional fixes are included in this update.
|Issue||Description and resolution|
|The "Alert only if service startup type is automatic" override does not work for a Basic Service Monitor if the override is set to False and the monitored service is set to Manual.||If this override is applied to a service monitor that is created from a Windows Service template, the override works fine. However, when a Basic Service Monitor is overridden and set to False, no alert is generated when the monitored service is stopped.|
|An instance of the MonitoringHost.exe process may stop responding when the event log is cleared.||If you clear a Windows event log by using the Clear Log operation from Event View or other methods, the MonitoringHost instance that monitors the event log may crash.|
|An instance of the MonitoringHost.exe process may consume lots of nonpaged pool memory.||When the MonitoringHost.exe process performs log file monitoring by using the Application log module, a memory leak may occur in the nonpaged pool.|
|The Operations Console may crash with an UnauthorizedAccessException exception when you run the Operations Console on a computer that is running Windows Vista, Windows 7, or Windows Server 2008 R2.||The Operations console crashes and the following exception is returned:|
Message: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)) Calling System.Windows.Forms.WebBrowser.get_Document()
|The System Center Configuration Manager 2007 Management Pack does not let you monitor a Windows 64-bit operating system directly. You can only perform the monitoring by using a 32-bit agent only.||This update contains support for the latest Configuration Manager 2007 SP2 Management Pack to monitor Configuration Manager 2007 SP2 by using the Operations Manager 2007 SP1 64-bit agent. For more information, refer to the Management Pack guide on the Microsoft TechNet Web site.|
|The State Change and State Rollup information may be incorrect.||This update contains state reliability fixes to correct these error situations.|
|WMI-based performance rules and monitors cannot override the Polling Frequency with the initial Polling Frequency.||This update contains an updated Management Pack library that exposes the Frequency override property for these rules and monitors.|
|The issue that is described in Knowledgebase article 959867 occurs not only in the Japanese version of Operations Manager 2007 SP1 but also in the Simplified Chinese, Traditional Chinese, and Korean versions.||The localized versions of this update contain fixes that enable overrides to be stored within a management pack in the Overrides Properties dialog box.|
Fixes included in this update that require manual interventionThis update contains two fixes that must be manually applied. The following table lists the symptoms that the fixes address and the installation steps for the fixes.
When you try to install the Gateway Server role on a Windows Server 2008 R2 computer, you receive the following error message and the installation fails:
To support installation of the Gateway server role on a Windows Server 2008 R2 computer, you must update the MOMGateway.msi file by using a transform file that is provided with this update. After you update the MOMGateway.msi file, you can use it to install the Gateway Server role and then install the server updates that are described here.
To update the MOMGateway.msi the file, follow these steps:
- Copy the MOMGateway.msi file that is appropriate for the platform from the Operations Manager 2007 SP1 installation media to a writable location on the hard disk.
- Copy the MOMGateway.mst and GatewayUpdate.vbs files from the Gateway folder that was created during the installation of this update to the same folder as the MOMGateway.msi file. By default, this file is extracted to the following folder:%ProgramFiles%\System Center 2007 Hotfix Utility\KB971541\Gateway
- At a command prompt, swift the working directory to the folder that contains the MOMGateway.mst and GatewayUpdate.vbs files.
- Run the following command:cscript.exe GatewayUpdate.vbs
- Use the MOMGateway.msi file to install the Gateway Server role in Windows Server 2008 R2.
After you upgrade SQL Server 2005 Reporting Services to SQL Server 2008 Reporting Services, if you try to generate a performance report or certain other report types, the following exception is generated:
Microsoft.Reporting.WinForms.ReportServerException: The report definition is not valid. Details: Deserialization failed: The value 'ContentsOnly' is not valid for DataElementOutput.
Resolution for Symptom 2
An updated Microsoft.SystemCenter.DataWarehouse.Reports.MP (version 6.0.6278.100) management pack is provided with this update. Import this management pack to resolve this issue. The updated management pack is located in the Management Packs folder that is created during the installation of this update.
After you import the management pack, you must allow the updated reports to deploy before you try to regenerate performance reports.
Known issues that are not resolved in this update
|When you open the Web Console in Internet Explorer 8, the Search text entry and the magnifier icon are overlapping.||To resolve this issue, open the Web Console in the Compatibility View of Internet Explorer 8.|
|The error "The value expression used in field 'FormattedDateTime' references a dataset field which contains an error: FieldValueException" is displayed when you generate a Custom Event report on SQL Server Reporting Services 2008.||You can include the "Date" Report Field in the report to resolve this issue.|
The issue is fully resolved in Operations Manager 2007 R2.
SQL Server 2008 SupportThis update provides support for the upgrade of Operations Manager database roles SQL Server 2005 to SQL Server 2008. These roles include the following:
- Operational Database
- DataWarehouse Database
- ACS Database Server
We recommend that you install SQL Server 2008 Service Pack 1 or a later version after you upgrade to SQL Server 2008. SQL Server 2008 Service Pack 1 contains fixes for SQL Reporting Services that provide improvements for Operations Manager 2007 Reporting.
Upgrading SQL Server Reporting Services 2005 to 2008To upgrade a SQL Reporting Services 2005 server that hosts Operations Manager 2007 SP1 reports to SQL Reporting Services 2008, you can use the following tools, which are included in this update:
For more information about upgrading SQL Server 2005 Reporting Service to SQL Server 2008 Reporting Service, visit the following Microsoft TechNet Web site:Notes
- The steps documented in the Upgrade Guide are the same for the SP1 version and the R2 version. We recommend that you install the necessary service packs immediately after finish the upgrade successfully.
- The tools that are mentioned this section are different for the SP1 and R2 versions of Operations Manager. Make sure that you use the tools appropriate for the specific version of Operations Manager that you are using. The R2 version of these tools is located in the SupportTools folder of the Operations Manager 2007 R2 installation media.
Installation instructionsApply the update to each computer that hosts one of the following roles:
- Microsoft Operations Manager root management server
- Microsoft Operations Manager management server
- Microsoft Operations Manager Operations console
- Microsoft Operations Manager Web console server
- Microsoft Operations Manager Reporting server
- Microsoft Operations Manager manually installed agent
- Microsoft Operations Manager ACS server
- Copy the following file to either a local folder or a shared folder:SystemCenterOperationsManager2007-SP1-KB971541-X86-X64-IA64-ENU.MSI
- On each computer that you want to upgrade, run the following file:SystemCenterOperationsManager2007-SP1-KB971541-X86-X64-IA64-ENU.MSINote You can run SystemCenterOperationsManager2007-SP1-KB971541-X86-X64-IA64-ENU.MSI either in Windows Explorer or at a command prompt. To run this file on Windows Server 2008, you must open an elevated command prompt by using the Run as Administrator option and then run the command at the elevated command prompt.
- On the System Center Operations Manager 2007 Software Update window, select the appropriate update option for the role on which you want to apply this update.
- When you apply this update on an Operations Manager 2007 SP1 server role, MSI Setup will start a second time to install a second update after the first update is successfully applied. This is expected behavior. The second update applies the localized fixes.
- If the updated files are being used during the update installation, you may be prompted to restart the computer by the following message: You can click No on the message and manually restart the computer when all updates for the role are completed.
- The installation of update on the ACS Server role requires you to restart the computer. The following message is displayed: Click OK on the message and manually restart the computer when all updates for the role are completed.
- Import the following management pack from the ManagementPacks folder:Microsoft.SystemCenter.DataWarehouse.Reports.MP
PrerequisitesThis update applies to System Center Operations Manager 2007 SP1 only.
Restart requirementYou do not have to restart the computer after you apply this update.
File informationThe English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
System Center Operations Manager 2007 Service Pack 1, x86-based version
|File name||File version||File size||Date||Time||Platform|
System Center Operations Manager 2007 Service Pack 1, x64-based version
|File name||File version||File size||Date||Time||Platform|
System Center Operations Manager 2007 Service Pack 1, Itanium-based version
|File name||File version||File size||Date||Time||Platform|
ID do Artigo: 971541 - Última Revisão: 09/10/2011 - Revisão: 1