<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Waas - Tag - byteben</title><link>https://byteben.com/tags/waas/</link><description>Waas - Tag - byteben</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>ben@byteben.com (Ben Whitmore)</managingEditor><webMaster>ben@byteben.com (Ben Whitmore)</webMaster><lastBuildDate>Mon, 12 Apr 2021 00:00:00 +0000</lastBuildDate><atom:link href="https://byteben.com/tags/waas/" rel="self" type="application/rss+xml"/><item><title>Running custom actions during a Windows 10 Feature Update with Configuration Manager</title><link>https://byteben.com/bb/running-custom-actions-during-a-windows-10-feature-update-with-configuration-manager/</link><pubDate>Mon, 12 Apr 2021 00:00:00 +0000</pubDate><author>ben@byteben.com (Ben Whitmore)</author><guid>https://byteben.com/bb/running-custom-actions-during-a-windows-10-feature-update-with-configuration-manager/</guid><description><![CDATA[<p>Deploying Windows 10 Feature Updates in your organisation can be approached in multiple ways. As we merge the perimeter with the Cloud some of us are trying to understand the best way to deliver Feature Updates to our devices. Should we deploy an in-place upgrade using a ConfigMgr task sequence? Perhaps we should push the Feature Update directly from ConfigMgr to our devices. Have we considered leveraging our CMG and using Microsoft as a source for the update binaries to save our VPNs? Maybe some of us are on a co-management journey and are looking at using WUfB. Which ever technology we are leveraging one of the questions that normally gets asked is &ldquo;Can we control the update process in a way that lets us &lsquo;Run Stuff&rsquo; after the Feature Update has completed&rdquo;.</p>]]></description></item></channel></rss>