TAG

Installing Microsoft System Center Operations Manager “SCOM” 2012. Step by Step guide-Part 5- Upgrading to SP1 and R2

Leave a comment

As Agreed starting this part of this article series we will be upgrading our lab for SCOM 2012 RTM to the SP1 then the R2 versions, afterwards we will migrate this upgraded installation to a new environment with Windows Server 2012 R2 as the Operating system and SQL 2012 as the Database server.. Let’s begin  🙂

What’s New in SCOM 2012 Service Pack 1 ?

SCOM 2012 Service Pack 1 has a number of new capabilities among which is the following:

  • New Management Packs and Support for Windows Server 2012 and IIS 8
  • Enabled APM of SharePoint 2010
    Operations Manager lets you monitor SharePoint web front-end components. You can monitor standard and custom SharePoint webpages for performance degradation and server-side exceptions.
  • Integration with Team Foundation Server 2010 and Team Foundation Server 2012
  • 360 .NET Application Monitoring Dashboards
    System Center 2012 Service Pack 1 (SP1) – Operations Manager can show you different perspectives of application health in one place—360 .NET Application Monitoring Dashboards. The 360 .NET Application Monitoring Dashboards display information from Global Service Monitor

A full list of the new capavilities introduced in Service Pack 1 for SCOM 2012 can be found here  ( What’s New in System Center 2012 SP1 – Operations Manager )

 Upgrading System Center 2012 – Operations Manager to System Center 2012 SP1

Warning
The only supported upgrade path to System Center 2012 Service Pack 1 (SP1), Operations Manager is from System Center 2012 – Operations Manager. If you are upgrading from System Center Operations Manager 2007 R2, you must first upgrade to System Center 2012

Review your System Requirements here ( System Requirements: System Center 2012 SP1 – Operations Manager )

Upgrade Scenarios

There are three scenarios for the upgrade:

  1. Upgrading a Single-Server management group
    You only need to run upgrade one time since all features are installed on a single server. The Operations Manager Upgrade wizard performs system prerequisite checks and provides resolution steps for any issues.
  2. Upgrading a distributed management group
    You must upgrade certain features before others. For example, you upgrade the management servers first, followed by the gateways, operations consoles, and then agents. Next, you can upgrade any remaining features, such as the web console, reporting and Audit Collection Services (ACS). You must also perform a number of pre-upgrade and post-upgrade tasks.
  3. Maintaining the existing SCOM 2007 environment
    You can install System Center 2012 Service Pack 1 (SP1), Operations Manager or System Center 2012 R2 Operations Manager in parallel and just upgrade your agents.

 

In our Lab we are following the distributed management group update scenario, which needs to be done in a specific sequence along with some pre-upgrade and post-upgrade tasks to be done. so let’s outline our upgrade steps:

  1. Accomplish Pre-Upgrade Tasks
  2. Upgrade the initial management server and then additional management servers (each management server must be upgraded)
  3. Upgrade ACS (because the ACS server must be on same machine as a management server, we recommend you perform this step along with the upgrade of the management server on which ACS resides.)
  4. Upgrade Gateway(s)
  5. Upgrade Console
  6. Push Install to Agent(s) / Upgrading Manually Installed Agents
  7. Upgrade Web Console
  8. Upgrade Reporting Server
  9. Accomplish Post-Upgrade Tasks

Note

Steps 4 to 8 can be done in parallel.

Okay let’s begin 🙂 .. Good Luck !

Pre-Upgrade Tasks When Upgrading to System Center 2012 SP1 – Operations Manager

Cleanup the Database (ETL Table)

Extraction Transformation Load (ETL) is the backbone for any data warehouse.Operations Manager installation (setup) includes a script that automatically performs a  cleanup for the ETL tables, grooming the database. However, in cases where there are a large number of rows (greater than 100,000) to cleanup, in those case cases it is recommended to run the script before starting the upgrade to promote a faster upgrade and prevent possible timeout of setup.

So first of all determine the number of rows in the ETL Tables by running the following script from the SQL Management studio against the OperationsManager database.

