I always see people comparing PowerShell with Orchestrator, or thinking of Orchestrator as a GUI for PowerShell. From my point of view the real power of Orchestrator lies in its capabilities to integrate at different levels to multiple systems and bring them together in a simple “runbook”.
Finally in this post, we can bring together all the previous runbooks and get to experiment with child runbooks. For this all the previous runbooks have to be ready:
- Part 1: Install SCCM agent
- Part 2: Generate Unique VM Name
- Part 3: Orchestrating Software Updates and Application Deployment
Another prerequisite for this runbook is having a VM template (with Windows 7 in my case) ready for deployment.
The main idea, when creating these little runbooks, was to have a VM that:
- Was auto generated
- Has an unique name that complies with a specific standard
- Is fully patched
- Has a minimum of applications installed
Following this scenario, we easily get to connect to Active Directory, Exchange, SCCM and SCVMM. And we could go even further, by integrating this runbook with SCSM, for change management (future post).