Website under construction

1.
Create the pull server. 
2.
Configure the LCM Meta Configuration of servers on the network. 
3.
Author the configurations. 
4.
Deploy the configurations on the pull server. 
We will look into the details of each of these steps, except for the creation of the pull server because 
that process is the same as for DSC v1. 
Setting up the LCM Meta Configuration 
To prepare a server’s LCM Meta Configuration, you must set the following: 

RefreshMode
with the value of 
Pull
. 

ConfigurationMode
with any value to keep the server in the expected state. 

ConfigurationRepositoryWeb
resource instance representing a pull server of either web or SMB. 

Multiple 
PartialConfiguration
resource instances, each representing a configuration on a pull 
server. 
In LCM, another Meta Configuration property you need to decide to set can be either 
ConfigurationID
or 
ConfigurationName
. Visit the following two links in reference to both properties: 

---

148 
CHAPTER 5 | Systems management 

ConfigurationName 
https://msdn.microsoft.com/powershell/dsc/pullclientconfignames
 

ConfigurationID 
https://msdn.microsoft.com/powershell/dsc/pullclientconfigid
 
To demonstrate partial configuration, the following example features an environment with a pull 
server (DemoServerWin10). There are also two configurations, each deployed to one of the pull 
servers. The LCM of a destination machine is configured with these two pull servers and 
configurations. The LCM configuration applied to the server named 
DemoServerWin
is shown in the 
following: 
[DSCLocalConfigurationManager()] 
Configuration ChangeLCMProperties 
{ 
Node DemoServerWin 
{ 
Settings
{ 
RebootNodeIfNeeded = $true 
RefreshMode = "Pull" 
ConfigurationMode = "ApplyAndAutoCorrect" 
ConfigurationID = "fcd03a8d-5a64-4982-92b3-5c89680add39" 
} 
ConfigurationRepositoryWeb PullServer1 
{ 
ServerURL = "http://demoserverwin10:8080/PSDSCPullServer.svc/" 
AllowUnsecureConnection = $true 
}