This method utilises the free utility NuGet Package Explorer to wrap existing software packages for bootstrapping with Cloud provisioning. These examples use a custom launcher (available on this site) to standatdise install and uninstall interfaces for software packages. Once packaged, the Chocolatey installers can be installed from a NuGet server using standard PowerShell cmdlines

This script shows how to use PowerShell to invoke a Jenkins workflow and retrieve the result.

Finding the results is depenent on each request being submitted with a unique request ID that may be filtered for. It also assumes that a unique API token for the workflow being called is known.

Unfortunately, the best that can be retrieved at the completion of a Jenkins job is the text based log file. This resides in a known folder on the jenkins server to the workflow can be hacked to replace the log with something a little more workable like JSON output.

Over the years I've posted a number of atricles related to using PowerShell with SCCM. The most read of these was about creating SCCM Applications with Enhanced Detection methods - specifically for File Based Detection. A number of people have asked for an example of the same script using Registry based detection for installed applications.

Not to go over old ground - the earlier blogs that may be of interest are found here:

Azure Automation is the next step in Microsoft’s Orchestration path. Using predefined workflows / with REST/Odata/WebAPI has been a core component of Orchestrator, Service Management Automation and the Cloud based Azure Automation.

WMI is easy to use and great for querying information about remote machines. It’s the obvious choice for reporting on hardware usage – especially for scoping EC2 instances. What is a little more interesting is using the retrieved information to construct a report.