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. 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 →
  2. 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 →
  3. 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

  4. 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 →
  5. Add MaintenanceWindow paramters to PartialConfiguration DSC

    Votes from Connect: 4

    Original Date Submitted: 12/13/2014 2:03:27 AM

    Description:
    Contact Information
    Handle: RobCannon
    Site Name: PowerShell
    Feedback ID: 1053308


    Frequency: Always Happens
    Regression: Yes, this happens in all previous versions

    Problem Description:
    I would like to a parameter in a PartialConfiguration section to specify a time period.

    Some configurations would always be running and could fix configuration drift. But other configurations (that would cause a service disruption if applied) could be target to only run during a specified maintenance window. The window parameter should allow you to specify a time window and either a day of the week…

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

    We’ll send you updates on this idea

    investigating  ·  0 comments  ·  Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
  6. 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 →
  7. 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 →
  8. Inline help for DSC resource properties

    Votes from Connect: 38

    Original Date Submitted: 3/20/2015 9:34:20 PM

    Description:
    Contact Information
    Handle: Trevor Sullivan [MVP]
    Site Name: PowerShell
    Feedback ID: 1192392


    Problem Description:
    To continue the trend of having built-in help with PowerShell structures, it would be great to add support for help documentation for DSC resource properties, in class-based DSC resources.

    My initial suggestion was to put comment-based help just prior to a [DscProperty()] declaration in a class, but Ravi suggested having a HelpMessage property added to the [DscProperty()] attribute, which I think is a better idea.

    Product Studio item created by Connect Synchronizer due to creation…

    9 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 →
  9. DSC Environment Resource Expands PATH Environment Variable

    Votes from Connect: 3

    Original Date Submitted: 11/25/2015 1:33:11 AM

    Description:
    Contact Information
    Handle: aolszowka
    Site Name: PowerShell
    Feedback ID: 2054029


    Frequency: Desired State Configuration (DSC)
    Regression: Prior to running the below DSC ensure that the environment variable is not already expanded/mangled, you can do this either by pulling up the System Environment Variables Dialog from System, or by querying the registry:

    REG.EXE QUERY "HKEYLOCALMACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment" /V "PATH"

    We should expect to see something similar to the following:

    HKEYLOCALMACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment

    PATH    REG_EXPAND_SZ    %SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SystemRoot%\System32\WindowsPowerShell\v1.0\
    

    Create a new DSC Script with the following:

    Environment EnvVarPATHNotepad2

        {
    
    7 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 →
  10. MOF Files Include Authoring Metadata

    Votes from Connect: 4

    Original Date Submitted: 8/20/2014 2:21:09 AM

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


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

    Problem Description:
    When converting configuration blocks to .mof files, they .mof files contain authoring metadata that causes the .mof file's contents and checksum to change, even when none of the configuration in the .mof file has changed. This makes it hard to know when a .mof file's configuration has really changed or not. All .mof files essentially look like they are always changing. This makes…

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

    We’ll send you updates on this idea

    investigating  ·  0 comments  ·  Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
  11. 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 →
  12. 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 →
  13. 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 →
  14. 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

  15. Add PSValidFrom/PSValidTo common properties for DSC resources

    Votes from Connect: 10

    Original Date Submitted: 10/6/2015 1:58:16 AM

    Description:
    Contact Information
    Handle: PowerShellDon
    Site Name: PowerShell
    Feedback ID: 1871366


    Problem Description:
    Suggest adding a PSValidFrom and PSValidTo common property set (a la PSCredential). These would need to implicitly become part of the key when exporting the MOF. The idea is to help cover maintenance and task windows: From DateTime to DateTime, I want Service ___ Stopped; from DateTime to DateTime, I want it Started. So that becomes:

    Service BITS {
    Name=BITS
    Present=$True
    StartMode=Auto
    PSValidFrom=02:00:00UTC
    PSValidTo=21:00:00UTC
    }
    Service BITS {
    Name=BITS
    Present=$True
    StartMode=Disabled
    PSValidFrom=21:00:00UTC
    PSValidTo=02:00:00UTC
    }

    Considerations: DateTime could…

    3 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. Get-DscConfiguration Fails With Embedded CIM type

    Votes from Connect: 3

    Original Date Submitted: 8/28/2015 4:09:14 AM

    Description:
    Contact Information
    Handle: Steve Murawski
    Site Name: PowerShell
    Feedback ID: 1721560


    Frequency: Desired State Configuration (DSC)
    Regression: install-module cWebAdministration
    configuration cWebsite_StopWebsite
    {

    param
    
    (
    # Target nodes to apply the configuration
    [string[]]$NodeName = &#39;localhost&#39;
    )

    # Import the module that defines custom resources
    Import-DscResource -ModuleName cWebAdministration

    Node $NodeName
    {
    # Install the IIS role
    WindowsFeature IIS
    {
    Ensure = &quot;Present&quot;
    Name = &quot;Web-Server&quot;
    }

    # Stop the default website
    cWebsite DefaultSite
    {
    Ensure = &quot;Present&quot;
    Name = &quot;Default Web Site&quot;
    State = &quot;Stopped&quot;
    PhysicalPath = &quot;C:\inetpub\wwwroot&quot;
    DependsOn = &quot;[WindowsFeature]IIS&quot; …

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

    This should be resolved with WMF 5.0. Please let us know if this is reproducible with WMF 5.0 RTM.

  17. Devices.edb does not exists when WMF5 is installed prior to deploying DSC Pull Server

    Votes from Connect: 5

    Original Date Submitted: 4/29/2015 2:50:27 AM

    Description:

    Contact Information
    Handle: Ben Gelens
    Site Name: PowerShell
    Feedback ID: 1286605


    Frequency: Desired State Configuration (DSC)
    Regression: Install a clean Windows Server 2012R2 system.
    Install WMF5 Feb preview.
    Download and install xPSDesiredStateConfiguration module.
    Run configuration:
    configuration PullSRV
    {

    Import-DSCResource -ModuleName xPSDesiredStateConfiguration
    
    xDscWebService PSDSCPullServer
    {
    Ensure = &#39;Present&#39;
    EndpointName = &#39;PSDSCPullServer&#39;
    Port = 8080
    PhysicalPath = &quot;$env:SystemDrive\inetpub\wwwroot\PSDSCPullServer&quot;
    ModulePath = &quot;$env:PROGRAMFILES\WindowsPowerShell\DscService\Modules&quot;
    ConfigurationPath = &quot;$env:PROGRAMFILES\WindowsPowerShell\DscService\Configuration&quot;
    State = &#39;Started&#39;
    CertificateThumbPrint = &#39;AllowUnencryptedTraffic&#39;
    }

    }
    Setup an simple config and add it to configuration repo using GUID.MOF and generate a checksum

    Problem Description:
    The…

    3 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 →
  18. Service DSC resource should not have a default $State

    The Service DSC resource defaults to state = running. It would be great to be able to say "I want to make sure the service is installed, but I don't care what state it's currently in."

    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

    Thanks for the feedback!

    We will take this into consideration in a future release.

    MarkG

  19. PowerShell DSC needs to support "Property Sets"

    Votes from Connect: 12

    Original Date Submitted: 3/24/2015 8:05:35 AM

    Description:
    Contact Information
    Handle: Trevor Sullivan [MVP]
    Site Name: PowerShell
    Feedback ID: 1199561


    Problem Description:
    NOTE: I believe this functionality is already in progress, but I wanted to make sure it was documented in the official PowerShell feedback channel.

    PowerShell DSC Resources need the ability to support multiple "property sets" similar to the "parameter sets" that are

    Suggested implementation:


    1. Add a "PropertySetName" property to the [DscProperty()] attribute (eg. [DscProperty(PropertySetName = "PropertySet1", Key)]

    2. Add a private property (eg. $PropertySetName) to the [DscResource()] attribute, to ensure that the Get(), Test(), and Set()…
    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 →
  20. Cmdlets in the WebAdministration module occasionally generates errors when used in a custom DSC configuration

    Votes from Connect: 5

    Original Date Submitted: 9/17/2014 2:30:56 AM

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


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

    Problem Description:
    When using cmdlets from the WebAdministration (IIS) PowerShell module in a custom DSC resource, errors are thrown when invoking the Get/Set/Test-TargetResource functions (for example by running Test-DscConfiguration).

    The error thrown is:
    Unable to cast COM object of type 'Microsoft.IIs.PowerShell.Framework.AppHostQueryProcessor' to interface type 'Mic
    rosoft.IIs.PowerShell.Framework.IAppHostQueryProcessor'. This operation failed because the QueryInterface call on the COM component for the
    interface with IID '{6E0E6BE3-71C1-4A66-800E-11B9CBA00EAB}' failed…

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

Feedback and Knowledge Base