In this post we are going to apply the DSC Configuration we uploaded in the last blog post to a Server Node.
Lets check the status of the compilation job
We can see that the status now says complete.
Check the status of the Node we want to apply the configuration too
you will notice that the NodeConfigurationName property is null, this means that there is not a configuration applied to the node.
Lets double check what Configurations we have loaded in Azure Automation DSC that we can apply to this node.
by running the cmdlet $MyAutomationAccount | Get-AzureAutomationDscNodeConfiguration we see that we have two configurations, we are going to use the webserver.IIS and apply it to the DemoDSC Node by running:
$WebNode = $MyAutomationAccount | Set-AzureAutomationDscNode -NodeConfigurationName “webserver.IIS” -id “024b8929-f98b-11e4-80bb-000d3a9096e9″
the ID parameter on the Set-AzureAutomationDscNode command is the ID of the Node as you can see in the above image the demodsc node now has a configuration and the ID property matches the ID I entered in the cmdlet.
below you can see that initially we had the base 14 Windows Features installed, I forced the configuration to apply by running the Update-DSCConfiguration -wait -verbose cmdlet, if i would not have run this command the configuration would have applied the next time the DSC client checked in to Azure Automation DSC. After the DSC Configuration was applied 27 windows Features were installed.