Geoff Posted February 4, 2016 Posted February 4, 2016 This has just appeared in our WSUS so we've blocked it from being pushed to our client pc's. The update (KB3123862) appears to be another, more aggressive push by Microsoft to get more people onto Windows 10. https://support.microsoft.com/en-us/kb/3123862
Arthur Posted February 4, 2016 Posted February 4, 2016 Probably a good idea to do this too... https://support.microsoft.com/en-us/kb/3080351 Computer Configuration / Administrative Templates / Windows Components / Windows Update [b]Setting[/b]: Turn off the upgrade to the latest version of Windows through Windows Update or Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate] "DisableOSUpgrade"=dword:00000001 Then you won't have to worry about blocking updates through WSUS. 1
DrCheese Posted February 4, 2016 Posted February 4, 2016 Well this is just asshatery now - We've blocked the "Upgrades" catagory & thought that would be the last of it. We generally approve "optional" updates as a matter of course & this would have slipped through the net. Sigh, I'll add the GPO entries in This is going to backfire on MS massively if they keep trying to force corps to upgrade
3s-gtech Posted February 4, 2016 Posted February 4, 2016 I have that update installed and have the very latest WindowsUpdate.admx but that policy setting doesn't show. Annoying.
Michael Posted February 4, 2016 Posted February 4, 2016 Probably a good idea to do this too... https://support.microsoft.com/en-us/kb/3080351 Computer Configuration / Administrative Templates / Windows Components / Windows Update [b]Setting[/b]: Turn off the upgrade to the latest version of Windows through Windows Update or Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate] "DisableOSUpgrade"=dword:00000001 Then you won't have to worry about blocking updates through WSUS. It's generally good practice to block updates by default however, giving you full control what's deployed with no nasty surprises.
Arthur Posted February 4, 2016 Posted February 4, 2016 I have that update installed and have the very latest WindowsUpdate.admx but that policy setting doesn't show. Annoying. The GPO setting is in the local group policy editor so for domain PCs you would need to use the registry value instead and deploy it via GPP. 2
3s-gtech Posted February 4, 2016 Posted February 4, 2016 Cheers, I have duly done so. My Windows 10 testing is going okay-ish, but I have no plans to deploy it site wide until Summer 2017 so I don't want any nag boxes!
kennysarmy Posted February 4, 2016 Posted February 4, 2016 The GPO setting is in the local group policy editor so for domain PCs you would need to use the registry value instead and deploy it via GPP. and with that registry string set the clients won't show or display anything at all that inquisitive mice could click ? Cheers
Arthur Posted February 4, 2016 Posted February 4, 2016 and with that registry string set the clients won't show or display anything at all that inquisitive mice could click? I would also add the following one just in case. It will hide the "Get Windows 10" icon in the notification area. Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Gwx] "DisableGwx"=dword:00000001 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now