1. One MOF to rule them all, and in the Azure bind them
One MOF – in Azure – can be leveraged to rapidly deploy and/or ensure ongoing compliance for all of your devices, both on-prem, and in the cloud.

2. DSC General Workflow Authoring Staging Execution LCM MOF Pending.mof
Current.mof

3. DSC – Node Specific PUSH PULL Author MOFs for every device to push out
Author MOFs for every device and place on pull server

4. Breaking out of a many MOF world
Single MOF for all devices
Benefits:
Single MOF to manage
Issues:
Limited to generic configurations
Too inflexible
Smart MOF
Benefits:
One MOF to manage all devices
Intelligent & Dynamic
Highly flexible
MOF
MOF
MOF
MOF
MOF
MOF
MOF
MOF
MOF
MOF
MOF
MOF
MOF
MOF
MOF
MOF
MOF
MOF
MOF
MOF
MOF
MOF
MOF
MOF
MOF
MOF
MOF

5. One MOF to rule them all – how can it be achieved?
Custom DSC
Resources
Locally sourced
configuration data

6. One intelligent MOF - sourced from Azure Automation DSC - interacts with all devices

8. One intelligent MOF – dynamic enough to know what floor it’s on?!

9. Closing Thoughts

10. Name: Jacob Morrison
Blog:
Git:
Get all of the code, files, and slides from today’s presentation:
URL:
Shortlink: