Migrating runbooks from ORCHESTRATOR 2012 R2 to a new ORCHESTRATOR 2016
In this post I will explain how to Deploy a separate environment of ORCHESTRATOR in order to allow for minimal interruption that might result from potential incompatibilities of integration packs and other unknown factors. This approach will allow you to conduct sufficient testing to ensure that the new environment meets all business requirements including disaster recovery testing. Migration Steps Install and configure SCORCH 2016 Orchestrator 2016 environment Apply Lastest update Rollup (UR4 ) You can download from here make sure you read the Know Issues https://support.microsoft.com/en-us/help/4047355/update-rollup-4-for-system-center-2016-orchestrator This link describes some of the errors you may encounter with UR4 https://blogs.technet.microsoft.com/germanageability/2017/11/14/quick-note-runbookservice-might-fail-to-start-after-applying-system-center-orchestrator-2016-ur4/ In my...