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
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.
- GP that sets Telemetry to Zero Exhaust
Is there a support case where machines were upgraded with that policy set?
Darrell Gorter [MSFT]
Hello,
the Case No. is
- Service Request #: 118052418249642
- Service Request Title: Unwanted Installation of Windows 1803 - GPO with 365 Day delay is setup
Fellow MVP, not behind a domain, therefore no WSUS/dual scan, telemetry on.
This is not the first time that feature releases have come down when they clearly should have respected the block.
Is there any News available.
I have set a Policy to my Clients that they dont check the MS Update Websites in order to stop the deployment. But this will lead to a lack of security. I want to use the normal semi annual channel with the acutal Build (1709 and not 1803) and defer the Installation like offered in the Policy. I have also set the telemetry to value 0 which is the same like 1 for Enterprise users.
Many thanks for any Feedback.
Thomas
Even with the dual scan issue these machines are set for "semi-annual". We are still at semi-annual targeted. There is no reason these machines should be getting 1803.
I have two other MVPs on a private list who are behind Windows update who got 1803 and they had semi-annual chosen as well.
