System Center Orchestrator Migration Toolkit Issues

D.R. Monroe 61 Reputation points
2022-02-23T14:37:57.72+00:00

Hello, I'm currently trying to use the System Center Orchestrator Migrator Toolkit, described here - https://learn.microsoft.com/en-us/azure/automation/automation-orchestrator-migration - to migrate a client's orchestrator workflows to Azure Automation.

The main problem is with the core functionality of the tool: anything Powershell gets converted correctly, anything non-powershell is still included in the export, visualised on Azure Automation, but cannot be used, since it is not expected as formed.

For example, time triggers on orchestrators get exported and when imported into Azure Automation, they are included as part of the runbook, rather than saying “Time trigger needs to be created separately” or providing like a Powershell/bash script that plugs everything together.

Here is the error -

Azure-Automation-Error.png

Any insights are appreciated!

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
Azure Automation
Azure Automation
An Azure service that is used to automate, configure, and install updates across hybrid environments.
1,256 questions
0 comments No comments
{count} votes

Accepted answer
  1. AnuragSingh-MSFT 21,376 Reputation points
    2022-02-25T09:49:39.847+00:00

    Hi @D.R. Monroe ,

    Welcome to Microsoft Q&A! Thanks for posting the question.

    I understand that you are converting "System Center Orchestrator's runbook" to "Azure Automation Graphical type runbook" using the "System Center Orchestrator Migrator Toolkit". Based on the error as mentioned in question:

    The first warning in the screenshot above is reported for "Monitor Date/Time" activity (177815-image.png) in Orchestrator runbook. Azure Automation does not support monitor runbooks, so any monitor activities in the integration pack is not converted. Instead, a placeholder cmdlet is created in the integration module for the monitor activity. This cmdlet does nothing. However, for this runbook to be started at a particular schedule, you will have to link it to Azure Automation schedule after publishing the runbook. Please refer to this link for details on adding schedule to Azure Automation runbook.

    The second warning in the screenshot above is for an un-supported activity (for conversion) of type "Check Schedule" (177862-image.png). You will have to remove that activity from the Orchestrator runbook (and add similar logic using PowerShell cmdlet), else the conversion won't go through.

    Please let me know if you have any questions.

    ---
    Please 'Accept as answer' and ‘Upvote’ if it helped so that it can help others in the community looking for help on similar topics.


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.