Orchestrator is Dead, Long Live Automation
If you reading this blog and are considering installing Orchestrator 2016/2019 – stop. Don’t. Do not pass go, do not collect your salary. Save your time and energy. Seriously, we know other consultants that are still getting requests for proposals to install System Center Orchestrator, but now is not the time for new installations of Orchestrator. It’s time to migrate from Orchestrator. For those of you that have used Orchestrator 2012 R2 and installed the upgrades to 2016/2019, then you know that it wasn’t much of an upgrade.
For those of you are already heavily invested in Orchestrator, it’s time to start considering your migration path. Time to consider what product(s) you’re going to leverage, what your options are, and how to move to new tools. Orchestrator isn’t literally dead in that MS is going to reach into your environment and kill your scorch servers(s), but don’t count on getting any new cutting edge features or updates. Without new features it’s going to continue to be more and more difficult to keep up with automating new products and services. Luckily Azure provides a myriad of ways to take on your automation workloads.
Migrating from Orchestrator to Azure – A new blog series
In this series I’ll be teaming up with Microsoft MVP Donnie Taylor (link) to show you various ways and technologies to accomplish tasks in a more modern way. We will explore automation options. Show you how to prepare your Orchestrator environment for migration. Pick the right tool for the right job, and even add new features and enhancements to your workloads. Stay tuned!
Mark this post as I will keep table of our Migrating from Orchestrator Posts here:
Posts by Donnie
Automation Tools in Azure Q1 2020
Triggering Automations with Event Grid
Posts by Billy
After Orchestrator, Learning Source Control
Triggering Automations from Azure Monitor Alerts