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. Test-DscConfiguration returns a String instead of a Boolean value

    Test-DscConfiguration returns a String instead of a Boolean value.

    Contrary to what is mentionned in the documentation, the function Test-DscConfiguration does not return a boolean value.

    When you do a GetType() of the return value of Test-DscConfiguration you get a string with 'true' or 'false'.

    It's impossible to do a simple if (Test-DscConfiguration) because the string 'false' enter inside the if, we are forced to cast the return value of this cmdlet in boolean or to do the comparison with -eq $True, which seems to cast it automatically.

    6 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 →
  2. Allow variable input to be passed to import-dscresource

    To keep configurations and composite resources as modular as possible, we should be able to pass an array of module specifications as a parameter.

    Consider the following:

    [Parameter()]

        [System.Collections.Hashtable[]]
    
    $DscResourcesToImport = @(
    @{ModuleName='xPSDesiredStateConfiguration'; ModuleVersion='3.9.0.0'},
    @{ModuleName='xComputerManagement'; ModuleVersion='1.4.0.0'}
    )
    )

    foreach ($Resource in $DscResourcesToImport)
    {
    $ModuleSpec = @{ModuleName="$Resource.ModuleName"; ModuleVersion="$Resource.ModuleVersion"}
    Import-DscResource -ModuleName $ModuleSpec
    }

    This fails with the error: "Arguments must be constant"

    Thanks for considering this.

    6 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 →
  3. Allow dot sourcing PowerShell Classes based DSC Resources into the psm1 module file

    WMF 5.0 lets you create DSC Resources using Powershell Classes like so:

    [DscResource()]
    class MyDSCResource
    {
    ...
    }

    But right now it will only look in the .psm1 file. If you try to dot source a class based DSC resource into the .psm1 file then Get-DSCResource can't find it and it can't be used in DSC configurations.

    We have many DSC resources combined into a single module, and our .psm1 file is getting difficult to manage. If two people are working on different resources they are likely to have a git merge conflict.

    We would prefer to have…

    6 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 →

    We are working on enabling support for multiple psm1 files. This will allow you to group different class-based DSC resources into different files.

  4. BUG: Using ConfigurationNames generates a weak certificate

    If a Node is configured using a RegistrationKey so that ConfigurationNames can be used, then the CertificateID attribute is ignored under the ConfigurationRepositoryWeb block, and instead a self-signed certificate is generated called "DSC-OaaS".

    This certificate is used for both client authentication to the pull server as well as encrypting configuration Mofs at rest on the server host.

    The problem is two fold:


    1. Becuase the CertificateID gets ignored when using CONfigurationNames, admins cannot control the key length or encryption of the files.


    2. The certificate generated is a SHA-1 1024bit length. This is completely unacceptable as 1024 went out of use years…

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

    We’ll send you updates on this idea

    planned  ·  3 comments  ·  Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
  5. 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

  6. DSC: Group resource fails to add a domain user to a local group without domain credentials

    Votes from Connect: 8

    Original Date Submitted: 8/28/2014 4:44:56 AM

    Description:
    Contact Information
    Handle: Aaron Jensen
    Site Name: PowerShell
    Feedback ID: 957378


    Frequency: Always Happens
    Regression: No, this is new to the most recent version

    Problem Description:
    The Group resource fails to add a domain user to a local group without domain credentials. Also, if using credentials, they have to be in the same domain as the account being added, so you can't mix accounts from different domains.

    I know the LCM can talk to our AD because I wrote the following Script resource which works. This is rough and…

    6 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 →
  7. DSC registry resource support '/' in the registry path.

    DSC registry resource support '/' in the registry path.

    If you use a path containing a / e.g. "HKEYLOCALMACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Ciphers\RC2 40/128" then the builtin registry resource you end up with an error or the wrong registry path being created.

    This config will not work. I've have to create my own module to create the folder and then us the registry resource to create the actual key.

        Registry &quot;DisableCipherRC240128&quot;
    
    {
    Key = &quot;HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Ciphers\RC2 40/128&quot;
    ValueName = &quot;Enabled&quot;
    ValueType = &quot;Dword&quot;
    ValueData = &quot;0&quot;
    Ensure = &quot;Present&quot;
    Force = $true
    }

    The register resource should support / in the path.

    5 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 →
  8. Partial Configurations should support validating ExclusiveResource reservations during publish or pull

    In the current implementation for Partial Configurations, the ExclusiveResources in the configuration fragment can be used to reserve resource modules or resources to a specific fragment. However, this is not validated until runtime. So, if there are two fragments that are using same resource modules and one fragment has those resources exclusively locked, the configuration enact will fail during runtime.

    These exclusive resource reservation checks should be done either at the publish time (push) or before enacting the configuration after a pull is complete.

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

    We’ll send you updates on this idea

    survey  ·  0 comments  ·  Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
  9. 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?

  10. Support text-oriented configuration management

    ... in a folder at C:\config containing text files (and perhaps a similar folder in the user's home directory). Changing those text files would directly apply changes to Windows settings. Services could read those files directly or use a Windows text-based configuration management API.

    Text-oriented configuration has many advantages: it makes devops-style workflows much more simple, entire server configurations could be versioned in git or svn along with the apps they host, spinning up new servers would be much simpler, and tools like Chef and Puppet would integrate far more smoothly and simply with Windows.

    I suggest this as a…

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

    We’ll send you updates on this idea

    3 comments  ·  Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
  11. [BUG] Cannot import both PSDesiredStateConfiguration in-box module and PSDscResources (gallery module) in the same configuration

    OS: Windows Server 2016 1607 (14393.1593)
    PSVersionTable:
    Name Value


    PSVersion 5.1.14393.1532

    PSEdition Desktop

    PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}

    BuildVersion 10.0.14393.1532

    CLRVersion 4.0.30319.42000

    WSManStackVersion 3.0

    PSRemotingProtocolVersion 2.3

    SerializationVersion 1.1.0.1

    PSDscResource module: v2.8.0.0

    Take a look at this configuration:
    Configuration DependentConfig
    {

    Import-DscResource -ModuleName PSDscResources -Name Registry
    
    

    Node MyNode01
    {

    File SetupScript
    {
    DestinationPath = &#39;C:\Scripts\hello.txt&#39;
    Contents = &#39;somecommand&#39;
    Type = &#39;File&#39;
    Ensure = &#39;Present&#39;
    DependsOn = &#39;[Registry]regCheck&#39;
    }

    Registry regCheck
    {
    Key = &#39;HKEY_LOCAL_MACHINE\SYSTEM\SomeKey&#39;
    ValueName = &#39;SomeValue&#39;
    ValueData = 0
    ValueType = &#39;DWord&#39;
    Ensure = &#39;Present&#39;
    }
    }

    }

    DependentConfig -OutputPath C:\DependentConfig

    This requires PSDscResources module version 2.8.0.0 from the gallery…

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

    We’ll send you updates on this idea

    investigating  ·  4 comments  ·  Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
  12. Bug: DSC Decryption across Servers not Working

    I have created a Pull Server Configuration. I have created the DSC Signing Certificate using a custom template on a Enterprise Root CA which has worked for 2012R2 nodes and also tested using xDSCUtils New-xSelfSignedDscEncryptionCertificate. Using the same Certificate to Compile and Execute the MOF on the same Computer works, it is only if you compile on one and execute on another that the problems arise.
    I kept getting errors when passing in credentials. I therefore wrote a tiny custom DSC Resource that Displays the Password as clear text when I run Start-DSCConfiguration -Wait -Verbose
    You can find it here …

    4 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 →
  13. 4 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 →
  14. BUG: WMF 5.0 RTM Encrypted MOFs copied to Windows temp directory in plain text

    Running on Windows 2012 R2 servers.

    MOFs and their checksums seem to be getting copied to the Windows temp directory on target nodes in plain text. The files below show up on nodes that have had their configurations deployed via either the push or pull methods.

    C:\Windows\Temp##############\localhost.mof
    C:\Windows\Temp##############\localhost.mof.checksum

    The configuration MOFs in C:\Windows\System32\Configuration look like they are encrypted correctly.

    4 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. BUG: Cim instances are not compiled correctly into MOF

    I'm trying to create a function that returns the bindinginfo for a website. This is intended to reduce the complexity of my dsc resource file that will have 20/30 websites with similar bindinginfo based on the node name. Anyway, it seems like the dsc compiler doesn't support cim instances. Doing the same thing with credentials actually works, so I wonder why this is the case for binding infos.

    This is an example to reproduce the problem

    configuration DscTest
    {
    Import-DscResource -ModuleName xWebAdministration;

    Node localhost
    {

    xWebsite TestWebSite
    
    {
    Ensure = &quot;Present&quot;
    Name = &quot;TestWebSite&quot;
    PhysicalPath = &quot;C:\inetpub\test&quot;
    BindingInfo = (Get-TestBindingInformation
    4 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    Can you take a look below and leave a comment to let me know if the workaround is sufficient for your purposes? If so, I will close this item. If not, I will keep it marked as survey.

  16. [Bug] Creating Local Users Fails Test-DSCConfiguration if the Users are Disabled

    I can successfully create a disabled local user account on a non-domain joined server which has a password policy enforced.

    If I try to create the disabled account with out a password, or one in violation of the policy, the configuration fails. This is expected.

    If I create a disabled local user account with a password that meets the requirements, the configuration applies. When I run Test-DSCConfiguration the test fails with:
    PowerShell DSC resource MSFT_UserResource failed to execute Test-TargetResource functionality with error message:
    There could be a possible connection error while trying to use the System.DirectoryServices API's.Exception calling
    "ValidateCredentials" with…

    4 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 →
    survey  ·  Mark Gray responded

    Phil,

    Sounds like a valid bug. Thanks for bringing it to our attention. I have opened a bug in our internal system to track this to resolution.

    MarkG

  17. Bug: WMF5 PullServer Configuration still accepts "IsComplianceServer" attribute

    When provisioning a new PullServer using WMF5, the "IsComplianceServer = $true" can still be specified a a valid attribute in the configuration despite the service being replaced by the reporting server role.

    It seems benign, however if this is done the resulting Pull Server will no longer work with ConfigurationNames and only work with ConfigurationID configured nodes. The process generates no errors, nodes will even state that registration of AgentID was successful, but clients will silently receive no files when they query for the appropriate <configurationname>.mof.

    This makes for a very difficult bug to track down if someone were to…

    4 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 →
    survey  ·  Mark Gray responded

    Justin,

    Thank you for your feedback! We recognize that this adds confusion to the deployment of the WMF 5.0 pull server and are looking into a solution.

    MarkG

  18. Add a timeout period property on the DSC Service Resource

    Votes from Connect: 4

    Original Date Submitted: 9/26/2014 7:49:25 PM

    Description:
    Contact Information
    Handle: Jan Egil Ring
    Site Name: PowerShell
    Feedback ID: 982292


    Frequency: Always Happens
    Regression: No, this is new to the most recent version

    Problem Description:
    There should be a property on the DSC Service Resource for configuring the stop/startup timeout value for a service.

    As an example, when using the xDhcpServerScope and configuring the DHCP Server service as a dependent resource the following error arise when the DHCP Server service is stopped:

    VERBOSE: [DEMODHCP02]: LCM: [ Start Set ] [[Service]DHCP]
    VERBOSE: [DEMODHCP02]: [[Service]DHCP] Failure starti
    ng service…

    4 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 →
  19. IncludeManagementTools in WindowsFeature

    Votes from Connect: 10

    Original Date Submitted: 9/2/2014 3:45:04 AM

    Description:
    Contact Information
    Handle: Andrew Barnes
    Site Name: PowerShell
    Feedback ID: 961489


    Frequency: Always Happens
    Regression: I don

    Problem Description:
    Could the WindowsFeature resource be updated to have the IncludeManagementTools switch.

    (it's a quick win) ;)

    Product Studio item created by Connect Synchronizer due to creation of feedback ID 961489 (http://connect.microsoft.com/PowerShell/feedback/ViewFeedback.aspx?FeedbackID=961489).

    Repro Steps:
    PS > Get-DscResource windowsfeature -Syntax
    WindowsFeature [string] #ResourceName
    {

    Name = [string]
    
    [ Credential = [PSCredential] ]
    [ DependsOn = [string[]] ]
    [ Ensure = [string] { Absent | Present } ]
    [ IncludeAllSubFeature =
    4 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 →
  20. Add support for Conditions on DSC Resources

    Currently the only way to apply conditions is using the Script resource. However the Script Resource has limitations especially when dealing with Azure credential objects. Conditions would be very useful, similar to what SCCM uses for it's Configuration Items.
    Syntax would be:

     Condition = [Boolean PowerShell Expression]
    

    Example #1: Apply a Package Resource only for SQL servers
    Example #2: Apply a WindowsFeature Resource only for IIS servers.

    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 →
  • Don't see your idea?

Feedback and Knowledge Base