I was just reading a good overview article on System Center Orchestrator by Paul Schnackenburg at 4Sysops.com. If you’re ramping up on Orchestrator, like I am, it’s a good piece of information that you can glean much from, even as an overview. A couple things in the article really solidify my thinking and it’s great to see someone else is thinking it, too.
First, Paul suggests in a section title that Orchestrator 2012 is the glue that binds the entire System Center 2012 suite. This is what I’ve been saying and promoting since the beginning. Those that have heard me speak in webcasts, interviews, and at conferences, have heard me say this many times.
The second piece comes from Paul’s very last statement in the article:
Playing with Orchestrator 2012 is a lot of fun, and I must say that the visual part of me is certainly picking up how to do things quicker than when struggling in the light blue sea of PowerShell.
I’ve thought this, and maybe said it a couple times in passing without stating it publicly, but I truly believe that Orchestrator *could* displace PowerShell as a common automation “language” – even though you can utilize PowerShell scripts within Orchestrator. There are those who just love command-line scripting and those folks will be around forever. But, I’m interested in how you perceive it. Stick your feedback into the following poll, and then read Paul’s article entitled: System Center 2012 – Orchestrator 2012 – Integration Packs.