Thank you Sherry for the response. I used the SCCM Client Center and performed a Hard-Reset on the policies. It appears to remove all the policies and re-download them however I end up getting the same exact errors. Do you have any other suggestions?
Brandon From: [email protected] [mailto:[email protected]] On Behalf Of Sherry Kissinger Sent: Wednesday, August 6, 2014 12:34 PM To: [email protected] Subject: [EXTERNAL EMAIL] :Re: [mssms] Policy Issues find what machine GUID:12389A49-8975-4RD5-88C5-B3AFEEB25234 really is. select * from v_r_system where sms_unique_identifier0 = 'GUID:12389A49-8975-4RD5-88C5-B3AFEEB25234' then go find that box, and using whatever favorite tool you feel like, policy reset on it. (and watch the client logs) Roger Zander's client center has policy reset in there, otherwise I'm sure it can be done via remote wmi in multiple other ways. Sherry Kissinger On Wednesday, August 6, 2014 9:42 AM, "Lassiter, Brandon" <[email protected]<mailto:[email protected]>> wrote: I am receiving many status messages with an ID of 10805 stating: The ConfigMgr Client has determined that its policy is incorrect. A full policy update will be requested to correct the issue. For more information see PolicyAgent.log on the client machine When reviewing the clients PolicyAgent.log I see: Policy assignment validation for this resource has failed. The next request for assignments from SMS:ABC will ask for a full update. Policy cookie history: 08/06/2014 06:15:24 Delta "2014-07-11 19:17:53.837" 08/06/2014 06:30:24 Delta "2014-07-11 19:17:53.837" 08/06/2014 06:45:24 Delta "2014-07-11 19:17:53.837" 08/06/2014 07:00:24 Delta "2014-07-11 19:17:53.837" 08/06/2014 07:15:24 Delta "2014-07-11 19:17:53.837" 08/06/2014 07:30:24 Delta "2014-07-11 19:17:53.837" 08/06/2014 07:45:24 Delta "2014-07-11 19:17:53.837" 08/06/2014 08:00:24 Delta "2014-07-11 19:17:53.837" 08/06/2014 08:15:24 Delta "2014-07-11 19:17:53.837" 08/06/2014 08:30:24 Delta "2014-07-11 19:17:53.837" 08/06/2014 08:45:24 Delta "2014-07-11 19:17:53.837" 08/06/2014 09:00:24 Delta "2014-07-11 19:17:53.837" 08/06/2014 09:15:24 Delta "2014-07-11 19:17:53.837" 08/06/2014 09:30:24 Delta "2014-07-11 19:17:53.837" 08/06/2014 09:45:24 Delta "2014-07-11 19:17:53.837" 08/06/2014 10:00:24 Delta "2014-07-11 19:17:53.837" 08/06/2014 10:15:24 Delta "2014-07-11 19:17:53.837" 08/06/2014 10:30:24 Delta "2014-07-11 19:17:53.837" 08/06/2014 10:45:25 Delta "2014-07-11 19:17:53.837" 08/06/2014 11:00:25 Delta "2014-07-11 19:17:53.837" 08/06/2014 11:15:25 Delta "2014-07-11 19:17:53.837" 08/06/2014 11:30:25 Delta "2014-07-11 19:17:53.837" 08/06/2014 11:45:25 Delta "2014-07-11 19:17:53.837" 08/06/2014 12:00:25 Delta "2014-07-11 19:17:53.837" 08/06/2014 12:09:24 Delta "2014-07-11 19:17:53.837" And Raising event: instance of CCM_PolicyAgent_PolicyMismatchWarning { ClientID = "GUID:12389A49-8975-4RD5-88C5-B3AFEEB25234"; DateTime = "20140806120924.173000+000"; PolicyNamespace = "\\\\.\\ROOT\\ccm\\Policy\\S_1_5_21_2085361252_1599615630_968895117_27601\\RequestedConfig<file:///\\\ROOT\ccm\Policy\S_1_5_21_2085361252_1599615630_968895117_27601\RequestedConfig>"; PolicySource = "SMS:ABC"; ProcessID = 5108; ThreadID = 2104; }; I also see on the MP in MP_Policy.log [cid:[email protected]] Does anyone have any ideas on how to resolve this? Thanks in Advance, Brandon Lassiter
