Having freshly installed SCCM clients not pick up their policy for the first time is, unfortunately, not terribly uncommon. A quick look at the LocationServices.log or ClientLocation.log files will generally pinpoint where the issue may lie, whether it be boundaries or certificate enrollment.
But what if the client had been working, but then, without any other change, it stops. Not only that, it’s happening to all clients. All the client logs are error free, and are indicating proper behavior.
We had this happen to one of our clients recently, and first clue or useful error was in the MP_Policy.log file:
Detected at least one row in the result set from PolicyAssignment table which does not have a Signature, rejecting all rows. CalculateCRCFullAssignments cookie has changed, old cookie
It turns out there’s an error in the database that needs to be cleaned up to resolve this. So, run the following queries on your SQL Server:
SELECT * FROM ResPolicyMap WHERE machineid = 0 and PADBID IN (SELECT PADBID FROM PolicyAssignment WHERE BodyHash IS NULL)
If the value of TargetSourceID is NULL, you’ll need to clear those rows:
Delete FROM ResPolicyMap WHERE machineid = 0 and PADBID IN (SELECT PADBID FROM PolicyAssignment WHERE BodyHash IS NULL)
That should do it. You may need to restart the SMS Agent Host service on the Management Point.
Shane Skriletz, PEI