Todd, This is for ConfigMgr 2012. I migrated from 2007 last October. The 2007 site has been retired since mid-November. I'm trying to find a way to identify the offending machine. If it is a left over 2007 client that would explain why I couldn't find the GUID in the database.
Now to figure out how to trace down the offending machine. Thanks, Ken ... From: [email protected] [mailto:[email protected]] On Behalf Of Todd Hemsell Sent: Thursday, July 18, 2013 3:21 PM To: [email protected] Subject: Re: [mssms] Error in MP ClientAuth.log file I had quite a few of those errors when I had CM07 clients inside of a MANAGED CM12 boundary. The CM07 clients would try to talk to the CM12 DB and could not (of course) IS this CM07 or 12 that is having this issue? DO you have more than one CM environment? If so go look in the other one for your mystery machine. As a last resort you can check the time against the iis log. look for CCM_POST/ at the same time as your error. Get the ip from the machine that posted the bad data. On Thu, Jul 18, 2013 at 12:24 PM, Lutz, Ken <[email protected]<mailto:[email protected]>> wrote: I'm getting a repeating error in the MP Clientauth.log file. This error gives the GUID of the machine in question. I can't seem to find the machine in the database. I have looked in the v_R_System view at the fields with GUIDs and cannot find this machine. Where do I have to go to find this GUID? Here are the fields that I have looked at for the GUID: Previous_SMS_UUID0 SMS_Unique_Identifier0 SMBIOS_GUID0 Here is the error messages from the MP CleintAuth.log: Encountered database error while verifying headers for client 'GUID:B3D62BD4-D238-4365-9323-647083B11C1E' (0x87d00238). ClientAuth 7/18/2013 10:15:40 AM 4408 (0x1138) Error verifying message from client 'GUID:B3D62BD4-D238-4365-9323-647083B11C1E' (0x87d00238). ClientAuth 7/18/2013 10:15:40 AM 4408 (0x1138) Thanks, [cid:[email protected]] Ken Lutz Senior Systems Administrator Information Systems Department Spokane County 815 N. Jefferson Spokane, Washington 99260
<<inline: image001.png>>
