Automation–Orchestrator Integration Pack for PowerShell Script Execution–Version 1.2!
Remember back in January of this year when I published the Automation–Orchestrator Integration Pack for PowerShell Script Execution post over here on the Building Clouds Blog? It was a re-introduction of thecontent I originally posted many moons ago on my old Blog D’Joy TechNet Blog (I will not expect you to remember that far back!) ;)
Either way, an update to this Integration Pack has been a long time in the making. In fact when I posted about it earlier this year, I had some really great feedback (thank you Greg Bray!) on how to improve and add some really great functionality to something that has already been installed many, many times. I have now taken that feedback, plus one additional “feature” and am proud to release the Orchestrator Integration Pack for PowerShell Script Execution 1.2!
So, this blog post will be a short recap of what is already in the updated documentation (available in the new download) – but first…
The download includes the following (2) files:
- ExecutePS_1.2.oip (System Center 2012 SP1 – Orchestrator Integration Pack)
- Integration Pack for PowerShell Script Execution 1.2 - User Guide.docx (updated documentation)
What’s New in Version 1.2?
The following list outlines the three main updates for version 1.2 of the Orchestrator Integration Pack for PowerShell Script Execution.
New IP Connection - Authentication Method - CredSSP
For more information about CredSSP, please review the following:
New IP Global Connection / Activity Functionality - Get Host Name from Activity
This requirement came directly from comments/suggestions in the original blog post here: Automation–Orchestrator Integration Pack for PowerShell Script Execution
IMPORTANT: Because the existing Global Configuration field for “Host Name” changed to “Host Name from Global Config”, existing configurations will need to be updated before their respective activities will function as expected.
New IP Activity Execution Option - Execute Asynchronously
While investigating Timeout Configuration for the IP, I came across yet another option for the execution of scripts within the runspace(s) created during exection. This option is now offered during design time (default is set to “False”, which imitates existing functionality pre-option). The options pertain to the following Methods:
NOTE: Each of the new features/enhancements are detailed within the updated documentation available in the new download.
- System Center 2012 Orchestrator (SP1+)
- System Center 2012 Orchestrator Integration Toolkit (SP1)
- Microsoft .NET 3.0 Framework
- PowerShell 2.0+
- winrm quickconfig command executed on local and target machines where PS Scripts will be executed
- Enable-WSManCredSSP for Client and Server roles as needed if CredSSP functionality is desired
Upgrading (from Version 1.1)
Via the Orchestrator Deployment Manager…
- Uninstall the existing Integration Pack (version 1.1) from any and all machines where it has been installed (both Runbook Designer and Runbook Server machines)
- Unregister the existing Integration Pack (version 1.1)
- Register the new Integration Pack (version 1.2 - ExecutePS_1.2.oip)
- Deploy/Install the new Integration Pack (version 1.2 - ExecutePS_1.2.oip) to any and all machines where it is needed (both Runbook Designer and Runbook Server machines)
Pre-System Center 2012 SP1 – Orchestrator Notes
As you likely know, a new version of the Orchestrator Integration Toolkit (OIT) shipped with SP1. This new Integration Pack was created with this new OIT, and likely will not be compatible with older versions of Orchestrator (due to Microsoft.SystemCenter.Orchestrator.Integration.dll changes).
If you will not be installing/using System Center 2012 SP1 Orchestrator and would like an older copy of the DLL for this IP that will work for older deployments, please find it here: http://sdrv.ms/10dEvfQ and reference the comments in the original blog post here: Automation–Orchestrator Integration Pack for PowerShell Script Execution
That’s it - thanks for checking it out!
And for more information, tips/tricks, and example solutions for Orchestrator, be sure to watch for future blog posts in the Automation Track!