Mark Gray

My feedback

  1. 73 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  PowerShell » Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
    Mark Gray commented  · 

    Changed the title to better reflect what this request is about and changed the status to survey. We have had lots of customers run into this issue and the current number of votes does not seem to reflect our current understanding of it's importance so if this is something that is important to you, vote it up.

  2. 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  ·  PowerShell » Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
    Mark Gray commented  · 

    Brandon,

    Are you seeing this issue in TP5?

    MarkG

  3. 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  ·  PowerShell » 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

    Mark Gray commented  · 

    Hey Daniel,

    The other thing that may be causing you trouble is the name of the configuration that is generating the MOF. It needs to match the name of the MOF when you are using partial configurations. So the configurations for my example below would be as follows:

    Configuration BaseConfig #Name of configuration which is saved in MOF
    {
    Node BaseConfig #Name of MOF generated by configuration
    {
    ...
    }
    }

    Configuration WebServer #Name of configuration which is saved in MOF

    {
    Node WebServer #Name of MOF generated by configuration
    {
    ...
    }
    }

    This is a result of the way that we handle partial configurations when using configuration names. We first use the name to get a MOF with the name then we check the configuration name within the MOF to ensure it is the same.

    Hopefully this helps you work through your issue. Let me know if it does not. I am happy to work with your example offline to get you running if need be.

    MarkG

    Mark Gray commented  · 

    Yes, multiple configurations are supported when defined in the DB on the pull server but you also currently need to have each of the configurations defined as partial configurations. We recognize that this is not ideal since it means that you need to change configuraitons both on the pull server and on the target node. We are looking into how to simplify this for future releases.

    Mark Gray commented  · 

    You can only use multiple configurations in combination with partial configs so you would need a couple more blocks below this as follows:
    [DscLocalConfigurationManager()]
    Configuration Meta
    {
    ConfigurationRepositoryWeb HillInt-Pull
    {
    ServerURL = 'http://server1:8080/PSDSCPullServer.svc';
    AllowUnsecureConnection = $true
    RegistrationKey = 'aaaa333-6c83-4636-a0cb-39b88a968849'
    ConfigurationNames = @('BaseConfig','WebServer')
    }

    PartialConfiguration BaseConfig
    {
    Description = "Base configuration to be applied to all servers"
    ConfigurationSource = @("[ConfigurationRepositoryWeb]HillInt-Pull")
    }

    PartialConfiguration WebServer
    {
    Description = "WebServer configuration"
    ConfigurationSource = @("[ConfigurationRepositoryWeb]HillInt-Pull")
    }
    }

    Also please keep in mind that the ConfigurationNames property is only used during registration. After that point, the configurations that the target node receives is dictated by the pull server.

    MarkG

  4. 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  ·  PowerShell » 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

    Mark Gray commented  · 

    Totally get it, Justin. Thanks for the additional context.

    I have filed a bug for this and we will take it into consideration.

Feedback and Knowledge Base