Windows as a Service

UUP is (still) coming soon, and dynamic update is (still) important

How many of you remember the Unified Update Platform, a.k.a. UUP, being announced in 2016?  Let me remind you:

And there was another update in 2017:

There was some documentation published in 2018:

And another blog in 2018:

And it was talked about at Ignite 2018:

There’s a slide in that video that explains why you care:


But notice the right-hand side:  This works great if you’re getting feature updates from the internet (Windows Update or Windows Update for Business), but you’re out of luck if you are using WSUS or ConfigMgr – you still get the older behavior with those (even when using servicing).  The mentioned public preview didn’t happen though, as some additional “kinks” needed to be worked out.  A new public preview will be available in the future, as mentioned in this recent blog:

Note: UUP for on-premises management solutions is not yet available. We will have future news regarding UUP, including a public preview, at a later date.

Let’s break down the points in the first column a little more:

  • Get Current and Secure in one step.  This means that as part of the feature update installation, the latest cumulative update will automatically be installed.  You’ll also get the latest compatibility information (as driver and app checks/blocks routinely change).
  • Preserve FoDs and LPs.  To translate, FoD stands for “features on demand” and LPs is short for language packs.  So, as part of the feature update process, these will automatically be reinstalled so you don’t have to worry about doing that.
  • Lower network traffic to PCs.  There are files (binaries, images, fonts, etc.) that don’t change from one Windows 10 release to the next.  UUP is smart enough to do a delta download, only downloading the pieces that have changed.
  • Better user experience.  When using a servicing-based approach for installing feature updates, installations happen after hours, users can control deferrals or choose to install now – simple capabilities to reduce the impact on the end user.

Great stuff, but if you’re using WSUS or ConfigMgr, you’re (mostly) missing out, waiting for that “later date.”

But you can do something in the short term to at least cover the first bullet point:  Get Current and Secure in one step.  Through dynamic update, it is possible to automatically install the latest cumulative update during the feature update process.  You really want to do this.  But the process for doing it varies, as described in another recent blog that is definitely worth reading:

  • When using ConfigMgr task sequences to install feature updates, check the box in the “Upgrade Operating System” step to “Dynamically update Windows Setup with Windows Update.”  This tells ConfigMgr to temporarily point the machine to Windows Update (instead of WSUS) and to include the “/DynamicUpdate enable” command line switch.
  • If using WSUS with Windows 10 1803 and earlier, you can manually approve the dynamic update content in WSUS.  I blogged about that back in 2017.
  • With Windows 10 1809 and later, SETUP will automatically talk to Windows Update for dynamic update content (unless you explicitly disable dynamic update via the command line or setupconfig.ini), even if the device is configured to talk to WSUS. 

Note that the dynamic update downloads will be hundreds of megabytes.

You can find a good summary of this (and more) in another recent blog from the language pack team

Categories: Windows as a Service

1 reply »