Simple DSC Pull Server
This example allows to you deploy a powershell desired state configuration pull server. This deployment creates a windows server and adds the dsc-service and deploys the powershell dsc pull server and configures the server. The server is not domain joined. This example uses the xPSDesiredStateConfiguration Module available in the PowerShell DSC Resource Kit available here https://gallery.technet.microsoft.com/xPSDesiredStateConfiguratio-417dc71d.
Note: There are a few workarounds in the dsc script to make this work on the Windows Server that you need to be aware of.
The appcmd command is used to unlock a few entries in IIS.
The Pull Server and Compliance Server "dbprovider" is changed to "System.Data.OleDb".
The Pull Server and Compliance Server "dbconnectionstr" is changed to use the Provider "Microsoft.Jet.OLEDB.4.0"
The Compliance Server authentication has been changed to anonymous as this machine is not domain joined.
After the template is deployed you can
Open the Internet Explorer and browse to http://localhost:8080/PSDSCPullServer.svc to test if the deployment was successful.
Open another tab in Internet Explorer and browse to http://localhost:9080/PSDSCComplianceServer.svc to test if the deployment was successful.
For further information on the DSC Pull server look here:
PowerShell DSC Resource for configuring Pull Server environment
How to retrieve node information from DSC pull server
Tags: Microsoft.Network/networkSecurityGroups, Microsoft.Network/virtualNetworks, Microsoft.Network/networkInterfaces, Microsoft.Compute/virtualMachines, extensions, DSC, Microsoft.Network/publicIPAddresses