I've read some links on this site for this error but have not found a solution. We have 1 remote office with 20 machines and all 20 machines are no longer SCCM clients. The MP this 20 machines point too is up and running and we have about 4,500 other clients reporting too it without error. From these 20 machines I can ping the MP but the ClientIDManagerStartup.log has this error over and over.... RegTask: Failed to send registration request message. Error: 0x80040231 ClientIDManagerStartup 5/4/2012 2:55:47 AM 3444 (0x0D74) RegTask: Failed to send registration request. Error: 0x80040231 ClientIDManagerStartup 5/4/2012 2:55:47 AM 3444 (0x0D74) RegTask: Client is not registered. Sending registration request... ClientIDManagerStartup 5/4/2012 5:03:48 AM 3444 (0x0D74) RegTask: Failed to send registration request message. Error: 0x80040231 ClientIDManagerStartup 5/4/2012 5:03:48 AM 3444 (0x0D74) RegTask: Failed to send registration request. Error: 0x80040231 ClientIDManagerStartup 5/4/2012 5:03:48 AM 3444 (0x0D74) RegTask: Client is not registered. Sending registration request... ClientIDManagerStartup 5/4/2012 7:11:47 AM 3444 (0x0D74) RegTask: Failed to send registration request message. Error: 0x80040231 ClientIDManagerStartup 5/4/2012 7:11:47 AM 3444 (0x0D74) RegTask: Failed to send registration request. Error: 0x80040231 ClientIDManagerStartup 5/4/2012 7:11:47 AM 3444 (0x0D74) The ClientLocation.log IS pointing to the correct MP. I have RDC'd into one of these machines and run the Discover Site and it says Site US3 was found. But the last time the execmgr.log was written too was in December of last year. The last thing written to the execmgr.log was this: OnVAppSettingChanged, failed to Enable/Disable VApp Client with error 0x80008281 execmgr 12/5/2011 4:49:42 PM 3860 (0x0F14) Software Distribution Site Settings for the client are missing from WMI. execmgr 12/5/2011 4:49:42 PM 3540 (0x0DD4) Failed to instantiate UI Server {C2F23AE4-82D8-456F-A4AF-A2655D8CA726} with error 80004005 execmgr 12/5/2011 4:49:42 PM 3540 (0x0DD4) Failed to instantiate UI Server 2 {E8425D59-451B-4978-A2AB-641470EB7C02} with error 80004005 execmgr 12/5/2011 4:49:42 PM 3540 (0x0DD4) Failed to instantiate Updates UI Server {2D023958-73D0-4542-8AD6-9A507364F70E} with error 80004005 execmgr 12/5/2011 4:49:42 PM 3540 (0x0DD4) Failed to instantiate VApp UI Server {00AAB372-0D6D-4976-B5F5-9BC7605E30BB} with error 0x80004005 execmgr 12/5/2011 4:49:42 PM 3540 (0x0DD4) So how can broken clients still update certain log files? The PolicyAgentProvider.log, ClientIDManagerStartup.log, ClientLocation.log & StatusAgent.log have all been written too today. The CCMExec.log was last written too on 4/28. Any suggestions would be nice. mqh7

I repaired the WMI on all of these machines. I then pushed the client from the Primary site. In the c:\windows\ccmsetup\ folder I see a file called BITC143.tmp (or a similar name) that is 6,780kb. it is dated today but it remains a .TMP file. And the ccmsetup.log has not been written too today. Each client has been in this state for a long while now. What causes this? mqh7

Error Code 0x80040231 = "Transient error that could indicate a network problem." Have you verified that the clinet can resolve the IP address of the assignd MP and can actually communicate with it?Jason | http://blog.configmgrftw.com | Twitter @JasonSandys

From several of the client machines I ran psexec \\brokenPCname cmd.exe then from the CMD line I was able to ping the MP and it returns the correct IP address. and as I said a few of the client .log files are being written to each day....but only 4 of them (PolicyAgentProvider.log, ClientIDManagerStartup.log, ClientLocation.log & StatusAgent.log) So at this point I'm not sure what else to check. mqh7

Have you reviewed locationservices.log? Is the client approved in the ConfigMgr console?Jason | http://blog.configmgrftw.com | Twitter @JasonSandys

Yes, I did look at locationservices.log It says the following. Attempting to retrieve default management point from AD LocationServices 5/3/2012 10:28:32 PM 3880 (0x0F28) Retrieved Default Management Point from AD: US2SCCM LocationServices 5/3/2012 10:28:33 PM 3880 (0x0F28) Persisting the default management point in WMI LocationServices 5/3/2012 10:28:33 PM 3880 (0x0F28) Persisted Default Management Point Location locally LocationServices 5/3/2012 10:28:33 PM 3880 (0x0F28) Attempting to retrieve local MP from AD LocationServices 5/3/2012 10:28:33 PM 3880 (0x0F28) Current AD site of machine is Boston-MA LocationServices 5/3/2012 10:28:33 PM 3880 (0x0F28) Retrieved local Management Point from AD: US2SCCM LocationServices 5/3/2012 10:28:34 PM 3880 (0x0F28) The 'Certificate Store' is empty in the registry, using default store name 'MY'. LocationServices 5/3/2012 10:28:34 PM 3880 (0x0F28) Refreshing client operational settings over AD LocationServices 5/3/2012 10:28:34 PM 3880 (0x0F28) Refreshed security settings over AD LocationServices 5/3/2012 10:28:34 PM 3880 (0x0F28) No security settings update detected. LocationServices 5/3/2012 10:28:34 PM 3880 (0x0F28). . Using Trace32 nothing is in red. But I see now it says the cert store in empty. Is that the issue? . and in the collection all the machine show like this: Domain is correct Site code is correct Client = No Approved = N/A Assigned = Yes mqh7 , I looked on a couple of the failed machines and I looked at the Cert. The both said "You have a private key that corresponds to this certificate" It also says that the CA Root is not trusted but it seems to say that on all of our SCCM clients, even my machine which is a working client.