I write this today as I have fallen in love with something really cool. Automation to the EXTREME!
Systems Center Orchestrator 2012. And this new fascination is enhanced over the top by it’s ability to internally leverage Powershell!
Excuse me for a minute while I wipe up this puddle of drool on the floor.
For those of you not aware, Systems Center 2012 Orchestrator is a massive workflow system that is EASY to use and gives you the ability to translate many IT Processes for managing your Infrastructure into solid workflows that can allow you to be many places at once, without actually BEING there.
Now the fact I can also get these workflows to work with my OTHER most favorite thing on the planet, POWERSHELL, is even better!
But I know there are little ears out there listening saying “What we do to improve?”
Little ears listen well and listen now. It’s so EASY to improve! Here’s what Systems Center Orchestrator 2012 needs to REALLY just start me singing. (Warning! Ask Jeffrey Snover as THIS HAS HAPPENED IN THE PAST!)
1. Integrate the Editor for Editing Powershell Scripts INTO the Powershell ISE
2.Allow Powershell Variables to be “AutoPublished” (whether this is a list to click on or something that can “prepopulate” the Publish field for the bus, don’t care)
3.Tie in the Powershell ISE into the Runbook tester to allow a more granular testing of the internal script structure
You see it won’t take much to send this over the top. Presently, editing internal Powershell scripts in Orchestrator when I am used to having an ISE is painful. Troubleshooting is worse. Editing…. Well Notepad even has CTRL-Z.
But I know you can do this. You have the ability and the power to improve Automation in a way that nobody else can. I put this to you Systems Center 2012 team. Make this happen and make Orchestrator 2012 go out and Kick ass in a way that nobody has EVER imagined!
”The Energized Tech”