Skip to main content

Start-DscConfiguration : The directory name is invalid.

By

I’ve been teaching PowerShell since version 1.  On occasion, I have to follow my own advice.  Here is the nifty little error that I received while playing around with DSC.

Start-DscConfiguration : The directory name is invalid.

At line:1 char:1

+ Start-DscConfiguration -Wait -Path C:\MyFaxConfig\LON-SVR1.mof -Verbo ...

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    + CategoryInfo          : NotSpecified: (:) [Start-DscConfiguration], IOException

    + FullyQualifiedErrorId : System.IO.IOException,Microsoft.PowerShell.DesiredStateConfiguration.Commands.StartDscConfigurationCommand

Well, this is a pleasant one. Actually it is very simple.  Here is what I typed:

Start-DscConfiguration -Wait -Path C:\MyFaxConfig\LON-SVR1.mof -Verbose

Anybody???  After a lot of internet searches that came up with nothing, I turned to the help files.  Here is the example from the help file for Start-DscConfiguration:

Start-DscConfiguration -Path "C:\DSC\Configurations\" -Wait –Verbose

In my version, I added the MOF file in the path.  That is not what the Path parameter is used for. Here is what I found for the Path parameter in the help file:

Specifies a file path of a folder that contains configuration settings files. The cmdlet publishes and applies this configuration to computers specified by the ComputerName parameter.


In other words, it will apply all configurations in that folder, not a specific one.  My bad.

Labels:

Comments

Unknown said…
Hi Jason

Could you please let me know if DSC is developed only for windows 8 and over? It doesn't seem to be working on windows 7.

Thank you
February 18, 2016 at 8:10 AM
aflac for nonprofits said…
Don't put the file name in the path, just the directory.
September 20, 2016 at 3:35 PM
Post a Comment

Popular posts from this blog

How to run GPResult on a remote client with PowerShell

By
In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection.  In all cases, this will disrupt the user.  First, you need PowerShell remoting enabled on the target machine.  You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target.  Remember, the target needs to be online and accessible to you.
Post a Comment
Read more

Set up your Environment to utilize Invoke-GPUpdate

By
I’m sitting in O’Hare enjoying my 3 hour layover as I get ready to teach a Windows 10 class in Fort Wayne.  I’m actually prepping for my class in Fort Wayne in a few weeks, 10982 Supporting and Troubleshooting Windows 10.  This class is very much like the Windows 7 version that I used to teach so I decided to up the detail quite a bit.  In the GPO troubleshootin chapter, I’m including a demonstration on how to use PowerShell’s Invoke-GPUpdate.  I needed to make sure the environment is set up for me to be able to utilize this cmdlet.  If you read the Notes section on Invoke-GPUpdate’s help file, you will see there are three firwall rules that need to be in place:          Remote Scheduled Tasks Management (RPC)          Remote Scheduled Tasks Management (RPC-ERMAP)          Windows Management Instrumentation (WMI-IN) I decided to create a little PowerShell script to crea...
Post a Comment
Read more

Where did a User’s Account Get Locked Out?

By
Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction.  The code below is correct.   My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...
18 comments
Read more