Upgrading from Operations Manager 2007 SP1 to R2
Applies To: Operations Manager 2007 R2
Use the following procedures to upgrade an Operations Manager 2007 SP1 environment to Operations Manager 2007 R2.
Important
Before you follow any of these procedures, make sure that you have completed all of the tasks outlined in Preparing to Upgrade Operations Manager 2007.
The procedures listed in this section are presented in the order in which they must be completed. Most procedures must be completed on the computer that hosts the component being upgraded.
Upgrading System Center Desktop Error Monitoring to System Center Operations Manager 2007 R2
Start with Microsoft System Center Desktop Error Monitoring SP1 (build 6278). Upgrade to System Center Desktop Error Monitoring R2 by using the System Center Desktop Error Monitoring SetupOM.exe and following the instructions in this guide. After you upgrade to System Center Desktop Error Monitoring R2, you can convert to System Center Operations Manager 2007 R2 by starting Microsoft System Center Operations Manager 2007 R2 SetupOM.exe.
Upgrade Evaluation Copies
To upgrade to the licensed version of Operations Manager 2007 R2, you must run the Setup Wizard by double-clicking SetupOM.exe on the root management server.
Upgrade the Root Management Server to Operations Manager 2007 R2
You can upgrade the root management server (RMS) by using either the standard setup interface or the command-line tool. Procedures for upgrading an RMS that is installed on a single server and for an RMS that is a located on a cluster are provided.
The procedure to upgrade the RMS from Operations Manager 2007 SP1 to Operations Manager 2007 R2 is performed locally on the RMS or locally on the nodes of the cluster that contains the RMS. In both procedures, the Operations Manager database is also upgraded, even when the Operations Manager database is on a server that is separate from the server that hosts the RMS. If you intend to install an agent on the server that hosts the stand-alone Operations Manager database, you must run SetupOM.exe on the server before you install the agent. See the topic “To upgrade the stand-alone Operations Manager database prior to installing an agent” later in this guide. The additional procedures that verify whether the upgrade is successful are optional.
Note
Prior to upgrading to Operations Manager R2, it is necessary to install WS-Management v1.1. WS-MAN is required for monitoring UNIX or Linux computers. The Operations Manager 2007 WS-Management module depends on WS-Management protocol. This is required for all server and gateway components.
Note
Close all Operations Manager consoles before proceeding with the upgrade.
To upgrade the root management server and OperationsManager database
Log on to the computer that hosts an RMS with an account that is a member of the Operations Manager Administrators role for your Operations Manager 2007 SP1 management group and a local administrator on the computer.
Insert the Operations Manager 2007 R2 media.
At the root of the media, double-click SetupOM.exe.
In the Install area, click Install Operations Manager 2007 R2. The System Center Operations Manager 2007 Setup Upgrade Wizard starts.
On the Welcome to the System Center Operations Manager 2007 R2 Server Setup Upgrade Wizard page, select the Upgrade to Operations Manager 2007 R2 check box, and then click Next.
On the End-User License Agreement page, read the licensing terms, click I accept the terms in the license agreement, and then click Next.
On the Ready to Install the Program page, click Install. The Installing System Center Operations Manager 2007 R2 page displays the progress of the upgrade.
Note
You might be presented with a Warning dialog box indicating that a service has failed to start. If a warning is displayed, click OK.
When the Completing the System Center Operations Manager 2007 R2 Setup Wizard page appears, click Finish.
If prompted, restart the server.
To upgrade the root management server from the command prompt
Log on to a computer that hosts the RMS with an Operations Manager Administrators role account for your Operations Manager 2007 SP1 management group.
Open a command prompt window as an administrator by using the Run as administrator feature.
Run the following command, where you substitute <path> with the actual path to the MOM.msi file:
msiexec /i <path>\MOM.msi /qn /l*v D:\logs\MOMUpgrade.log
To verify the root management server upgrade
Log on to the RMS with an account that has local administrator rights and on the Microsoft Windows desktop, click Start, and then click Run.
Type regedit, and then click OK. The Registry Editor starts.
Warning
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.
Navigate to the HKey_Local_Machine\Software\Microsoft\Microsoft Operations Manager\3.0\Setup key. If the value of the ServerVersion entry is 6.1.####.#, where # is any positive integer, your RMS upgraded successfully.
In the Windows Services snap-in, ensure that the status is set as Started on the following services:
System Center Management Configuration (formerly OpsMgr Config Service)
System Center Data Access (formerly OpsMgr SDK Service)
System Center Management (formerly OpsMgr Health Service)
To upgrade the root management server on a cluster and OperationsManager database on Windows Server 2003
Log on to the cluster node that the RMS is running on with an account that has local administrator rights and is a member of the Operations Manager Administrators role for the SP1 management group.
Open Cluster Administrator, in the navigation pane, expand the cluster name, expand Groups, and then click the resource group that contains the RMS service resource.
In the results pane, examine the cluster resources listed in Name column, and ensure they are online.
In the results pane, in the Owner column, note which node is the owner node.
Ensure that you have logged on to the owning node. If you are not logged onto the owning node, in the navigation pane, right-click the Operations Manager cluster group, click Move Group, and then select the node from the list representing the node you have logged onto.
During the upgrade of a multiple-node cluster, if a service is stopped during the upgrade, the cluster might interpret this as a failure and fail over to another node. To prevent this issue, use steps 6a through 6c to limit the nodes that a service can run on to the specific node you are upgrading. This must be done for the HealthService, OMCFG, and the OMSDK cluster resource services.
In the results pane, right-click the Cluster Resource service you want to change (for example, OpsMgr Health Service), and then click Properties.
In the Properties dialog box, click Modify.
In the Modify Preferred Owner dialog box, under Available nodes, select the node you are performing the upgrade on, make sure it is the only node listed under Preferred owners, and then click OK.
Note
Step 6 must be followed on every node that is being upgraded. After the upgrade of a particular node is complete, users should re-add failover nodes to the Available Nodes list. After all the nodes have been upgraded, configure your Operations Manager 2007 group to failover to the original primary node.
Open your Operations Manager 2007 R2 source media.
At the root of the media, double-click SetupOM.exe.
In the Install area, click Install Operations Manager 2007 R2. The System Center Operations Manager 2007 Setup Upgrade Wizard starts.
On the Welcome to the System Center Operations Manager 2007 R2 Server Setup Upgrade Wizard page, select the Upgrade to Operations Manager 2007 R2 check box, and then click Next.
On the End-User License Agreement page, read the licensing terms, click I accept the terms in the license agreement, and then click Next.
On the Ready to Install the Program page, click Install. The Installing System Center Operations Manager R2 2007 page displays the progress of the upgrade. This process might take up to 20 minutes for the first node. Remaining nodes will take 5 to 10 minutes.
Note
You might be presented with a Warning dialog box indicating that a service has failed to start or stop. If a warning is displayed, click OK.
When the Completing the System Center Operations Manager 2007 Setup Wizard page appears, click Finish. If prompted, restart the server.
Repeat the upgrade steps of this procedure on all nodes of the cluster. For each subsequent node, you must select the Second node of a Windows Server Cluster option on the Welcome to the System Center Operations Manager 2007 R2 Server Setup Upgrade Wizard. For each additional node, ensure that you log on to the node you are upgrading and that all cluster groups are owned by that node.
To upgrade the root management server on a cluster and OperationsManager database on Windows Server 2008
Log on to the RMS owning node of the cluster with an account that is a member of the Operations Manager Administrators role for your Operations Manager 2007 SP1 management group.
Open the Failover Cluster Management tool, expand the cluster and expand Services and Applications and select the RMS application.
In the results pane, ensure that the Current Owner is the node that you are logged onto. If the node that you are logged onto is not the owning node, right click the RMS application, select Move this service or application to another node and select the node that you are logged on to.
Examine all the resources and ensure that they are all online.
During the upgrade of a multiple-node cluster, if a service is stopped during the upgrade, the cluster might interpret this as a failure and fail over to another node. To prevent this issue, stop or pause the cluster service on all nodes except the one that you are upgrading. Alternately you can use steps 5a through 5c to limit the nodes that a service can run on to the specific node you are upgrading. This must be done for all resources listed.
In the Failover Cluster Management right-click the resource you want to change (for example, OpsMgr Health Service), and then click Properties.
In the Properties dialog box, click Advanced Policies.
In the Possible Owners box, select the node on which you are performing the upgrade, make sure it is the only node selected, and then click OK.
Note
Step 5 must be followed on every node that is being upgraded. After the upgrade of a particular node is complete, the application should be moved to each node that is participating in the cluster. After all the nodes have been upgraded, configure all the cluster resources that are part of your RMS application to have all cluster nodes as possible owners again.
Open your Operations Manager 2007 R2 source media.
At the root of the media, double-click SetupOM.exe.
In the Install section, click Install Operations Manager 2007 R2. The System Center Operations Manager 2007 Setup Upgrade Wizard starts.
On the Welcome to the System Center Operations Manager 2007 Server Setup Upgrade Wizard page, select the Upgrade to Operations Manager 2007 R2 check box, and then click Next.
On the End-User License Agreement page, read the licensing terms, click I accept the terms in the license agreement, and then click Next.
On the Ready to Install the Program page, click Install. The Installing System Center Operations Manager 2007 page displays the progress of the upgrade. This process might take up to 20 minutes for the first node. Remaining nodes will take 5 to 10 minutes.
Note
You might be presented with a Warning dialog box indicating that a service has failed to start. If a warning is displayed, click OK.
When the Completing the System Center Operations Manager 2007 Setup Wizard page appears, click Finish. If prompted, restart the server.
Repeat the upgrade steps of this procedure on all nodes of the cluster. For each additional node, ensure that you log into the node you are upgrading and that all cluster groups have failed over to the node.
To verify the root management server upgrade on a cluster
For every node in the cluster, click Start, and then click Run.
Type regedit, and then click OK. The Registry Editor starts.
Warning
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.
Navigate to the HKey_Local_Machine\Software\Microsoft\Microsoft Operations Manager\3.0\Setup key. If the value of the ServerVersion entry is 6.1.####.#, where # is any positive integer, your RMS upgraded successfully.
Using the Cluster Administrator, move the cluster group to each cluster node and verify that the following services are online.
System Center Management Configuration (formerly OpsMgr Config Service)
System Center Data Access (formerly OpsMgr SDK Service)
System Center Management (formerly OpsMgr Health Service)
To verify the OperationsManager database upgrade
On the computer that hosts the OperationsManager database, open SQL Server Management Studio.
In the Connect to Server dialog box, in the Server Type list, select Database Engine
In the Server Name list, select or type the server and instance for your operations database (for example, computer\INSTANCE1).
In the Authentication list, select Windows Authentication, and then click Connect.
In the Object Explorer pane, expand Databases, expand OperationsManager, expand Tables, right-click dbo.__MOMManagementGroupInfo__, and then click Open Table. In the DBVersion column, if the version number is 6.1.####.#, where # is any positive integer, your operations database upgraded successfully.
Upgrade Reporting to Operations Manager 2007 R2
The procedure to upgrade the Reporting Server from Operations Manager 2007 SP1 to Operations Manager 2007 R2 is performed on the computer that hosts the Reporting Server. During this procedure, the Reporting data warehouse is also upgraded with no additional steps. Do not attempt to upgrade the Reporting component from a dedicated OperationsManagerDW installation, it has no effect.
Prior to running the upgrade on the Reporting server, you must remove the Operations Manager 2007 agent; the upgrade will fail if this is not done.
The additional procedure that verifies whether the upgrade is successful is optional.
To upgrade the Reporting Server and the Reporting data warehouse
Log on to the computer that hosts the Reporting Server with an account that is a member of the Operations Manager Administrators role for your Operations Manager 2007 SP1 management group.
Open the Operations Manager 2007 R2 source media.
At the root of the media, double-click SetupOM.exe.
In the Install section, click Install Operations Manager 2007 R2 Reporting. The Operations Manager 2007 Reporting Setup Wizard starts.
On the Welcome to the Operations Manager 2007 Reporting Setup Upgrade Wizard page, select the Upgrade Operations Manager Reporting check box, and then click Next.
On the End-User License Agreement page, read the licensing terms, click I accept the terms in the license agreement, and then click Next.
On the Ready to Install the Program page, click Install.
When the Completing the Operations Manager Reporting Components Setup Wizard page appears, click Finish.
To upgrade the Reporting Server from the command prompt
Log on to a computer that hosts the Reporting Server with an Operations Manager Administrators role account for your Operations Manager 2007 SP1 management group.
Open a command prompt window by using the Run as Administrator option.
Change directory to your Operations Manager 2007 R2 source media.
Run the following command, substituting <path> with the path to the R2 source media:
msiexec /i <path>\Reporting2007.msi SET_ACTIONS_ACCOUNT=0 /qn /l*v D:\logs\ReportingUpgrade.log
To verify the Reporting Server upgrade
On the computer that hosts the Reporting Server, click Start, and then click Run.
Type regedit, and then click OK. The Registry Editor starts.
Warning
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.
Navigate to the HKLM\Software\Microsoft\Microsoft Operations Manager\3.0\Setup key. If the value of the CurrentVersion entry is 6.1.####.#, where # is any positive integer, your Reporting Server upgraded successfully.
Upgrade a Stand-Alone Operations Console to Operations Manager 2007 R2
This procedure upgrades a stand-alone Operations console from Operations Manager 2007 SP1 to Operations Manager 2007 R2. Perform this procedure locally on the computer that has a stand-alone Operations console installed. You do not need to perform this procedure to upgrade Operations consoles that are installed locally on a management server. See “How to Upgrade a Management Server to Operations Manager 2007 R2” later in this guide for instructions on upgrading your management servers.
The additional procedure that verifies whether the upgrade is successful is optional.
Note
If an agent is installed, you must uninstall it before beginning this procedure. You can reinstall the agent after the Operations console is upgraded.
To upgrade a stand-alone Operations console
Log on to the computer that hosts the Operations console with an Operations Manager Administrators role account for your Operations Manager 2007 SP1 management group.
Open the Operations Manager 2007 R2 source media.
At the root of the media, double-click SetupOM.exe.
In the Install section, click Install Operations Manager 2007 R2.
In the System Center Operations Manager 2007 R2 Setup dialog box, click Yes.
Note
You might be presented with a Warning dialog box indicating that a service has failed to start. This behavior is expected. If a warning is displayed, click OK.
On the Welcome page, select the Upgrade to Operations Manager 2007 R2 check box, and then click Next.
On the End-User License Agreement page, read the licensing terms, click I accept the terms in the license agreement, and then click Next.
On the Ready to Install the Program page, click Install. The Installing System Center Operations Manager 2007 page displays the progress of the upgrade.
When the Completing the System Center Operations Manager 2007 Setup Wizard page appears, click Finish.
To upgrade a stand-alone Operations console from the command prompt
Log on to the computer that hosts the Operations console with an Operations Manager Administrators role account for your Operations Manager 2007 SP1 management group.
Open a command prompt window by using the Run as Administrator option.
Change directory to your Operations Manager 2007 R2 source media.
Run the following command, substituting <path> with the path to the MOM.msi file:
msiexec /i <path>\MOM.msi /qn /l*v D:\logs\MOMUpgrade.log
To verify the Operations console upgrade
On the Windows desktop, click Start, and then click Run.
Type regedit, and then click OK. The Registry Editor starts.
Warning
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.
Navigate to the HKey_Local_Machine\Software\Microsoft\Microsoft Operations Manager\3.0\Setup key. If the value of the UIVersion entry is 6.1.####.#, where # is any positive integer, the Operations console upgraded successfully.
Note
After a successful upgrade of a management server, it can take several minutes before the upgraded version numbers are displayed in Operations console.
Upgrade a Management Server to Operations Manager 2007 R2
Perform the procedure to upgrade a management server from Operations Manager 2007 SP1 to Operations Manager 2007 R2 locally on each management server. You must upgrade the root management server of a management group before you upgrade any of the management servers.
The additional procedure that verifies whether the upgrade is successful is optional.
Note
Prior to upgrading to Operations Manager R2, it is necessary to install WS-Management v1.1, in order to enable monitoring of UNIX or Linux computers. The Operations Manager 2007 WS-Management module depends on WS-Management protocol. Operations Manager 2007 R2 setup prerequisite recommends installing WS-Management v1.1 if it is not installed on the computer where Operations Manager 2007 R2 server or gateway is being installed. Setup prerequisite explicitly checks for WS-Management v1.1 while installing Operations Manager server. This check is not present on gateway, although it is also recommended for gateway.
To upgrade a management server
Log on to the computer that hosts the management server with an Operations Manager Administrators role account for your Operations Manager 2007 SP1 management group.
Open the Operations Manager 2007 R2 source media.
At the root of the media, double-click SetupOM.exe.
In the Install section, click Install Operations Manager 2007 R2. The System Center Operations Manager 2007 Server Setup Upgrade Wizard starts.
On the Welcome to the System Center Operations Manager 2007 Server Setup Upgrade Wizard page, select the Upgrade to Operations Manager 2007 R2 check box, and then click Next.
On the End-User License Agreement page, read the licensing terms, click I accept the terms in the license agreement, and then click Next.
On the Ready to Install the Program page, click Install. The Installing System Center Operations Manager 2007 page displays the progress of the upgrade.
Note
You might be presented with a Warning dialog box indicating that a service has failed to start. This behavior is expected. If a warning is displayed, click OK.
When the Completing the System Center Operations Manager 2007 Setup Wizard page appears, click Finish.
To upgrade a management server from the command prompt
Log on to the computer that hosts the Operations console with an Operations Manager Administrators role account for your Operations Manager 2007 SP1 management group.
Open a command prompt window by using the Run as Administrator option.
Change directory to your Operations Manager 2007 R2 source media.
Run the following command, where <path> is substituted with the path to the MOM.msi file:
msiexec /i <path>\MOM.msi /qn /l*v D:\logs\MOMUpgrade.log
To verify the management server upgrade
On the computer that hosts the management server, click Start, and then click Run.
Type regedit, and then click OK. The Registry Editor starts.
Warning
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.
Navigate to the HKey_Local_Machine\Software\Microsoft\Microsoft Operations Manager\3.0\Setup key. If the value of the ServerVersion entry is 6.1.####.#, where # is any positive integer, your management server upgraded successfully.
Upgrade a Gateway Server to R2
The procedure to upgrade a gateway server from Operations Manager 2007 SP1 to Operations Manager 2007 R2 is performed locally on the gateway server. The additional procedure that verifies whether the upgrade is successful is optional.
Note
Prior to upgrading to Operations Manager R2, it is necessary to install WS-Management v1.1, in order to enable monitoring of UNIX or Linux computers. The Operations Manager 2007 WS-Management module depends on WS-Management protocol. Operations Manager 2007 R2 setup prerequisite recommends installing WS-Management v1.1 if it is not installed on the computer where Operations Manager 2007 R2 server or gateway is being installed. Setup prerequisite explicitly checks for WS-Management v1.1 while installing Operations Manager server. This check is not present on gateway, although it is also recommended for the gateway.
To upgrade the gateway server
Log on to a computer that hosts the gateway server with an Operations Manager Administrators role account for your Operations Manager 2007 management group.
Open SetupOM.exe on your Operations Manager 2007 R2 source media
In the Install area, click the Install Operations Manager 2007 R2 Gateway.
On the Welcome to the System Center Operations Manager 2007 R2 Gateway Upgrade Wizard page, click Next.
On the The wizard is ready to begin gateway upgrade page, click Upgrade.
On the Completing the System Center Operations Manager 2007 R2 Gateway Setup wizard page click, Finish.
To verify the gateway server upgrade
On the computer that hosts the gateway server, click Start, and then click Run.
Type regedit, and then click OK. The Registry Editor starts.
Warning
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.
Navigate to the HKey_Local_Machine\Software\Microsoft\Microsoft Operations Manager\3.0\Setup key. If the value of the MOMGatewayVersion entry is 6.1.####.#, where # is any positive integer, your gateway server upgraded successfully.
Upgrade an Agent to R2
Four procedures are available for upgrading agents from Operations Manager 2007 SP1 to Operations Manager 2007 R2:
Using the Operations console
Using the Setup Wizard
Using the Discovery Wizard (for Operations Manager 2007 R2 cross-platform agents only)
Using the command line
Agents that were manually installed must use one of the manual processes to upgrade the agent. Agents that were installed using the console can use any of these options.
Note
Information about upgraded agents might not display in the Operations console for up to 30 minutes after performing the upgrade.
If you are upgrading multihomed agents (reporting to multiple management servers), or if the agent is multihomed between different versions of management servers (SP1 and R2), it might take one day or longer for the discovered instances of the agent to be made part of the R2 management group. They will be added after the next discovery interval.To upgrade agents from Operations Manager 2007 SP1 (build 6278) to Operations Manager 2007 R2 using the Operations console
Log on to the computer that hosts the Operations console with an account that is a member of the Operations Manager Administrators role for the Operations Manager 2007 SP1 management group.
In the Operations console, click Administration.
In the Administration pane, expand Device Management, and then click Pending Management.
In the Pending Management pane, expand Type: Agent Requires Update, right-click each agent-managed computer listed, and then click Approve.
In the Update Agents dialog box, enter the administrator account credentials, and then click Update. The upgrade status is displayed in the Agent Management Task Status dialog box.
When the upgrade is complete, click Close.
To manually upgrade an agent by using the Setup Wizard
Log on to a computer that hosts the agent with an Operations Manager Administrators role account for your Operations Manager 2007 SP1 management group.
Open the Operations Manager 2007 R2 source media.
At the root of the media, double-click SetupOM.exe.
In the Install section, click Install Operations Manager 2007 R2 Agent. When the Welcome to the System Center Operations Manager Agent Upgrade Wizard page opens, click Next.
In the System Center Operations Manager Agent Setup dialog box, click Upgrade. The status page displays the progress of the upgrade.
When the Completing the System Center Operations Manager Agent Setup Wizard page appears, click Finish.
To upgrade R2 Beta UNIX or Linux agents
Open the Operations console with an account that is a member of the Operations Manager 2007 R2 Administrator profile.
Select the Administration view.
At the bottom of the navigation pane, select the Discovery Wizard link.
In the Computer and Device Management Wizard, select Discovery Type, choose UNIX/Linux Discovery Wizard, and then click Next.
Complete the wizard as prompted. The agents will be upgraded.
To manually upgrade an agent from the command prompt
Log on to a computer that hosts the agent with an Operations Manager Administrators role account for your Operations Manager 2007 SP1 management group.
Open a command prompt window by using the Run as Administrator option.
Change directory to your Operations Manager 2007 R2 source media.
Change to the directory where the MOMAgent.msi file is located.
Run the following command, where D:\ is the location for the upgrade log file: msiexec /i MOMAgent.msi SET_ACTIONS_ACCOUNT=0 /qn /l*v D:\logs\AgentUpgrade.log
To verify the agent upgrade
On the computer that hosts an agent, click Start, and then click Run.
Type regedit, and then click OK. The Registry Editor starts.
Warning
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.
Navigate to the HKey_Local_Machine\Software\Microsoft\Microsoft Operations Manager\3.0\Setup key. If the value of the AgentVersion entry is 6.1.####.#, where # is any positive integer, your agent upgraded successfully.
Upgrade a Web Console Server to Operations Manager 2007 R2
Perform this procedure on the computer that hosts the Web console server to upgrade a Web console from Operations Manager 2007 SP1 to Operations Manager 2007 R2.
Note
Prior to upgrading the SP1 Web console, you must install ASP.NET AJAX Extensions 1.0 (v 1.0.61025.0) for ASP.NET 2.0. The prerequisite checker result details also point to the Ajax installer web location. This is located at https://go.microsoft.com/fwlink/?LinkId=132195
If your Web console server is on the same computer as a management server, the Web console server is upgraded when the management server is upgraded, rendering this upgrade procedure unnecessary. You can still run the verification procedure to ensure that the Web console server upgrade was successful.
To upgrade the Web console server
Log on to the computer that hosts the Web console server with an Operations Manager Administrators role account for your Operations Manager 2007 SP1 management group.
Open the Operations Manager 2007 R2 source media.
At the root of the media, double-click SetupOM.exe.
In the Install section, click Install Operations Manager 2007 R2. The System Center Operations Manager 2007 Server Setup Upgrade Wizard starts.
On the Welcome page, select the Upgrade to Operations Manager 2007 R2 check box, and then click Next.
On the End-User License Agreement page, read the licensing terms, click I accept the terms in the license agreement, and then click Next.
On the Ready to Install the Program page, click Install. The Installing System Center Operations Manager 2007 page displays the progress of the upgrade.
When the Completing the System Center Operations Manager 2007 Setup Wizard page appears, click Finish.
To upgrade the Web console server from the command prompt
Log on to the computer that hosts the Operations console with an Operations Manager Administrators role account for your Operations Manager 2007 management group.
Open a command prompt window by using the Run as Administrator option.
Change directory to your Operations Manager 2007 R2 source media.
Run the following command, where <path> is replaced with the path to the MOM.msi file :
msiexec /i <path>\MOM.msi /qn /l*v D:\logs\MOMUpgrade.log
To verify the Web console server upgrade
On the computer that hosts the Web console server, click Start, and then click Run.
Type regedit, and then click OK. The Registry Editor starts.
Warning
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.
Navigate to the HKey_Local_Machine\Software\Microsoft\Microsoft Operations Manager\3.0\Setup key. If the value of the CurrentVersion entry is 6.1.####.#, where # is any positive integer, your Web console server upgraded successfully.
Upgrade the ACS Collector to R2
Perform this procedure to upgrade the Audit Collection Services (ACS) Collector from Operations Manager 2007 SP1 to Operations Manager 2007 R2 locally on the ACS Collector. During this procedure, the ACS database is also upgraded with no additional steps.
Note
A computer that hosts an ACS Collector must also be an Operations Manager management server or gateway. You must upgrade the management server components before you upgrade the ACS Collector component.
To upgrade an ACS Collector
Log on to the computer that hosts the ACS Collector with an Operations Manager Administrators role account for your Operations Manager 2007 SP1 management group.
Open the Operations Manager 2007 R2 source media.
On the root of the media, double-click SetupOM.exe.
In the Install section, click Install Audit Collection Server. The Audit Collection Services Collector Setup Wizard starts.
On the Welcome to the Audit Collection Services Collector Setup Wizard page, click Next.
On the Database Installation Options page, click Use an existing database, and then click Next.
On the Data Source page, type the name that you used as the Open Database Connectivity data source name for your ACS database in the Data Source Name box. By default, this name is OpsMgrAC. Click Next.
On the Database page, if the database is on a separate server than the ACS Collector, click Remote Database Server, and then type the computer name of the database server that will host the database for this installation of ACS. Otherwise, click Database server running locally, and then click Next.
On the Database Authentication page, select one authentication method. If the ACS Collector and the ACS database are members of the same domain, you can select Windows authentication; otherwise, select SQL authentication, and then click Next.
Note
If you select SQL authentication and click Next, the Database Credentials page displays. Enter the name of the user account that has access to the SQL Server in the SQL login name box and the password for that account in the SQL password box, and then click Next.
The Summary page displays a list of actions that the installation program will perform to upgrade ACS. Review the list, and then click Next to begin the installation.
Note
If a SQL Server login dialog box displays and the database authentication is set to Windows authentication, select the correct database and verify that the Use Trusted Connection check box is checked. Otherwise, clear it, enter the SQL login name and password, and then click OK.
When the upgrade is complete, click Finish.