Skip to content

Upgrading System Center 2012 RTM/SP1 RC to SP1 RTM-Part 1 (SCCM, SCOM, Orchestrator)

01/15/2013

With the release of the final version of Service Pack 1 for System Center 2012 was required to upgrade version of the products without the Service Pack (RTM) or with the Service Pack 1 Release Candidate (RC). I will not address the Beta because it was already outdated compared to tests.

In my case, I made the updates from the two versions of all products and this will be a summary in two parts, first with System Center Configuration Manager 2102, System Center Operations Manager 2012 and Orchestrator 2012.

Follows a basic table with the result and then the detailing:

  From RTM From SP1 RC Agents
Configuration Manager Upgrade after you uninstall WAIK and install Windows ADK Upgrade without interventions Does not require upgrading, but agents lists the versions report
Operations Manager Upgrade without interventions Upgrade without interventions Does not require the upgrade, only presents the corresponding version in "Agent Managed"
Orchestrator Does not allow upgrade but lets you select the same database. Does not allow upgrade but lets you select the same database. Integration Packs with the new features in SP1 must be installed
System Center Configuration Manager (SCCM)

Both RTM and SP1 Migration RC were transparent and simple, but it is important to remember that the CONFIGURATION MANAGER 2012 still using Windows AIK. SCCM 2012 SP1 has been updated to use Windows ADK that was beta on the occasion of the release of SCCM 2012. However, the process is simply uninstall WAIK and install Windows ADK.

Important: a bug in timestamp the certificate used in SCCM 2012 SP1 Agent generates an error "couldn’t verify the authenticode signature ‘ C:\WINDOWS\ccmsetup\MicrosoftPolicyPlatformSetup.msi ‘. Return code 0x800b0101 ". Download the hotfix in http://support.microsoft.com/kb/2801987

In environments with hierarchy "Parent-Child" (where they are independent but they make exchanging data) you can start the update on any of the sites with the risk of being refused the upload data in Parent in different versions. On the other hand, in hierarchies "Primary-Secundary" (only the primary have database) the upgrade must be done from top to bottom, i.e., first update the primary server for the database to be updated and then the secondary, which will not function properly until they are updated. Recalling that in this case the update can be done by SCCM console itself.

To open the setup it is possible to see the Upgrade option available, without any intervention, as shown in the two following prints.

07-01-2013 12-06-15

07-01-2013 12-36-18

The sites and settings remain active without any problems, including the agents:

07-01-2013 14-45-31

System Center Operations Manager (SCOM)

It was the simplest of all migration, it was not necessary to any component or upgrade from the RTM.

In environments with installation on multiple servers, the basic order remains as the upgrade from previous versions. We start the migration by the server that contains the Operational Database before the Management Servers and Gateway Servers.

The installation wizard has detected easily the components installed and listed what was being updated:

07-01-2013 15-29-13

To perform the update have changed the structures of the database, which is why the wizard recommends backing up databases before the upgrade process.

07-01-2013 16-19-38

In the end, the console opens with all healthy and SCOM agents updated. Remembering that the agent shows the previous version but does not require the upgrade:

07-01-2013 16-37-05

System Center Orchestrator (SCO)

In the order in which I start migrations, the Orchestrator was the first to not allow direct upgrade from previous versions. Both from the RTM and SP1 RC the message below was the result:

07-01-2013 22-41-24

In this case the process is to uninstall the Orchestrator and reinstall the product, but using the option "Retain database" in the selection of the database to be used.

07-01-2013 22-46-43

After this, all Runbooks were available and functioned properly, as well as Integration Packs that were available in Runbook Designer.

However, it is important to take advantage of new features in SP1 is required to download the Integration Packs new (http://msincic.wordpress.com/2013/01/07/new-integration-packs-and-toolkit-for-orchestrator-2012-sp1/) and make the deploy from the Orchestrator Deployment Manager, which shall show the version 7 (RTM) and 7.1 (SP1):

07-01-2013 23-13-20

It is important that after the installation of the new Integration Packs the Runbooks continued operating normally, as the example below:

image

About these ads

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

Follow

Get every new post delivered to your Inbox.

%d bloggers like this: