{"id":1951,"date":"2013-11-26T11:31:00","date_gmt":"2013-11-26T11:31:00","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/powershell\/2013\/11\/26\/push-and-pull-configuration-modes\/"},"modified":"2024-02-22T15:08:12","modified_gmt":"2024-02-22T23:08:12","slug":"push-and-pull-configuration-modes","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/powershell\/push-and-pull-configuration-modes\/","title":{"rendered":"Push and Pull Configuration Modes"},"content":{"rendered":"

\/\/ bw + bsl && x + aw – ah \/ 2 – cw >= bsl )\n{ c.style.left = x + aw – ah \/ 2 – cw; }\nelse\n{ c.style.left = x + ah \/ 2; }\nif (y + ch + ah \/ 2 > bh + bst && y + ah \/ 2 – ch >= bst )\n{ c.style.top = y + ah \/ 2 – ch; }\nelse\n{ c.style.top = y + ah \/ 2; }\nc.style.visibility = “visible”;\n} } }\nfunction msoCommentHide(com_id)\n{\nif(msoBrowserCheck())\n{\nc = document.all(com_id);\nif (null != c && null == c.length)\n{\nc.style.visibility = “hidden”;\nc.style.left = -1000;\nc.style.top = -1000;\n} }\n}\nfunction msoBrowserCheck()\n{\nms = navigator.appVersion.indexOf(“MSIE”);\nvers = navigator.appVersion.substring(ms + 5, ms + 6);\nie4 = (ms > 0) && (parseInt(vers) >= 4);\nreturn ie4;\n}\nif (msoBrowserCheck())\n{\ndocument.styleSheets.dynCom.addRule(“.msocomanchor”,”background: infobackground”);\ndocument.styleSheets.dynCom.addRule(“.msocomoff”,”display: none”);\ndocument.styleSheets.dynCom.addRule(“.msocomtxt”,”visibility: hidden”);\ndocument.styleSheets.dynCom.addRule(“.msocomtxt”,”position: absolute”);\ndocument.styleSheets.dynCom.addRule(“.msocomtxt”,”top: -1000″);\ndocument.styleSheets.dynCom.addRule(“.msocomtxt”,”left: -1000″);\ndocument.styleSheets.dynCom.addRule(“.msocomtxt”,”width: 33%”);\ndocument.styleSheets.dynCom.addRule(“.msocomtxt”,”background: infobackground”);\ndocument.styleSheets.dynCom.addRule(“.msocomtxt”,”color: infotext”);\ndocument.styleSheets.dynCom.addRule(“.msocomtxt”,”border-top: 1pt solid threedlightshadow”);\ndocument.styleSheets.dynCom.addRule(“.msocomtxt”,”border-right: 2pt solid threedshadow”);\ndocument.styleSheets.dynCom.addRule(“.msocomtxt”,”border-bottom: 2pt solid threedshadow”);\ndocument.styleSheets.dynCom.addRule(“.msocomtxt”,”border-left: 1pt solid threedlightshadow”);\ndocument.styleSheets.dynCom.addRule(“.msocomtxt”,”padding: 3pt 3pt 3pt 3pt”);\ndocument.styleSheets.dynCom.addRule(“.msocomtxt”,”z-index: 100″);\n}\n\/\/ ]]><\/p>\n

\n

Windows PowerShell Desired State Configuration: Push and Pull Configuration Modes<\/p>\n

What are push and pull modes?<\/h2>\n

The Windows PowerShell Desired State Configuration (DSC) system has two configuration modes, which are referred to as push<\/em> and pull<\/em> modes. Each mode allows the user to apply a desired state over a target node.<\/p>\n

Push mode vs. pull mode<\/h2>\n

How push mode works<\/p>\n

\"Image<\/a><\/p>\n

As illustrated in the preceding diagram, the push model is unidirectional and immediate. . The configuration is pushed to its intended targets, and they are configured.<\/p>\n

How to push a configuration<\/h3>\n

In push mode, the user initiates configuration processing via the Start-DscConfiguration<\/a> cmdlet. This command immediately<\/span> applies the configuration to the target, which can be specified by the –ComputerName<\/strong> parameter of the Start-DscConfiguration DSC cmdlet. By default, this cmdlet uses the files in the -Path folder to find the target node details.<\/p>\n

 <\/p>\n

How pull mode works<\/p>\n

\"pull_graphic\"<\/a><\/p>\n

In the preceding diagram, we have 4 machines that participate in the request, delivery and application of the configuration. Each one of the pull client machines is configured to get its desired state configuration from the pull server. Likewise, the pull server has been set up to host the DSC service, and has been provisioned with the configurations and resources that are required by the pull clients.<\/p>\n

