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:

• The issues that the hotfix rollup package fixes
• The prerequisites for installing the hotfix rollup package
• Download information
• Hotfix installation information
• Whether you must restart the computer after you install the hotfix rollup package
• Whether the hotfix rollup package is replaced by any other hotfix rollup package
• How to extract the files
• The files that the hotfix rollup package contains
• Additional information and known issues

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:

Supported configurations

This hotfix provides support for the following scenarios:

• A clean installation of Operations Manager 2007 or Essentials 2007 on a Windows Server 2008-based computer
• An in-place operating system upgrade to Windows Server 2008 on a computer that has Operations Manager 2007 or Essentials 2007 installed in a supported configuration
  
  For more information about supported configurations for Operations Manager, visit the following Microsoft Web site:
  http://technet.microsoft.com/en-us/library/bb309428.aspx (http://technet.microsoft.com/en-us/library/bb309428.aspx)
  For more information about supported configurations for Essentials 2007, visit the following Microsoft Web site:
  http://www.microsoft.com/systemcenter/essentials/en/us/system-requirements.aspx (http://www.microsoft.com/systemcenter/essentials/en/us/system-requirements.aspx)

Issues that the hotfix package fixes

This hotfix package fixes the following issues that are not previously documented in a Microsoft Knowledge Base article:

Issue 1

When 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 2

The 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:

• The Web Console does not open.
• The My Workspace page does not display.
• Performance views do not display.

Issue 3

After 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 information

The following file is available for download from the Microsoft Download Center:

