Share via

  • Article

How to Upgrade an Operations Manager 2007 R2 Single-Server Management Group

 

Updated: May 13, 2016

Applies To: System Center 2012 R2 Operations Manager, System Center 2012 - Operations Manager, System Center 2012 SP1 - Operations Manager

When you upgrade a System Center Operations Manager 2007 R2 single-server management group to System Center 2012 – Operations Manager, all features that are installed on the server are upgraded. This includes the Operations Manager 2007 R2 operational database, management server, operations console, web console, and Reporting server, if installed. The Operations Manager 2007 R2 data warehouse is also upgraded, if it exists. Otherwise, the System Center Operations Manager 2012 Setup Wizard installs it.

Important

Before you follow any of these procedures, make sure that you verify that the servers in your Operations Manager 2007 R2 management group meet the minimum supported configurations for System Center 2012 – Operations Manager. This will help you determine whether you need to add any new servers to your management group before you upgrade. For more information, see Supported Configurations for System Center 2012 – Operations Manager.

If your single-server management group meets the supported configuration requirements, but you do not want to experience any downtime during the upgrade process, you can add a secondary management server, and then follow the upgrade process for a distributed upgrade. For more information, see Supported Configurations for System Center 2012 - Operations Manager. If your server cannot meet the supported configurations because it requires new hardware, you can add a secondary management server, and then follow the upgrade process for a distributed upgrade. For more information, see Upgrade Path Checklists for Operations Manager.

To upgrade a single-server management group

  1. Log on to the computer that is hosting a root management server (RMS) with an account that is a member of the Operations Manager Administrators role for your Operations Manager 2007 R2 management group and a local administrator on the computer.

  2. On the System Center 2012 – Operations Manager media, run Setup.exe, and then click Install.

    Note

    The Getting Started page displays information about what will be upgraded. The Operations Manager data warehouse will be installed if it does not already exist. Click Next to proceed with the upgrade.

  3. On the Getting Started, Please read the license terms page, read the Microsoft Software License Terms, click I have read, understood, and agree with the license terms, and then click Next.

  4. On the Select installation location page, accept the default value of C:\Program Files\System Center 2012\Operations Manager, or type in a new location or browse to one. Then click Next.

  5. On the Prerequisites page, review and address any warnings or errors that the Prerequisites checker returns, and then click Verify Prerequisites Again to recheck the system.

    Note

    Microsoft SQL Server Full Text Search must be enabled.

    Note

    The Agent Upgrade Check warning can be ignored if you plan to upgrade the agents after the single-server management group has been upgraded.

  6. If the Prerequisites checker does not return any other errors or warnings that have to be addressed, click Next.

  7. If the single-server management group does not already have a data warehouse installed, a data warehouse is created, and you must configure it as follows:

    1. On the Configure the data warehouse database page, in the Server name and instance name box, type the server name of the SQL Server database and instance for the database server that will host the data warehouse database.

    2. After you have typed in the correct values for the server name of the SQL Server database, Setup attempts to validate the values that you have typed as the SQL Server name and the port number. In the Database name, Database size (MB), Data file folder, and Log file folder boxes, we recommend that you accept the default values. Click Next.

      Warning

      These paths do not change if you connect to a different instance of SQL Server.

    3. On the Configuration, Specify a web site for use with the Web console page, select the Default Web Site, or the name of an existing website. Select Enable SSL only if the website has been configured to use Secure Sockets Layer (SSL), and then click Next.

    4. On the Configuration, Select an authentication mode for use with the Web console page, select your options, and then click Next.

  8. On the Configuration, Configure Operations Manager accounts page, we recommend that you use the Domain Account option for the System Center Configuration service and System Center Data Access service accounts. Enter the credentials for a domain account in each box, and then click Next.

    Important

    If you receive a message about using the wrong version of SQL Server, or experience a problem with the SQL Server Windows Management Instrumentation (WMI) provider, you can resolve this. Open a Command Prompt window by using the Run as administrator option. Then run the following command, where <path> is the location of Microsoft SQL Server:

    mofcomp.exe “<path>\Microsoft SQL Server\100\Shared\sqlmgmproviderxpsp2up.mof”.

  9. When the Ready to Upgrade page appears, review the upgrade summary, and then click Upgrade.

To upgrade a single-server management group by using the Command Prompt window

  1. Log on to the computer that is hosting a RMS with an account that is a member of the Operations Manager Administrators role for your Operations Manager 2007 R2 management group and a local administrator on the computer.

  2. Open a Command Prompt window by using the Run as Administrator option.

  3. Change the path to where the System Center 2012 – Operations Manager Setup.exe file is located.

    Important

    Use the /WebConsoleUseSSL parameter only if your website has Secure Sockets Layer (SSL) activated. For a default web installation, specify Default Web Site for the /WebSiteName parameter.

    Note

    If the web console reports to an unsupported or inaccessible root management server, you must also pass the following parameter: /ManagementServer:<servername>.

    Important

    The following commands assume that you specified the Local System for the Data Access service (/UseLocalSystemDASAccount). To specify a domain\user name for these accounts, you must provide the following parameters instead:

    /DASAccountUser: <domain\username> /DASAccountPassword: <password>

    If you installed a data warehouse in your Operations Manager 2007 R2 management group, use the following command.

      setup.exe /silent /upgrade /UseLocalSystemDASAccount
  /WebsiteName: "<WebSiteName>" [/WebConsoleUseSSL]
  /WebConsoleAuthorizationMode: [Mixed|Network]

    If you did not install a data warehouse in your Operations Manager 2007 R2 management group, use the following command.

      Setup.exe /silent /upgrade /UseLocalSystemDASAccount
  /AcceptEndUserLicenseAgreement
  /WebsiteName: "<WebSiteName>" [/WebConsoleUseSSL]
  /WebConsoleAuthorizationMode: [Mixed|Network]
  /DWSqlServerInstance: <server\instance> 
  /DWDatabaseName: <DW name>
  /DataReaderUser: <domain\username>
  /DataReaderPassword: <password>
  /DataWriterUser: <domain\username>
  /DataWriterPassword: <password>