From 31934b32e60859ca860f15d407db78147f557b07 Mon Sep 17 00:00:00 2001 From: joeyaiello Date: Fri, 30 Oct 2015 14:31:09 -0700 Subject: [PATCH 1/2] ahem --- .openpublishing.publish.config.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.openpublishing.publish.config.json b/.openpublishing.publish.config.json index 7c219aecae1f..5f1cb099f83c 100644 --- a/.openpublishing.publish.config.json +++ b/.openpublishing.publish.config.json @@ -9,5 +9,5 @@ "open_to_public_contributors": "false" } ], - "notification_subscribers": ["jaiello@microsoft.com"] + "notification_subscribers": [""] } From 62f44b5db0038d00086f609e0ed33f2fb65084dc Mon Sep 17 00:00:00 2001 From: joeyaiello Date: Fri, 30 Oct 2015 14:39:23 -0700 Subject: [PATCH 2/2] ACTUALLY fix image links --- dsc/enactingConfigurations.md | 4 ++-- dsc/partialConfigs.md | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/dsc/enactingConfigurations.md b/dsc/enactingConfigurations.md index 4a657f1f41ea..78d83d175fed 100644 --- a/dsc/enactingConfigurations.md +++ b/dsc/enactingConfigurations.md @@ -2,7 +2,7 @@ There are two ways to enact PowerShell Desired State Configuration (DSC) configurations: push mode and pull mode. ## Push mode -![Push mode](../images/Push.png "How push mode works") +![Push mode](images/Push.png "How push mode works") Push mode refers to a user actively applying a configuration to a target node by calling the [Start-DscConfiguration](https://technet.microsoft.com/en-us/library/dn521623.aspx) cmdlet. @@ -12,7 +12,7 @@ After creating and compiling a configuration, you can enact it in push mode by c >__Note__: By default, DSC runs a configuration as a background job. To run the configuration interactively, call the [Start-DscConfiguration](https://technet.microsoft.com/en-us/library/dn521623.aspx) with the __-Wait__ parameter. ## Pull mode -![Pull Mode](../images/Pull.png "How pull mode works") +![Pull Mode](images/Pull.png "How pull mode works") In pull mode, pull clients are configured to get their desired state configurations from a remote 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. 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) 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. diff --git a/dsc/partialConfigs.md b/dsc/partialConfigs.md index 93bb3fd03950..b321c39c2d74 100644 --- a/dsc/partialConfigs.md +++ b/dsc/partialConfigs.md @@ -31,7 +31,7 @@ PartialConfigDemo The __RefreshMode__ for each partial configuration is set to "Push". The names of the __PartialConfiguration__ blocks (in this case, "OSInstall" and "SharePointConfig") must match exactly the names of the configurations that are pushed to the target node. ###Publishing and starting push-mode partial configurations### -![PartialConfig folder structure](../images/PartialConfig1.jpg) +![PartialConfig folder structure](./images/PartialConfig1.jpg) You then call __Publish-DSCConfiguration__ for each configuration, passing the folders that contain the configuration documents as the Path parameters. After publishing both configurations, you can call `Start-DSCConfiguration –UseExisting` on the target node. @@ -91,7 +91,7 @@ After creating the meta-configuration, you must run it to create a configuration The partial configuration documents must be placed in the folder specified as the __ConfigurationPath__ in the `web.config` file for the pull server (typically `C:\Program Files\WindowsPowerShell\DscService\Configuration`). The configuration documents must be named as follows: _ConfigurationName_. _ConfigurationID_`.mof`, where _ConfigurationName_ is the name of the partial configuration and _ConfigurationID_ is the configuration ID defined in the LCM on the target node. For our example, the configuration documents should be names as follows. -![PartialConfig names on pull server](../images/PartialConfigPullServer.jpg) +![PartialConfig names on pull server](images/PartialConfigPullServer.jpg) ### Running partial configurations from a pull server###