Upgrading SCOM 2012 to SP1

On 20.12.2012 Microsoft released SP1 for the System Center 2012 Suite, for all TechNet and MSDN subscribers. This release makes it possible to upgrade our LAB environment.

In this blog I want to describe my experience with upgrading from System Center 2012, Operating Manager RTM to SP1 in our LAB environment. As like any upgrade in the past [CU, SP or 2007R2 to 2012], keep in mind to

– Backup your servers;
– Backup your SQL databases;
– Backup your unsealed Management Packs;
– Backup your encryption key;

In my opinion this should be done on a regular basis, but especially when making changes on your environment. Also make sure your installation is meets the required hardware and software for System Center 2012 SP1 – Operations Manager. Click on the following TechNet article for more information. [http://technet.microsoft.com/en-US/library/jj656654.aspx]

Accept the License Terms, Confirm the installation location.

System Center 2012 – Operations Manager supported SQL 2008 R2, not any additional SP was required on SQL Server, but System Center 2012 SP1 only supports SQL Server 2008 R2 SP1 and SP2. In my case I needed to update my SQL Server first.

Within our LAB environment I didn’t stumble upon any errors. And SP1 installed succesfully.

**Remember the following when upgrading your existing SCOM 2012 environment **

– Make sure all your components of your System Center 2012 SP1, Operations Manager environment are upgraded with SP1. The Network Summary Dashboard doesn’t function, if you are trying to connect to a SP1 upgraded Management Server, with a RTM Console. 

Microsoft updated the Release Notes after the release of SP1 BETA with 9 more known issues. Click on the following TechNet article for more information. [http://technet.microsoft.com/en-us/library/jj656651.aspx]

System Center 2012 Suite SP1 released

On 20.12.2012 Microsoft released SP1 for the System Center 2012 Suite, for all TechNet and MSDN subscribers. This release makes it possible to upgrade our LAB environment.

Exciting new features are being introduced. Microsoft made a summary of all new features, this summary can be found here.

.. This will be promising for 2013..

SCOM 2012 – Installation MS could not find database

When installing an additional Management Server within an existing management group at one of my customers. I encountered the following issue. When I entered the correct MS-SQL Server and the correct SQL Server Port, there was no database found. The DBList in the wizard was empty.

After double checking all the known and common issues; sufficient permissions on the database, firewall and DNS settings. I checked the OpsMgrSetup.log for more information

[13:50:35]: Info: :Adding to DBList
[13:50:35]: Info: :Key: OperationsManager OMDB: False Empty:False
[13:50:35]: Info: :Key: OperationsManagerDW OMDB: False Empty:False

Why is the wizard not adding the database to the list? I already removed the SCOM 2012 Agent from the server because the installation of the Management Server doesn’t liked it one bit. The solution is to also remove the server (as agent) from the SCOM Console, the installation of the Management Server role runs successfully.

I also check the OpsMgrSetup.log for more information

[14:02:21]: Info: :Adding to DBList
[14:02:21]: Info: :Key: OperationsManager OMDB: True Empty:False
[14:02:21]: Info: :Adding OperationsManager

You can see that the database is added to the DBList.

Zeitgeist 2012: Year in Review

Google’s review of the year 2012.

SCOM 2012 – Upgrade – Failed to update user role

I would recommend everyone before starting any upgrade to carefully read and check these blogs,

http://thoughtsonopsmgr.blogspot.nl/2012/04/migrating-from-scom-r2-cu5-to-om12-part.html [MVP Marnix Wolf]

http://blogs.technet.com/b/mihai/archive/2012/05/23/know-issues-when-upgrading-from-om-2007-r2-to-om-2012.aspx [Mihai Sarbulescu]

After “making my list, and checking it twice” I started my inplace upgrade. Next, Next, Next, .. F*&^%$^v^$%!!

There I was with nothing, no RMS and 2.100 Agents waiting for my move.

luckily, I was running in SnapShot-Mode and had a backup of the Database. So, I saved the log file and restored back the SCOM 2007 Environment. I checked the OpsMgrSetupWizard.log for more information, and noticed the following;

[15:34:54]:        Info:      :Adding S-1-5-21-1046319769-833967741-3563887046-249691 to 47f9d68a-5630-413e-a5f6-1c8504106dee
[15:34:54]:        Error:    :Failed to update user role: : Threw Exception.

After these entries, the installation failed and a attempt for the roll-back was initiated. So, Failed to update user role. Which account was causing this problem?

get-userrole | fl

In this case it was “User Role” group and the “DisplayName” field empty. I’ve deleted the group within the SCOM 2007 Console, succesfully updated to SCOM 2012, and re-created the group again. This solved my issue.