question

DRMonroe-3873 avatar image
0 Votes"
DRMonroe-3873 asked XinGuo-MSFT edited

System Center Orchestrator Migration Toolkit Issues

Hello, I'm currently trying to use the System Center Orchestrator Migrator Toolkit, described here - https://docs.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!

azure-automationmsc-orchestrator
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

1 Answer

AnuragSingh-MSFT avatar image
0 Votes"
AnuragSingh-MSFT answered DRMonroe-3873 commented

Hi @DRMonroe-3873,

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.



image.png (5.6 KiB)
image.png (10.8 KiB)
· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@DRMonroe-3873, I wanted to check if you had a chance to review my answer above. Please let me know if you have any queries or concerns.

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

0 Votes 0 ·

Hi @AnuragSingh-MSFT - Thanks for your reply which is very helpful.

0 Votes 0 ·