Support for Windows Server 2008 R2 and Windows 7 in System Center Operations Manager 2007

This article discusses support for the Windows Server 2008 R2 and Windows 7 operating systems with Microsoft System Center Operations Manager 2007 Service Pack 1 (SP1) and Operations Manager 2007 R2. The information includes management pack availability, known issues, and updates that will be released to address these issues.

Support is now available for running Operations Manager 2007 SP1 and Operations Manager 2007 R2 on the following operating systems:

• Windows Server 2008 R2
• Windows 7

The following table lists the Operations Manager roles and components that are supported on these operating systems.The updated Windows Server Operating System Management Pack (version 6.0.6667.0), which includes support for Windows Server 2008 R2, is available on the System Center Operations Manager 2007 Catalog (http://go.microsoft.com/fwlink/?LinkId=82105) Web site.

When updated management packs become available to support these operating systems and their features, they will be available on the System Center Operations Manager 2007 Catalog (http://go.microsoft.com/fwlink/?LinkId=82105) Web site and from the Operations Manager 2007 R2 Operations console.

Note No support for Windows Server 2008 R2 or Windows 7 will be provided with Microsoft Operations Manager 2005.

Known issues

Known issues with upgraded operating systems

The following known issues may occur if your operating system was upgraded to Windows Server 2008 R2. These issues will be fixed in updates that will be available in the future for Operations Manager 2007 SP1 and for Operations Manager 2007 R2.

Operations Manager services stop unexpectedly on a Root Management Server whose operating system was upgraded to Windows Server 2008 R2

Problem: After you upgrade the operating system on a Root Management Server to Windows Server 2008 R2, the following services may continue to stop unexpectedly:

• In Operations Manager 2007 SP1: The OpsMgr Config service and the OpsMgr SDK service
• In Operations Manager 2007 R2: System Center Management Configuration and System Center Data Access

In this case, some events are logged for these service terminations in the System log. These events have a source of "Service Control Manager" and an Event ID of 7031.

Impact: No SDK connectivity will be available. The Operations Console, Connectors, and any other SDK client connections will fail. Additionally, the Root Management Server will be unable to calculate or distribute new configurations, such as updates to group memberships, new or updated overrides, or management pack distribution.

Workaround:This issue is resolved for Operations Manager 2007 SP1 by applying the update rollup that is documented in the Knowlege Base (KB) article 971541. After an upgrade of the root management service (RMS) operating system to Windows Server 2008 R2 either apply, or reapply the update rollup to the RMS.

This issue is resolved for Operations Manager 2007 R2 by applying Cumulative Update 1 documented in the Knowlege Base (KB) article KB974144. After an upgrade of the root management service (RMS) operating system to Windows Server 2008 R2 either apply, or reapply the update rollup to the RMS.

The AdtServer service does not start after you upgrade the operating system to Windows Server 2008 R2

Problem: After you upgrade the operating system from Windows Server 2003 to Windows Server 2008 R2, the Adtserver service does not start. Additionally, the following event is logged:

Event ID: 4672
AdtServer encountered the following problem during startup:
Task: Open Audit Database
Failure: An error occurred connecting to the database
Error: 0x00000002
Error Message:
The system cannot find the file specified. Error2: The system cannot find the file specified when we attempt to start the service manually.

Impact: The service that performs the audit collection service (ACS) Server functions cannot start. This occurs for both Operations Manager SP1 and Operations Manager R2. During ACS startup, the location of the Open Database Connectivity (ODBC) driver that is used for the data source is queried to make sure that it matches the location that is used in setting up the data source name (DSN). In Windows Server 2008 R2, the registry parameter for the location of the database driver contains environment variables instead of the actual path. The DSN uses "C:\Windows\System32\Sqlsrv32.dll" and the SQL Server driver uses "%Windir%\System32\SQLSRV32.dll." When the Adtserver process compares these values on startup to make sure that they are the same, the Adtserver process finds them different. This occurs only during an operating system upgrade.

Workaround: Make the following registry change:On an Operations Manager 2007 R2 Audit Collection Services (ACS) server, apply Cumulative Update 1 (KB 974144) for the ACS server role before upgrading the ACS server operating system to Windows Server 2008 R2. If the KB 974144 update has already been applied to the ACS server role, the operating system can be upgraded without reapplying the KB 974144 update.

On an Operations Manager 2007 SP1 Audit Collection Services (ACS) server, apply the SP1 update rollup (KB 971541) for the ACS server role before upgrading the ACS server operating system to Windows Server 2008 R2. If the KB 971541 update has already been applied to the ACS server role, the operating system can be upgraded without reapplying the KB 971541 update.

Known issues with Operations Manager 2007 SP1

The following known issues may occur with Operations Manager 2007 on Windows Server 2008 R2 and Windows 7 operating systems.

Installation of the Operations Manager 2007 SP1 agent on Server Core installations of the 64-bit edition of Windows Server 2008 R2 fails with the error message "Windows Installer Service could not be accessed"

Problem: When you try to install the Operations Manager 2007 SP1 agent Server Core installations of the 64-bit edition of Windows Server 2008 R2, the operation fails, and you receive the following error message: This issue occurs because the Operations Manager 2007 SP1 setup for 64-bit systems has some components that must run in 32-bit emulation, and the required subsystem is not installed by default in a Server Core installation of Windows Server 2008 R2.

Impact: The installation does not complete.

Workaround: You can upgrade to Operations Manager 2007 R2. Or, follow these steps on each system on which this issue occurs:

1. Log on to the computer on which you want to install the agent.
2. Run the following command to install the necessary subsystem:
   Start /w ocsetup ServerCore-WOW64
   Note The Ocsetup.exe program takes case-sensitive parameters. Therefore, you must use type "ServerCore-WOW64" with the capitalization exactly as it appears here.
3. Restart the computer to complete the installation.
4. When the computer is back online, install the Operations Manager agent.
5. When the agent installation is complete, you can remove the ServerCore-WOW64 feature by using the /uninstall parameter of the Ocsetup.exe program because this feature is not required for the agent to function. However, you will have to restart the computer after you remove the ServerCore-WOW64 feature.

Note This issue will not be fixed in any updates for Operations Manager 2007 SP1. However, it is fixed in Operations Manager 2007 R2.

"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'"

Problem: When an Operations Manager 2007 SP1 agent is installed on a computer that is running Windows 7 or Windows Server 2008 R2, an alert may occur in the Operations console or an event may be logged on the computer that is being monitored. The alert reports that backward compatibility scripts failed.

The following are the details that are present in the alert and its corresponding event on the agent.

Log Name: Operations Manager
Source: Health Service Modules
Event ID: 9100
Level: Error
Description:
An error occurred on line 123 while executing script 'MOM Backward Compatibility Service State Monitoring Script' Source: Microsoft VBScript runtime error Description: Type mismatch: 'get'

Impact: Low. This occurs because Windows 7 and Windows Server 2008 R2 have some services that have null values that the script does not expect. Therefore, the script fails with an error. The services for which these scripts fail are not critical. Therefore, you can safely ignore this alert.

Workaround: Ignore the alert or upgrade to Operations Manager 2007 R2. This issue is resolved for Operations Manager 2007 SP1 by applying the update rollup that is documented in the KB article 971541.

Event ID 26017 from source "Health Service Modules" will be raised for Operations Manager 2007 SP1 agents, indicating "Event log Provider monitoring the <LogName> Event Log is # minutes behind," and the number of minutes is in the hundreds of millions.

Problem: When an Operations Manager 2007 SP1 agent is installed on a computer that is running Windows 7 or Windows Server 2008 R2, the following event may be logged in one or more event logs. Additionally, value for the number of minutes is very large.

Log Name: Operations Manager
Source: Health Service Modules
Event ID: 26017
Level: Warning
Description: The Windows Event Log Provider monitoring the %1 Event Log is %2 minutes behind in processing events. This can occur when the provider is restarted after it is offline for some time, or there are too many events to be handled by the workflow.

Impact: None. These events are generated because of the delta between timestamps is calculated incorrectly. The event log processing is actually working correctly, and the events can be ignored.

Workaround: No workaround is required. Ignore the events or upgrade to Operations Manager 2007 R2. This issue will be fixed in updates that will be available in the future for Operations Manager 2007 SP1.

Agent push installations fail occasionally on Windows Server 2008 R2 and Win7 with the error "A COM Proxy was called from the wrong context"

Problem: When you use the Discovery Wizard to perform a push installation of the Operations Manager 2007 SP1 agent on a Windows Server 2008 R2 or Window 7 system, the installation task may fail with an "A COM Proxy was called from the wrong context" error message.

Impact: You cannot install the agent on this system by using the Operations Manager 2007 Discovery Wizard.

Workaround: Log on to the system locally and perform a manual agent installation. For more information, visit the following Microsoft TechNet Web site: This issue is resolved for Operations Manager 2007 SP1 by applying the update rollup that is documented in the KB article 971541.

Known issues with Operations Manager 2007 SP1 and Operations Manager 2007 R2

Installation of the Web Console role on Windows Server 2008 R2 servers fails with "Unknown error (0x80005000)"

Problem: Installation of the Web Console role on Windows Server 2008 R2 fails with an "Unknown error (0x80005000)" error message.

Impact: The Web Console role cannot be installed.

Workaround: You must add the IIS 6 Management Compatibility component because it contains the prerequisites that are required for the installation and operation of the Operations Manager 2007 Web Console. To install the IIS 6.0 Management Compatibility Components by using Server Manager, follow these steps:

1. Click Start, click Administrative Tools, and then click Server Manager.
2. In the console tree, expand Roles, right-click Web Server (IIS), and then click Add Role Services.
3. In the Select Role Services pane, scroll down to IIS 6 Management Compatibility.
4. Click to select the IIS 6 Metabase Compatibility check box and the IIS 6 Management Console check box.
5. Click Next on the Select Role Services page, and then click Install on the Confirm Installations Selections page.
6. Click Close to exit the Add Role Services Wizard.

The prerequisite checker will detect this missing dependency in a future update for Operations Manager 2007 SP1 and Operations Manager 2007 R2.