![]() ![]() While the various days for deadlines can be subjective to your organization’s requirements, setting Auto reboot before deadline to No is really the key for getting a good experience for end users. For our general group I will leave Enable pre-release builds to Not Configured and Update Windows 10 devices to Latest Windows 11 release to No. Previously the first option was to configure a channel, but now we have the Enable pre-release builds option instead, which makes more sense. For this policy, I will leave Quality and Feature update deferrals to a 0 day delay (if I had a second group, for feature updates I’d set it as 30, and then the next group as 60, etc.). We will leave Microsoft product updates and Windows drivers to Allow. The first group of settings, Update settings, are mostly unchanged. ![]() Provide a name for the new update ring profile: NameĪnd then we can start configuring the settings. Go to > Devices > Update rings for Windows 10 and later > + Create profile Update rings Fundamentally I still believe in this experience – but now there are newer policies and settings we should be using! I’m basing this updated experience on a fantastic TechCommunity article: Why you shouldn’t set these 25 Windows policies – Windows IT Pro Blog (). In that article, which continues to be one of the most popular ones on this blog, I talked about how users want to be informed and in control of when to update and how you can provide lots of notifications before an update is forced. Over two years ago, I wrote an article describing how to configure Windows 10 update rings for the best user experience.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |