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. DSC StatusRetentionTimeInDays is not deleting files

    WMF 5 RTM

    StatusRetentionTimeInDays is not deleting files in C:\Windows\System32\Configuration\ConfigurationStatus as per http://powershell.org/forums/topic/cwindowssystem32configurationconfigurationstatus-directory-growing/#post-40747

    25 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 →
  2. 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 →
  3. Allow 'resource syntax' for nested configurations

    Currently, we can dot source a configuration from another file and use it as a nested configuration, but to pass any parameters they need to be passed or splatted as regular PowerShell arguments (because, well, they really are.)

    It would be nice if the nested configurations could receive their parameters with the same syntax as a 'proper' resource.

    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 →
  4. #Group resource fails to add a domain user\group when a domain user\group exists

    Cannot enforce a domain user or domain group in a local group when the group contains any domain member. Example. local TestGroup contains domain\user1 and domain\user2. If domain\user1 is removed from TestGroup, DSC configuration cannot add domain\user1 back to TestGroup using the Group resource.


    Group TestGroup5
    {
    GroupName = 'TestGroup5'
    Ensure = 'Present'
    MembersToInclude = user1@domain.com','user2@domain.com'
    Credential = $DomainCredential
    }


    Is this a bug?

    2 votes
    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 →
  5. DSC File Resource Recurse directory description is wrong

    The documentation for the DSC File Resource states that the Recurse is a) only valid for directories and b) only for sub-directories. This would imply that any files in a SourcePath would be copied. However, they are not. $Recurse has to be $true to pull files. If not, it just makes sure the directory exists.

    However, this requires that I have the whole recursive directory kept on my sourcepath as well vs. just a few files.

    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 →
  6. Test-PartialConfiguration / LCM Test Server

    When using Partial Configurations, add a Test-PartialConfiguration command that accepts the mof files and checks for problems before sending it to the LCM.

    I can run pester tests on each of the configuration scripts as part of my pipeline to make sure each of them are ok as single files, but to actually see what happens on the LCM and how it combines the mofs would requires like a LCM TestServer without actually enacting on the real node.

    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 →
  7. Using hashes inside Composite Resources

    Instead of using 20 "single" Service Resource, we can now use ServiceSet, however its only if the parameters for the services are the same like State for example.

    IF i have 10 services i want their state to be Started and 10 i want to be stopped , i have to use 2 ServiceSets.

    Would be helpful to be able to use just one Service set, but then have the parametes use either positional values or allow hashing

    ServiceSet ServiceSetComposite{
    Name ='AudioSrv','WinMgmt'
    State='Started','Stopped'
    Ensure='Present'
    }

    or
    (bit better as it allows Ensure to be taken into calculation

    ServiceSet ServiceSetComposite{
    Service…

    2 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. Control in Composite Resources

    Add option to use DependsOn inside a Composite Resource, between the inner members of the resource. Like in ServiceSet, running it with multiple services i cant use the DependsOn commands. Would be nice if i could do this:

    ServiceSet ServiceSetComposite{
    Name='audiosrv','winmgmt'
    Ensure='Present'
    Order = 'winmgmt',*
    }
    As in the order i want the services to be done is winmgmt first, then what ever comes after and then * to symbol the rest of the services

    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. LCM Extensible Architecture - PowerShell

    Type: Feature Request
    Summary: Make LCM extensible simply by adding a psm1 in a folder, which will be loaded automatically.
    Details here: https://github.com/gaelcolas/LCM_ExtensibleArch

    Here's the workflow:
    1. LCM loads a psm1 file(s) from a pre-defined directory (or defined in LCM meta-configuration).
    2. Every LCM events are triggered and forwarded into the extensions' session
    3. $Global variables of the extension should be accessible from the Test/Set/Get methods of the DSC Resource
    3. The author of the PSM1 extension register-EngineEvent for required LCM Events
    4. He defines Event Handlers Actions that can call psm1's exported functions

    Having this extensible architecture would allow…

    25 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 →
  10. Allow ConfigurationModeFrequencyMins < 15 and RefreshFrequencyMins< 30

    Hi,
    as I am using DSC to deploy fresh clouds and as I have some nodes and resources dependancies, I have to wait for nodes to report, and then nodes to deploy.
    Because ConfigurationModeFrequencyMins and RefreshFrequencyMins minimum are very large, fresh cloud deployments take some time.

    Please allow minimums as 1

    3 votes
    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 →
  11. 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 →
  12. Invoke-DSCResource on WindowsFeatureSet fails

    As subject says. Example is below

    PS C:\Windows\system32> Invoke-DscResource -Name WindowsFeatureSet -Property @{Name = "Storage-Services"; Ensure = "Present" } -Method test -ModuleName PSDesiredStateConfiguration
    Invoke-DscResource : Failed to serialize properties into CimInstance.
    At line:1 char:1
    + Invoke-DscResource -Name WindowsFeatureSet -Property @{Name = "Storag ...
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    + CategoryInfo          : NotSpecified: (:) [Invoke-DscResource], SerializationException
    
    + FullyQualifiedErrorId : System.Runtime.Serialization.SerializationException,Microsoft.PowerShell.DesiredStateConfiguration.C

    ommands.InvokeDscResourceMethodCommand

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

    Thanks for the 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

  13. Remove Dependency on TLS 1.0 for HTTPS Pull Server

    After disabling TLS 1.0 on our Pull Server and nodes, the nodes are unable to re-register with the Pull Server. This is keeping us from making changes to the LCM on nodes.

    I have posted on PowerShell.org forum about this:
    http://powershell.org/wp/forums/topic/tls-1-0-required-for-https-pull-server/

    1 vote
    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 →
  14. Get-DSCResource -Syntax for WindowsFeatureSet incorrect

    Get-DscResource for WindowsFeatureSet showing "ensure" parameter as being optional, while it's actually required

    <PRE>

    PS C:\windows\system32> get-dscresource windowsfeatureset -Syntax
    WindowsFeatureSet [String] #ResourceName
    {

    [DependsOn = [String[]]]
    
    Name = [String[]]
    [Ensure = [String]]
    [Source = [String]]
    [IncludeAllSubFeature = [Boolean]]
    [Credential = [PSCredential]]
    [LogPath = [String]]

    }
    </PRE>

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

    Thanks for the feedback, Gregory! This certainly is a bug albeit a little different that what you have described. The Ensure property should be optional but it should default to ‘Present’ if it is not provided just like the underlying resource does. I have opened a bug for this.

    MarkG

  15. Having ";" in PSModulePath breaks Get-DSCResource cmdlet

    If your PSModulePath ends with ";" then Get-DSCResource fails on line 3810 which is using Test-path to check empty path with no -ErrorActionVariable set will always fail

    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 →
  16. ValidatePattern doesn't work as expected in class based DSC resources

    When using ValidatePattern in a class based resource, this should be evaluated once the configuration is generated. However, it's only evaluated the moment the LCM tries to apply the configuration, which then throws a not very helpful 'Failed to create an object of PowerShell class InsertNameOfClassHere' if the ValidatePattern check returns false.

    Demo code:
    [DscResource()]
    Class MyClass {

    [DscProperty(Key)]
    
    [ValidatePattern(&#39;Client|Server&#39;)]
    [string]$Input

    [myclass] Get () {
    $Class = $This.Input
    return [myclass]$Class
    }

    [Bool] Test () {
    return $false
    }

    Set () {
    $Class = $This.Input
    Write-Verbose $Class
    }

    }

    Configuration:
    configuration SetMyClass
    {

    Import-DscResource -ModuleName dscClass -Name MyClass -ModuleVersion 1.0.0.0
    
    

    MyClass…

    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. Shared Partial Configurations (ConfigurationNames) and encrypted credentials.

    At the moment to use encrypted credentials in partial configurations with ConfigurationNames it is necessary to share certificate across all nodes, else decryption will fail. I believe it should be technically possible to use more dynamic approach:
    - encrypt MOF with certificate for which pull server has private key
    - during registration client would send over certificate for which it has private key so that pull server can encrypt any credentials in the mofs sent to this node with this certificate.

    At the moment it's manual labour on the operators side: make sure that encrypt/decrypt just works. It would be…

    18 votes
    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 →
  18. why can't I use a http-based "Path" in the Archive Resource ?

    When I use the Archive Resource it appeares to be restricted to SMB or UNC Path's.

    I would like to configure a http based sourcepath.

    1 vote
    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 →
  19. 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.

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

Feedback and Knowledge Base