SCCM client failures on hash when evaluating rule from SMS_DCM "All_x64_Windows_11_and_higher_Clients" due to client having the wrong hash : invalid URL
We start to notice random failure with compliant items and software applications that used the SMS_DCM = "All_x64_Windows_11_and_higher_Clients" rule the client used to determine the OS version when determine applicability. We are on client version 5.00.9141.1011
I took a while do understand that client were all failing the download part of the document CI
the MP had the document as this call would work :
'https://SERVER/SMS\_MP/.sms\_dcm?Id&DocumentId=Windows/All\_x64\_Windows\_11\_and\_higher\_Clients/PROPERTIES'
but the client uses a hash in this manner :
'https://SERVER/SMS\_MP/.sms\_dcm?Id&DocumentId=Windows/All\_x64\_Windows\_11\_and\_higher\_Clients/PROPERTIES&Hash=4137DC6565554E9104738B34603A9C118A4E615C57ADEA859471A34F6377E350'
During my troubleshooting process I forced a policy reset to force all of the client logs to show full activity and low and behold after the ([wmiclass]'ROOT\ccm:SMS_Client').ResetPolicy(1)
the client now download the CI document for "All_x64_Windows_11_and_higher_Clients" with a different hash and URL now works ! Problem solved.
So I have only used ([wmiclass]'ROOT\ccm:SMS_Client').ResetPolicy(1) while troubleshooting, now I am wondering if we should run this proactively once on month to avoid strange issue as this one.