Article ID: 954049 - View products that this article applies to.
This article describes the Microsoft Operations Manager 2007 and Microsoft System Center Essentials 2007 issues that are fixed in the hotfix rollup package that is dated July 25, 2008. This article describes the following items about the hotfix rollup package:
This article describes the hotfix rollup package for System Center Operations Manager 2007 Service Pack 1 (SP1) and for Essentials 2007 Service Pack 1 that is dated July 25, 2008.
This hotfix provides support to install Operations Manager 2007 Service Pack 1 or Essentials 2007 Service Pack 1 on a Windows Server 2008-based computer.
Note Earlier versions of Operations Manager 2007 and Essentials 2007 are not supported in Windows Server 2008.
For more information about support in Windows Server 2008 for Operations Manager 2007 and Essentials 2007, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/953141/ )Support for running System Center Operations Manager 2007 Service Pack 1 and System Center Essentials 2007 Service Pack 1 on a Windows Server 2008-based computer
Supported configurationsThis hotfix provides support for the following scenarios:
Issues that the hotfix package fixesThis hotfix package fixes the following issues that are not previously documented in a Microsoft Knowledge Base article:
Issue 1When you upgrade an Operations Manager agent computer from Windows Server 2003 to Windows Server 2008, the Health Service does not start on the computer. This issue occurs because the upgrade removes the certificate store in which the Health Service includes its certificate for secure storage data encryption. When the secure storage manager component of the Health Service initializes, it fails if there is a certificate serial number that is set, but the store does not exist.
Issue 2The Operations Manager Web Console does not display pages correctly because of changes in User Access Control (UAC) in Windows Server 2008. You may experience one or more of the following symptoms:
Issue 3After you upgrade a computer that performs the Operations Manager Management Server role from Windows Server 2003 to Windows Server 2008, the Operations Manager performance counters are not registered.
Download informationThe following file is available for download from the Microsoft Download Center:
Download the 954049 package now.
Collapse this imageExpand this image
Release Date: July 25, 2008
For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.
(https://support.microsoft.com/kb/119591/ )How to obtain Microsoft support files from online services
Currently, this hotfix is provided in the English language only. However, the hotfix applies to all Operations Manager 2007 or Essentials 2007 released languages. Localized packages for all released languages will be available shortly and will be listed in this article as they become available.
PrerequisitesBefore you install hotfix 954049, you must comply with the following prerequisites:
Restart requirementYou do not have to restart the computer after you apply this hotfix for nonclustered environments. On a clustered Root Management Server (RMS), you must stop the Operations Manager 2007 services manually before you install the hotfix. If you do not stop the services manually on a clustered Root Management Server, you will have to restart each clustered node.
Hotfix replacement informationThis hotfix does not replace any other hotfixes.
Hotfix installation informationTo install the hotfix, you must follow these rules:
How to extract the filesTo extract the files from the hotfix package, you must run the following file:
SystemCenterOperationsManager2007-SP1-KB954049-X86-X64-ENU.MSIIn Windows Server 2008, you must run this file from an elevated command prompt that was executed with the "Run as Administrator" option. If you do not execute this MSI file under an elevated command prompt, the System Center Operations Manager 2007 Software Update splash screen will not be displayed. This prevents the hotfix from being installed. Copy the file to each computer or to a network share, log on to each computer, and then run the file.
File informationThis hotfix package may not contain all the files that you must have to fully update a product to the latest build. This hotfix package contains only the files that you must have to correct the issues that are listed in this article.
The English version of this hotfix package 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, x86-based versions
Collapse this tableExpand this table
System Center Operations Manager 2007, x64-based versions
Collapse this tableExpand this table
Additional information and known issues
After you do an in-place upgrade from Windows Server 2003 to Windows Server 2008 on a computer that is running an Operations Manager 2007 role or an Essentials 2007 role, reports do not display in the Operations Manager console or in the Essentials Administrator console.
Resolution for Issue 1
To resolve this issue, follow these steps:
Operations Manager 2007 or Essentials 2007 may fail during installation when the software tries to enumerate the installed SQL Server databases.
Cause of Issue 2
This issue can occur if the Windows Server 2008 Windows Internal Database feature is enabled. This dependent feature is enabled when any one of the following features is enabled:
In the Services.msc snap-in, locate and then start the s Windows Internal Database (MICROSOFT##SSEE) service. Then, reinstall Operations Manager 2007 or Essentials 2007.
An in-place upgrade of Windows Server 2003 to Windows Server 2008 will be blocked if PowerShell V1.0 (KB926139) is installed.
Workaround for Issue 3
To work around this issue, follow these steps:
When you install the SQL Server 2005 management pack, you receive a "Script or executable failed to run" alert for the DiscoverSQL2005DB.vbs script for database instance MICROSOFT##SSEE.
Cause of Issue 4
This issue occurs when the Windows Server 2008 Internal Database Feature is enabled. The associated Windows service (Windows Internal Database (MICROSOFT##SSEE)) is configured for manual startup. This behavior causes the SQL Server database engine discovery to fail.
Workaround for Issue 4
We recommend that you exclude this Windows Server 2008 internal SQL Server database from discovery. To do this, follow these steps:
When you open the Operations Console or the Web Console on a Windows Server 2008-based computer, you are asked for authentication when User Access Control (UAC is enabled)
Workaround for Issue 5
Open the Operations Console by using the "Run as administrator" option to open the Administrator console. Run Internet Explorer by using the "Run as administrator" option, and then provide the Web Console URL.
You may receive an error message when you open the Windows events log on a monitored Windows Server 2008 cluster. This issue prevents the Operations Manager 2007 SP1 agent from monitoring some Virtual Server installations that are running in a Windows Server 2008 cluster.
Workaround for Issue 6
An Operations Manager hotfix is available that resolves this issue. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/959865/ )Issues that are resolved by the Operations Manager Module rollup update for System Center Operations Manager 2007 Service Pack 1: June 10, 2009
The in-place upgrade of a Windows Server 2003-based computer that is hosting a System Center Essentials server to Windows Server 2008 is currently not supported.
Workaround for Issue 7
Support for in-place upgrades of System Center Essentials server roles from Windows Server 2003 to Windows Server 2008 is currently under investigation.
After you install the Web Console on a Windows Server 2008 computer, and you try to use the Mobile (http://<webconsoleserver>:51908/Mobile) or RSS (http://<webconsoleserver>:51908/RSS) links, you receive an HTTP Error 500.19 - Internal Server error that resembles the following:
The requested page cannot be accessed because the related configuration data for the page is invalid
When you review the Physical Path information on the returned IIS 7 error page, a double backslash is visible. For example:
C:\Program Files\System Center Operations Manager 2007\Web Console\\Mobile\login.aspxResolution for Issue 8
Within the Internet Information Services (IIS) Manager on the Web Console server, follow these steps:
For more information about configurations that support Operations Manager 2007, visit the following Microsoft TechNet Web site:
http://technet.microsoft.com/en-us/library/bb309428.aspxFor more information about system requirements for Essentials 2007, visit the following Microsoft Web site:
Article ID: 954049 - Last Review: July 23, 2009 - Revision: 9.1