Each one of the pull clients has a scheduled task that performs a periodic compliance check on the configuration of the node. When the event is triggered the first time, it causes the Local Configuration Manager (LCM<\/strong>) on the pull client to validate the configuration. If the pull client is configured as desired, nothing happens. Otherwise, the LCM makes a request to the pull server to get a given configuration. If that configuration exists on the pull server, and it passes initial validation checks, the configuration is transmitted to the pull client, where it is then executed by the LCM.<\/p>\n

How to pull a configuration<\/h3>\n

Pulling a configuration requires that a series of steps be taken on the pull server and target nodes. We will look at this series of steps in detail in the section titled The pull mode configuration steps\u00a0<\/span><\/span> in<\/span> this post.<\/p>\n

……….<\/p>\n

NOTE ADDED 2\/6\/2018 –\u00a0The latest information regarding DSC Pull Service can be found in the DSC documentation using the link:\nhttps:\/\/docs.microsoft.com\/en-us\/powershell\/dsc\/pullserver<\/a><\/p>\n

\u00a0……….<\/strong><\/p>\n

Push and pull configuration deployment steps<\/strong><\/h2>\n

Push sequence<\/h2>\n

\"Image<\/a><\/p>\n

Authoring a configuration<\/h3>\n

First thing to do when configuring nodes through DSC is to define a configuration. Consider the following example, and then we\u2019ll examine each part of the configuration.<\/p>\n

InstallDscService.ps1<\/strong><\/p>\n

 <\/p>\n

configuration<\/span> InstallDSCService<\/span><\/span><\/p>\n

{ <\/span><\/p>\n

\u00a0\u00a0\u00a0 node localhost<\/span><\/span><\/p>\n

\u00a0\u00a0\u00a0 {\u00a0\u00a0\u00a0\u00a0\u00a0 <\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 WindowsFeature DSCService<\/span><\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 {<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Name\u00a0 =<\/span> “DSC-Service”<\/span> <\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Ensure =<\/span> “Present”<\/span><\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 }<\/span><\/p>\n

\u00a0\u00a0\u00a0 }<\/span><\/p>\n

}<\/span><\/p>\n

InstallDSCService<\/span> -output<\/span> “.”<\/span>\u00a0 <\/span><\/p>\n

 <\/p>\n

In this simple example, we have the following main elements:<\/p>\n

a)\u00a0\u00a0\u00a0\u00a0\u00a0 <\/span>The configuration<\/strong> keyword<\/em>, followed by a user-supplied name.<\/p>\n

b)\u00a0\u00a0\u00a0\u00a0\u00a0 <\/span>The Node<\/strong> keyword<\/em>, followed by the name of the node to be configured. In this case, it is the localhost. Note that the Node keyword is not case-sensitive.<\/p>\n

c)\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/span>Within the scope of the node definition, we list the resources we will use to configure the node. In this case, we are using the WindowsFeature<\/strong> built-in resource provider to install the DSC Service feature on the local machine.<\/p>\n

d)\u00a0\u00a0\u00a0\u00a0\u00a0 <\/span>Finally, we have a statement making an invocation of the configuration, designating the location of the .mof output as the current directory.<\/p>\n

Generate configuration MOF file<\/h3>\n

Now that we have our .ps1 file with the configuration defined above, we need to generate the MOF file that we will use to initiate the configuration. To generate the MOF file, all that is needed is to execute the .ps1 file containing the configuration. This generates a MOF file named with the same name as the node within the configuration, with the .mof file name extension. In this case, we\u2019ll end up with localhost.mof<\/span>.<\/p>\n

PS D:<\/span>\\> .\\InstallDscService.ps1<\/span><\/p>\n

\u00a0<\/span><\/p>\n

\u00a0<\/span><\/p>\n

\u00a0\u00a0\u00a0 Directory: D:\\InstallDscService<\/span><\/p>\n

\u00a0<\/span><\/p>\n

\u00a0<\/span><\/p>\n

Mode\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 LastWriteTime<\/span>\u00a0\u00a0\u00a0\u00a0 Length Name\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/span><\/p>\n

—-\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 ————-\u00a0\u00a0\u00a0\u00a0 —— —-\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/span><\/p>\n

-a—\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 8\/28\/2013\u00a0\u00a0 4:17 PM\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 1260 localhost.mof\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/span><\/p>\n

Push the desired configuration to target nodes<\/h3>\n

Once we have the configuration mof file generated, we are ready to start the configuration using the Start-DscConfiguration<\/strong> command. In the following example, we provide a few extra parameters, explained below.<\/p>\n

PS D:\\InstallDscService> Start-DscConfiguration -Wait -Verbose -ComputerName localhost –Path .<\/span><\/span><\/p>\n

