Stuff on my ToDo list can be found in the same repository under How to use the DSC resource If I like what you’ve done, I’ll happily merge it into my repository and give ALL the credits! You think I could’ve done a better job and want to contribute to my resource? Awesome! Head over to Github and contribute: The Resource / Module itself is available on the PowerShell Gallery and can easily be installed by executingįrom here on you can use the resource in any of your DSC configurations or via Invoke-DscResource. WMF 5 / PowerShell v5 (preferably Production Preview or later).In order to use my custom DSC resource the following prerequisites need to be met: These cmdlets use nuget to reach out to Microsoft’s PowerShell Gallery to find and install PowerShell Modules, which by the way also includes DSC Resources. The Set() Method uses Find-Module and Install-Module / Uninstall-Module to bring the machine into its desired state. This resource supports the installation and removal of PowerShell modules through native PowerShell version 5 functionality. If you want to read more about class based resources, check out my previous articles, here and here. So I sat down (I already sat, on a plane, for 14.5 hours…) and started writing code, a PowerShell DSC resource, class-based, obviously. Vagrant doesn’t only provision new machines, it can also call scripts or execute commands while provisioning the machine, such as applying DSC configuration to a machine. The Vagrant boxes I use might not always be up to date with everything or might miss some things.

I use Vagrant to quickly spin up new test environments on my MacBook as I need them.

While on my way back from the 2015 IT DevConnections conference, it was a loooooong way back, I got the idea that I somehow wanted to make sure that certain PowerShell modules were installed on my servers, without logging on to every server (*brrr*) and installing them all manually. PowerShell DSC to manage PowerShell modules

Dsc modules