This Article will show, how to migrate a System Center Orchestrator Server to a new Machine, when connected to a System Center Service Manager Server.
So the Challenge is. To keep the Runbook ID and change the Orchestrator SCSM Connector to the new URL otherwise, SCSM will sync each Runbook again, and you need to touch each Runbook Activity.
Our Scenario is as this
Old SCO Server Name: SCO01
New SCO Server Name: SCO02
Backup Master Key from SCO01 SQL Server with the following SQL Command
BACKUP SERVICE MASTER KEY TO FILE =’C:\BACKUP\MASTER_KEY.BAK’ ENCRYPTION BY PASSWORD = ‘password1!!!1’
Backup Orchestrator DB from SCO01 SQL Server with the following SQL Command
BACKUP DATABASE Orchestrator TO DISK=N’C:\BACKUP\OrchestratorDB.bak’
Take a Note of all Orchestrator IP’s and PowerShell Module installed on SCO01
Install SQL Server on SCO02
Restore SQL Master KEY on SCO02 SQL
RESTORE SERVICE MASTER KEY FROM FILE = ‘C:\BACKUP\MASTER_KEY.BAK’ DECRYPTION BY PASSWORD = ‘password1!!!1’
Restore SQL DB Backup on SCO02 SQL
RESTORE DATABASE [Orchestrator] FROM DISK = N’C:\BACKUP\OrchestratorDB.bak’ WITH FILE = 1, NOUNLOAD, STATS = 10
Install Orchestrator with existing Database.
Install and Deploy all PowerShell Modules and Orchestrator Integration Pack son SCO02
Now, we need to tell the Orchestrator Connector on SCSM Side, the New Server name. Unfortunately you cannot edit the Connector in the Gui.
So, open SCSM Console as Admin
Navigate to ADMINISTRATION/MANAGEMENT PACKS
Find and Export the Management Pack “Service Manager Linking Framework Configuration”
Open the File and look for your old Server Name “SCO01” and Replace with “SCO02”. The MP contains the URL 5 time
Then import the Management Pack again, and thats it.
Your SCSM Server is now syncing with the new Orchestrator Server
Michael Seidl aka Techguy
1 thought on “Migrate Orchestrator Server in an SCSM Environment”
Pingback: Migrate System Center Orchestrator in an au2mator Environment - TechGuy