VERBOSE: Perform operation ‘Invoke CimMethod<\/span>‘ with the following parameters, ”methodName<\/span>‘ = SendConfigurationApply<\/span>,’className<\/span>‘ = MSFT_DSCLocalConfigurationManager<\/span>,’namespaceName<\/span>‘ = root\/Microsoft\/Windows\/DesiredStateConfiguration<\/span>‘.<\/span><\/p>\n

VERBOSE: An LCM method call arrived from computer LOUISC-VMHOSTD with user sid<\/span><\/span> S-1-5-21-2800768176-829124343-4290817346-1106.<\/span><\/p>\n

VERBOSE: [LOUISC-VMHOSTD]: LCM:\u00a0 [ Start<\/span>\u00a0 Set\u00a0\u00a0\u00a0\u00a0\u00a0 ]<\/span><\/p>\n

VERBOSE: [LOUISC-VMHOSTD]: LCM:\u00a0 [ Start<\/span>\u00a0 Resource ]\u00a0 [[WindowsFeature]DSCService<\/span>]<\/span><\/p>\n

VERBOSE: [LOUISC-VMHOSTD]: LCM:\u00a0 [ Start<\/span>\u00a0 Test\u00a0\u00a0\u00a0\u00a0 ]\u00a0 [[WindowsFeature]DSCService<\/span>]<\/span><\/p>\n

VERBOSE: [LOUISC-VMHOSTD]:\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 [[WindowsFeature]DSCService<\/span><\/span>] The operation ‘Get-WindowsFeature’ started: DSC-Service<\/span><\/p>\n

VERBOSE: [LOUISC-VMHOSTD]:\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 [[WindowsFeature]DSCService<\/span><\/span>] The operation ‘Get-WindowsFeature’<\/span>\u00a0<\/span><\/span>succeeded: DSC-Service<\/span><\/p>\n

VERBOSE: [LOUISC-VMHOSTD]: LCM:\u00a0 [ End<\/span>\u00a0\u00a0\u00a0 Test\u00a0\u00a0\u00a0\u00a0 ]\u00a0 [[WindowsFeature]DSCService<\/span>]\u00a0 in 1.6720 seconds.<\/span><\/p>\n

VERBOSE: [LOUISC-VMHOSTD]: LCM:\u00a0 [ Skip<\/span>\u00a0\u00a0 Set\u00a0\u00a0\u00a0\u00a0\u00a0 ]\u00a0 [[WindowsFeature]DSCService<\/span>]<\/span><\/p>\n

VERBOSE: [LOUISC-VMHOSTD]: LCM:\u00a0 [ End<\/span>\u00a0\u00a0\u00a0 Resource ]\u00a0 [[WindowsFeature]DSCService<\/span>]<\/span><\/p>\n

VERBOSE: [LOUISC-VMHOSTD]: LCM:\u00a0 [ End<\/span>\u00a0\u00a0\u00a0 Set\u00a0\u00a0\u00a0\u00a0\u00a0 ]<\/span><\/p>\n

VERBOSE: [LOUISC-VMHOSTD]: LCM:\u00a0 [ End<\/span>\u00a0\u00a0\u00a0 Set\u00a0\u00a0\u00a0\u00a0\u00a0 ]\u00a0\u00a0\u00a0 in\u00a0 2.3120 seconds.<\/span><\/p>\n

VERBOSE: Operation ‘Invoke CimMethod<\/span>‘ complete.<\/span><\/p>\n

VERBOSE: Time taken for configuration job to complete is 2.365 seconds<\/span><\/p>\n

\u00b7<\/span>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/span>–Wait<\/strong>: This parameter ensures that the invocation of configuration is interactive and synchronous with user commands. Otherwise, a job object is returned that continues the operation in the background.<\/p>\n

\u00b7<\/span>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/span>–Verbose<\/strong>: This parameter ensures that any status or progress messages that are written by the resource implementation are displayed in the console. This is particularly helpful during development and debugging.<\/p>\n

\u00b7<\/span>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/span>–ComputerName<\/strong>: If this parameter is omitted, the Local Configuration Manager (LCM) will try to use all the files in the configuration folder. Because we specified localhost<\/em> as the name of the MOF file, the configuration is applied to the local computer.<\/p>\n

\u00b7<\/span>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/span>–Path<\/strong>: Points to the path where the MOF file resides. In this case, it is in the current directory.<\/p>\n

<\/h2>\n

The pull mode configuration steps<\/h2>\n

\"image\"<\/a><\/p>\n

Set up configuration<\/h2>\n

The following sections describe how to set up the configuration.<\/p>\n

Author configuration for a target node<\/h3>\n

