Upgrading to SCOM 2012 R2

Over the past months I have collected a number of “pitfalls” when upgrading to R2 – please be sure to have a backup before you start and check the following before you begin upgrading to SCOM 2012 R2

  1. Installation Account must be a member of the local administrators group on:
    a. SQL Server (both in cluster or always-on)
    b. Management Servers
    c. Reporting Servers
  2. Install Account must be a member of the Sysadmin role on the SQL Server
  3. On the SQL Server the Modal Database must not be more than 100 MB
  4. The Operationsmanager database must have 50% free space or database must be able to extend in size – not fixed
  5. The Action and the SDKConfig accounts needs to be members of the local administrators group on all of The Management Servers.
  6. Collation on SQL: SQL_Latin1_General_CP1_CI_AS
  7. SQL Server Agent must be running and “automatic” startup
  8. Upgrade from a CMD running in a uplifted administrator context
  9. Be 110% sure the Service Broker is enabled and running for the SQL server

If you have any more issues please send me an email or add it to this blog

Have a great day


By | 2014-01-28T03:56:01+00:00 January 28th, 2014|Operations Manager (SCOM)|1 Comment

About the Author:

Kåre Rude Andersen
Microsoft Certified Trainer since 1996, MCSE, TS and ITP in Microsoft Windows, SQL (also Microsoft), Exchange (MS) and Microsoft Operations Manager. Senior Consultant and have recently worked as a consultant at CSC, SAS, ISS, Nokia and Scandlines.

One Comment

  1. Victor Delgado April 4, 2014 at 7:09 - Reply

    And apparently, after the 2-day saga in class, if you have multiple management servers, the System Center Data Access Service and the System Center Management Configuration service accounts can’t be set to Local Service (must be domain accounts) or else all your reports will disappear after the upgrade! 🙂

Leave A Comment