Forum Discussion
1607 and 1703 autoupdating, and bypassing sccm updates
I found our mistake.
During our image creation we had selected "current branch for business" as a branch readiness level. I couldn't see this in rsop, or in any of our group policies.
Turns out the registry entry that caused us this grief was the following.
hklm\software\microsoft\windowsupdate\ux\settings "branchreadinesslevel" . It was set to 32, and after chaning it to 0 our comptuers look only to sccm/wsus.
We are seeing the same thing. Tough to say when it started, though...it killed our internet connection yesterday.
We don't use SCCM, only WSUS.
Interested in what others are seeing, I am going to go search for te setting you spoke of, as we don't make use of the windows store.
Thanks
Steve
I found an amazing article
https://social.technet.microsoft.com/Forums/en-US/88771e56-8be0-4bc9-b674-648619eab2ac/windows-10-pro-1703-and-windows-update-with-wsus?forum=winserverwsus
I am in the process of testing this to see if it solves my issue or not...
I found our mistake.
During our image creation we had selected "current branch for business" as a branch readiness level. I couldn't see this in rsop, or in any of our group policies.
Turns out the registry entry that caused us this grief was the following.
hklm\software\microsoft\windowsupdate\ux\settings "branchreadinesslevel" . It was set to 32, and after chaning it to 0 our comptuers look only to sccm/wsus.
Excellent.
I am hoping we tracked down our issue as well. We recently enabled the GPO setting - "Do not include drivers with Windows Updates" -- that is mentioned in one of the technet links above as something that would cause this scenario.Hoping to get a definitive answer on that change tomorrow.
Thanks for the update
Steve