Home > Articles > Programming > Windows Programming

Working with the PowerShell Desired State Configuration, Part 2: Implementation and Troubleshooting

Concluding his two-part series on using the PowerShell DSC, Timothy Warner, author of Sams Teach Yourself Windows PowerShell 5 in 24 Hours, shows how to work with Managed Object Format (MOF) files in your PowerShell scripts. Configure remote systems, use commands to perform necessary tasks, and find/fix problems without having to set foot outside your office.
Like this article? We recommend

Working with the PowerShell Desired State Configuration, Part 2: Implementation and Troubleshooting

In Part 1 of this Windows PowerShell Desired State Configuration (DSC) mini-series, we explored the basic theory behind DSC. More importantly, we created a simple DSC configuration script called EnforceScripts.ps1 (shown in Figure 1) that performs the following actions:

  1. Create a directory on the target node.
  2. Copy PowerShell script files from the DSC server to the target node.
  3. Figure 1 Our example DSC configuration script.

Running the configuration performs the following actions:

  1. Create a directory with the same name as the configuration container in the script.
  2. Create Managed Object Format (MOF) files for every target node referenced in the config script call.

I have a small lab, so I targeted my script at my Windows Server 2012 R2 member server named adfs1. Figure 2 shows the MOF file.

Figure 2 Our MOF file is ready to be applied to the target node. Each node can have only one MOF applied to it at a time.

Starting a DSC Configuration

Let's refresh our memories as to the DSC command list:

Get-Command -Module PSDesiredStateConfiguration | Select-Object -Property CommandType, Name

CommandType         Name
-----------         ----
   Function         Configuration
   Function         Find-DscResource
   Function         Get-DscConfiguration
   Function         Get-DscConfigurationStatus
   Function         Get-DscLocalConfigurationManager
   Function         Get-DscResource
   Function         New-DscChecksum
   Function         Remove-DscConfigurationDocument
   Function         Restore-DscConfiguration
   Function         Stop-DscConfiguration
     Cmdlet         Invoke-DscResource
     Cmdlet         Publish-DscConfiguration
     Cmdlet         Set-DscLocalConfigurationManager
     Cmdlet         Start-DscConfiguration
     Cmdlet         Test-DscConfiguration
     Cmdlet         Update-DscConfiguration

On dc1, our DSC management server, we'll use the Start-DSCConfiguration cmdlet to apply the adfs1.mof configuration to the target node adfs1.company.pri:

Start-DSCConfiguration -Path 'C:\Placescripts' -Wait -Verbose

I added the -Verbose optional switch to instruct PowerShell to give us as much detail as possible as it works its magic. The -Wait optional switch locks the PowerShell session until the operation completes.

We can verify that the configuration "took" on the adfs1 host simply by examining whether (a) the new C:\scripts directory exists; and (b) the contents of C:\scripts match what's on the server:

Get-ChildItem -Path \\dc1\psscripts

    Directory: \\dc1\psscripts

Mode                LastWriteTime         Length Name
----                -------------         ------ ----
-a----        6/11/2015  10:49 AM             39 hello-world.ps1
-a----        6/11/2015  10:49 AM             41 howaya-world.ps1

Get-ChildItem -Path '\\adfs1\c$\scripts'

    Directory: \\adfs1\c$\scripts

Mode                LastWriteTime         Length Name
----                -------------         ------ ----
-a----        6/11/2015  10:49 AM             39 hello-world.ps1
-a----        6/11/2015  10:49 AM             41 howaya-world.ps1

Awesome! It looks like DSC is working. Now we'll turn our attention to customizing the type of DSC enforcement we want, as well as tweaking target node settings.

Working with the Local Configuration Manager (LCM)

The Local Configuration Manager (LCM) is the underlying "engine" that powers DSC on Windows computers. We use Get-DSCLocalConfigurationManager to view the LCM properties of local or remote systems.

For instance, let's examine the adfs1 LCM from our dc1 management server by implementing Common Information Model (CIM) sessions and Windows PowerShell remoting. For brevity, I'm showing only partial, relevant output here:

$session = New-CimSession -ComputerName 'adfs1'
Get-DscLocalConfigurationManager -CimSession $session

ActionAfterReboot              : ContinueConfiguration
ConfigurationID                : caa3357b-7ec4-417d-b9d4-a5c508edbc56
ConfigurationMode              : ApplyAndAutoCorrect
ConfigurationModeFrequencyMins : 15
LCMState                       : Idle
RebootNodeIfNeeded             : False
RefreshMode                    : PUSH
PSComputerName                 : adfs1

