Desired State Configuration (DSC) basics in PowerShell

Introduction

Desired State Configuration (DSC) helps you keep your computer or server set up the way you want it, automatically fixing things if they change.

You want to make sure a software is always installed on your computer.

You want a folder to always exist with certain files inside.

You want to keep a service running and restart it if it stops.

You want to set network settings the same way on many computers.

You want to automate setup tasks so you don't do them by hand every time.

Syntax

PowerShell

Configuration ConfigName {
    Node 'localhost' {
        ResourceName ResourceType {
            Property1 = 'Value1'
            Property2 = 'Value2'
        }
    }
}

ConfigName
Start-DscConfiguration -Path ./ConfigName -Wait -Verbose

A Configuration block defines the desired setup using resources.

Node specifies which computer(s) the configuration applies to.

Examples

This example ensures a folder named C:\Example exists on your computer.

PowerShell

Configuration SampleConfig {
    Node 'localhost' {
        File ExampleFolder {
            DestinationPath = 'C:\Example'
            Type = 'Directory'
            Ensure = 'Present'
        }
    }
}

SampleConfig
Start-DscConfiguration -Path ./SampleConfig -Wait -Verbose

This example installs Notepad++ if it is not already installed.

PowerShell

Configuration InstallNotepadPlusPlus {
    Node 'localhost' {
        Package NotepadPlusPlus {
            Name = 'Notepad++'
            Path = 'C:\Installers\npp.8.5.2.Installer.exe'
            ProductId = ''
            Ensure = 'Present'
        }
    }
}

InstallNotepadPlusPlus
Start-DscConfiguration -Path ./InstallNotepadPlusPlus -Wait -Verbose

Sample Program

This script creates a configuration named EnsureFolder that makes sure the folder C:\MyFolder exists. Then it applies the configuration immediately.

PowerShell

Configuration EnsureFolder {
    Node 'localhost' {
        File MyFolder {
            DestinationPath = 'C:\MyFolder'
            Type = 'Directory'
            Ensure = 'Present'
        }
    }
}

EnsureFolder
Start-DscConfiguration -Path ./EnsureFolder -Wait -Verbose

Important Notes

DSC uses resources like File, Package, Service to define what you want on your machine.

You run the configuration function first to create files, then apply them with Start-DscConfiguration.

Use -Wait and -Verbose to see progress and wait until the setup finishes.

Summary

DSC helps keep your computer setup the way you want automatically.

You write a Configuration block with resources describing your desired setup.

Run the configuration and then apply it to enforce the desired state.

Practice

1. What is the main purpose of Desired State Configuration (DSC) in PowerShell?

easy

A. To monitor network traffic continuously

B. To write scripts that run only once manually

C. To automatically keep your computer setup as you want it

D. To create user accounts interactively

Solution

1. Step 1: Understand DSC's role

   DSC is designed to keep system configurations consistent automatically.

2. Step 2: Compare options

   Only To automatically keep your computer setup as you want it describes automatic maintenance of computer setup, which is DSC's goal.

3. Final Answer:

   To automatically keep your computer setup as you want it -> Option C

4. Quick Check:

   DSC purpose = automatic setup maintenance [OK]

Hint: DSC means automatic setup enforcement [OK]

Common Mistakes:

• Thinking DSC only runs scripts once
• Confusing DSC with network monitoring
• Assuming DSC manages user accounts interactively

2. Which of the following is the correct way to start a DSC configuration block in PowerShell?

easy

A. Start-DSCConfig MyConfig { }

B. Configuration MyConfig { }

C. Config MyConfig { }

D. New-DSCConfig -Name MyConfig { }

Solution

1. Step 1: Recall DSC syntax

   The DSC configuration block always starts with the keyword 'Configuration' followed by the name.

2. Step 2: Check options

   Only Configuration MyConfig { } uses the correct keyword 'Configuration' to define the block.

3. Final Answer:

   Configuration MyConfig { } -> Option B

4. Quick Check:

   DSC block starts with 'Configuration' [OK]

Hint: DSC configs start with 'Configuration' keyword [OK]

Common Mistakes:

