scorch 2012 r2 to scorch 2019 upgrade

Richard Scott 41 Reputation points
2020-10-30T14:59:26.853+00:00

Hi , have been tasked with upgrading orchestrator to 2019 from its current version of 2012 r2 i have a little understanding of orchestrator but have the below questions surrounding upgrades

the environment consists of 1 management server and 4 runbooks servers in domain A and 4 runbook servers in domain B with all runbook servers having web services installed
all running server 2012
and a separate sql 2012 DB server

the environment consists of approx 1000 runbooks within structured folders utilising various integration packs

I have read the many upgrade posts on technet and various forums and the steps suggest it is pretty much an uninstall re-install as i need to upgrade the OS , so i have concerns the functionality of the runbooks and integration packs once I upgrade.
it was my intention to follow the below path

Uninstall the Orchestrator management server, any runbook servers, the Web Service, and the Runbook Designer.
Migrate database to sql 2017
upgrade OS to 2016
Install SCORCH 2016 UR6
Uninstall the 2016 Orchestrator management server, any runbook servers, the Web Service, and the Runbook Designer.
Install SCORCH 2019

In regards to the integrations and runbooks already configured am i right in thinking as long as i perform the upgrade on all runbook servers that these integrations will follow the upgrade and still continue to work & that the accounts and information configured within them will not need to be recreated even with an OS Update in the middle ?

System Center Orchestrator
System Center Orchestrator
A family of System Center products that provide an automation platform for orchestrating and integrating both Microsoft and non-Microsoft IT tools.
229 questions
0 comments No comments
{count} votes

Accepted answer
  1. Leon Laude 85,786 Reputation points
    2020-10-30T15:28:57.283+00:00

    Hi @Richard Scott ,

    The steps you have outlined look OK, upgrading Orchestrator is pretty straight forward, but you need to make sure you have backups of the following:

    Orchestrator database
    The Orchestrator database backup can easily be done from the SQL Server Management Studio (SSMS)

    Runbooks
    The runbooks can easily be exported from the Runbook Designer.

    Integration Packs
    The Orchestrator core has not changed much so the integration packs of Orchestrator 2012 R2 will work in Orchestrator 2019, just make sure you have a copy of all installed integration packs so you don't get into a situation with runbooks having unknown runbook acitvities.

    If you perform in-place upgrades you won't need to reinstall any integration packs, but it's always good to keep a backup of them somewhere.

    As for the accounts everything, permissions should remain when performing an in-place upgrade, but since you will uninstall Orchestrator and reinstall it, you will of course need to re-enter the acocunts used for your Orchestrator services, but these accounts should stay in their local admin/other groups on the server.

    Another thing is to document which runbooks were running before you stop everything and uninstall Orchestrator, you can also use the Orchestrator Health Checker to get some information of running runbooks.

    ----------

    (If the reply was helpful please don't forget to upvote or accept as answer, thank you)

    Best regards,
    Leon

    0 comments No comments

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.