Jump to content


j1mmyd3an

SCCM 2012 SP1 - Client Policy Errors

Recommended Posts

Hi there, I've updated our site to SP1 which was a total nightmare. After correcting all the issues I am still stuck on one major one. My PolicyAgent.log file on my clients is full of the following errors:

 

Signature verification failed for PolicyAssignmentID {GUID}

 

Followed by:

 

 

Raising event:
instance of CCM_PolicyAgent_PolicyAuthorizationFailure
{
ClientID = "GUID:9cc7d533-db8f-4cf9-a874-97c174d06649";
DateTime = "20130212164743.208000+000";
PolicyNamespace = "\\\\computername\\ROOT\\ccm\\Policy\\Machine\\RequestedConfig";
PolicySource = "SMS:sitename";
ProcessID = 664;
ThreadID = 6580;
};
I have read through more troubleshooting posts than I care to think about and I'm still stuck. I've gone through the logs that keep getting mentioned and this PolicyAgent.log is the only one that shows me errors. The certificates were set up as outlined in http://technet.microsoft.com/en-us/library/gg682023.aspx and the logs seem to indicate they are working OK. Of course, the error I'm having trouble with also seems to be certificate related so obviously I missed something.
I've been going in circles trying to get to the bottom of this so I've decided to post. If anyone has any suggestions on where to start troubleshooting this I'd love to hear them.
Thanks for all your help!

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.