PowerShell

The PowerShell forum accepts bug reports as well as feedback and suggestions. For more information, check out the PowerShell Homepage

The following is a list of the states we use to track items.

status meaning
survey We saw this and we are considering it. Please upvote if it’s important to you.
needs more information We don’t understand the issue and need additional details.
investigating We are looking at this internally to understand things like: scenario, reproduction of issue, costing, or other technical details.
in queue The issue is understood and in our unprioritized backlog. Your votes will be used to drive prioritization of this work.
  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Enable PowerShell module auto-discovery in DSC

    I recently discovered that in my DSC resource I can't call a powershell cmdlet that internally calls into another powershell cmdlet - that fails because DSC doesn’t explicitly import the full powershell module, but only imports specific .psm1 files.

    Note, same (cmdlet calling another cmdlet) works perfectly fine when executed from Powershell cmd prompt. Let's fix it for DSC.

    12 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
    investigating  ·  Mark Gray responded

    Thank you for your feedback!

    Based on its current ranking compared to other feedback items and product schedule, work on this item is pending (and will be driven by) further customer input. If you did not open this issue and are also impacted by it, please vote this item up.

    MarkG

  2. Bug: DSC error when executing configuratin with Set-PSDebug -Strict - "$notAllowedValue cannot be retrieved because it has not been set"

    When you execute a configuration .ps1 script with Set-PSDebug -Strict turned on, you get the following error:

    PSDesiredStateConfiguration\Node : The variable '$notAllowedValue' cannot be retrieved because it has not been set.

    I can work around this by using the following code snippet:

    Set-PSDebug -Off
    $mofFile = SetPullMode -ComputerName $comp -OutputPath $mofFilePath -ConfigurationId $ConfigurationId -Thumbprint $cert.Thumbprint -PullserverUri $PullServerUri
    Set-PSDebug -Strict

    This sounds like a scoping issue in DSC somewhere with the notAllowedValue variable.

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    In Queue  ·  1 comment  ·  Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
  3. Officially release more DSC Resources

    We only have around 12 officially released DSC resources. I had expected PowerShell V5 would include more officially supported resources, but it was not to be. Please releae them, preferably via Windows Update.

    5 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    6 comments  ·  Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →

    What would you describe as “official”? We are moving forward with some of the x-named DSC resources in the Gallery, with the intent of removing the x and fully supporting them once they hit a certain level of quality. Is that sufficient?

  4. Test-DscConfiguration fails once running against remote machine

    Having the following script:

    configuration SimpleConfig2
    {

    Import-DscResource –ModuleName 'PSDesiredStateConfiguration'
    
    

    node $remoteCommputer
    {
    Environment TestVersion
    {
    Ensure = "Present" # You can also set Ensure to "Absent"
    Name = "TestEnvironmentVariable"
    Value = "TestValue2"
    }
    }

    }

    SimpleConfig2

    Start-DSCConfiguration -Path "SimpleConfig2" -Force -Wait -ComputerName $remoteCommputer -Credential $g_AutomationDefaultVMAccounCred -verbose

    $result = Test-DscConfiguration -Path "SimpleConfig2" -ComputerName $remoteCommputer -Credential $g_AutomationDefaultVMAccounCred

    The config is applied correctly, yet Test-DscConfiguration fails with the following message:

    The configurationData parameter is reserved for future use. The current configuration is used by default.

    + CategoryInfo          : InvalidArgument: (root/Microsoft/...gurationManager:String) [], CimException
    
    + FullyQualifiedErrorId : MI RESULT 4
    + PSComputerName : target-machine
    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
    investigating  ·  Mark Gray responded

    Anton,

    I am not able to reproduce your issue. What PS / WMF version are you running into this on? Also what OSes are running on the local and remote machines?

    MarkG

  5. Issue with DSCFileDownloadManager Credentials

    So, it seems as though in WMF 5.0 there is a regression in functionality. In WMF 4.0, you could set up a DSCFileDownloadManager and Credential to have a Target Node contact a Pull Server SMB Share and download new mof files and resources. Everything worked perfectly including Certificate based encryption of the credentials. However, in WMF 5, it seems as though the LCM of the Target Node attempts to contact the SMB Share Anonymously, even in credentials are provided. Now, in a Non domain joined environment, you can just provide EVERYONE full control and then change Local Security Policy such…

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
    planned  ·  Zachary Alexander responded

    This bug has been identified and the issue has been resolved. The fix will be available in future releases, including the Windows Insider Fast Ring preview

  6. If module version is not specified, composite configurations fail to load

    BUG
    Version occurs in: WMF5 Production Preview
    Previous versions? No.

    In a composite configuration scenario, if one of the composite resources contains an import-dscresource statement, and multiple versions of the module are available, the resource fails to load unless a moduleversion is specified.

    The resource works fine if there is only one version available on the machine in question, or a minimum version is specified.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
    investigating  ·  Mark Gray responded

    Justin,

    This behavior is common to all DSC resources, if I understand your issue correctly. If there are multiple versions of a module installed on your authoring system, you must specify the version that you intend to use in your configuration.

    What behavior are you expecting?

    MarkG

  7. OpenSource the Pull Server

    Advances to the current PullServer are, quite frankly, slow and moving in a direction questionable to most MVPs. Microsoft should follow their own lead they took with the DSC modules: opensource it and place it on GitHub so that the community can invest in making a tool that we'd actually like to use.

    Example of features still missing that everyone wants:
    1. certificate management (use self-signed or pki)
    2. web interface for compliance reporting

    Example of features added that are questionable/actually bad ideas:
    1. partial configurations (multiple pull server sources, mofs, and reports all being managed by the node? who…

    98 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    14 comments  ·  Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
    survey  ·  Mark Gray responded

    Justin,

    We totally understand that a robust Pull server / central management solution is something that is critical to your success with DSC. We have invested quite heavily in Azure Automation DSC (AA DSC) to fill many of these needs. With that said, I would be very interested to understand if the AA DSC solution does not work for you (and other customers) and why? Vote and comment if this is important to you.

    Also interesting feedback on our ‘bad ideas’. Thanks!

    MarkG

  8. Make modules and cmdlets available for current script

    The ability to package a script with the cmdlets and modules used to make that script.

    E.g.

    The ability to put a cmdlet at the start of the script such as:
    Monitor-ScriptModule -All

    Then as a module is imported or a cmdlet is used, the script will include the modules and cmdlets in some file that allows an admin to deploy the script to other workstations and the script is able to include the modules and cmdlets on older versions that may not have the cmdlets or modules included.

    This would help avoid older versions from not working because the…

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
  9. Multiple ConfigurationNames Results In Failure During Pull

    When multiple configurations names are specified in LCM configuration the pull fails get obtain any configuration.

    LCM Config Example

        ConfigurationRepositoryWeb HillIntl-Pull
    
    {
    ServerURL = &quot;<a rel="nofollow noreferrer" href="http://server1:8080/PSDSCPullServer.svc&quot;">http://server1:8080/PSDSCPullServer.svc&quot;</a>;
    AllowUnsecureConnection = $true;
    RegistrationKey = &quot;aaaa333-6c83-4636-a0cb-39b88a968849&quot;;
    ConfigurationNames = @(&#39;BaseConfig&#39;,&#39;WebServer&#39;);
    }

    Resulting errors

    Job {C7312E94-D405-11E5-80B5-00155D086627} :
    Message UpdateMetaConfig is not a valid value for GetActionResponse.
    HResult -2146233087
    StackTrack at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate)
    at System.Management.Automation.Runspaces.LocalPipeline.InvokeHelper()
    at System.Management.Automation.Runspaces.LocalPipeline.InvokeThreadProc()

    Job {C7312E94-D405-11E5-80B5-00155D086627} :
    This event indicates that failure happens when LCM is trying to get the configuration from pull server using download manager NULL. ErrorId is 0x1. ErrorDetail is A generic exception occurred during…

    6 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    7 comments  ·  Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
    investigating  ·  Mark Gray responded

    Thanks for the feedback Daniel. We are looking into the issue and will either get back to you with any follow-up questions or create a bug and fix the issue.

    Thanks for helping make DSC better!!
    MarkG

  10. Set ConfigurationMode per PartialConfiguration

    I would be nice to be able to set the ConfigurationMode on a PartialConfiguration. For example I want that my SQL config automatically remediated is, however the Windows OS config just alerts to changes. Similar to a Syntax like below

    [DSCLocalConfigurationManager()]
    configuration MyConfig
    {
    Node localhost
    {

      Settings
    
    {
    RefreshMode = &quot;Pull&quot;
    ConfigurationID = &#39;a5f86baf-f17f-4778-8944-9cc99ec9f992&#39;
    RebootNodeIfNeeded = $true
    }

    ConfigurationRepositoryWeb PullSvc1
    {
    URL = &#39;<a rel="nofollow noreferrer" href="http://pullserver1:8080/OSConfig/PSDSCPullServer.svc&#39">http://pullserver1:8080/OSConfig/PSDSCPullServer.svc&#39</a>;
    AllowUnSecureConnection = $true
    }

    ConfigurationRepositoryWeb PullSvc2
    {
    URL = &#39;<a rel="nofollow noreferrer" href="http://pullserver2:8080/SQLConfig/PSDSCPullServer.svc&#39">http://pullserver2:8080/SQLConfig/PSDSCPullServer.svc&#39</a>;
    AllowUnsecureConnection = $true
    }

    PartialConfiguration OSConfig
    {
    Description = &#39;Configuration for the Base OS&#39;
    ConfigurationSource = &#39;[ConfigurationRepositoryWeb]PullSvc1&#39;
    ConfigurationMode =…

    8 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    survey  ·  1 comment  ·  Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
  11. Allow multiple values for ConfigurationModeFrequencyMins of LCM (Local Configuration Manager)

    With a single value, now all settings in the DSC configuration are re-applied at the same interval.

    I would like to have some settings (may be non-critical) once , to be re-applied less frequently.

    This flexibility shall make LCM less stressed as well.

    3 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
  12. Bug: [nullable[enum]] DSC Property throws System.NotSupportedException in WMF5 RTM

    In WMF5 Production Preview the [nullable] flag was required to allow a DSC Property to be null valued. Without this flag a default value was being added to the mof file.

    In WMF5 RTM (Windows 10 installation) the [nullable] flag causes a System.NotSupportedException error to be thrown when running a configuration block.

    In WMF5 RTM, if the [nullable] flag is not used, null values are allowed. I believe this is the same functionality as WMF4.

    The [nullable] flag is shown in the MSDN documentation for DSC. https://msdn.microsoft.com/en-us/powershell/dsc/authoringresourceclass

    This should be fixed/clarified to the community.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
  13. Using dynamic parameters in a DSC resource

    I just tried to use dynamic parameters in a DSC resource. Unfortunately during testing, DSC prompted me with the following message:
    "The command Test-TargetResource of the PS module MSFTx<RESOURCENAME> does not implement the write property ApplicationPool mentioned in the corresponding MOF schema file C:\Program Files\WindowsPowerShell\Modules&lt;RESOURCENAME>\0.9.0.0\Ds
    cResources\MSFT
    xSPWordAutomationServiceApp\MSFT_<RESOURCENAME>.schema.mof. All write paramenters mentioned in the schema file must be implemented by the command Test-TargetResource."

    So it looks like Dynamic Parameters isn't supported in DSC resource, which is too bad. This forces me to add additional checks in my code.

    Can you please add this support to DSC?

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
  14. Partial Configurations handled by the LCM is a terrible implimentation

    Frequency: Always Happens
    Regression: feature unavailable in previous versions.

    The current implementation of Partial Configurations is ... to put it mildly ... awful. By placing the actual merge of the various MOFs on the agent you create more problems than you solve:


    1. Adding new configurations, which can be of a consequence as simple as an existing configuration getting too large, now requires a complete reconfiguration of each node so the nodes are aware of the change.


    2. There is no way to do any kind of collision detection or configuration validation before it reaches the host, as the pull server does…

    3 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
  15. DSCPullServer needs improved client registration

    The DSCPullServer is basically a knock off of Puppet-OpenSource project .. so let's finish some of the critically missing tools

    I'm talking mainly about client registration (or lack thereof).

    How it's done in puppetOS:
    1. Make sure "puppet" CNAME is in DNS
    2. Install puppet_agent (no questions asked, just install)
    3. On the puppet server, use "puppet cert list" to see pending machines, and "puppet cert sign" to add it.

    That's it I'm ready to write manifests and go for it. It issues the cert, tracks the box, basically handles everything.

    Compare that to DSC:
    1. Create a CName to…

    13 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
  16. Allow Import-DSCResource to leverage PowerShellGet to add missing modules dynamically

    Frequency: current as of WMF4.0 (unknown in 5)

    Right now, DSC is really only valuable in "established" environments with push configurations only looking for local module directories or a "Defined" repository already setup. This makes using DSC in a "consulting capacity" almost useless as I have to no only have a script to establish settings for a new machine ... but I need to copy modules into the right path first.

    It would be awesome if I could add a flag to import-dscresource to tell the configuration to download the modules it needs via PowerShellGet if they are missing (maybe…

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
  17. Generate DSC from existing servers

    For those of us with heavily-configured snowflake servers, it would great if it were possible to generate DSC files from existing builds. This may not be possible in all areas, but perhaps a subset of areas could be supported, with IIS 7.0+ at the top of the list.

    14 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    survey  ·  3 comments  ·  Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
  18. Bug: Trouble Setting LCM for Partial Configurations

    I've been unable to set partial configurations with WMF 5 PP, so I waited to RTM to see if it was resolved. It's not. I originally posted on powershell.org but without success. Here's the original post and link:

    I'm using WMF 5 Production Preview on Server 2012 R2, trying to set a node to use Partial Configurations. I've tried with a remote node and localhost, but all give an error. Sample config (I've tried a few variations, with more or less partial configs):

    [DSCLocalConfigurationManager()]
    configuration foo
    {

    Node localhost
    {

    PartialConfiguration SomeConfig
    {
    RefreshMode = 'Push'
    }
    }
    }

    foo…

    12 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
  19. BUG: DSC resource name cannot start with a number if another resource depends on it

    I have a resource named [xHotfix]2012R2_April2014CU and if I use that in the depends on field for another resource, I get this error:

    Test-DependsOn : The format of the resource reference '[xHotfix]2012R2CU1' in the Requires list for resource '[xHotfix]2012R2April2014CU::[ContosoWindowsUpdates]SampleConfig' is not valid. A required resource name should be in the format '[<typename>]<name>', with alphanumeric characters, spaces, '', '-', '.' and '&#39;.

    If I add an alpha character to the resource name, then it generates correctly.

    xHotfix 2012R2_CU1

        {
    
    Path = &quot;$InstallRoot\WindowsUpdates\2012R2\Windows8.1-KB2919355-x64.msu&quot;
    Id = &quot;KB2919355&quot;
    Ensure = &quot;Present&quot;
    DependsOn = &quot;[WindowsFeature]DotNetFX3dot5&quot;
    }

    xHotfix 2012R2_April2014CU
    {
    Path =…

    3 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
    investigating  ·  Mark Gray responded

    Thanks for the feedback!

    We have looked into this issue and cannot seem to reproduce it in the latest builds WMF 5.0 RTM. Please try to reproduce it with the RTM bits and let us know if you still have the issue.

    Regards,

    MarkG

  20. BUG : WMF5 RTM Pull Server HTTPS

    I have setup new DSC Pull Server HTTPS with WMF 5 RTM on Windows server 2012 r2 .

    Any client with WMF 5 RTM installed is able to pull configuration from Pull Server without certificate installed on the machine .

    Even if AllowUnsecureConnection is set to $false in LCM .

    I have tested that on WMF 4.0 machines and I'm getting error if the certificate is not presented .

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
    investigating  ·  Mark Gray responded

    Mariusz,

    Thanks for the feedback!

    We are attempting to investigate this issue but need more details from you in order to make progress.

    Is the issue that you are running into as follows:
    - WMF 5. based DSC Pull Server configured with HTTPS and server certificate installed properly. I assume this is not a certificate issued by a trusted authority, correct?
    - A WMF 5.0 RTM client does not have the trusted SSL certificate installed in the trusted root folder and the client is able to successfully connect to the Pull Server.
    - A WMF 4.0 client fails to connect when it does not have the trusted root cert installed.

    Please let us know if this is or is not what you are experiencing.

    Thanks, again,

    MarkG

  • Don't see your idea?

Feedback and Knowledge Base