There's no in-place upgrade from
System Center 2012
Orchestrator 2012 RTM to System Center Orchestrator 2012 SP1, so here are a few steps you'll need to take:
- Back up the Orchestrator database in SQL Server--typically called Orchestrator, it can be easily backed up from the SQL Server Management Studio by right-clicking the database and selecting Back Up... from the Tasks.
- Uninstall all Runbook Servers and Runbook Designers by using the Programs and Features Control Panel applet (see the screen shot below).
Uninstalling Orchestrator Runbook Designer
- Uninstall Orchestration Console and Web Service.
- Uninstall the Management Server.
- As an optional step, you might decide at this point to reinstall the server with Windows Server 2012 (or if a virtual machine, just delete the virtual hard disk and replace with a Windows Server 2012 template OS then configure the IP address, name, etc). If you reinstall the OS, ensure the .NET Framework 3.5 Features are installed (NET-Framework-Core). IIS is also required but will be automatically installed during the installation if not installed.
- Using the System Center 2012 Orchestrator SP1 media, install the Management Server (and other roles, if needed, on the server, such as Runbook server). The existing service account should be specified and the existing SQL Server database and existing database should be selected. Complete all other steps.
Configuring the Database for System Center Orchestrator SP1 Setup
During installation the SQL Server database schema for Orchestrator will be upgraded.
- Continue deployment of other Orchestrator services and components.
- Deployment Integration Packs to servers by using the Deployment Manager. SP1 Integration Packs for System Center 2012 SP1 can be found at the Microsoft Download Center and the RTM Integration Packs can also be deployed, providing compatibility with RTM System Center 2012 components in addition to SP1.
Orchestrator Integration Pack Selection
- Confirm functionality is OK, and you're all done!