Compliance for Needed patch count per device in a collection based on scan report

SELECT CS.Name0 AS [Server Name], CASE WHEN (SUM(CASE WHEN UCS.status = 2 THEN 1 ELSE 0 END)) > 0 THEN (‘Needs ‘ + (CAST(SUM(CASE WHEN UCS.status = 2 THEN 1 ELSE 0 END) AS varchar(10)) + ‘ Patches’)) ELSE ‘Good Client’ END AS ‘Status’, ws.LastHWScan AS ‘Last HW scan’, FCM.CollectionID
FROM v_UpdateComplianceStatus AS UCS LEFT OUTER JOIN
v_GS_COMPUTER_SYSTEM AS CS ON CS.ResourceID = UCS.ResourceID INNER JOIN
v_CICategories_All AS catall2 ON catall2.CI_ID = UCS.CI_ID INNER JOIN
v_CategoryInfo AS catinfo2 ON catall2.CategoryInstance_UniqueID = catinfo2.CategoryInstance_UniqueID AND catinfo2.CategoryTypeName = ‘UpdateClassification’ LEFT OUTER JOIN
v_GS_WORKSTATION_STATUS AS ws ON ws.ResourceID = CS.ResourceID LEFT OUTER JOIN
v_FullCollectionMembership AS FCM ON FCM.ResourceID = CS.ResourceID
WHERE (UCS.Status = ‘2’) AND (FCM.CollectionID = ‘P01000xx’)
GROUP BY CS.Name0, ws.LastHWScan, FCM.CollectionID
ORDER BY [Server Name], ‘Last HW scan’, FCM.CollectionID

High CPU Utilization during Dual scan – Intune/Configmgr

We have an issue where the client has workload enabled in Intune for WufB and Office click to run apps but the client scan from both Intune and Configmgr reported the memory leak 100% and Froze the PC from workability.

we have it back on normal or decent level 40~50 % when the MECM and or Intune agent has the assigned workload only.

For some reason the workload is not assigned properly, when there is a clash b/w on prem vs cloud within the agent then this is happening.

What to check ?

1. Check for the windows update agent log.
2. Check for the applied policy both from on-Prem and Intune (device configuration status if any)

What action to be done for the remediation?

1. Uninstall and reinstall the agent.
2. C:/windows/system32/grouppolicy/machine/registry.pol ( recreation)
3. Cross test.
4. check the status and create MDMdiagnostics report.

Also , the Clickshare app auto update has contributed considerably once the above is resolved, removal of the app brought the memory utilization from high 50~ 60% to lower 20~,so which may also played its part., as per the Windows OS support