Let me draw your attention to some of the more important LCM properties:

  • ConfigurationMode: The ApplyOnly option applies the configuration, after which the node never again checks its compliance. ApplyAndMonitor reports compliance discrepancies to a log file, but doesn't take corrective action. ApplyAndAutoCorrect detects and correct DSC compliance violations during update cycles.
  • RefreshMode: In push mode, configurations are pushed from the management server to the target node. In pull mode, the target node periodically queries the DSC management server for changes.
  • ConfigurationModeFrequencyMins: This value, which defaults to 30 (minutes), represents the frequency at which the DSC configuration is enforced on the target node.

Setting up a DSC pull server is beyond the scope of our current discussion. Therefore, we'll use push mode in this example. You may want to adjust the ConfigurationModeFrequencyMins property depending on (a) your need for repeated compliance checking, and (b) your tolerance for extra network traffic.

We can use Get-DSCConfigurationStatus to get a quick peek at the system's compliance status and configuration mode:


Status     StartDate                 Type            Mode  RebootRequested
------     ---------                 ----            ----  ---------------
Success    2015/07/15 12:52:11       Consistency     PUSH  False

I like to put my LCM directives within the configuration script itself. Check out the highlighted lines in Figure 3.

Figure 3 It's convenient to configure the target node's LCM directly from its DSC configuration script.

Run the configuration script again to generate an updated MOF file. You'll find that the LCM settings are stored in a separate file named nodename.meta.mof.

Next, run Start-DSCConfiguration to push the new configuration to the target node.

Testing and Troubleshooting

Let's verify that the DSC auto-correction works by first deleting the C:\scripts folder and its contents from the adfs1 target node:

Remove-Item -Path 'C:\scripts' -Recurse -Force

You can either wait until you reach your ConfigurationModeFrequencyMins value, or you can run Start-DSCConfiguration again on the management server. (If we had configured the node in pull mode, we could run Update-DSCConfiguration on the target to have it query the DSC management server.)

On my system, the C:\scripts folder and its contents arrived on the node as expected, after 15 minutes.

DSC jobs are actually PowerShell job objects. Thus we can use Receive-Job to get details on DSC configuration status. For example, I ran Update-DSCConfiguration on my adfs1 target node. (Remember, I just stated that the UpdateDscConfiguration command won't work when we're in push mode. I'm attempting to run the command because I want to test how my DSC system responds to trouble.)


Id     Name            PSJobTypeName   State         HasMoreData     Location
--     ----            -------------   -----         -----------     --------
10     Job10           Configuratio... Running       True            localhost

Then we view the job object:

PS C:\> Get-Job

Id     Name            PSJobTypeName   State         HasMoreData     Location
--     ----            -------------   -----         -----------     --------
10     Job10           Configuratio... Failed        True            localhost

Uh oh. The update failed. I wonder why? Let's investigate (showing only partial output here):

Receive-Job -Name Job10 -Keep

No attempt was made to get a configuration from the pull server because LCM RefreshMode is currently set to Push.

To view the DSC logs, open Event Viewer and browse to the following path:

Applications and Services Logs/Microsoft/Windows/Desired State Configuration

Figure 4 shows the previous error's event log entry.

Figure 4 PowerShell DSC writes to the Windows event logs.

The Microsoft Developer Network (MSDN) website has a great article on DSC troubleshooting if you need to go further.

Before we end this discussion, I want to address how you can reset a target node's DSC configuration. Let's imagine that we target five member servers such that DSC enforces the installation of the Windows Backup feature.

We can remove the configuration by deploying a new DSC configuration to the hosts that simply doesn't include the appropriate resource references. DSC resources that aren't specified in a configuration script are implicitly out of scope and ignored by the target nodes.

If you don't mind the manual work, you can also delete all MOF files from the target node with the following path:


Next Steps

By now you should have a solid understanding of how Windows PowerShell Desired State Configuration prevents configuration drift on Windows Server systems. Going forward, I challenge you to try the following procedures to extend your understanding:

  1. Deploy a pull server and configure a target node to pull a configuration from it.
  2. Create a DSC configuration script that references two or three different resources as well as the LCM.
  3. Search the Internet to see what other PowerShell community members have done to make their DSC work more efficient and effective.

Thanks very much for reading. Share your DSC experiences and questions in the comments section. Happy PowerShelling!

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020