DECLARE @SubscriptionWatermark bigint = 0;
SELECT @SubscriptionWatermark = dbo.fn_GetEntityChangeLogGroomingWatermark();
Select COUNT (*)
FROM EntityTransactionLog ETL with(nolock)
WHERE NOT EXISTS (SELECT 1 FROM EntityChangeLog ECL with(nolock) WHERE ECL.EntityTransactionLogId = ETL.EntityTransactionLogId)
AND NOT EXISTS (SELECT 1 FROM RelatedEntityChangeLog RECL with(nolock) WHERE RECL.EntityTransactionLogId = ETL.EntityTransactionLogId)
AND EntityTransactionLogId < @SubscriptionWatermark;

As you can see belowhave 7885 entry in the ETL table, and to avoid time-out issues during my upgrade i am going to run the following script.

1Clean up the ETL Table by running the following SQL script, Please note that cleanup of ETL can require several hours to complete.

DECLARE @RowCount int = 1;
DECLARE @BatchSize int = 100000;
DECLARE @SubscriptionWatermark bigint = 0;
DECLARE @LastErr int;
SELECT @SubscriptionWatermark = dbo.fn_GetEntityChangeLogGroomingWatermark();
WHILE(@RowCount > 0)
BEGIN
DELETE TOP (@BatchSize) ETL
FROM EntityTransactionLog ETL
WHERE NOT EXISTS (SELECT 1 FROM EntityChangeLog ECL WHERE ECL.EntityTransactionLogId = ETL.EntityTransactionLogId)
AND NOT EXISTS (SELECT 1 FROM RelatedEntityChangeLog RECL WHERE RECL.EntityTransactionLogId = ETL.EntityTransactionLogId)
AND ETL.EntityTransactionLogId < @SubscriptionWatermark;
SELECT @LastErr = @@ERROR, @RowCount = @@ROWCOUNT;
END

2Now let’s run the previous script again to make sure the ETL table is now empty.

3

Remove Agents from Pending Management

Approve or reject any Pending Managements from the SCOM console, from the Administration pane go to the Pending Management section.

4

Disable the Notification Subscriptions

To avoid notification being sent during the upgrade process, disable the Notifications subscriptions from the SCOM Console.

5

Stop the Services or Disable any Connectors

Disable any installed connectors from the Services console, for an example a Service Manager connector.

Verify that the Operational Database Has More Than 50 Percent Free Space

To avoid an upgrade failure please make sure that the operational database has more than 50 percent of free space. You should also ensure that the transactions logs are 50 percent of the total size of the operational database.

Run the Disk Usage report for the OperatrionsManager database

6Review the free space availability

7

To increase the free space for the operational database and log files open the properties for the OperationsManager database, under Files edit the values for MOM_Data and MOM_Log for the column Initial Size (MB). set the value of MOM_Log to a value that is equal to 50 percent of the MOM_Data value.

8

Back up the Operations Manager Databases

This includes the OperationsManager and OperationsManagerDW databases along with any other databases for other SCOM features like reporting or Audit collection services.

9

Upgrading Management Servers

Important Do not install a System Center 2012 Service Pack 1 (SP1), Operations Manager version-ed management group pointing to a System Center 2012 – Operations Manager versioned data warehouse. The data warehouse will not function. There is no work around for this, that’s why we need to do an in-place upgrade first for the servers before moving them to the new Windows Server 2012 R2 environment.

Note Because the ACS server must be on same machine as a management server it is recommended to perform the steps required to Upgrade an ACS Collector to System Center 2012 SP1 – Operations Manager along with the upgrade of the management server on which ACS resides. ACS is out of the scope of this article.

Important When having multiple management servers, do not attempt to upgrade them at the same time, upgrade one by one. Failing to do so can cause a SQL update script that runs early in the set up process to run on multiple management servers and result in database issues. This SQL update script only needs to run on the initial management server being upgraded.

Before firing the installation make sure you have installed Microsoft Report Viewer 2010 Redistributable Package 

Okay so let’s start by launching the setup wizard for the System Center SP1 media on the new SCOMMS-01 server and click Install.

10The wizard should automatically detect the available SCOM features on this server and will notify you to upgrade them.

11Choose the Accounts for the System Center Configuration and Data access services.

12

Start the upgrade… 🙂

13And we are done with upgrading our first management server.

14

Now go ahead and upgrade any additional Management Servers, one at a time.

15

First thing to do after the management servers are upgraded is to upgrade the agents installed on your monitored servers, you do this by going to the Pending Management pane and approve pending updates.

