Windows Servicing

On Twitter I asked the following to David James (Director of Engineering, ConfigMgr, Microsoft) and Johan Arwidmark (CTO @ TrueSec): https://twitter.com/DevSecNinja/status/1024927840138145793 For example, I have 3 device collections in SCCM that I call: “Windows 10 Feature Updates - Test” “Windows 10 Feature Updates - Pre-Production” “Windows 10 Feature Updates - Production” With ADRs, that’s quite simple. Just add the deployment to the Software Update Group in SCCM and you’re done. But I was wondering if that is supported in the Servicing Plan scenario too, as with a Servicing Plan you define the amount of days it will take after a build release, before SCCM will deploy the feature update to the collection. ...

With Windows Servicing, Microsoft is forcing consumers and businesses to upgrade to a Windows 10 Build twice a year. Theoretically you could go for one build per year, but that forces you to upgrade to a new build within 6 months. Otherwise you will end up without support for the old build. This introduces quite some issues within both SMBs and large organizations. Recently a friend asked me about a recent printer that stopped working. ...

Lost track of the service channel naming of Windows and Office Servicing? Is it “Current Branch” or “Semi-Annual Channel” now?! Or Standard Release?! Windows 10: Ready: Semi-Annual Channel (Targeted) Ready for Business: Semi-Annual Channel Office 365: Ready: Semi-Annual Channel (Targeted) (Or [Targeted Release](http://Ready: Semi-Annual Channel (Targeted) Ready for Business: Semi-Annual Channel)) Ready for Business: Semi-Annual Channel (Or [Standard Release](http://Ready: Semi-Annual Channel (Targeted) Ready for Business: Semi-Annual Channel)) Last update: recently… :) Every day is a new day to change these again, so stay tuned!