Forum Discussion
1803 (Targeted)?
Microsoft updated the docs to make it clear, that when Telemetry is set to Zero, the deferral policies do not take affect and you make get the feature updates.
Here are the links to the updated Docs
https://docs.microsoft.com/en-us/windows/deployment/update/waas-overview
Important Devices on the Semi-Annual Channel (formerly called Current Branch for Business) must have their diagnostic data set to 1 (Basic) or higher, in order to ensure that the service is performing at the expected quality. If diagnostic data is set to 0, the device will be treated as if it were in the Semi-Annual Channel (Targeted)(formerly called Current Branch or CB) branch. For instructions to set the diagnostic data level, see Configure the operating system diagnostic data level.
https://docs.microsoft.com/en-us/windows/deployment/update/waas-configure-wufb
Note Users will not be able to change this setting if it was configured by policy. Important Devices on the Semi-Annual Channel (formerly called Current Branch for Business) must have their diagnostic data set to 1 (Basic) or higher, in order to ensure that the service is performing at the expected quality. If diagnostic data is set to 0, the device will be treated as if it were in the Semi-Annual Channel (Targeted)(formerly called Current Branch or CB) branch. For instructions to set the diagnostic data level, see Configure the operating system diagnostic data level.
Thanks
Darrell Gorter
"The documentation is incorrect."
that's cant be, Its Microsoft! they wouldn't release a feature update to 10 million devices and mess up the release communication (LOL)
I need MS to either fix their documentation or standby the release
Take a look at this. Why is 1803 installed on a client with Semi-Annual Channel?
You aren't alone. I'm getting reports that 1803 is getting on machines that have semi-annual selected. It shouldn't even be near that machine.
Use that to block it. (and come on Microsoft , I've lost count how many times deferrals haven't worked)
Hello,
The machines should not have been upgraded with that policy set, with a couple of exceptions
There are two ways this can happen.
- The dual scan scenario where the polices settings configuration is not set properly, we took changes to address this last summer, by adding a new policy but it’s possible that people have not figured it properly. The fix was to offer a new option but it’s possible that policy is not set.
- https://blogs.technet.microsoft.com/wsus/2017/05/05/demystifying-dual-scan
- GP that sets Telemetry to Zero Exhaust
Is there a support case where machines were upgraded with that policy set?
Darrell Gorter [MSFT]
- The dual scan scenario where the polices settings configuration is not set properly, we took changes to address this last summer, by adding a new policy but it’s possible that people have not figured it properly. The fix was to offer a new option but it’s possible that policy is not set.
Great and now? Microsoft please tell us a solution to stop this.... Thanks.
