The complete idiots guide to Windows as a Service

By Johan Arwidmark / May 6, 2017

For what feels like the tenth time, Microsoft is changing their terminology/strategy around Windows 10 updates. Below is a recent thread covering the topic (thanks to Ami Arwidmark (@AArwidmark) and SystemCenterDudes (@scdudes) for making me aware of the changes):

Confused about Semi-Annual Channel (Pilot) and Semi-Annual Channel (Broad) Timing
http://techcommunity.microsoft.com/t5/Windows-as-a-service-AMA/Confused-about-Semi-Annual-Channel-Pilot-and-Semi-Annual-Channel/m-p/67179#M59

It's called work for a reason (yes, this is the guide)

Instead of trying to explain how the latest reincarnation of Windows as a service works, below you find some real world guidance you can follow. These steps does involve some work from you part, but that's typically why you got hired in the first place. So don't argue, just get on with it 🙂

Stay away from LTSB versions of Windows 10.
Stay away from OEM versions of Windows 10.
Deploy Windows 10 Enterprise or Windows 10 Education editions only.
When a new Windows 10 version is released, find a few victims in your organization (including you), and then upgrade these machines to the new version using a task sequence.
Start testing the new Windows 10 version as soon as possible on these machines, and make sure to complete it within 4 – 5 months. That includes report any bugs found to Microsoft etc.. Then, after tests are completed, but not sooner than four months after initial release, upgrade the remaining machines in your environment.
Watch TV-series for a month, I can recommend Vikings, Sense8, Game of Thrones, House of Cards, or Sons of Anarchy to name a few.

Update: Ami Arwidmark (@AArwidmark) says The Mindy Project should be added to the list of TV series, and Zeng Yinghua (Sandy) (@sandy_tsang) recommends Prison Break and Shield. All very valid comments 🙂
Repeat the preceding steps for the rest of your IT career.

Note: If you are using ConfigMgr to manage Windows 10, then upgrade to the latest version every time there is a new version available.

Written by Johan Arwidmark