Windows as a Service

Windows as a Service cheat sheet

By on • ( 8 Comments )

It’s been three years since I worked in Windows marketing talking about Windows as a Service. At the time, I was quite happy to say that I would never have to talk about WaaS again. Well, you can never really escape that conversation, you can just do your best to avoid it. Now, I don’t even mind…

I’ve seen some questions recently about how the latest announcements about the 21H1 release of Windows should be considered. But really you should be looking more broadly, depending on what release you are currently running and how much time is left on that release. The Windows 10 release information page remains the authoritative source that everyone should be following, but here’s a quick take projecting that forward with (a) the new 21H1 release details, and (b) the expected 21H2 full release:

If you are running an Enterprise SKU of…You should …
Something earlier than Windows 10 1803Seek help. You’re already unsupported.
Windows 10 1803 or 1809Hurry up and deploy at least Windows 10 2004. You only have until May 11, 2021.
Windows 10 1903This is already unsupported. Install the Windows 10 1909 enablement package right now, so that you are again supported.
Windows 10 1909This is supported until May 10, 2022. You should deploy Windows 10 2004, 20H2, or 21H1 as a full feature update (my vote would be for 20H2 because you’ll be scared of 21H1 being “too new”), starting somewhere around or before May 2021 to give yourself at least a year to complete the process. Don’t wait for 21H2 as that won’t leave you enough time to safely upgrade.
Windows 10 2004This is supported until December 14, 2021. Install the Windows 10 20H2 enablement package by then.
Windows 10 20H2This is supported until May 9th, 2023. You’ve got plenty of time. Installing the Windows 10 21H1 enablement package won’t change that date any (if we assume a release of April 13, 2021 + 18 months, that’s still before May 9th 2023). Look to deploy 21H2 or 22H1 (probably 21H2) by May 2022.
Any LTSC/LTSB releaseYou didn’t listen to me before, so I don’t expect you to start now. You’re on your own. Remember you can upgrade from LTSC to a semi-annual channel release at any time, just needs to be a newer build number.

A few general comments:

  • Enablement packages should be fairly safe to deploy (following a controlled rollout process), since they just turn on features that were otherwise hidden when you installed previous cumulative updates. The real risk is with those cumulative updates…
  • Tanium fully supports deploying feature updates and enablement packages using the Deploy and Patch solutions. For feature updates, you can deploy an initial compatibility scan to detect issues, then use the results of that detection for targeting later. See here for more process details.

Categories: Windows as a Service

8 replies »

  2. Bookmarking this for the next time I have to explain why it’s not a good idea to use LTSC for the general population.

    Like

    • For just you or for your company? For you, install the feature update from Windows Update. For your company, it depends on what management tool you have in place and if you are running an LTSC release.

      Like

  4. Michael, thanks for your assistance re my Windows 1809.
    However when I checked my “View Update History” I found “Feature update to Windows 10 version 20H2” already installed on 3/14/2021, plus three “2021-01 Updates for Windows 10 Version 20H2” installed 3/17/2021.
    It looks like this was the “Forced Upgrade” described in this website https://borncity.com/win/2020/06/18/windows-10-v1809-auto-update-to-version-2004-has-begun/
    I have mixed feelings about it: glad that I have been relieved of having to go through the arduous process of installing it manually and yet I’m mildly apprehensive given the problems with the 20H2 mentioned in the above website.
    Cheers,
    Al Louis

    Like