Export (0) Print
Expand All

Operations Manager 2007 R2 Release Notes

Updated: January 6, 2010

Applies To: Operations Manager 2007 R2

These release notes apply to Microsoft System Center Operations Manager 2007 R2 and contain the most detailed information about how to deploy Operations Manager 2007 R2, and any known issues that you might experience. You can also find additional information, including updated product documentation, at the Operations Manager 2007 R2 TechNet library, available at http://go.microsoft.com/fwlink/?LinkId=150481.

The following sections provide detailed information:

Installation and Upgrade

You might see the following issues during an installation or upgrade of Operations Manager 2007 R2.

Baseline monitors might get unloaded after you upgrade a management server

Baseline monitors might be unloaded after a management server is upgraded to Operations Manager 2007 R2 but before the agents are upgraded. If this occurs, Error and Warning events will be written to the event log and will indicate that performance monitors were unloaded. During this time, Operations Manager 2007 R2 will no longer monitor those performance counters.

Workaround: This issue is resolved as soon as the agents are upgraded. Upgrade any agents that are managed by the upgraded server as soon as possible.

Operations console might not upgrade successfully

On Operations Manager 2007 SP1 and Operations Manager 2007 R2 RC servers that have both the Web console and the Operations console installed, if you uninstall the Web console before you upgrade to Operations Manager 2007 R2, the Operations console does not upgrade completely.

Workaround: Do one of the following, depending on whether you have already upgraded:

  • If you have not yet upgraded: Reinstall the Operations Manager User Interface and Command Shell features by using the Modify option in the Add or Remove Programs tool.

  • If you have already upgraded and are seeing this problem: Use the Add or Remove Programs tool to install the User Interface feature.

Web console upgrade – Security issue

After you upgrade to Operations Manager 2007 R2, you might have to make the following changes to the web.config file for the Web.

Operations Manager 2007 SP1 to Operations Manager 2007 R2 upgrade

Edit the web.config file to change the identity element to false:

  1. Edit the web.config file that is located in the \WebConsole subdirectory in the location where you installed Operations Manager 2007.

  2. Locate the following line in the file: <identity impersonate ="true" />

  3. Change “true” to “false” as shown: <identity impersonate ="false" />

Operations Manager 2007 R2 RC to Operations Manager 2007 R2 upgrade

Edit the web.config file to add the viewStateEncryptionMode attribute:

  1. Edit the web.config file that is located in the \WebConsole subdirectory in the location where you installed Operations Manager 2007.

  2. Locate the following line in the file: <pages validateRequest="false">

  3. Change the line as follows, to add the viewStateEncryptionMode attribute: <pages validateRequest="false" viewStateEncryptionMode="Always">

You cannot upgrade from the Evaluation or DEM version of Operations Manager 2007 to Operations Manager 2007 R2

If you originally installed the Evaluation or DEM version of Operations Manager 2007 (RTM) and subsequently used the licensing wizard to change the license to Select, and you then upgraded to Operations Manager 2007 SP1, upgrading to Operations Manager 2007 R2 will fail unless you use the following steps:

  1. Run the SetupOM.exe file from the Operations Manager SP1 installation media.

  2. Choose Install Operations Manager 2007. You will be prompted to upgrade.

  3. Select Upgrade to Operations Manager 2007 SP1 and click Next.

  4. Finish the installation wizard.

You can now upgrade to Operations Manager 2007 R2 using the procedure documented in the Upgrade Guide.

Workaround: Follow the process above for upgrading to Operations Manager 2007 SP1. Notice that you must have the full Operations Manager 2007 SP1 installation image in order to follow this process.

Cross Platform Installation and Usage

You might see the following issues when you install and use Cross Platform agents.

Upgrading an environment that has cross-platform monitoring deployed

If you have previously deployed the beta version of cross-platform monitoring on Operations Manager 2007 SP1 (or an early release of Operations Manager 2007 R2), you must perform the following steps before you upgrade your environment to Operations Manager 2007 R2:

  • Delete any monitored UNIX and Linux agents from Operations Manager. You do not have to uninstall the agent. Instead, delete the agents by using the Operations console.

  • Delete the Cross Platform Management Packs. These will be replaced by newer versions.

  • Uninstall Cross Platform extensions.

After you upgrade to Operations Manager 2007 R2, you can re-discover agents by using the Discovery wizard.

WS-Man 1.1 requirement

Operations Manager 2007 R2 requires WS-Man 1.1, also known as WinRM, to monitor computers that are running UNIX and Linux operating systems. WS-Man is a Web service-based protocol that enables remote computer management over HTTP and HTTPS, which includes hardware management and policy-based event forwarding. WS-Man 1.1 must be installed to facilitate communication between Operations Manager 2007 and UNIX or Linux computers.

noteNote
WS-Man is only required if you are monitoring UNIX or Linux computers.

You can download WS-Man 1.1 from http://go.microsoft.com/fwlink/?LinkId=103610.

After you have installed WS-Man on the management server, configure it to use Basic Authentication. Run the following command:


winrm set winrm/config/client/auth @{Basic="true"}

If you do not configure WS-Man to allow Basic authentication, discovery of UNIX or Linux computers will fail.

You receive an error message about transaction lock during Linux agent installation

When you are installing the Linux agent, you might see the following error message in the standard output for the rpm:

error: can't create transaction lock on /var/lib/rpm/__db.000

This is caused by installing the agent as a non-root user. The installation of the agent requires root privileges.

Workaround: When you run discovery, specify the root user. If your system does not allow root logins over SSH, you can also specify a non-root user, clear the This is a superuser account option and enter the root password.

If you cannot use a root user for installation, read the deployment and security guides on how to install manually.

Existing security certificates are not deleted during agent installation on a UNIX or Linux computer

If there are existing certificates on the system, they are reused during agent installation. New certificates are not created. Certificates are not automatically deleted when you uninstall an agent.

Workaround: Manually delete the certificates. The certificates can be found under /etc/opt/microsoft/scx/ssl. This folder can be removed before agent installation to regenerate the certificates at install.

For more information about how to create and manage certificates in Operations Manager 2007 R2, see the Operations Manager 2007 R2 Security Guide, available at http://go.microsoft.com/fwlink/?LinkId=150914.

Running the Recovery task for Logical disks fails on UNIX or Linux computers

When you run the Recovery task for a Logical disk on a UNIX or Linux computer, the task seems to run but no output is returned. In reality, the task is not run.

Workaround: Upgrade to the 6.2 SP2 version of MSXML. You can download MSXML 6.2 SP2 from KB955218, available at http://go.microsoft.com/fwlink/?LinkId=151505.

WinRM loaded by the Health service fails, and an error message appears that says that the Registry key is marked for deletion

If a user uses a domain account for the Default Action Account and that user is logged on interactively when the Health service is started and later the user logs off, then monitoring fails. Windows will unload the registry of that user, and WinRM, loaded by the Health service, fails with an error that the Registry key is marked for deletion. This issue occurs on Windows Server 2008, as well as on other versions of Windows if the User Profile management add-on is installed.

Workaround: Associate the Default Action Account Run As profile with Local System or a domain account that never logs in interactively on the management server that is used to monitor UNIX or Linux computers.

Operations

You might see the following issues when you use Operations Manager 2007 R2.

Alert descriptions that contain HTML tags are displayed incorrectly

After you upgrade from Operations Manager 2007 SP1 to Operations Manager 2007 R2, alert descriptions that are formatted with HTML tags such as the <br> or <hr> tag are not displayed correctly.

In previous versions of Operations Manager, the alert description was parsed as an HTML page. In Operations Manager 2007 R2, the ability to format alert descriptions by using HTML tags was removed due to security issues; the HTML tags are now shown as text.

In Operations Manager 2007 R2, you can use carriage returns directly within the alert description instead of the HTML tags.

Run As accounts created in Operations Manager 2007 SP1 are marked as “More Secure” and have an empty distribution list

When you upgrade Operations Manager 2007 SP1 to Operations Manager 2007 R2, existing Run As accounts are configured with the More Secure distribution option, but the Selected Computers list (on the Distribution tab of the Run As account’s properties) is empty.

Workaround: None needed. The account will continue to function without problem, as long as it has a System type association targeted to a Health Service in the Run As profile in which it is used. Typically, Run As accounts that are created by using Operations Manager 2007 R2 and that are configured with the More Secure option must be correctly distributed by adding the correct computer in the Selected Computer list.

An error might occur when you use the Operations console and attempt to connect to an upgraded root management server

When you use the Operations console to connect to an upgraded root management server (that is running Operations Manager 2007 R2), the following error message might display:

“Server version ('6.1.XXXX.X') installed on management group <management group name> does not match assembly version ('6.1.XXXX.X').”

or

“Failed to connect to server "RMS hostname." You have attempted to connect to a server which is incompatible with your Operations console. Please ensure both client and server are using compatible Microsoft-signed versions of the software.”

