So, this is a quick one. We are talking about the “old” SCO Rest API, not the 2022 API. In former releases, It could happen that you cannot see newly created Runbooks with the API. So for example, you cannot see the new Runbook in SCSM or au2mator. There is a quick Solution for this. […]
Runbooks not visible in SCO API Read More »
System Center Orchestrator is an excellent Workflow Engine to run and trigger PowerShell Code. Additionally, SCO provides a way to store Credentials, Server Names, and other recording Values in global Variables. So if a Server Name Changes or Azure App Thumbprint needs to be renewed, you only have to change one Value. That said, it
Orchestrator SQL Query to query a specific String in .Net Acticity Read More »
I already did an article some time ago on migrating an Orchestrator Server in an SCSM Environment. Now we take a look at the Steps in an au2mator Environment. The challenge here is to keep all the Runbook and Input Parameter Ids as au2mator uses them as a Unique Key to trigger the correct Runbook.
Migrate System Center Orchestrator in an au2mator Environment Read More »
From time to time, I need to Trigger an Orchestrator Runbook via PowerShell and the WebService SCO offers. So I will walk you through all the steps, from creating the Runbook with Initialize Data, assigning the needed Permission, and writing the PowerShell Script. The PowerShell Script Will trigger the Runbook Wait for a Complete Status
PowerShell Script to trigger Orchestrator Runbook Read More »
This will be a short post, but I often need the SQL Query to get the Runbook ID and the Parameter ID from a specific Runbook in System Center Orchestrator. So, as I always look on the Internet, I decided to write this post for you and me when I need this. Put the Name
SQL Query to get Runbook and Parameter ID from SQL – System Center Orchestrator Read More »
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
Migrate Orchestrator Server in an SCSM Environment Read More »
This short post will give you an example to query a Runbook Queue Count. In some scenarios, it can help to get the actual Queue Count before triggering a Runbook. To Query the Queue, use the following SQL Query against your Orchestrator SQL Server and Database. Put the Name of the Runbook in the Query,
Get Runbook Queue Count – System Center Orchestrator Read More »
Hi, as you may noticed, i have been at CDC Germany in Hanau a few weeks ago, talking about Service Management and Automation. The Session has been recorded an is available now (German) If the Preview is not working, you can click on that URL: https://vimeo.com/341831252/ff1f56351e
System Center SCSM und SCO Session from CDCGermany Read More »
Since a few days, System Center 2019 is GA, so lets upgrade our environment to the latest bits. I will start with System Center 2019 Orchestrator. Very important note here, System C So lets start with a quick overview on what’s new. What’s new with SCO 2019 Support for PowerShell 4.0+ Support for SQL 2017
Upgrade to System Center Orchestrator 2019 Read More »
In some cases it can happen that the Log Purge is not working anymore, or not working correctly. In a real bad situation it can happen, that the daily Log Purge will make more troubles, maybe stops your Runbooks from working. Than you will see a lot of orphaned Runbooks, and in the most cases
System Center Orchestrator–SQL Query detailed Logs and behind the Scene Read More »
