1. Azure ARM Linked Templates and Complete mode

    Just a small blog post on Azure ARM Linked Template deployment and Complete mode since I couldn’t find a satisfying answer quickly enough via my favorite search engine.

    TL;DR: Linked Template resources together with the master template resources are deployed / kept / updated. Resources out of the cumulative result of master + linked templates are deleted.


  2. DSC Pull Server reloaded. Part 5: Containers!

    With Windows Server 2016, container support was introduced. Now that the Pull Server supports SQL, it felt naturally to me to try and see if the Pull Server could be containerized. A containerized Pull Server allows us to run a Pull Server anywhere where Windows Server Containers are supported (also on Windows 10!). Let’s investigate a prototype!

    On PSConfAsia and PSConfEU I demoed the Pull Server running in containers. Please see the video section for the session recordings.


  3. New Terraform Azure Automation Resources

    Some time ago I contributed 3 new Terraform resources to the AzureRM Resource Provider:

    This was my first ever contribution to a Go project so I’m very proud this got merged! These 3 resources where the missing pin (for me at least) to have an end-2-end scenario enabled where pre-compiled DSC mof files and DSC resource modules could be send to an Azure Automation Account. This enables Terraform VM deployments including Guest state configuration assignment handled through Azure Automation. In this blog post I’ll demonstrate the use of these resources. I won’t go into detail on how to get started with Terraform and such as there is plenty of info available already. …


  4. DSC Pull Server reloaded. Part 4: Migrate EDB or MDB to SQL

    In the last post, we have seen how to use pre-create the Pull Server Database as an Azure SQL Database. It’s always nice to be able to start fresh but a lot of you already deployed Pull Servers based on WMF5+ backed by an EDB or MDB database and you want to move forward right? Now it’s time to figure out how to “migrate” your existing Pull Servers to a new SQL backed Pull Server. The key here is to again use DSCPullServerAdmin to make your life easy! If you haven’t already:

    Install-Module DSCPullServerAdmin -Verbose -Force -Scope CurrentUser
    


  5. 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. …