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 case, I ran into issues that were fixes with links above. However, AI also had to give the Runbook Service Account necessary permission in SQL by adding the account to proper roles.

        After this update rollup is applied, SCORCH stopped logging Events in Events Table.

There is a stored procedure in the Orchestrator database named sp_insertevent which has a parameter @message.

If the datatype of the @message parameter is nvarchar(max), then the Log Purge function may fail. To fix this issue, change the datatype of the @message parameter from nvarchar(max) to nvarchar(4000). You can use the code below or SQL Server Management Studio to make this change in Orchestrator Database.

USE [Orchestrator]


SET ANSI_NULLS ON

GO

SET QUOTED_IDENTIFIER ON

GO

ALTER PROCEDURE [dbo].[sp_insertevent] @type nvarchar(50), @computer nvarchar(50), @summary nvarchar(200), @message nvarchar(4000)

AS

  insert into EVENTS values (newid(), @type, @computer, getutcdate(), @summary, @message)


  •  Install all new version of Integration Packs Register and then

http://www.garethjones294.com/implementing-system-center-orchestrator-2016-step-by-step-part-2-basic-configuration-integration-packs/


  • Register and Deploy Runbook Designer to Server(s)
  • Export Runbooks, global variables, counters, computer groups, schedules and global configurations from Orchestrator 2012.
  • Documentation
  1. Document  Permissions for Runbooks, Computer Groups, Variables, Counters and Schedules (Add Runbook Server account).
  2. Document any folder or runbook permissions that are different from Top Level “Runbooks”. 
  3. Document any dependencies in Orchestrator 2012 environment.  e.g. folder maybe utilized by an activity in a Runbook

  • Import Runbooks, global variables counters, computer groups, schedules and global configurations to Orchestrator 2016.

  • Orchestrator 2016 Apply Special Permissions documented in previous step.
     Apply Top Level Permissions on Runbooks Folder before moving to next steps
    recreate dependencies documented in previous step
  • Check SCORCH configurations:
    In Runbook Designer Options>Active Directory
    Repeat for each configuration that exist in your environment: SCCM Configuration Manager, SCOM, Exchange, SharePoint etc.
  • Registry Change in order to use Latest PS CLR
    Create a new  DWord-Value (32bit)  OnlyUseLatestCLR = 1 in key HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework
  • Configure Other Components e.g. Install PowerShell Modules
    e.g. to install Active Directory Module

    Install-windowsfeature -name AD-Domain-Services –IncludeManagementTools
  •  Install SCOM (System Center Operations Manager) Consoles if you are using SCOM IP
  •  Test your Runbooks
    Runbook with an email activity with attachment
    https://scorchking.blogspot.com/2018/02/scorch-2016-migration-issue-error.html


Comments

Post a Comment

Popular posts from this blog

SCORCH 2016 Migration issue: an error occurred saving the activity to the data store Please check the orchestrator management service trace logs

Issue  After migrating to System Center Orchestrator 2016,  you encounter this error: An error occurred saving the activity to the data store Please check the orchestrator management service trace logs  The Management Service log (C:\ProgramData\Microsoft System Center 2012\Orchestrator\ManagementService.exe\Logs) contains only thes line for every attempt 2015-10-15 12:45:02 [3752] 1 COpalisManager::ModifyObject::CheckAccess (HRESULT=0x80070005) 2015-10-15 13:16:09 [3176] 1 COpalisManager::ModifyObject::CheckAccess (HRESULT=0x80070005) 2015-10-15 13:17:21 [3176] 1 COpalisManager::ModifyObject::CheckAccess (HRESULT=0x80070005) Cause This happens because the Runbook has an Email activity with attachment. This is a known bug with System Center Orchestrator 2016. Workaround If you only have few runbooks with  Email activity with attachment .you can perfrom these 2 workarounds: 1)  You need to remove the attachements and re-add in order to ch...
Read more

Useful Orchestrator T-SQL Queries

In this article, I will share some useful T-SQL queries for Orchestrator 2012. --List all active Runbooks in your environment SELECT       [Name]       FROM [Orchestrator].[dbo].[POLICIES]   where [Deleted] = '0' --Find Runbook/Parameter GUIDs for Web Service call Select lower(POLICIES.UniqueID) as RunbookID, lower(CUSTOM_START_PARAMETERS.UniqueID) as ParameterID, CUSTOM_START_PARAMETERS.value From POLICIES INNER JOIN OBJECTS  on POLICIES.UniqueID = OBJECTS.ParentID LEFT OUTER JOIN CUSTOM_START_PARAMETERS on OBJECTS.UniqueID = CUSTOM_START_PARAMETERS.ParentID Where POLICIES.Name = 'CloseIncident' and policies.deleted = 0 --List  Runbooks are currently running SELECT J.[RunbookId], P.[Name], A.[Computer] FROM [Orchestrator].[Microsoft.SystemCenter.Orchestrator.Runtime.Internal].[Jobs] J INNER JOIN [dbo].POLICIES P ON J.RunbookId = P.UniqueID INNER JOIN [dbo].[ACTIONSERVERS] A ON J.RunbookServerId = A.UniqueID WHER...
Read more

Error in Orchestrator Web console and Web Service after moving Database

Image
I encountered these errors with Orchestrator Web console and Web Service Web console Errors: 1) Error executing the current operation [Arg_SecurityException] [ httpWebRequest_WebException_RemoteServer] Arguments: NotFound Debugging resource strings are unavailable. Often the key and arguments provide sufficient information to diagnose the problem 2) Error executing the current operation. Web Service Error: Orchestrator server encountered an error processing the request. The exception message is 'Keyword not supported: 'server'.'. See server logs for more details This happened after moving the database server. However, I have used the same process to fix issues with Web Console after a new installation. I updated the Data Store Configuration and the connection string in IIS Manager. This was recommended by this post: https://social.technet.microsoft.com/Forums/en-US/c3afc430-5811-4c8c-a797-79c98459d792/console-fails-to-open-error-executi...
Read more