Skip to content

REALLY fix images #7

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Oct 30, 2015
Merged

REALLY fix images #7

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
31934b3
ahem
Oct 30, 2015
62f44b5
ACTUALLY fix image links
Oct 30, 2015
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .openpublishing.publish.config.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,5 +9,5 @@
"open_to_public_contributors": "false"
}
],
"notification_subscribers": ["jaiello@microsoft.com"]
"notification_subscribers": [""]
}
4 changes: 2 additions & 2 deletions dsc/enactingConfigurations.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand All @@ -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.

Expand Down
4 changes: 2 additions & 2 deletions dsc/partialConfigs.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down Expand Up @@ -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###

Expand Down