#SCOrch: upgrading to Service Pack 1

systemcenter_2_2d9647a3Today I am upgrading my System Center 2012 development environment to SP1, and, as Orchestrator is first in the recommended upgrade sequence, that is where I will start and walk you through the process as I go along.

Before you begin:

  • Backup the Orchestrator database
  • Make sure there are no pending reboots on any of the Orchestrator servers
  • Stop currently running runbooks
  • As an extra step, I also exported all the runbooks.

    Now for the fun. Following the steps outlined in the upgrade guide:


    1. Put all of the Orchestrator servers in maintenance mode in Opsmgr

    2. Uninstall the Orchestrator management server, any runbook servers, the Web Service, and the Runbook Designer.

    3. Install the Orchestrator management server in System Center 2012 SP1, as described in the Deployment Guide. Install any Orchestrator runbook servers in System Center 2012 SP1.

    4. Install the Orchestrator Runbook Designer in System Center 2012 SP1.

    5. If needed, install the Orchestrator Web Service in System Center 2012 SP1.

    6. Take the Orchestrator servers out of maintenance mode.

    7. Return to the Upgrade Sequencing Guide.

    Ok, easy enough, right?

    A couple of notes. Firstly, when you launch the installer, be sure to read the screen correctly, and choose the first install option rather than the one at the bottom of the screen – the second option is to install the Service Provider Foundation components and not Orchestrator. And yes, I know it is labelled, but sometimes, the blonde kicks in.

    You can also install all components in one go, should you so choose:


    The installation, from start to end, took about 15 minutes on my lab server.

    I had a small issue with the runbook server component failing to install as part of the overall installation (all other components completed successfully) on the primary server, but it went without a hitch on the secondary server and installed happily on the primary as a standalone installation after a quickl reboot. When I perform the upgrade in the production environment, I will start with the management server installation, and install the runbook server component afterwards.

    Once you’ve completed the server components, remember to update any runbook designers you may have installed and start up all your runbooks again.


    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 )

    Google photo

    You are commenting using your Google 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 )

    Connecting to %s