Operations Manager 2007 Release Notes

  • Article

Important

These release notes are created for Operations Manager 2007. Please read these release notes thoroughly before you install Operations Manager 2007 or begin importing and using Management Packs. For any updates to these release notes, see https://go.microsoft.com/fwlink/?LinkId=85633.

64-bit Compatibility

64-bit ASP.NET Applications Running on 64-bit Windows Platforms Cannot Be Monitored Using the ASP.NET Management Pack.

If a user selects a 64-bit ASP.NET application using 'ASP.NET Web application' and 'ASP.NET Web service" Management Pack templates, the application will not be monitored. Delete the application from the Management Pack template list.

Workaround: None.

Setup

Setup Will Fail If the Initial System Center Operations Manager 2007 Setup Window is Closed During Installation

Closing the initial setup window during installation causes setup to fail.

Workaround: Run setup again, and do not close the setup window during installation.

The Prerequisite Checker Might Return a Failure Indicating That ASP .NET 2.0 Is Missing

The Prerequisite Checker might return a failure indicating that ASP .NET 2.0 is missing. This failure occurs if you install Internet Information Services (IIS) after you have installed .NET Framework 2.0. If you install .NET Framework 2.0, then install IIS while selecting ASP .NET 2.0 as an optional component, the ASP .NET 2.0 extensions might not be registered in the IIS metabase.

Workaround: Go to the \Windows\Microsoft.NET\Framework\v2.0.50727 folder and from a command prompt, run the command aspnet_regiis.exe –i –enable.

Agentless Exception Monitoring

Cannot Change the Polling Interval for Alert Aging Notification Subscriptions

The default polling interval for alert aging notification subscriptions is 15 minutes. This value cannot be changed to any value less than 15 minutes.

Workaround: None.

The Create File Share Task in the Client Monitoring Configuration Wizard Might Stop with an "Access to <path> is denied" Error

When running the Client Monitoring Configuration Wizard, the Create File Share task might fail with an error indicating that access to the <path> is denied.

Workaround: Run the Client Monitoring Configuration Wizard again, and on the Create File Share page, select Other user account, and then enter an account that has sufficient privileges to write to the intended file share.

Operations Console

A "Failed to retrieve view from the server" Error Might Be Displayed When Selecting Dashboard Views

A "Failed to retrieve view from the server. An object of type ManagementPackView with id <GUID> was not found" error might display when a dashboard view is selected.

Workaround:Grant permission for the dashboard view to the user role again from the Views tab in the User Role Properties dialog box

Web Console

Users Are Denied Access Connecting to the Web Console Using Windows Authentication When the Web Console Is Not Installed on the Root Management Server

Users are unable to remotely access a Web Console which has been configured for Windows Authentication when the Web Console has not been installed in the Root Management Server.

Workaround: The following two solutions are available.

  1. Configure the Web Console for Forms-based Authentication and install the Web Console on a standalone server.
  2. Configure the Web Console for Windows authentication and install the Web Console on the Root Management Server.

Diagram Views Containing More Than 400 Nodes Might Take an Excessive Amount of Time to Display When Viewed on the Web Console

When using the Web Console, a diagram view containing more than 400 nodes might take an excessive amount of time to display.

Workaround: Use the Operations Manager Console to view diagrams containing large numbers of nodes.

Monitoring

A User Might Receive Multiple Alerts When Multiple Rules Match a Single Alert

If multiple rules match a single alert and these rules are configured to notify the same e-mail address, the user will receive multiple notifications for the alert.

Workaround: Ensure that the recipient is not configured for multiple subscriptions that may have overlapping criteria.

Computer May Not Come Out of Maintenance Mode at the Scheduled Time

When maintenance mode is complete, there can be a delay of up to five minutes before maintenance mode is reported in the Operations Console.

Workaround: None.

You Need to Manually Restart the OpsMgr Health Service if a Virtual Server Is Modified or Deleted

If you add or delete a new virtual server on a cluster after an Operations Manager 2007 agent is installed, the agent does not recognize the changes and new virtual servers are not reported.

Workaround: Restart the OpsMgr Health Service on the node where the virtual server is active.

State Calculation Might Be Delayed When a New Group or Distributed Application Is Created

In a large deployment of Operations Manager, there might be a delay between the time a new group or a distributed application is created and when its state is calculated. Until rollup configuration is calculated, the state will be displayed as unmonitored (white icon).

Workaround: None.

Reporting

A "Could not verify if current user is in sysadmin Role" Error Might Be Displayed When Installing the Reporting Server

A "Could not verify if current user is in sysadmin Role" error might be displayed when installing Reporting if the reporting server and the Root Management Server are separated by a firewall. This error message might be displayed even if the proper firewall ports have been opened. This error occurs after entering the computer name for the Root Management Server and clicking Next. This error might be displayed because Reporting setup was unable to connect to the Operations Manager database on the Root Management Server.

Workaround: Use the following procedures to determine what port SQL Server is using, and then enter that port number into the dbo.MT_ManagementGroup table. It is assumed in the following procedures that the Operations Manager database is located on computer\INSTANCE1.

How to determine the port number used by SQL Server

  1. On the Windows desktop, click Start, point to Programs, point to Microsoft SQL Server 2005, point to Configuration Tools, and then click SQL Server Configuration Manager.

  2. In the SQL Server Configuration Manager dialog box, expand SQL Server 2005 Network Configuration, and then click Protocols for INSTANCE1.

  3. In the results pane, right-click TCP/IP, and then click Properties.

  4. In the TCP/IP Properties dialog box, click the IP Address tab, expand IPAll and make note of the port number listed next to TCP Dynamic Ports, and then click OK.

  5. Click File, and then click Exit.

How to enter the SQL Server port number into the dbo.MT_ManagementGroup table

  1. On the Windows desktop, click Start, point to Programs, point to Microsoft SQL Server 2005, and then click SQL Server Management Studio.

  2. In the Connect to Server dialog box, in the Server Type list, select Database Engine; in the Server Name list, select the server and instance for your Operations Manager database (for example, computer\INSTANCE1); in the Authentication list, select Windows Authentication; and then click Connect.

  3. In the Object Explorer pane, expand Databases, expand OperationsManager, and then expand Tables.

  4. Right-click dbo.MT_ManagementGroup, and then click Open Table.

  5. In the results pane, scroll to the right to the column titled SQLServerName_<guid>.

  6. In the first row, enter computer\INSTANCE1 followed by a comma, a space, and then the SQL Server port number (for example, computer\INSTANCE1, 1140).

  7. Click File, and then click Exit.