Download the 954049 package now. (http://www.microsoft.com/downloads/details.aspx?FamilyId=58529AF1-243D-41F5-B681-342AC04AA17B)

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: Microsoft 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.

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.

Prerequisites

Before you install hotfix 954049, you must comply with the following prerequisites:

• If you do an in-place upgrade of the operating system to Windows Server 2008 on a computer that has one of the Operations Manager 2007 or Essentials 2007 computer roles installed, you must complete the upgrade.
• For Windows Server 2008, you must either install Windows Server 2008 Service Pack 2 or the following hotfixes that are available separately for Windows Server 2008:
  
  951327  (http://kbalertz.com/Feedback.aspx?kbNumber=951327/ ) The System Center Operations Manager 2007 console may crash in Windows Server 2008 or in Windows Vista when you open the Health Explorer window
  952664  (http://kbalertz.com/Feedback.aspx?kbNumber=952664/ ) The Event Log service may stop responding because of a deadlock on a Windows Server 2008-based computer
  953290  (http://kbalertz.com/Feedback.aspx?kbNumber=953290/ ) An application may crash when it uses legacy methods to query performance counter values in Windows Vista or in Windows Server 2008
  951116  (http://kbalertz.com/Feedback.aspx?kbNumber=951116/ ) A memory leak occurs in performance counters that are used to monitor Windows Server 2008-based computers
  Note You must install the hotfixes that are mentioned in Knowledge Base articles 952664, 953290, and 951116 on the Root Management Server (RMS), on the Management Server, on the Gateway Server, and on computers on which the System Center Essentials server and agent roles are installed (or will be installed).

Restart requirement

You 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 information

This hotfix does not replace any other hotfixes.

Hotfix installation information

To install the hotfix, you must follow these rules:

• You must install the hotfix on computers that perform one or more of the following roles:
  • Root Management Server
  • Management Server
  • Gateway Server
  • Web Console Server
  • System Center Essentials Server
  • Agent
• On manually installed agent computers, you must manually install the hotfix.
• For automatically deployed agents, you can approve the upgrade in the Pending Management view on a server that has one of the following roles installed:
  • Root Management Server
  • Management Server
  • Gateway Server

How to extract the files

To extract the files from the hotfix package, you must run the following file: In 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 information

This 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

System Center Operations Manager 2007, x64-based versions

Additional information and known issues

Requirements

• After you install the Web Console Server role on a Windows Server 2008-based computer, you must restart the Internet Information Server (IIS) to make sure that the Web Console operates correctly.
• You must restart or stop the Windows services for Operations Manager 2007 or for Essentials 2007 in the following scenarios:
  • After you install hotfix 954049 on an Essentials 2007 server, you must manually restart the Essentials 2007 services.
  • Before you install hotfix 954049 on a clustered Root Management Server, you must stop the Operations Manager 2007 services in Cluster administrator. After you apply the hotfix to the active node, you must apply the hotfix to all other clustered RMS nodes.
  In both these scenarios, you must restart or stop the following services:
  • OpsMgr Config Service (OMCFG)
  • OpsMgr Health Service (HEALTHSERVICE)
  • OpsMgr SDK Service (OMSDK)

Issues

Issue 1
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:

1. Open Microsoft SQL Reporting Services Configuration Manager.
2. In Report Server Virtual Directory, select Apply default settings, and then click Apply.
3. In Report Manager Virtual Directory, select Apply default settings, and then click Apply
4. Notice that the Web Service Identity turns from a green check mark to a red "X." On that page, reset the AppPool option to its original setting, and then click Apply.
5. Open Internet Information Services (IIS) Manager (Inetmgr.exe), and then follow these steps:
   1. Select the Operations Manager 2007 Web Console site from the Sites node.
   2. Double-click the Handler Mappings icon in the Features view, and then look for a Microsoft .NET 1.1 mapping for the following file name extension:
      *.aspx
   3. Note the path of the executable, and then delete that mapping. For example, you may have to delete a mapping that resembles the following path:
      C:\Windows\Microsoft.Net\Framework\v1.1.4322\aspnet_isapi.dll
   4. In the Actions pane, click Add Script Map, and then type *.aspx in the Request path value box.
   5. Next to the Executable value box, click the ellipsis button (...) to locate the following file:
      aspnet_isapi.dll
      For example, the file is typically located in the following folder:
      C:\Windows\Microsoft.Net\Framework\v2.0.50727\aspnet_isapi.dll
   6. In the Sites node, click the Operations Manager 2007 Web Console site one more time, and then click the Restart option in the Actions pane.

Issue 2
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:

• Active Directory Rights Management Services
• Windows Server Update Services
• Windows System Resource Manager
• UDDI Services (Universal Description, Discovery, and Integration services)

Workaround for Issue 2
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.

Issue 3
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:

1. Uninstall the Operations Manager 2007 SP1 Command Shell feature by using Add/Remote Programs.
2. Use administrative credentials to uninstall PowerShell v1.0 (KB926139) before you upgrade to Windows Server 2008. (You must be the only user who is logged on to the computer when you remove PowerShell.)
3. After you upgrade to Windows Server 2008, add the PowerShell feature from the Features option of Server Manager.
4. After PowerShell is installed, reinstall the Operations Manager 2007 SP1 Command Shell from Operations Manager Setup.

Issue 4
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:

1. In the Operations Manager 2007 or Essentials 2007 Administration interface, move to the Authoring pane, and then click Object Discoveries under the Management Pack Objects node.
2. Click the Scope button on the toolbar, click View all targets, and then type SQL 2005 DB Engine in the Look for box.
3. Click the SQL DB Engine displayed target, and then click OK.
4. In the Object Discoveries pane, open the properties for the Discover SQL 2005 Database Engines (Windows Server) discovery.
5. Click the Overrides tab, click Windows Server in the For all objects of type field, and then click the Override button.
6. In the Override Properties dialog box, click New under the Management Pack section, to create a new management pack in which to store the override. Do not use the Default Management Pack to store the override.
7. Click to select the Exclude List parameter check box, type MICROSOFT##SSEE in the Override Setting box, and then click OK to apply the override.

Issue 5
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.

Issue 6
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:

Issue 7
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.

Issue 8
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:
When you review the Physical Path information on the returned IIS 7 error page, a double backslash is visible. For example: Resolution for Issue 8
Within the Internet Information Services (IIS) Manager on the Web Console server, follow these steps:

1. Under the Sites node, locate the Operations Manager 2007 Web Console site, and then expand the node.
2. Locate and then click the application named Mobile.
3. Click Basic Settings from the Actions menu or click Advanced Settings from the Content menu, and then locate the double backslash (\\) within the physical path.
4. Remove one of the backslash characters.
5. Perform the same operation for the RSS application.

For more information about configurations that support Operations Manager 2007, visit the following Microsoft TechNet Web site: For more information about system requirements for Essentials 2007, visit the following Microsoft Web site: