In my previous post, we have seen , how to use the "User Resource" of the "Desired State Configuration".
Today, we are going to see how to use the "Service Resource" of the "Desired Sate Configuration".
It's a very useful resource, I do like it very much, you can set and and configure services as per you own need, and using this DSC script, you can configure service as you want them on your servers.
The Syntax of the Service Resource is :
What we are going to do today?
By using the "Service Resource", we are going to change the "Virtual Disk" service's start-up mode from "Manual" to "Automatic".
We also changing the "State" of "Virtual Disk" service from "Stopped" to "Running".
You can see that the usage of the "Service Resource" is very straight forward.
In my Script, the name of the script is "DSC_ServiceResourceDemo" .The name of the Configuration block is "settingServices". and the name of the "Service Resource" block is "virtualDiskService".
Name = Actual name of the Service, for example , the actual name of "Virtual Disk" service is "vds".
State : Set the running state of the Service, either it can be "Running" or "Stopped".
StartupType : The Startup type can be either, "Automatic", "Disabled", or "Manual".
Name = 'vds'
State = 'Running'
StartupType = 'Automatic'
Start-DscConfiguration -Path .\settingServices -Wait -Verbose
In the below screenshot, you can see that ,the command finishes successfully. Let's check, if the changes which we configured in the script, are applied successfully or Not.
Yay! They are applied successfully.
If you want to run the Service using any of these there built-in-account. You can use the "BuiltInAccount" parameter and the provide the below options as a string argument.
BuiltInAccount = "NetworkService"
Now, run the DSC script again, when the MOF file created, deploy it again using the same process like above.
If the pushing of the MOF is successful, you can see that the "Log On As" account of the Service is set to the "Network Service" now.
That's all for today. See you in my next blog post.