As part of the November 2014 Update (KB3000850), we released updates to PowerShell 4.0 for Windows 8.1 and Windows Server 2012 R2. We are now pleased to make these same PowerShell 4.0 updates available for Windows Server 2012 (KB3119938),
Many of you have seen the demos done by our friends at Chef, which show how they planned to leverage PowerShell DSC.
Those plans are now public as of the publishing of the PowerShell DSC Cookbook for Chef announced in the recent blog post by Adam Edwards.
Traditionally, IT environments have secured their business critical information against external threats by adding additional layers of security to the org’s network (e.g. firewalls, DMZs, etc.).
However many of today’s attacks are coming from inside the network so a new “assume breach”
Desired State Configuration resources are used to model and change the state of different components of the system. In an earlier blog post, we discussed details about deploying and discovering those resources and introduced Import-DscResource dynamic keyword.
The DSC engine caches resources implemented as a PowerShell module for efficiency purposes. This can sometimes turn out to be annoying, when you are authoring a resource and testing it simultaneously. The only way to cause DSC to load the newer version every time is to explicitly kill the process hosting the DSC engine.
In September, Microsoft released PowerShell Desired State Configuration (DSC) with twelve built in resources.
Three months later (December), we added eight more resources with Wave One of the DSC Resource Kit.