Automation Engineering on the Microsoft Stack
  • Introduction
  • What?
  • Delivery
    • Team
      • Dev Automation Lead
    • Environment
    • Workflow
    • Pipeline
    • Architecture
    • Tools
      • Task Manager
      • Continuous Delivery Server
    • Managing
      • Metrics
  • Development
    • Tools
      • Polly
      • Brighter
      • Topshelf
  • Source Control
    • Tools
      • SVN
      • Git
    • Managing
      • Metrics
  • Build
    • Stages
    • Tools
      • MSBuild
      • Roslyn
    • Managing
      • Metrics
  • Deployment
    • Stages
    • Tools
      • OctopusDeploy
    • Managing
      • Metrics
  • Quality
    • Team Quality
    • Stages
    • Scripting
    • Tools
      • NUnit
      • Web Driver
      • TestPipe
      • TestShot
      • Tarsvin
      • Montebank
      • Postman
    • Managing
      • Metrics
    • Stages
    • Coverage
  • Continuous Delivery Meetup
  • Infrastructure
    • Virtualization
    • PowerShell
    • DSC
      • Get Started
      • Configuration
      • Managed Object Format
      • Resources
      • Make It So
      • Automation
      • Testing
      • Security
      • Debug and Troubleshoot
      • Managing
      • Learn More
    • Managing
      • Metrics
  • Monitoring
  • Management
Powered by GitBook
On this page
  • Push Configuration
  • Pull Configuration
  • Create a Pull Server

Was this helpful?

  1. Infrastructure
  2. DSC

Make It So

PreviousResourcesNextAutomation

Last updated 5 years ago

Was this helpful?

Push Configuration

In order to apply the configuration to a node, the node has to have all of the required resources available. Then you have to run the configuration on the node. You can do this by simply running the command Start-DscConfiguration, but it's best (IMHO) to use a pull server.

#Invoke Configuration with CIM session
PS C:\Scripts> $Session = New-CimSession –ComputerName "Server01" –Credential ACCOUNTS\SomeUser
PS C:\Scripts> Start-DscConfiguration -Path "C:\Scripts\DSC\Configurations\" -CimSession $Session

If you push to to a node set to pull it will change the LCM to cause it not to pull anymore.

Pull Configuration

Create pull server with DSC Resource.

Download the xPSDesiredStateConfiguration module from . Unzip the module to the %programfiles%\WindowsPowerShell\modules directory.

Add Windows PowerShell Desired State Configuration feature.

If you push to to a node set to pull it will change the LCM to cause it not to pull anymore. Use Invoke-DscPull to force the node to pull new config. This is helpful when you need to get a quick fix to a node and can't wait for the pull server.

Create a Pull Server

A pull server is the best way to deploy MOF and resources. Since this is DSC it makes sense to use DSC to create the server instead of laboring through a manual process...manual is so old school.

http://gallery.technet.microsoft.com/xPSDesiredStateConfiguratio-417dc71d