Authoring a configuration to work in pull mode is almost identical to the process of authoring a configuration for push. There are some special considerations, however, which we\u2019ll cover in this section of the post.<\/p>\n

First, let\u2019s look at a simple configuration that we can use for pull mode.<\/p>\n

SimpleConfigurationForPullSample.ps1<\/strong><\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n

Configuration<\/span> SimpleConfigurationForPullSample<\/span><\/span><\/p>\n<\/td>\n<\/tr>\n

\n

{ <\/span><\/p>\n<\/td>\n<\/tr>\n

\n

\u00a0\u00a0\u00a0 Node 1C707B86-EF8E-4C29-B7C1-34DA2190AE24 <\/span><\/span><\/p>\n<\/td>\n<\/tr>\n

\n

\u00a0\u00a0\u00a0 {\u00a0\u00a0\u00a0\u00a0\u00a0 <\/span><\/p>\n<\/td>\n<\/tr>\n

\n

\u00a0<\/span><\/p>\n<\/td>\n<\/tr>\n

\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Computer ManagedNode<\/span><\/span><\/span><\/p>\n<\/td>\n<\/tr>\n

\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 {<\/span><\/p>\n<\/td>\n<\/tr>\n

\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Ensure\u00a0\u00a0 =<\/span> “Present”<\/span><\/span><\/p>\n<\/td>\n<\/tr>\n

\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Name\u00a0\u00a0\u00a0\u00a0 =<\/span> \u201cDomainClient1\u201d<\/span><\/span><\/p>\n<\/td>\n<\/tr>\n

\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 DomainName<\/span> =<\/span> \u201cTestDomain<\/span>\u201d<\/span><\/span><\/p>\n<\/td>\n<\/tr>\n

\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 }<\/span><\/p>\n<\/td>\n<\/tr>\n

\n

\u00a0\u00a0\u00a0 }<\/span><\/p>\n<\/td>\n<\/tr>\n

\n

}<\/span><\/p>\n<\/td>\n<\/tr>\n

\n

\u00a0<\/span><\/p>\n<\/td>\n<\/tr>\n

\n

SimpleConfigurationForPullSample<\/span>-output<\/span> “.”<\/span><\/span><\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

There is not much difference in the way that configurations are constructed for pull scenarios. The main difference to note in this simple example is the node name, which is a GUID. This is because we provide a configuration ID that matches this GUID when we are performing the pull from the pull server.<\/p>\n

Designate configuration to target machine<\/h3>\n

To define the configuration above, we must have a GUID value that we can use in the node definition. To generate a new GUID, refer to Create GUID (guidgen.exe)<\/a> or Guid.NewGuid<\/span> Method<\/a>.<\/p>\n

Using unique identifiers for configurations ensures that the mapping between the pull server and its pull clients is unambiguous, and each receives its own configuration.<\/p>\n

Generate configuration MOF<\/h3>\n

Once the configuration script is complete, the next step is to run the script to generate a new <yournewguid<\/em>>.mof. Once you run the script is, there is a new folder with the name of the configuration containing the MOF file. It is always good practice to ensure that the contents of the new MOF file match the contents of the configuration before moving forward.<\/p>\n

Generate MOF file checksum<\/h3>\n

A checksum file is required before deploying the configuration to the pull server. This allows the LCM to validate the configuration before applying it. To generate a new checksum for the configuration, we need to run the New-DSCCheckSum<\/strong> command as follows.<\/p>\n

PS D:\\Samples> New-DSCCheckSum –ConfigurationPath<\/span> .\\SimpleConfigurationForPullSample –OutPath<\/span> .\\SimpleConfigurationForPullSample -Verbose -Force<\/span><\/p>\n

VERBOSE: Create checksum file ‘D:\\Samples\\SimpleConfigurationForPullSample\\1C707B86-EF8E-4C29-B7C1-34DA2190AE24.mof.checksum’ <\/span><\/p>\n

When the .ps1 script was generated, it was generated under the folder SimpleConfigurationForPullSample<\/strong>, which is created and named after the configuration. The new MOF file is placed in that directory, so in the call to New-DSCCheckSum<\/strong>, we must provide the configuration path. It is recommended to use the output path to have the new checksum file stored in the same place as the MOF file. Later, during the preparation of the pull server, we must copy both of these files to a specific location on the pull server.<\/p>\n

Set up the pull server<\/h2>\n

For configuring a machine as a pull server from which the pull clients will get their respective configurations, please refer to \u201cDSC Resource for configuring pull server environment\u201d blog<\/a>\u00a0.<\/p>\n

Deploy MOF and checksum files to the pull server<\/h3>\n

In order to provision the pull server with configuration files, we need to:<\/p>\n