Almost 6 years ago, I wrote some PowerShell scripts in a multi-part series explaining WMI namespace security and also how to manage them using PowerShell. If you’re not familiar with WMI namespace security, I recommend reading the blog posts above or even as a refresher.
We are excited to announce the recent updates which were made to DSC Resource Kit since open sourcing it on GitHub! We were working hard on improving coverage and robustness of DSC as well as saw incredible engagement from the community in the recent months.
I’ve heard from a few DSC resource authors that they need a method to implement a resource that has a single instance; a singleton. The problem they encountered is a DSC resource must define a Key property but singleton resources generally should not have a key because there is only one instance that can be updated.
NOTE: For information on OS support, and other features, please refer to our release history.
Today we are releasing version 2.0 of the Azure DSC Extension, with improvements for DSC configurations that reboot the VM, and fixes for ARM deployments.
We are releasing this version as a major version change,
(Warning: Long blog post ahead! If you’d like to read (or share) this as a whitepaper, you can download it here: “Scripting Security and Protection Advances in Windows 10”).
At Microsoft, we invest an enormous amount of time and energy managing world-class cloud services and incredibly large enterprise networks.
[UPDATE]: Read more about our detailed plans, roadmap, and where you can play with the in-progress code here.
As Microsoft has shifted towards a more customer-oriented culture, Microsoft engineers are using social networks, tech communities and direct customer feedback as an integral part on how we make decisions about future investments.