Update LCM Settings on a Client Configured to a Pull Server

This topic contains 2 replies, has 2 voices, and was last updated by  Ryan Strope 3 months ago.

  • Author
    Posts
  • #71279

    Ryan Strope
    Participant

    Just starting out playing around with DSC in our environment (I've been coding in C# and PowerShell for years)

    I've setup a Server 2016 VM running an SSL DSC Pull Web Service

    I've successfully created a LocalConfigurationManager script and a simple test configuration to make a folder and a file. I've gone through the process of mofing, checksuming, and pushing the meta.mof to the target systems which all happily picked it up and grabbed the test configuration I had created.

    Then it dawned on me in all the documentation I had read through all the training videos, etc not once did I see how to update the settings for the LCM AFTER a client is pulling information from a pull server.

    I'm not just talking a manual change that I can do no problem I'm talking about things like deciding to change the RefreshFrequencyMins for ALL the connected clients. Or maybe splitting the Pull and Reporting Web Services between two servers.

    Is It possible? Can you effectively update the settings of the LCM on a client that is already tied to a pull server?

    I tried what I thought would work from naming the meta.mof files after the named configuration of my actual test configuration, and by the name of the clients in questions but nothing seemed to work.

  • #71285

    Mark Gray (MSFT)
    Participant

    Ryan,

    You can push a new meta-configuration to the target nodes. This will overwrite the meta-configuration that is on the node. You cannot update individual settings of the meta-config and leave all of the other settings, however. To overwrite the meta-config, just compile your new meta-config and run Set-DscLocalConfigurationManager against the target nodes again.

    MarkG

  • #71287

    Ryan Strope
    Participant
    You can push a new meta-configuration to the target nodes. This will overwrite the meta-configuration that is on the node. You cannot update individual settings of the meta-config and leave all of the other settings, however. To overwrite the meta-config, just compile your new meta-config and run Set-DscLocalConfigurationManager against the target nodes again.
    
    MarkG

    Yeah I already know I can PUSH a new meta-configuration I want the clients to PULL a new meta-configuration.

    It really baffles me that this is not something DSC can do.

    Even if I wrote a script to loop through AD and run Set-DSCLocalConfigurationManager there's no way to be sure they would all be on, and available to get the new meta-configuration

    I would THINK that DSC in a pull scenario would want the ability to send a new meta-configuration so clients would grab it whenever they did their next check-in.

    Image for instance an organization that started out with an HTTP Pull Web Service with 10,000+ clients and they decide to change to an HTTPS Pull Web Service.

    It would seem that once you have a client configured to PULL its configurations you would want it to have the ability to pull ALL its configurations even a new meta-configuration.

    Or is it just me?

You must be logged in to reply to this topic.