Upgrade Sequencing for System Center 2012 R2

Upgrade Sequencing for System Center 2012 R2

Update:
There is an updated article regarding the Upgrade Sequencing for System Center 2012 R2
http://technet.microsoft.com/library/dn521010.aspx

The article has been updated to reflect these changes. When reading blog posts like this. Always look at TechNet for the most up to date information.

First of all if you plan on upgrading more than one System Center component it is important to read the upgrade guidelines in the product documentation. It will save you a lot of time.

It is important that you understand the order to upgrade System Center if you do not follow the sequencing guidelines you might end up in a non-recovery situation

The upgrade order for System Center components are as follows:

  1. Service Management Automation
  2. Orchestrator
  3. Service Manager
  4. Data Protection Manager (DPM)
  5. Operations Manager
  6. Configuration Manager
  7. Virtual Machine Manager
  8. Service Provider Foundation
  9. Windows Azure Pack for Windows Server
  10. Service Bus Clouds
  11. Windows Azure Pack
  12. Service Reporting
  13. App Controller

Since Orchestrator is the first System Center component to be upgrades we better start upgrading it first.
I will perform this upgrade in my Lab environment and I currently use a single server installation with a separate database. I will point out the differences along the way if you have another setup in your environment.

There are some things that we need to do prior to installing the new version

1. Let your runbooks finish and make sure no runbooks are running.

2. Verify that you don’t have any pending restarts.

3. Backup your Orchestrator database (Full backup)

4. Verify that your hardware, software and OS version specs meet the requirement of System Center 2012 R2

5. Put all orchestrator servers in maintenance mode. (SCOM or your other monitoring software)

6. Uninstall all Orchestrator components management server, Runbook Designer, runbook servers and Web Service.

IMPORTANT:
Do not uninstall any integration Pack (IP) at this stage. Leaving the System Center 2012 IPs in place makes sure that current functionality continues to work until the other components are upgraded. The old integration packs will continue to work until you upgrade the subsequent components, for example after the System Center 2012 – Service Manager upgrade (which is next in line) you will also deploy a new Integration Pack.
After the upgrade you will be able to run integration packs for a:
System Center 2012 component
System Center 2012 SP1 component
System Center 2012 R2 component
You can’t perform an in place upgrade, following message is displayed if the software isn’t uninstalled.

clip_image002

7. Install the Orchestrator management server
Click Install
clip_image004

8. Enter your registration information. Note that if you don’t provide a product key Orchestrator will be installed as an evaluation edition.

clip_image006

9. Select the features to install. If you want to separate your features you just select the Management Server. To install Orchestrator across multiple servers is a wise thing to do. I will post a separate post explaining why in the next day or so.
clip_image008
Management Server
The management server deploys runbooks and Integration Packs to the runbooks server and the runbook designer
Runbook Server
Runbook Servers handle running instances of active runbooks. Runbook servers require active communication to the Datastore (part of the Management server installation) Atleast one runbookserver is required per installation.
Orchestration Console and Web Service
The Web Components consist of the Orchestration console and the Orchestrator Web Services. The Orchestration Console enables real time monitoring and control of runbook operation and status from a brower based interface. The Web Service allows developers to build automation that interacts with Orchestrator runbook operations.
Runbook Designer
The Runbook Designer provides for creation, modification, testing and activation of runbooks and includes the Runbook testing Console.

10. Read thru the license terms and accept to continue.

11. Checking for required hardware and software
clip_image010

12. Configure the service account
clip_image012

13. Configure the database server
clip_image014

14. Configure the database and select existing database
clip_image016

15. Configure Orchestrator user group. This can be a local group or an Active Directory
clip_image017

16. Configure the ports for the web service. (port 81 and 82 are the default ports)
clip_image019

17. Select where to install.
clip_image021

18. Microsoft Update
I select Off (I update my environment with a local WSUS installation.)
clip_image023

19. Chose if you are willing to participate in the Customer Improvement program and how you will participate in Error Reporting.
clip_image025

20. Installation summary, review the selections for the components you are installing.
Click install to continue.
To change something click the appropriate Change link or click previous
clip_image027

21. Installing features
clip_image029

22. Finsished
Note the checkboxes that will launch Windows Update, visit System Center Orchestrator Online or wheter to launch the Orchestrator Runbook Designer.
clip_image031

23.Start your runbooks.
clip_image033

27. Take the Orchestrator servers out of maintenance mode.

28. Return to the Upgrade Sequencing Guide, next up is System Center Service Manager 2012 R2 Ler

C you in the next post, upgrading System center Service Manager 2012 R2

Start upgrading, you know I do

Advertisements

2 Responses to Upgrade Sequencing for System Center 2012 R2

  1. Reza says:

    Great post, thank you. Did you have any issues with the Orchestrator Web Service after the upgrade?

    • Nops it worked great. But it’s is my lab and I have very high access on my accounts. I’ve experienced issue with the web service account and the solution is to grant it dbo rights on the database.

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

%d bloggers like this: