I’m an active CBT nuggets subscriber and I just watched Don Jones’s series there on DSC, awesome stuff. And I’m getting a better grasp of what it can and can’t do. I’ve followed the guides on the net out there on setting up a pull server, so I have that. I have not yet pushed/pulled a config to/from a target/slave server “node”. I’m just at more of a brainbuster / trying to wrap my head around something issue than a technical one and hoping someone can shed some light:
Goal: I have a 2012 R2 template that has the latest DSC module and I redeploy this template using a vmware customization script that applies an IP address, changes the computername, and joins the domain. I want to setup such a template computer to automagically configure itself based on its AD-OU or AD computer group using DSC.
Problem: I’m at the point where I want to SetPullConfig on the target nodes to become slaves to my pull server. In all these guides I’m reading they’re talking about GUIDs vs hostnames, GUIDs required for pull while hostnames are good for push. It gets a little confusing, do I use a CSV file or a sql DB, or the brilliant idea I saw about AD guid? Is there a more comprehensive guide for the newbie about the AD guid way?
Topping it off, most guides seem to suggest you ‘should’ do things in this order:
- Create a MOF with a config for a target node (like install IIS on that server)
- Generate guid for node
- rename mof file
- apply to pull server
When my goal is more like:
- I don’t have a config for you yet.
- AD guid is fine, but if I have to generate one myself err what’s best practice?
- would I even have a mof file at this point - I don’t have any config for you!
- Ask me for your config and you shall receive!
I like the idea of being able to bring up a new server from template and it join itself to a particular server config group based on what location/group I add it to in AD. It’s not very clear to me how to go about getting there, any help would be appreciated!