Support for System Center Operations Manager 2007 R2 that runs on a SQL Server 2008 R2 database

The support is divided into two phases. Phase one supports new installations of System Center Operations Manager 2007 R2. Phase two supports upgrading an existing System Center Operations Manager 2007 R2 deployment to run on a SQL Server 2008 R2 database. The existing deployment has database roles hosted on a Microsoft SQL Server 2005 Service Pack 3 (SP3) server or on a Microsoft SQL 2008 Service Pack 1 (SP1) server.

This article talks about the support for phase one. Please see KB2449679 for support on phase two.   

High level steps for a new installation

1. Use the DBCreateWizard tool to install the OperationsManager database.
2. Install the first management server in the management group that was specified in step 1.
   For more information, see the System Center Operations Manager R2 Deployment guide.
   
   Important When you install the first management server, you should not install the Database component.
3. Use the DBCreateWizard tool to install the OperationsManagerDW database.
4. Install System Center Operations Manager 2007 R2 Reporting.
   1. On the SQL Server Reporting Services server, rename the local group SQLServerReportServerUser$<hostname>$MSSRS10_50.<SQLInstanceName> to SQLServerReportServerUser$<hostname>$MSSRS10.<SQLInstanceName>
   2. Install System Center Operations Manager 2007 R2 Reporting.
      
      Important When you install System Center Operations Manager 2007 R2 Reporting, you should not install the Data Warehouse component.
   3. Rename the local group SQLServerReportServerUser$<hostname>$MSSRS10.<SQLInstanceName> back to original name SQLServerReportServerUser$<hostname>$MSSRS10_50.<SQLInstanceName>

How to use the DBCreateWizard tool to install the OperationsManager database

Note You must run the DBCreateWizard tool on the server that is running SQL Server 2008 R2.

1. Open the <InstallationMedia>\SupportTools\AMD64 folder
   Note <InstallationMedia> represents installation media of System Center Operations Manager 2007 R2.
2. Double-click the DBCreateWizard.exe file to start the Database Configuration Wizard.
   Note You may receive an error message when you start the wizard.
   For more information, click the following article number to view the article in the Microsoft Knowledge Base:
   938997 Operations Manager 2007 Support Tools requirements
3. On the Welcome page, click Next.
4. On the Database Information page, perform the following operations:
   • Under Database Type, select Operations Manager Database.
   • Under Full Database Instance Name, select the instance of SQL Server where you want the database to be installed.
     Note An instance of SQL Server has the name of <ServerName>\<InstanceName>. The default instance has the name of <ServerName>.
   • Leave the Create New Database option selected.
   • Leave the SQL Port box blank.
     Note If you do not provide a port, the Database Configuration Wizard uses the port 1433 to connect to SQL Server. However, if the instance of SQL Server that you specify uses a port other than 1433 for connection, you must specify the port in the SQL Port box.
   • By default, the database name is OperationsManager under Database Name.
   • By default, the database size is 500 megabyte (MB) under Database Size.
5. Click Next.
6. On the Management Group page, perform the following operations:
   • Under Management Group name, specify a name for the management group.
   • By default, the BUILTIN\Administrators user group is specified under Configuration Administrator. If you want to specify a different user group, follow these steps:
     1. Click Browse.
     2. In the Select Group dialog box, click Locations.
     3. In the Locations dialog box, select the domain that contains the user group that you want to specify, and then click OK.
     4. Under Enter the object name to select, type the user group, and then click Check Names.
     5. If the name that you typed becomes underlined, click OK.
     For more information, see the "Before you Start" section of the following Microsoft TechNet website:
     http://technet.microsoft.com/en-us/library/dd789046.aspx
7. On the Error Reporting page, optionally indicate whether you want to send error reports to Microsoft, and then click Next.
8. On the Summary page, review the configuration summary, and then click Finish.

How to use the DBCreateWizard tool to install the OperationsManagerDW database

Note You must run the DBCreateWizard tool on the server that is running SQL Server 2008 R2.

1. Open the <InstallationMedia>\SupportTools\AMD64 folder
   Note <InstallationMedia> represents installation media of System Center Operations Manager 2007 R2.
2. Double-click the DBCreateWizard.exe file to start the Database Configuration Wizard.
   Note You may receive an error message when you start the wizard.
   For more information, click the following article number to view the article in the Microsoft Knowledge Base:
   938997 Operations Manager 2007 Support Tools requirements
3. On the Welcome page, click Next.
4. On the Database Information page, perform the following operations:
   • Under Database Type, select Operations Manager Data Warehouse Database.
   • Under Full Database Instance Name, select the instance of SQL Server where you want the database to be installed.
     Note An instance of SQL Server has the name of <ServerName>\<InstanceName>. The default instance has the name of <ServerName>.
   • Leave the Create New Database option selected.
   • Leave the SQL Port box blank.
     Note If you do not provide a port, the Database Configuration Wizard uses the port 1433 to connect to SQL Server. However, if the instance of SQL Server that you specify uses a port other than 1433 for connection, you must specify the port in the SQL Port box.
   • By default, the database name is OperationsManagerDW under Database Name.
   • By default, the database size is 500 megabyte (MB) under Database Size.
5. Click Next.
6. On the Summary page, review the configuration summary, and then click Finish.
   

How to install System Center Operations Manager 2007 R2 Reporting

Note You must follow these steps on the SQL Server Reporting Services server.

1. Open Computer Management.
2. In the Computer Management MMC snap-in, expand System Tools, expand Local Users and Groups, and then click Groups.
3. Locate the following group:
   SQLServerReportServerUser$<hostname>$MSRS10_50.<SQLInstanceName>
4. Rename the group to the following by removing "_50" from the group name:
   SQLServerReportServerUser$<hostname>$MSRS10.<SQLInstanceName>
5. Install System Center Operations Manager 2007 R2 Reporting.
   For more information, see the following Microsoft TechNet Website:
   http://technet.microsoft.com/en-us/library/bb432143.aspx
   
   Important When you install System Center Operations Manager 2007 R2 Reporting, you should not install the Data Warehouse component.
6. After you install System Center Operations Manager 2007 R2 Reporting, rename SQLServerReportServerUser$<hostname>$MSSRS10.<SQLInstanceName> back to original name SQLServerReportServerUser$<hostname>$MSSRS10_50.<SQLInstanceName>

Supported configurations for System Center Operations Manager 2007 R2

For more information about supported configurations for Operations Manager 2007 R2 that runs on a SQL Server 2008 R2 database, visit the following Microsoft Website:

Known issues

The following are the knows issues for System Center Operations Manager 2007 R2 that runs on a SQL Server 2008 R2 database.

Issue 1

You log on the computer by using an account that is a member of the Operations Manager Report Operators role. Additionally, the account is not a member of the Operations Manager Administrators role. In this case, scheduled reports cannot run successfully.

Note This problem does not occur if the account is a member of the Operations Manager Administrators role.

This problem occurs because the user name and password that are specified to run scheduled reports are corrupted. To work around this problem, manually reset the user name and password for each scheduled report before the reports run.

Issue 2

The Alert View window does not open when you click the Alert View link in the notification emails. No workaround for this is available currently.