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
SusanBradleyGeek wrote:
If you don't use WSUS, if you are choosing "semi annual channel" what number of days did you select for deferral? As I recall even if you set the deferral for X number of days, if you click on "check for updates" this will trigger the install of 1803. Check for updates isn't like the old Windows 7 scan where you would see what would be offered, check for updates actually triggers detection and install.
Not for me. No WSUS, Win10 Pro 1709, deferral set to 180 days. On most machines, I can Check for updates all day long and not get offered 1803.
Once it IS offered, you're right, it won't ask if it's okay to install it.
I've now confirmed that my machine did NOT have the deferral group policy applied before 1803 was released. Although the machine is domain-joined, group policy updates started failing after the machine's NIC lost its Domain profile on February 14. It's unclear if this was due to a Windows update or due to a general failure of Network Location Awareness.
Details: https://www.mcbsys.com/blog/2018/06/windows-10-unexpectedly-updated-to-1803/
Thanks to the MS team for reviewing the logs, which led me to restore a pre-update image.
I tend not to "check for updates" unless I'm positive I want the thing that might be up there.
BTW I pointed another Consultant who had a client who got 1803 with deferrals in place to this thread. Is there anyway to have a checking tool to check if what you think will be deferred is going to be deferred? The state of affairs right now is you never know if
a. you've set something wrong
or
b. it's a detection bug. And given that we have had them in the past we are constantly in a state of questioning.