You are correct that currently a lot of those defaults would be flipped back on. At this point the general recommendation is to not use the Servicing Model but instead to create your own Task Sequence with your customizations.
That being said, I envision a future version of Windows 10 (Redstone 2?) that would preserve these settings but we have to wait and see. MSFT is pushing the Servicing Model hard so I would image they are working on a way to preserve these settings. Other than that, some new Group Policy Settings have come out that enable you to disable the Customer Experience side of things. These would be preserve much of the settings that users want disabled in a Managed Environment. You need the update Admin Templates for this and Enterprise/Education on the client, though. On Sat, Oct 1, 2016 at 9:48 PM, Miller, Todd <[email protected]> wrote: > I was watching the What's new in OSD from Ignite on demand. > > So it seems like a lot of work at MS has focused on the servicing plan > idea with the deployment rings and the talk about the ease of which windows > 10 can be kept current. In order to use a servicing plan, don't I have to > just take all the defaults that come when a client applies a feature > update? To use the deployment rings and servicing model, don't we as IT > pros need to give nearly all control over OS customization and control over > what features get installed? > > Is there any way to take advantage of the deployment rings and scheduling > and reporting and all that while still using task sequences to run through > the servicing upgrades? If past experience predicts the future, every one > of these Windows 10 feature updates is going to take some degree of > post-configuration... and that is only possible via task sequence > delivered feature updates right? > > Maybe it is only possible to deploy customized windows feature updates via > true imaging- but then that means doing wipe and load installs on every > machine every 8-16 months? > > So let's take the 1511 deployment. Let's say I had 1507 installed and I > want to update computers to 1511. Let's say that I would be fired if those > computers got the 1511 feature update, rebooted and every machine now had > Twitter installed and every user started receiving advertisements for > office 365 every day. What update methods are available to me among > imaging, servicing (via task sequence?), and WaaS via WSUS/SUP that would > allow me to deploy the feature update and remove components of that update > that were deemed inappropriate in our environment? > > > ________________________________ > Notice: This UI Health Care e-mail (including attachments) is covered by > the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521 and is > intended only for the use of the individual or entity to which it is > addressed, and may contain information that is privileged, confidential, > and exempt from disclosure under applicable law. If you are not the > intended recipient, any dissemination, distribution or copying of this > communication is strictly prohibited. If you have received this > communication in error, please notify the sender immediately and delete or > destroy all copies of the original message and attachments thereto. Email > sent to or from UI Health Care may be retained as required by law or > regulation. Thank you. > ________________________________ > > > > >