16

Okay, now we have upgraded the Operational databases along with the Management Servers, time to upgrade the Report and Web Console Server.

17

 Post-Upgrade Tasks

  1. Re-enable the Notification Subscriptions.
  2. Restart or Re-enable the Connector Services (if needed)
  3. Verify That the Upgrade Was Successful by checking the health for the management servers and agents , and try running reports from the SCOM console.

That would be it for upgrading to the Service Pack 1. now let’s move on to upgrade this lab to the R2 Version 🙂

What’s New in SCOM 2012 R2 ?

System Center 2012 R2 Operations Manager has new capabilities and changes among of which is the following:

  • Fabric Monitoring A close integration between System Center 2012 R2 Virtual Machine Manager and System Center 2012 R2 Operations Manager introduces System Center cloud monitoring of virtual layers for private cloud environments. To get this new functionality, use the System Center 2012 Management Pack for System Center 2012 R2 Virtual Machine Manager Dashboard, which is imported automatically when you integrate Operations Manager and Virtual Machine Manager
  • Microsoft Monitoring Agent Microsoft Monitoring Agent is a new agent that replaces the Operations Manager Agent and combines .NET Application Performance Monitoring (APM) in System Center with the full functionality of Visual Studio IntelliTrace Collector for gathering full application profiling traces.
  • Support for IPv6 In System Center 2012 R2 Operations Manager the Operations console can take IPv6 addresses as input for Network Discovery and display IPv6 addresses in the network-related views.
  • UNIX and Linux Monitoring UNIX and Linux agents for Operations Manager are now based on the Open Management Infrastructure (OMI) open-source CIM Object Manager.
    Debian GNU/Linux 7 is now supported by the Universal Linux agents and Management Packs.

A full list of the new feature can be found hereWhat’s New in System Center 2012 R2 Operations Manager

Upgrading to R2

Warning
The only supported upgrade path to System Center 2012 R2 Operations Manager is from System Center 2012 Service Pack 1 (SP1), Operations Manager. If you are upgrading from System Center 2012 – Operations Manager, you must first upgrade to System Center 2012 Service Pack 1 (SP1), Operations Manager before upgrading to System Center 2012 R2 Operations Manager

Upgrade Sequence is the same to upgrading to SP1 that is mentioned in the Upgrade Scenarios sections of this article.

Pre upgrade tasks step is identical to the ones we did when upgrading to SP1 nothing new, emtpy the ETL table from SQL Server management studio, Complete Pending managements, stop connector services, Disable email subscriptions, Run the usage report to check the Operational databases free space and take your backups.

Now before you start the upgrade complete the following prerequisites:

  1. Download and install Microsoft® System CLR Types for Microsoft® SQL Server® 2012
    19
  2. Download and install MICROSOFT® REPORT VIEWER 2012 RUNTIME
    20

Once you are done fire the installation wizard on the management servers to upgrade them.

18

Once you are done, upgrade any any additional Management Servers, please remember not to upgrade several management servers at the same time, upgrade them one by one.

21

23

Now let’s move on and upgrade the Report and Web console servers. Please note that upgrading those features also requires the following prerequisites:

  1. Download and install Microsoft® System CLR Types for Microsoft® SQL Server® 2012
  2. Download and install MICROSOFT® REPORT VIEWER 2012 RUNTIME

22That would be all to upgrade to the R2 version. 🙂

24

Do not forget to update your agents and finish with the post installation tasks, they are the exactly the same as the ones we did for the SP1 upgrade.

25

We have Installed a Distributed SCOM 2012 on 5 Servers , we have upgraded it to Service Pack 1 and then to the latest R2 version, in our next part of this series i will show you how to move this deployment to new servers with an Operating system Windows Server 2012 R2 installed and SQL 2012 R2 as the Database server while making sure we still have all the historical data.

Related Articles

Installing Microsoft System Center Operations Manager “SCOM” 2012. Step by Step guide- Part 1- Introduction

Installing Microsoft System Center Operations Manager “SCOM” 2012. Step by Step guide-Part 2- Planning

Installing Microsoft System Center Operations Manager “SCOM” 2012. Step by Step guide-Part 3- Installation

Installing Microsoft System Center Operations Manager “SCOM” 2012. Step by Step guide-Part 4- Installation

 

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s