Forum Discussion
HenrikInAB
Jun 08, 2021Copper Contributor
Intune Windows Update/Feature Update Ring applied but clients not updating
We recently moved some of our co-managed workloads from SCCM to Intune, not pilot, and for the most part our devices are happy with our Intune Windows 10 Update Ring settings. We have a profile crea...
Oct 11, 2021
Hi,
isnt that because the SCCM client is still installed on the devices and a configured windows update group/point?
isnt that because the SCCM client is still installed on the devices and a configured windows update group/point?
MSIreport
Oct 11, 2021Copper Contributor
Hi Rudy,
We do have SCCM client and Software Update client policy disabled for all our Windows update workload computers.
We still see the WUServer in our registry path and i do not know why.
We do have SCCM client and Software Update client policy disabled for all our Windows update workload computers.
We still see the WUServer in our registry path and i do not know why.
- NicklasAhlbergOct 11, 2021Brass ContributorIs the workload set to Intune or Intune pilot? If it is set to "intune pilot" any device(s) not part of the selected collection will not have the workload changed.
The SCCM client policy is supposed to change the regvalues as soon as the SCCM client policy has been set to not use SCCM as SUP. - Oct 11, 2021Just wondering, but what happens when removign the sccm client.. is the wuserver key also removed or?
- MSIreportOct 11, 2021Copper ContributorYes, i removed my SCCM client completely and rebooted the device.
Still i could not see anything under "Policies set on your device" 😞
Thanks...- NicklasAhlbergOct 12, 2021Brass ContributorI do not think that uninstalling the SCCM client will actually solve this as this issue should not be related to the client itself.
1. SCCM Client Policy is correctly configured (make sure you do not have any overlapping policies)
2. Co-Management SU workload is set to Intune or Intune pilot
2.1 If Intune pilot is being used, make sure that your devices are members of the pilot collection
3. Windows Update for Business policies are successfully assigned and applied
4. Check CoManagementHandler.log - make sure the merged capabilities are successfully applied to the device. %WinDir%\CCM\logs\CoManagementHandler.log
After step 1-4, check this registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU
If possible share a print screen (blur any sensitive info)
//Nicklas