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
We run the Enterprise Version. Comparing with the explanations above we have telemetry 0 which is the same as 1 in the Enterprise Environment (so i have Unterstand it.)
At the moment i habe stopped all Scans against the MS Update in the Internet. This stopped the search for all Updates. Bit the Problem is that i dont want stop this Kind of Setup. We dont WSUS for deploy Win 10 Updates because the most of our staff works outside of our company. We have make the decission that the Dual scan fits Perfect to us. Bit now it looks for me that Microsoft has overwritten the behavior which Microsoft has offered with the GPO Settings. My question is is this a bug which they will solve or not. And in which timeframe they will help there customers which pay several 100.000 Euros for the company Contest. I have already openend a Ticket See above in the Discussion. But the answer was Not what i have expected. Yes this is May a bug - i dont know what Happens we try to Contact a tier 2 Support. That was the last Reply since last friday. A i fortget the close Incident Message. Its now on hold.
So i Hope the Issue will be solved and i can go back and Scan Updates against Microsoft without installing 1803. the actual State Stopps my daily work.
Thanks for your help and support
Thomas
Thomas Czekalla wrote:
hi Susan,
We run the Enterprise Version. Comparing with the explanations above we have telemetry 0 which is the same as 1 in the Enterprise Environment (so i have Unterstand it.)
I don't have Enterprise so I'm not speaking from experience, but I understand that differently. The way I read it, it is only possible to set a value of 0 if you DO have Enterprise; in that case, it is NOT treated as a 1. Then, under "Select when Preview Builds and Feature Updates are received," it says, "To configure Feature Updates, you must have a telemetry level setting of 1 or higher." Does deferral work as expected on your Enterprise machines if you set AllowTelemetry to 1?
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
Hi Mark,
I have now set the Telemetry from 0 to 1.
After this my policies worked like expected.
Still strange why i worked with 0 for at least one year and all was also fine.
Thanks to all for support and help