Last weeks I have received a lot of questions around what will happen to runbooks and integration packs when upgrading to Orchestrator R2. Here are top five questions and answers.
Can I integrate with System Center 2012 SP1 or 2012 from Orchestrator 2012 R2?
Yes, R2 supports running Integration Packs from both 2012 SP1 and 2012
Can I integrate with both System Center 2012 SP1 and 2012 R2 from same Orchestrator?
Most likely the R2 integration pack will work for both. But from a support point of view you need to have the 2012 SP1 integration pack AND the 2012 R2 integration pack. The challenge is that the R2 integration pack will replace/upgrade the SP1 integration pack. To be fully supported you will need two Orchestrator envrionemnts, one with 2012 SP1 integration pack and one with R2 integration pack.
I have a number of runbooks today working with Service Manager 2012 SP1, I am planning to upgrade Orchestrator to R2, will these runbooks work?
Yes, you will keep the same integration packs in R2, in this scenario the SP1 integration pack.
I have a number of runbook today, do I need to rebuild them after R2 upgrade?
No, you donâ€™t. The same integration packs and activities will be in Orchestrator after upgrade
I have System Center 2012 SP1 today, I am planning to upgrade both Service Manager and Orchestrator. Do I have to update all my Service Manager runbooks?
No, when you have upgraded Service Manager to R2 you will upgrade the integration pack for Service Manager to R2 too. Orchestrator is the first component to upgrade and the Service Manager R2 integration pack works with Service Manager SP1 too. The upgrade sequencing for System Center 2012 R2
- Service Management Automation
- Service Manager
- Data Protection Manager (DPM)
- Operations Manager
- Configuration Manager
- Virtual Machine Manager (VMM)
- App Controller
- Service Provider Foundation
- Windows Azure Pack for Windows Server
- Service Bus Clouds
- Windows Azure Pack
- Service Reporting
More info about the upgrade here.
Note that this is provided â€œAS-ISâ€ with no warranties at all. This is not a official support statement.