This topic contains 3 replies, has 3 voices, and was last updated by
November 6, 2017 at 9:41 pm #83705ParticipantPoints: 0Rank: Member
I was toying with the idea of building a DSC configuration library (similar to the Powershell Gallery) as i have already built a DSC Script/MOF generator to manage my scripts and Nodes (first iteration and a work in progress).
The new web site would allow anyone to login and create DSC Configurations using any modules from the Powershell Gallery and letting them flag it as for public use, my idea is to only store agnostic information (no node names or service account info of course) and to generate as required.
If it is a public use configuration that required node name etc then the person downloading it would enter that info in at download time and the new DSC script or MOF would be generated with their specific info.
Does anyone think it would be useful as a public domain.
Or any suggestions would be greatly appreciated or if anyone would like to contribute.
November 7, 2017 at 3:07 pm #83737ParticipantPoints: 0Rank: Member
I think it could be useful, like a basic configuration library (here's a best practice setup for Web Servers, Exchange Servers, etc...). Just make sure that the files are machine name agnostic so all that would be necessary is pointing the configuration at a psd1 file and BAM you get your mof.
Not sure how this can be differentiated from really strong documentation though. Just my 2 cents.
November 8, 2017 at 5:39 pm #83807ParticipantPoints: 0Rank: Member
That is the goal of this effort. Feedback welcome.
November 8, 2017 at 9:27 pm #83842ParticipantPoints: 0Rank: Member
An interesting effort, i look forward to seeing more.
I started with the idea of building a DSC Generator and possibly commercializing it (lots of work 🙂 ) but i am thinking of making it a free download and also using it as the base to create the DSC Library site i mentioned.
There are a few videos of use cases :
The topic ‘DSC Config Library’ is closed to new replies.