• Using 'Config' instead of 'Configuration'
• Trying to use cmdlets to start config blocks
• Confusing DSC syntax with other PowerShell commands

3. Given this DSC configuration snippet, what will be the output file name generated after running MyConfig?

Configuration MyConfig {
  Node 'localhost' {
    File ExampleFile {
      DestinationPath = 'C:\temp\example.txt'
      Contents = 'Hello DSC'
    }
  }
}
MyConfig

medium

A. localhost.mof

B. MyConfig.ps1

C. example.txt

D. MyConfig.mof

Solution

1. Step 1: Understand DSC output files

   Running a DSC configuration generates a MOF file named after the Node, here 'localhost'.

2. Step 2: Identify the MOF file name

   The MOF file will be 'localhost.mof' because the Node is 'localhost'.

3. Final Answer:

   localhost.mof -> Option A

4. Quick Check:

   DSC MOF file = NodeName.mof [OK]

Hint: DSC MOF file named after Node, not config [OK]

Common Mistakes:

• Assuming MOF file is named after config
• Confusing MOF with script files
• Expecting output as the destination file

4. You wrote this DSC configuration but get an error when running it:

Configuration SampleConfig {
  Node 'localhost' {
    File MyFile {
      DestinationPath = 'C:\temp\file.txt'
      Content = 'Test content'
    }
  }
}
SampleConfig

What is the error in this script?

medium

A. The Node name 'localhost' is invalid

B. The configuration block must end with 'End-Configuration' command

C. The DestinationPath must be a folder, not a file

D. The property 'Content' should be 'Contents' in the File resource

Solution

1. Step 1: Check File resource properties

   The File resource requires the property 'Contents' (plural), not 'Content'.

2. Step 2: Validate other parts

   Node 'localhost' is valid, DestinationPath can be a file path, and no 'End-Configuration' command exists.

3. Final Answer:

   The property 'Content' should be 'Contents' in the File resource -> Option D

4. Quick Check:

   File resource uses 'Contents' property [OK]

Hint: File resource property is 'Contents' plural [OK]

Common Mistakes:

• Using 'Content' instead of 'Contents'
• Thinking Node names must be IP addresses
• Expecting a special end command for configuration

5. You want to ensure a folder C:\Logs always exists on a remote computer using DSC. Which configuration snippet correctly enforces this desired state?

hard

A. Configuration EnsureFolder {
Node 'RemotePC' {
File LogsFolder {
DestinationPath = 'C:\Logs'
Type = 'Directory'
Ensure = 'Present'
}
}
}

B. Configuration EnsureFolder {
Node 'RemotePC' {
Directory LogsFolder {
Path = 'C:\Logs'
State = 'Exists'
}
}
}

C. Configuration EnsureFolder {
Node 'RemotePC' {
File LogsFolder {
DestinationPath = 'C:\Logs'
Ensure = 'Present'
}
}
}

D. Configuration EnsureFolder {
Node 'RemotePC' {
File LogsFolder {
DestinationPath = 'C:\Logs'
Type = 'File'
Ensure = 'Present'
}
}
}

Solution

1. Step 1: Identify correct resource and properties

   To ensure a folder exists, use the File resource with Type='Directory' and Ensure='Present'.

2. Step 2: Check options for correctness

   Configuration EnsureFolder {
     Node 'RemotePC' {
       File LogsFolder {
         DestinationPath = 'C:\Logs'
         Type = 'Directory'
         Ensure = 'Present'
       }
     }
   }

   correctly uses File resource with Type='Directory' and Ensure='Present'.

   Configuration EnsureFolder {
     Node 'RemotePC' {
       File LogsFolder {
         DestinationPath = 'C:\Logs'
         Ensure = 'Present'
       }
     }
   }

   misses Type, D wrongly uses Type='File', B uses a non-existent Directory resource.

3. Final Answer:

   Option A snippet correctly ensures folder presence -> Option A

4. Quick Check:

   File resource + Type='Directory' + Ensure='Present' = folder exists [OK]

Hint: Use File resource with Type='Directory' to create folders [OK]

Common Mistakes:

• Using Type='File' for folders
• Omitting Type property for directories
• Using non-existent 'Directory' resource