Orchestrator 2019 Upgrade

In this post, I will demonstrate System Center Orchestrator upgrade from 1807 to 2019.

    1. Back up the Orchestrator database.
    2. Backup all Runbooks (Right click on Runbooks folder and Export)
    3. Note all the Monitor Runbooks.
    4. Stop all running runbooks by executing the below query against the Orchestrator database.
      USE Orchestrator -- Ensure that this is the name of your Orchestrator database
      GO
      Declare @polID nvarchar(40)
      Declare @SeqNum bigint
      Declare @getid CURSOR
      Declare @getid2 CURSOR
      Set @getid = cursor for
      SELECT pin.PolicyID, ppq.SeqNumber
      FROM [SCO].[dbo].[POLICY_PUBLISH_QUEUE] ppq -- Verify database Name
      LEFT JOIN SCO.dbo.POLICYINSTANCES pin on pin.PolicyID = ppq.PolicyID -- Verify database Name
      LEFT JOIN SCO.dbo.POLICIES pin2 on pin2.UNiqueID = ppq.PolicyID -- Verify database Name
      Where AssignedActionServer IS NOT NULL
      and TimeEnded IS NULL
      Set @getid2 = cursor for
      SELECT pin.PolicyID, ppq.SeqNumber
      FROM [SCO].[dbo].[POLICY_PUBLISH_QUEUE] ppq -- Verify database Name
      LEFT JOIN SCO.dbo.POLICYINSTANCES pin on pin.PolicyID = ppq.PolicyID -- Verify database Name
      LEFT JOIN SCO.dbo.POLICIES pin2 on pin2.UNiqueID = ppq.PolicyID -- Verify database Name
      Where AssignedActionServer IS NOT NULL
      and TimeEnded IS NULL
      OPEN @getid
      Fetch next
      From @getid into @PolID, @SeqNum
      WHile @@FETCH_STATUS = 0
      Begin
      EXEC [dbo].[sp_UnpublishPolicyRequest] @PolID, @SeqNum
      Fetch next
      From @getid into @PolID, @SeqNum
      End
      DECLARE @return_value int EXEC @return_value = [Microsoft.SystemCenter.Orchestrator.Runtime.Internal].[ClearOrphanedRunbookInstances] SELECT 'Return Value' = @return_value
      Close @getid
      Deallocate @getid
      OPEN @getid2
      Fetch Next
      From @getid2 into @PolID, @SeqNum
      While @@FETCH_STATUS = 0
      Begin
      EXEC [dbo].[sp_PublishPolicy] @PolID
      Fetch next
      From @getid2 into @PolID, @SeqNum
      End
      Close @getid2
      Deallocate @getid2
      
    5. Uninstall all 4 Orchestrator components (Control Panel/Uninstall a program)
    6. Install the Orchestrator 2019 from the installation media.
    7. Uninstall Integration Packs (IP) and unregister them by using Deployment Manager.
    8. Register and deploy 2019 IPs using Deployment Manager.
    9. Install the latest roll ups.
    10. Reconfigure the Data Store Configuration by entering the database server and selecting the existing database.
    11. Check if the Orchestrator services are running. If not, start them manually.
    12. Upgrading Orchestrator resets the root Runbook folder permissions. Modify it accordingly.
    13. Start all Monitor runbooks.

Related Posts

SQL Upgrade of Orchestrator Server

In this post, I will demonstrate the steps for in-place upgrade of the SQL server version of System Center Orchestrator from 2016 to 2019. Orchestrator Version: 2019…

Moving Orchestrator Database

In this post, I will demonstrate the steps for moving the remote Orchestrator database to the local management server. Since SQL 2016 is out there, we can…

In-place OS Upgrade of Orchestrator

Since the EOL of Windows Server 2012 R2 has been announced, it is time to upgrade the OS of the System Center products to Server 2016. In this…

Get AC Unit Temperature with Orchestrator

The other day I was requested to develop an interface that displays the temperature of the Air Condition (AC) units. You may ask that how is this…

Service Manager Task ile Orchestrator Runbook Çalıştırmak

Service Manager, Task özelliği ile harici bir komutun çalıştırılmasına ve Work Item’lar üzerinde işlem yapılmasına olanak tanır. PowerShell komutları kolaylıkla çalıştırılabildiği gibi Orchestartor Runbook’lar da Service Manager’da…