1. DSC Pull Server reloaded. Part 3: Pre-create the Pull Server Database

    In the last post, we have seen how to use some of the functions of DSCPullServerAdmin to make your life easier! In this post, we’ll look at another function from this module which allows you to pre-create the Pull Server Database. This is nice if you have a SQL Server where you don’t have the correct permissions to setup new databases (but are allowed to connect to a database of course) and somebody else needs to create it, or where you are trying to host the Database in a service like Azure SQL where the Pull Server itself is not capable of creating the Database due the inability to use the initial catalog in the connection string. In this post we’ll use Azure SQL as our target Database platform. …


  2. DSC Pull Server reloaded. Part 2: Managing the Pull Server with DSCPullServerAdmin

    In the last post, we have seen how to setup a simple DSC Pull Server backed by a SQL Database. In this blog post, I’ll expand upon that Pull Server by onboarding a new node and exploring some of the options of the DSCPullServerAdmin PowerShell module to interact with the database directly. DSCPullServerAdmin is a project I started a while ago to interface with the PullServer edb, making several administrative tasks better achievable. Since Microsoft announced the addition of SQL support in Windows Server 1803 and 2019, it was clear to me that this would be the way forward for the Pull Server so I decided to reboot the project focusing mainly on SQL support. Migrating from edb to SQL is also one of the things handled by this project, more on this in a later post! …


  3. DSC Pull Server reloaded. Part 1: SQL Support

    Windows Server 1803 (Semi-Annual Channel release) and the upcoming Windows Server 2019 introduces a big change for the DSC Pull Server in the form of SQL support. Having SQL as a (supported) backend unlocks a lot of potential for the “inbox” DSC Pull Server (making it more alive then ever). In this blog post, and the following blog posts in this series, I’m exploring some of the options that came to my mind and hopefully will get you inspired as well! …


  4. Working with DSC in the context of 3rd party CM tooling. Part 10: Puppet bootstrap

    In the previous post I’ve set things up for the Puppet agent to tell the server what role configuration it wants. By default new Puppet agents need to have their certificate signed before they are enrolled. In this post we look to further automate the process of the agent onboarding so we have a integrated VM deployment experience similar to how it’s done with the DSC LCM. …


  5. Working with DSC in the context of 3rd party CM tooling. Part 9: Puppet Modules, Roles and more

    In the previous post we setup a Puppet server on an Azure VM and on-boarded the first Puppet agent to it. We assigned a node configuration by modifying the site.pp in the production environment using a node block. …