SCCM Co-management issue

Billy Cullen 21 Reputation points
2020-09-20T08:15:12.017+00:00

Hi,

We have recently started to move all our devices to a co-managed state to leverage the additional functionality that Intune will be able to provide our organisation in terms of managing our Windows 10 devices. The move has been quite easy with very little issues, however I have a couple of devices that just won't receive the 2004 feature upgrade since becoming co-managed. These devices receive both quality and driver updates via Intune without any issue, but just won't display the feature update. All of them are running 1909 and have the latest CU, SSU's installed. Bothe the comanagement handler log and wuahandler logs both show that the devices updates are being managed by intune.

There isn't any blockers present on these devices as I have ran the 2004 media to ensure that there was no issues with any drives, disk space etc and they all passed. I have repaired the SCCM client and reinstalled it to no avail, I really don't want to rebuild these devices, but at the moment it seems like the only option that I have left. Has anyone else experienced a similar issue?

Thanks

Billy

Windows 10
Windows 10
A Microsoft operating system that runs on personal computers and tablets.
11,052 questions
Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
12,508 questions
Microsoft Intune Configuration
Microsoft Intune Configuration
Microsoft Intune: A Microsoft cloud-based management solution that offers mobile device management, mobile application management, and PC management capabilities.Configuration: The process of arranging or setting up computer systems, hardware, or software.
1,783 questions
Accepted answer
  1. Jason Sandys 31,186 Reputation points Microsoft Employee
    2020-09-20T20:52:44.887+00:00

    These devices are most likely subject to a feature update safeguard/compatibility hold. Some safeguard holds are listed at https://video2.skills-academy.com/en-us/windows/release-information/status-windows-10-2004. Also, see https://video2.skills-academy.com/en-us/windows/deployment/update/update-compliance-feature-update-status#safeguard-holds for implementing Updates Compliance so that you have visibility into these holds and overall update tracking to boot.

    0 comments

3 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Eswar Koneti 2,201 Reputation points
    2020-09-20T16:01:02.82+00:00

    As per the docs https://video2.skills-academy.com/en-us/mem/intune/protect/windows-update-for-business-configure#limitations-for-windows-10-feature-updates,
    While Windows 10 feature updates remains in public preview, when co-managing devices with Configuration Manager and Intune, there is a limitation where feature update policies may not immediately take effect, causing devices to update to a later feature update than configured in Intune. This limitation will be removed with a future update to Configuration Manager.

    reference https://video2.skills-academy.com/en-us/answers/questions/74051/intune-device-will-update-to-windows-10-version-20.html

    0 comments
  2. Billy Cullen 21 Reputation points
    2020-09-21T07:46:39.45+00:00

    Hi Jason,

    Thanks for sharing the links it looks like you could onto something as they all have Conexant ISST audio installed, so that could be the reason why they aren't upgrading. I will opt out of safeguard hold on one of the devices to see if that allows the device to upgrade, and let you know the results

    Thanks

    Billy

    0 comments
  3. Billy Cullen 21 Reputation points
    2020-09-21T08:45:06.69+00:00

    Hi Jason,

    I can confirm that the answer you provide was correct and the devices were in fact being prevent from upgrading by the safeguard hold because of the Conexant audio issues.

    Thank you for help

    Regards

    Billy

    0 comments