Forum Discussion

HenrikInAB's avatar
HenrikInAB
Copper Contributor
Jun 08, 2021

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...
Intune
mobile device management (mdm)
NicklasAhlberg's avatar
NicklasAhlberg
Brass Contributor
Jun 08, 2021

Hello HenrikInAB!

 

I am sure we can solve this together, I have some questions to get us going 🙂

 

  • From the printscreen it seems the faulty device does not have a Primary User, is this the case for the working devices as well?
  • Are the MDM-policies deployed to User och Device objects?
  • Are you able to find any differences in the MECM client policy deployed to working/faulty devices?
  • Please see this article. We want to make sure that we do not have a WUserver value pointing towards a WSUS-server. https://docs.microsoft.com/de-de/security-updates/windowsupdateservices/21669493
  • Please see this article describing feature update(s) policy and Co-Management. https://docs.microsoft.com/en-us/troubleshoot/mem/intune/create-feature-update-hold-co-managed-devices

 

Let me know if above helps, otherwise we will keep digging 🙂

 

Best regards

 

Nicklas Ahlberg

 

https://nicklasahlberg.se/ 

MSIreport's avatar
MSIreport
Copper Contributor
Oct 08, 2021

NicklasAhlberg 

 

I am facing exact similar issue and found .

Do we have any working solution and fix .

 

Note : 

I can see all the registry values from : HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PolicyManager\current\device\Update

But when i goto Settings->Windows Update -> View Configured Update Policy -> still seeing "No policy have been configured Yet"

 

This is happening to only some computers (not all).

 

  • NicklasAhlberg's avatar
    NicklasAhlberg
    Brass Contributor
    Oct 10, 2021

    MSIreport 

     

    Hi,
    this does probably come down to Co-Management workloads not being applied to the faulty devices yet.


    Please try below to start the troubleshooting:
    1. Open SCCM Agent from control panel or from cmd/Powershell by running: control smscfgrc

    2. Compare "Co-management capabilities" score on a faulty and a functional device... do both devices have same score?

     

    //Nicklas

    • MSIreport's avatar
      MSIreport
      Copper Contributor
      Oct 11, 2021

      Thank youNicklasAhlberg .

       

      I did compare the SCCM workload values and all are same but only the problem which i noticed after my deep dive was, i was able to see WUServer details from SCCM eventhough we disabled Software Update client policy.

       

      Do we have any correct procedure from MS to handle this situation.

       

      Thanks in advance.

Resources