I recently started with PowerShell DSC, this post is to get you up to speed.
Last year Microsoft announced Windows PowerShell Desired State Configuration (DSC) as part of PowerShell v4 during TechEd North America. DSC is a very cool new feature that lets administrators write a declarative “script” that describes what a computer should look like. PowerShell takes that, matches the declarative components with underlying modules, and ensures that the computer does, in fact, look like that. Nearly anything can be checked and controlled: roles, features, files, registry keys. Anything that a PowerShell module can do.
This year Microsoft announced the CTP release of the Windows PowerShell DSC for Linux on GitHub, the step by step guide for Linux DSC.
Will DSC replace other Configuration Managers like Puppet/Chef/etc.? No surely not, Microsoft enables the other Configuration Managers to leverage DSC to saves them, and their users, work.
How does DSC work?
The process is very much like any other Configuration Managers:
- Client configuration (Windows Management Framework 4)
- Push or Pull Server
- Managed Object Format (MOF), the declarative “script”
Basically there is no need to manually create the MOF script, there are already a lot of MOF scripts available on the DSC GitHub.
So where should you start?
I started with 2 related pages: DSC GitHub and Building a DSC Pull Server.
Creating a DSC Pull server on Windows 2008 R2 like me then you need some extra step, I still have some issues getting the Pull server to work on a AD server.
Let me know if you find some cool and useful stuff about DSC.