Skip to main content

Desired State Configuration with Powershell

At TechEd North America 2013 Microsoft has shed some light on the upcoming release of Powershell Version 4. The big news is the DSC or Desired State Configuration feature. Though I should just make a few comments about it.

What is it?

With DSC you can apply a configuration to your servers/datacenter i matter of minutes from powershell. DSC does not have any dependencies of the underlying infrastructure, however it is a tool to configure it. The scope of the DSC can be a server, a collection of servers or other infrastructure items.

How is it delivered?

DSC support both PUSH and PULL configurations. You can apply an configuration with a script that targets specific objects (PUSH) or you can provide an URI to the configuration and the scoped selection and the targets will download the configuration from there (PULL) at scheduled intervals which also can be configured. If you use a PULL model, you must configure your target nodes with an URI and an UUID. 

How do you write it?

You use a declarative syntax to express the state of operating system features. Each feature requires an provider. You can easily write an provider with powershell. I also expect it to be possible to write a provider from Visual Studio. Currently only a few providers exist, however I expect this to change dramatically over the next moths while we wait for the final release of the product.

Operating systems supported?

We expect Powershell V4 to be preinstalled on Windows Server 2012 R2 and Windows 8.1. It is also highly likely that the distribution channel for V4 will be the Windows Management Framework. Further it has been an tradition from Microsoft to support the current release of the operating system and 2 back. This way V4 will be supported in Windows server 2008 R2, Windows 7 and Windows 8 if Microsoft decides to follow their tradition. This implies that Windows 2008 servers are falling behind, as is to be expected. 

How does DSC work?

Using the declarative syntax powershell compiles your script to a MOF-file. You then apply the MOF to your datacenter/servers. When the target system applies an MOF, it checks to see it has all the modules required by the MOF and apply the configuration described in the MOF. When used in combination with the PULL model, the target will automatically try and download any missing modules/providers, extract it to the correct location and finally run them. 

My 2 cents

The linux guys has been enjoying this for years with puppet/chef. I am really excited about this as it will be an turning point in how we apply configuration across different scopes of servers. In software development I see a huge potential as your application evolves through the different stages (Development-, test- and production environment). 

I will definitely write more when I can get my hands on a preview of 2012 R2.   

You can watch a demo here: 


Popular posts from this blog

Developing PowerShell modules for REST APIs – Part1

Over the years I have developed different PowerShell modules for different web APIs. I thought it would be a good idea to write a 2 series post about how you could go about to do this. This will be a 2 part blog series where we will run through the entire process of building a module for a REST API. I will try my best to keep this as simple as possible and leave more advanced stuff for a follow up post if the interest is there.What you needDepending on your experience with source control and PowerShell in general, you might want to use GIT or some other software repro for the code. In addition we are going to create a test REST API using the splendid UniversalDashboard PowerShell module created by Adam Driscoll. It is available on the PowershellGallery. Other prerequisites are built-in to Powershell. I will assume that you will be following along using at least PowerShell version 5 or greater.
What is HTTP metods for REST API.The primary or most common HTTP verbs used are POST, GET, PU…

Serialize data with PowerShell

Currently I am working on a big new module. In this module, I need to persist data to disk and reprocess them at some point even if the module/PowerShell session was closed. I needed to serialize objects and save them to disk. It needed to be very efficient to be able to support a high volume of objects. Hence I decided to turn this serializer into a module called HashData.

Other Serializing methods

In PowerShell we have several possibilities to serialize objects. There are two cmdlets you can use which are built in:
Both are excellent options if you do not care about the size of the file. In my case I needed something lean and mean in terms of the size on disk for the serialized object. Lets do some tests to compare the different types:


You might be curious why I do not use the Export-CliXML cmdlet and just use the [System.Management.Automation.PSSerializer]::Serialize static method. The static method will generate the same xml, however we …

Developing PowerShell modules for REST APIs – Part2

This is part 2 of the REST API blogpost. In part1 we successfully setup two REST API endpoints using the UniversalDashboard PowerShell module. In this part we are going to create a simple module that support some CRUD operation against our API. As we are trying to keep things as simple as possible, we will not use any fancy framework (like Plaster) to build our module. We are also going to skip a very important step you should familiarize yourself with, Pester tests. Lets get to it.

The moduleWe will build a module called FilesAPI. The module folder will look like this:

In the functions folder I have already added the 2 helper functions from part 1, Get-AuthorizationHeader and ConvertTo-Base64. The other folders are just placeholders for important stuff like classes, private functions that you do not want to make available for the module consumer and tests for Pester tests. For such a small module that we are going to create, one could argue that it is much easier to just add the functi…