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), Windows Server 2008 R2 SP1 (KB3109118),
Updated 05/03/2016 – On Jan 19th 2016, we had published the Windows Management Framework (WMF) 4.0 update packages for Windows Server 2012 (KB3119938), Windows Server 2008 R2 SP1 (KB3109118), and Windows 7 SP1 (KB3109118) . At this time, these update packages are only available by request through the aforementioned links.
The DSC Resource Kit Wave 8 has landed! You can find it right here.
This wave contains an astounding 48 resources, our largest release ever! We just went from 90 resources released via the Resource Kit to 138, a whopping 53% boost!
UPDATE 11/4/2014: For information on using PSCredential objects, please refer to this blog post.
UPDATE 11/21/2014: For information on OS support, and other features, please refer to our release history.
For the latest information regarding DSC Extension, refer to the product documentation.
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”
For those of you fortunate enough to be at TechEd North America last week, you might have seen Jeffrey Snover announcing Windows PowerShell Desired State Configuration (DSC) for Linux! (If you missed that session, you can watch a replay of it online).
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. In this post, we will discuss some more details about the usage and internal working of this 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.
Two months after that (February), we totaled fourteen additional resources with Wave Two of the DSC Resource Kit.