This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(147.20000000000002, 50%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMS%3C/text%3E%3C/svg%3E)
Took over an environment that was 1910. Upgraded to 2107 and then 2111. No Issues
Moved SQL to separate box, pointed SCCM to it. No issues
Added a passive server to SCCM. No issues
switched passive to active. No issues. Left it like that for a couple days
Removed passive server (old original server). No Issue
Then the weekend happened. enjoyed it and came back Monday. No, no client can get policy, If I do a machine policy retrieval on a client, in the policyagent.log I get....
Raising event:
instance of CCM_PolicyAgent_PolicyAuthorizationFailure
{
ClientID = "GUID:09726F11-832C-4827-927F-0544133C5B66";
DateTime = "20220222221431.180000+000";
PolicyNamespace = "\\.\ROOT\ccm\policy\machine\requestedconfig";
PolicySource = "SMS:WRI";
ProcessID = 13560;
ThreadID = 13424;
};
PolicyAgent_RequestAssignments 2/22/2022 4:14:31 PM 13424 (0x3470)
[Assignment Request] Assignments request for Machine <machine-name> completed with status 0x80004005 PolicyAgent_RequestAssignments 2/22/2022 4:14:31 PM 13424 (0x3470)
After doing some searching, some ideas thrown out were around the self signed certs, it was still in HTTP. No enchanced.
So I added web server pki cert to one of MP's, changed the bindings in IIS, told that MP to use https.
Added a client pki cert to my machine and a server. both show PKI as cert instead of old self signed.
When doing the policy retrieval, same exact error.
So my conclusion is it's not the certs, pki or self signed.
Stumped on this one, never seen anything like it before.
Any errors in ccmmessaging? Also, did the clients also upgrade to 2111?
No errors in ccmmessaging.
Was going to start upgrading clients. There are 14 of the new clients, including my laptop and the server itself. All do the same thing no matter the version of client.
Hi,
Hope everything goes well.
Does the issue persist? If all clients could not retrieve the policy, the issue may be on the server side, please help check if the site server and the MP are working well? Could we find any clues in the MP_GetPolicy.log and MP_Policy.log?
Thanks for your time.
Best regards,
Simon
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(240, 47%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETB%3C/text%3E%3C/svg%3E)
Hi Mike!
Have you ever solved this problem? Could you share it? I am facing the same problem, CB 2303. Out of nowhere all the clients stopped processing machine policy. The exact same error you posted.
Raising event:
instance of CCM_PolicyAgent_PolicyAuthorizationFailure
{
ClientID = "GUID:50F63C6B-BFBB-4D2D-B6DD-A379406E86DA";
DateTime = "20240321155854.150000+000";
PolicyNamespace = "\\\\.\\ROOT\\ccm\\policy\\machine\\requestedconfig";
PolicySource = "SMS:SDE";
ProcessID = 1020;
ThreadID = 4232;
};
[Assignment Request] Assignments request for Machine <MachinePolicy> completed with status 0x80004005
Regards,
Thiago