![]() NoAutoUpdateĭisableDualScan is another policy setting that can adversely affect the delivery of Windows Updates when you move workloads to Intune in a Co-management scenario. Largely, it is not used today but I still find this registry key tattooed on some of my customers devices. It was a way that some used to control duplicate Windows Update balloon notifications from appearing on Windows 7 devices. NoAutoUpdate was a policy some ConfigMgr admins used to set back in the day. What are these bad settings you speak of? ![]() Previous experience taught me that there are also some legacy settings that will “absolutely break” the Windows Update experience for users – especially when the Windows Update workload is moved from ConfigMgr to Intune. In the post Aria explains which settings will give your users a “sub optimal” experience with Windows Updates and which settings have absolutely no effect. It had occurred to me to mention that I had previously seen environments where legacy policy was either “breaking” updates completely or adversely affecting the update experience for the end users.Īt around the same time, Aria had published a fantastic article on the Microsoft Tech community blog Why you shouldn’t set these 25 Windows policies I was working with a customer recently and we were having a conversation around the optimal settings to ensure a great experience when delivering Windows Update policy using Intune. Script Option 2 (Function App URL Embedded in Script).Script Option 1 (Shared Key Embedded in Script). ![]() ![]() What Intune Reports show me if I have these bad settings in my environment?.What are these bad settings you speak of?. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |