Feb 06 2022 07:35 PM - edited Feb 07 2022 12:05 AM
[Edited]
Hello everyone,
hoping you all are having a good day.
I need some inputs on my current Windows 10 update rings policy.
I set the deadline settings as shown below to multiple pilot devices. These devices are identical in all hardware but has different windows 10 builds (1909, 1709, 1903, 20H1, 21H2).
Devices with Windows 10 1709 builds has been successful but I got this error "-2016281111 (Not applicable for this device)" on other versions.
Policy Applied : User group
User License : M365 Business premium and Windows 10 Enterprise E3
Feb 06 2022 10:57 PM
Feb 06 2022 11:15 PM
Feb 06 2022 11:47 PM
Feb 07 2022 12:09 AM
Feb 07 2022 12:12 AM - edited Feb 07 2022 12:13 AM
These devices are using SCCM before we hybrid-joined them to AD. And yes, they have very old versions of Windows 10 when we came in to the picture to manage their devices. No idea why the previous MSP did that to these devices but as of this writing, we already decommissioned the SCCM server and unenrolled these devices from SCCM. I also removed any group policies that was set before to block the Windows updates. However, the Not applicable error I am getting is only showing from devices with 1903 and above version.
Feb 07 2022 12:18 AM - edited Feb 07 2022 12:22 AM
Hi,
Ahh good to know some "backstory" about the issue. Just wondering but what happens when you install a totally new device with 1903? Normally the not applicable just means you have some licensing issues...
What is the latest update those 1903 devices got?
ANd what happens when you manually create a custom csp to define 1 of those settings and target a test device with it?
Feb 07 2022 12:25 AM