Workaround: Upgrade the Operations console to Operations Manager 2007 R2. If this is not practical, you can disable version checking by using the following procedure:

  1. Close the Operations console.

  2. On the Windows desktop, click Start, and then click Run.

  3. Type regedit, and then click OK to start Registry Editor.

    CautionCaution
    Incorrectly editing the registry can severely damage your system. Before you make changes to the registry, you should back up any valued data that is on the computer.

  4. Browse to HKey_CURRENT_USER\Software\Microsoft\Microsoft Operations Manager\3.0\Console.

    CautionCaution
    Ensure that you are not making changes to the HKEY_LOCAL_MACHINE version.

  5. Right-click Console, click New, and then click Key.

  6. Rename New Key #1 to ManagementGroupSessionManager, and then press ENTER.

  7. Right-click ManagementGroupSessionManager, click New, and then click DWORD Value.

  8. Rename New Value #1 to DisableServerVersionCheck, and then press ENTER.

  9. Right-click DisableServerVersionCheck, and then click Modify.

  10. In the Edit DWORD Value dialog box, in the Value data text box, type the number 1 (decimal, not hexadecimal), and then click OK.

The Web console does not open and you receive a “Server Error” message

If you install the Web console component after the UI console has already been installed, the Web console will not open. Instead, you will receive the following error:

“Server Error in ‘/’ Application”

Workaround: Copy the following files from the %Program Files%\System Center Operations Manager 2007 directory to the %Program Files%\System Center Operations Manager 2007\Web Console\Bin directory:

Corgent.Diagramming.CommandResources.dll

Corgent.Diagramming.CustomElements.dll

Microsoft.ReportViewer.Common.dll

Microsoft.ReportViewer.Webforms.dll

The Operations console crashes during discovery of UNIX or Linux computers

The Operations console might crash while you are running discovery for UNIX or Linux computers.

Workaround: Ensure that you have Microsoft .NET Framework 3.5 installed. You can download Microsoft .NET Framework 3.5 from http://go.microsoft.com/fwlink/?LinkId=136754.

The Operations console crashes in Windows Server 2008 or in Windows Vista when you open the Health Explorer

In an Operations console that is installed on Windows Vista or Windows Server 2008, the console might crash when you right-click an item in the Alerts view to open the Health Explorer.Because of this, you cannot use Health Explorer to view any monitored objects in Windows Server 2008 or in Windows Vista.

This issue is caused by a problem in the Tooltip module, which does not correctly check the NULL condition.

Workaround: Download and apply the hotfix from KB951327, available at http://go.microsoft.com/fwlink/?LinkId=150873.

You cannot uninstall or delete an agent from a node in a cluster

When you try to uninstall or delete an agent from a node in cluster, the following error message is displayed:

Agent is managing other devices and cannot be uninstalled. Please resolve this issue via Agentless managed view in Administration prior to attempting uninstall again.

Notice that the agent can be uninstalled from the node that is agentlessly managing the virtual servers. However, the agent cannot be uninstalled from the node that is managing the virtual servers.

Workaround: None at this time.

Uninstalling the ACS collector is reported to fail despite actually being uninstalled

When you uninstall the Audit Collection Services (ACS) Collector by using the OMSetup.exe file, you see the following status:

Stop ADTServier Services: Success
Unregister Performance DLL: Success
Unregister Application Log: Success
Delete AdtServer Service: Success
UnInstall ACS: Failure [0x00000645]

Workaround: None. You can safely ignore the message. The ACS Collector has been uninstalled.

ACS events have “n/a” as their category in the ACS database

For some Windows Server 2008 events, ACS might record their event category as “n/a.”

Workaround: You can look up the event source and ID to determine the event’s category.

The Web console always defaults to port 51908

When you start the Web console, the URL that is used by the Web console always includes port 51908. If you used a command-line install to deploy the Web console server to a port other than the default of 51908, the Web console will fail to connect to the Web Console server.

Workaround: Start the Web console and manually edit the port number in the Address line to match the port number that you used to deploy the Web console server.

Searches against the Data Warehouse return invalid results that are inconsistent with your search criteria

Searches for certain types against the Data Warehouse return some invalid results that are inconsistent with the specified search criteria. For example, if you choose to search by Begins with and specify M as the criteria, the search results return all of the types beginning with “M” as well as another type, "System.Mom.BackwardCompatibility.ScriptDiscoveredComputerGroup."

This is caused by a problem in Microsoft SQL Server 2008.

Workaround: Download and install the hotfix available in KB 958214, at http://go.microsoft.com/fwlink/?LinkId=150900.

Clicking on links in Service Level Tracking Summary report could display incorrect information in the Service Level Objective Detail Report

If you use links in the Service Level Tracking Summary report to drill into the Service Level Objective Detail report, the wrong parameters might be passed and the Service Level Objective detail report will display information for the wrong service level.

Workaround: Expand all rows in the summary report before you click on any of the links to drill down to the detail report. See KB971406, available at http://go.microsoft.com/fwlink/?LinkId=151823, for additional information about this issue.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft