Hello, Im using the System Center Configuration Manager 2007. In the ClientIDManagerStartup.log there is every time the same Error like: Code Snippet <![LOG[RegTask: Failed to send registration request. Error: 0x8000000a]LOG]!><time="06:47:17.531+420" date="07-25-2008" component="ClientIDManagerStartup" context="" type="3" thread="3308" file="regtask.cpp:1314"> <![LOG[RegTask: Client is not registered. Sending registration request...]LOG]!><time="08:55:17.531+420" date="07-25-2008" component="ClientIDManagerStartup" context="" type="1" thread="3308" file="regtask.cpp:1434"> <![LOG[RegTask: Failed to send registration request message. Error: 0x8000000a]LOG]!><time="08:55:17.546+420" date="07-25-2008" component="ClientIDManagerStartup" context="" type="3" thread="3308" file="regtask.cpp:1139"> <![LOG[RegTask: Failed to send registration request. Error: 0x8000000a]LOG]!><time="08:55:17.546+420" date="07-25-2008" component="ClientIDManagerStartup" context="" type="3" thread="3308" file="regtask.cpp:1314"> Pleas help me to get this error away, I dont know what I have do to. Thanks! German: Hallo, Ich verwende den System Center Configuration Manager 2007. In der Logdatei: ClientIDManagerStartup.log kommt immer der gleiche Fehler: Code Snippet <![LOG[RegTask: Failed to send registration request. Error: 0x8000000a]LOG]!><time="08:55:17.546+420" date="07-25-2008" component="ClientIDManagerStartup" context="" type="3" thread="3308" file="regtask.cpp:1314"> <![LOG[RegTask: Failed to send registration request. Error: 0x8000000a]LOG]!><time="06:47:17.531+420" date="07-25-2008" component="ClientIDManagerStartup" context="" type="3" thread="3308" file="regtask.cpp:1314"> <![LOG[RegTask: Client is not registered. Sending registration request...]LOG]!><time="08:55:17.531+420" date="07-25-2008" component="ClientIDManagerStartup" context="" type="1" thread="3308" file="regtask.cpp:1434"> <![LOG[RegTask: Failed to send registration request message. Error: 0x8000000a]LOG]!><time="08:55:17.546+420" date="07-25-2008" component="ClientIDManagerStartup" context="" type="3" thread="3308" file="regtask.cpp:1139"> Vielleicht habt ihr ja eine Ahnung wie dieser Fehler hervorgerufen wird und wie ich ihn wegbekommen kann. Danke fr eure Hilfe. Mit freundlichen Gren, Argre

Are there any error in other logs (for example ccmexec.log)? Is this only one client? Are all clients affected? Does it work for other clients? Is your MP working without any issues?

Is this a Mixed or Native mode site?

Hi,thanks very much for your quick answer.I missed to tell some details: I've a testing environment with a couple of clients but I try to get one (for now) up and running. I use just SCCM 2007 and its clients, not upgraded from SMS 2003.My site is in mixed mode to use clients in subnets.In the site boundary there is the subnet 172.16.0.0 where to find the clients.I use the network discovery method - SNMP - to find clients.I can't use push installation for clients so I install them manually (just one till yet).It seems to me that the MP works without issues because of one entry in mpMSI.log: Code Snippet MSI (s) (5C:10) [16:38:33:898]: Product: SMS Management Point -- Installation operation completed successfully.There are other errors in other logfiles. For example in the ccmexec.log you mentioned: Code Snippet <![LOG[Failed in WinHttpSendRequest API, ErrorCode = 0x2ee7]LOG]!><time="13:44:54.437+420" date="07-24-2008" component="CCMEXEC" context="" type="3" thread="3308" file="ccmhttppost.cpp:786"><![LOG[[CCMHTTP] HTTP ERROR: URL=http://w2k3xpedev.SCCMDomain.local/ccm_system/request, Port=80, Protocol=http, SSLOptions=0, Code=12007, Text=ERROR_WINHTTP_NAME_NOT_RESOLVED]LOG]!><time="13:44:54.437+420" date="07-24-2008" component="CCMEXEC" context="" type="1" thread="3308" file="ccmhttperror.cpp:264"><![LOG[Raising event:instance of CCM_CcmHttp_Status{ DateTime = "20080724204454.453000+000"; HostName = "w2k3xpedev.SCCMDomain.local"; HRESULT = "0x80072ee7"; ProcessID = 524; StatusCode = 0; ThreadID = 3308;};]LOG]!><time="13:44:54.453+420" date="07-24-2008" component="CCMEXEC" context="" type="1" thread="3308" file="event.cpp:525"><![LOG[HandleRemoteSyncSend failed (0x80040231).]LOG]!><time="13:44:54.468+420" date="07-24-2008" component="CCMEXEC" context="" type="3" thread="3308" file="forwarder_client.cpp:1308"><![LOG[CForwarder_Sync::Send failed (0x80040231).]LOG]!><time="13:44:54.468+420" date="07-24-2008" component="CCMEXEC" context="" type="3" thread="3308" file="forwarder_client.cpp:1380"><![LOG[CForwarder_Base::Send failed (0x80040231).]LOG]!><time="13:44:54.468+420" date="07-24-2008" component="CCMEXEC" context="" type="3" thread="3308" file="forwarder_base.cpp:393">Other error messages are in the LocationServices.log: Code Snippet <![LOG[Retrieved SLP [w2k3xpedev] from Registry]LOG]!><time="02:32:56.640+420" date="07-25-2008" component="LocationServices" context="" type="1" thread="3308" file="lsad.cpp:2255"><![LOG[Failed to resolve 'SMS_SLP' to IP address from WINS]LOG]!><time="02:33:05.703+420" date="07-25-2008" component="LocationServices" context="" type="3" thread="3308" file="lswins.cpp:324"><![LOG[LSGetSLP : Failed to resolve SLP from WINS, is it published]LOG]!><time="02:33:05.703+420" date="07-25-2008" component="LocationServices" context="" type="3" thread="3308" file="lsad.cpp:2277"><![LOG[LSGetSLP: Successfully discovered SLP(s) for Lookup]LOG]!><time="02:33:05.703+420" date="07-25-2008" component="LocationServices" context="" type="1" thread="3308" file="lsad.cpp:2300"><![LOG[Failed to send request to /sms_slp/slp.dll?site&sc=123 at host w2k3xpedev, error 0x2ee7]LOG]!><time="02:33:07.953+420" date="07-25-2008" component="LocationServices" context="" type="3" thread="3308" file="ccmhttpget.cpp:790"><![LOG[[CCMHTTP] HTTP ERROR: URL=http://w2k3xpedev/sms_slp/slp.dll?site&sc=123, Port=80, Protocol=http, SSLOptions=0, Code=12007, Text=ERROR_WINHTTP_NAME_NOT_RESOLVED]LOG]!><time="02:33:07.953+420" date="07-25-2008" component="LocationServices" context="" type="1" thread="3308" file="ccmhttperror.cpp:264"><![LOG[Raising event:instance of CCM_CcmHttp_Status{ DateTime = "20080725093307.968000+000"; HostName = "w2k3xpedev"; HRESULT = "0x80072ee7"; ProcessID = 524; StatusCode = 0; ThreadID = 3308;};]LOG]!><time="02:33:07.968+420" date="07-25-2008" component="LocationServices" context="" type="1" thread="3308" file="event.cpp:525"><![LOG[LSGetManagementPointForSiteFromSLP : No Default MP returned from SLP for site <123>]LOG]!><time="02:33:07.968+420" date="07-25-2008" component="LocationServices" context="" type="3" thread="3308" file="lsad.cpp:3135"><![LOG[Failed to retrieve Default Management Point from SLP]LOG]!><time="02:33:07.968+420" date="07-25-2008" component="LocationServices" context="" type="3" thread="3308" file="lsad.cpp:2619"><![LOG[Attempting to retrieve default management point from WINS]LOG]!><time="02:33:07.984+420" date="07-25-2008" component="LocationServices" context="" type="1" thread="3308" file="lsad.cpp:2652"><![LOG[Attempting to retrieve NLB default management point from WINS]LOG]!><time="02:33:07.984+420" date="07-25-2008" component="LocationServices" context="" type="1" thread="3308" file="lsad.cpp:2658"><![LOG[Failed to resolve 'NLB_123' to IP address from WINS]LOG]!><time="02:33:12.484+420" date="07-25-2008" component="LocationServices" context="" type="3" thread="3308" file="lswins.cpp:324"><![LOG[No NLB default management point is present, attempting to resolve default management point from WINS]LOG]!><time="02:33:12.484+420" date="07-25-2008" component="LocationServices" context="" type="1" thread="3308" file="lsad.cpp:2664"><![LOG[Failed to resolve 'MP_123' to IP address from WINS]LOG]!><time="02:33:16.984+420" date="07-25-2008" component="LocationServices" context="" type="3" thread="3308" file="lswins.cpp:324"><![LOG[Failed to retrieve default MP through WINS.]LOG]!><time="02:33:16.984+420" date="07-25-2008" component="LocationServices" context="" type="3" thread="3308" file="lsad.cpp:2674"><![LOG[Failed to retrieve AMP for site code '123' with error (0x80004005). Nulling existing entry in WMI]LOG]!><time="02:33:16.984+420" date="07-25-2008" component="LocationServices" context="" type="1" thread="3308" file="lsad.cpp:3855"><![LOG[Failed to reset certificate request times. (0x80041002)]LOG]!><time="02:33:17.015+420" date="07-25-2008" component="LocationServices" context="" type="3" thread="3308" file="lssecurity.cpp:4231"><![LOG[Persisted Default Management Point Location locally]LOG]!><time="02:33:17.015+420" date="07-25-2008" component="LocationServices" context="" type="1" thread="3308" file="lsad.cpp:3863"><![LOG[The 'Certificate Store' is empty in the registry, using default store name 'MY'.]LOG]!><time="02:33:17.062+420" date="07-25-2008" component="LocationServices" context="" type="1" thread="3308" file="ccmcert.cpp:204"><![LOG[The 'Certificate Store' is empty in the registry, using default store name 'MY'.]LOG]!><time="02:33:17.062+420" date="07-25-2008" component="LocationServices" context="" type="1" thread="3308" file="ccmcert.cpp:204"><![LOG[No security settings update detected.]LOG]!><time="02:33:17.078+420" date="07-25-2008" component="LocationServices" context="" type="1" thread="3308" file="lssecurity.cpp:4350">I read that the file ClientLocation.log is also important to solve problems with SCCM clients. In this file there are no errors, just some information: Code Snippet <![LOG[Current Management Point is w2k3xpedev.SCCMDomain.local with version 5931 and capabilities: <Capabilities SchemaVersion="1.0"/>.]LOG]!><time="02:33:08.015+420" date="07-25-2008" component="ClientLocation" context="" type="1" thread="2712" file="smsclientclass.cpp:1094"><![LOG[Getting Assigned Site]LOG]!><time="11:03:56.593+420" date="07-25-2008" component="ClientLocation" context="" type="1" thread="3144" file="smsclientclass.cpp:922"><![LOG[Assigned Site is 123]LOG]!><time="11:03:56.609+420" date="07-25-2008" component="ClientLocation" context="" type="1" thread="3144" file="smsclientclass.cpp:933">The goal of my test is to figure out the reason why clients (except the DC) have an approved status of "N/A" and then identify manual installed clients and to run them.Thanks for your help!

Hi, Fast response then I had to get back to work :-( Ok I see that you definately have IIS problems, HTTP ERROR: URL=http://w2k3xpedev/sms_slp/slp.dll?site&sc=123 Go check the IIS log files %windir%\system32\logfiles and you should see errors in there as well

Thanks for your response.I looked into the folder %windir%\system32\logfiles and found 4 other folders. The one named "W3SVC1" belongs to ISS I guess. In this folder there are files named "ex<year><month><day>.log.Here are some snippets from the file ex080725.log: Code Snippet #Fields: date time s-sitename s-ip cs-method cs-uri-stem cs-uri-query s-port cs-username c-ip cs(User-Agent) sc-status sc-substatus sc-win32-status 2008-07-25 06:15:15 W3SVC1 172.16.1.1 POST /SMS_FSP/.sms_fsp - 80 - 172.16.1.1 ccmhttp 200 0 02008-07-25 06:15:41 W3SVC1 172.16.1.1 GET /SMS_MP/.sms_aut MPKEYINFORMATION 80 - 172.16.1.1 SMS+CCM 200 0 02008-07-25 06:15:41 W3SVC1 172.16.1.1 POST /SMS_FSP/.sms_fsp - 80 - 172.16.1.1 ccmhttp 200 0 02008-07-25 06:15:46 W3SVC1 172.16.1.1 CCM_POST /ccm_system/request - 80 - 172.16.1.1 ccmhttp 200 0 02008-07-25 06:15:46 W3SVC1 172.16.1.1 CCM_POST /ccm_system/request - 80 - 172.16.1.1 ccmhttp 200 0 02008-07-25 06:15:48 W3SVC1 172.16.1.1 CCM_POST /ccm_system/request - 80 - 172.16.1.1 ccmhttp 200 0 02008-07-25 06:16:08 W3SVC1 172.16.1.1 GET /SMS_MP/.sms_aut MPLIST 80 - 172.16.1.1 SMS_MP_CONTROL_MANAGER 200 0 222008-07-25 06:16:08 W3SVC1 172.16.1.1 GET /devicemgmt selftest 80 - 172.16.1.1 SMS_MP_CONTROL_MANAGER 200 0 222008-07-25 06:19:22 W3SVC1 172.16.1.1 CCM_POST /ccm_system/request - 80 - 172.16.1.1 ccmhttp 200 0 0...2008-07-25 08:16:09 W3SVC1 172.16.1.1 GET /SMS_MP/.sms_aut MPLIST 80 - 172.16.1.1 SMS_MP_CONTROL_MANAGER 200 0 222008-07-25 08:16:09 W3SVC1 172.16.1.1 GET /devicemgmt selftest 80 - 172.16.1.1 SMS_MP_CONTROL_MANAGER 200 0 222008-07-25 08:19:29 W3SVC1 172.16.1.1 CCM_POST /ccm_system/request - 80 - 172.16.1.1 ccmhttp 200 0 02008-07-25 08:19:30 W3SVC1 172.16.1.1 GET /SMS_MP/.sms_pol %7B6126df56-f3f8-441c-a2c2-8ab67e06dc0c%7D.5_00 80 - 172.16.1.1 SMS+CCM 200 0 02008-07-25 08:19:35 W3SVC1 172.16.1.1 GET /SMS_MP/.sms_pol {32c73d45-fa39-4d3a-8cbb-ee4d47aaa961}.7_00 80 - 172.16.1.1 Microsoft+BITS/6.7 200 0 02008-07-25 08:19:38 W3SVC1 172.16.1.1 GET /SMS_MP/.sms_pol {32c73d45-fa39-4d3a-8cbb-ee4d47aaa961}.7_00 80 - 172.16.1.1 Microsoft+BITS/6.7 200 0 02008-07-25 08:19:42 W3SVC1 172.16.1.1 GET /SMS_MP/.sms_pol {32c73d45-fa39-4d3a-8cbb-ee4d47aaa961}.7_00 80 - 172.16.1.1 Microsoft+BITS/6.7 200 0 02008-07-25 08:19:44 W3SVC1 172.16.1.1 GET /SMS_MP/.sms_pol {32c73d45-fa39-4d3a-8cbb-ee4d47aaa961}.7_00 80 - 172.16.1.1 Microsoft+BITS/6.7 200 0 02008-07-25 08:19:46 W3SVC1 172.16.1.1 GET /SMS_MP/.sms_pol {32c73d45-fa39-4d3a-8cbb-ee4d47aaa961}.7_00 80 - 172.16.1.1 Microsoft+BITS/6.7 200 0 02008-07-25 08:19:47 W3SVC1 172.16.1.1 GET /SMS_MP/.sms_pol {a7b12fde-a57e-408f-8d06-6191ecb080a3}.4_00 80 - 172.16.1.1 Microsoft+BITS/6.7 200 0 02008-07-25 08:21:09 W3SVC1 172.16.1.1 GET /SMS_MP/.sms_aut MPLIST 80 - 172.16.1.1 SMS_MP_CONTROL_MANAGER 200 0 222008-07-25 08:21:09 W3SVC1 172.16.1.1 GET /devicemgmt selftest 80 - 172.16.1.1 SMS_MP_CONTROL_MANAGER 200 0 222008-07-25 08:21:51 W3SVC1 172.16.1.1 CCM_POST /ccm_system/request - 80 - 172.16.1.1 ccmhttp 200 0 02008-07-25 08:22:29 W3SVC1 172.16.1.1 CCM_POST /ccm_system/request - 80 - 172.16.1.1 ccmhttp 200 0 02008-07-25 08:26:09 W3SVC1 172.16.1.1 GET /SMS_MP/.sms_aut MPLIST 80 - 172.16.1.1 SMS_MP_CONTROL_MANAGER 200 0 222008-07-25 08:26:09 W3SVC1 172.16.1.1 GET /devicemgmt selftest 80 - 172.16.1.1 SMS_MP_CONTROL_MANAGER 200 0 222008-07-25 08:30:29 W3SVC1 172.16.1.1 GET /SMS_MP/.sms_pol %7B6126df56-f3f8-441c-a2c2-8ab67e06dc0c%7D.5_00 80 - 172.16.1.1 SMS+CCM 200 0 02008-07-25 08:31:09 W3SVC1 172.16.1.1 GET /SMS_MP/.sms_aut MPLIST 80 - 172.16.1.1 SMS_MP_CONTROL_MANAGER 200 0 222008-07-25 08:31:09 W3SVC1 172.16.1.1 GET /devicemgmt selftest 80 - 172.16.1.1 SMS_MP_CONTROL_MANAGER 200 0 222008-07-25 08:36:09 W3SVC1 172.16.1.1 GET /SMS_MP/.sms_aut MPLIST 80 - 172.16.1.1 SMS_MP_CONTROL_MANAGER 200 0 222008-07-25 08:36:09 W3SVC1 172.16.1.1 GET /devicemgmt selftest 80 - 172.16.1.1 SMS_MP_CONTROL_MANAGER 200 0 222008-07-25 08:41:09 W3SVC1 172.16.1.1 GET /SMS_MP/.sms_aut MPLIST 80 - 172.16.1.1 SMS_MP_CONTROL_MANAGER 200 0 222008-07-25 08:41:09 W3SVC1 172.16.1.1 GET /devicemgmt selftest 80 - 172.16.1.1 SMS_MP_CONTROL_MANAGER 200 0 222008-07-25 08:45:30 W3SVC1 172.16.1.1 GET /SMS_MP/.sms_pol %7B6126df56-f3f8-441c-a2c2-8ab67e06dc0c%7D.5_00 80 - 172.16.1.1 SMS+CCM 200 0 02008-07-25 08:45:52 W3SVC1 172.16.1.1 POST /SMS_FSP/.sms_fsp - 80 - 172.16.1.1 ccmhttp 200 0 02008-07-25 08:45:54 W3SVC1 172.16.1.1 GET /SMS_MP/.sms_aut MPKEYINFORMATION 80 - 172.16.1.1 SMS+CCM 200 0 02008-07-25 08:45:54 W3SVC1 172.16.1.1 POST /SMS_FSP/.sms_fsp - 80 - 172.16.1.1 ccmhttp 200 0 02008-07-25 08:45:56 W3SVC1 172.16.1.1 GET /SMS_MP/.sms_pol %7B6126df56-f3f8-441c-a2c2-8ab67e06dc0c%7D.5_00 80 - 172.16.1.1 SMS+CCM 200 0 02008-07-25 08:45:56 W3SVC1 172.16.1.1 CCM_POST /ccm_system_windowsauth/request - 80 SCCMDOMAIN\W2K3XPEDEV$ 172.16.1.1 ccmhttp 200 0 02008-07-25 08:45:56 W3SVC1 172.16.1.1 CCM_POST /ccm_system_windowsauth/request - 80 SCCMDOMAIN\W2K3XPEDEV$ 172.16.1.1 ccmhttp 200 0 02008-07-25 08:46:09 W3SVC1 172.16.1.1 GET /SMS_MP/.sms_aut MPLIST 80 - 172.16.1.1 SMS_MP_CONTROL_MANAGER 200 0 222008-07-25 08:46:09 W3SVC1 172.16.1.1 GET /devicemgmt selftest 80 - 172.16.1.1 SMS_MP_CONTROL_MANAGER 200 0 222008-07-25 08:51:09 W3SVC1 172.16.1.1 GET /SMS_MP/.sms_aut MPLIST 80 - 172.16.1.1 SMS_MP_CONTROL_MANAGER 200 0 222008-07-25 08:51:09 W3SVC1 172.16.1.1 GET /devicemgmt selftest 80 - 172.16.1.1 SMS_MP_CONTROL_MANAGER 200 0 222008-07-25 08:52:53 W3SVC1 172.16.1.1 CCM_POST /ccm_system/request - 80 - 172.16.1.1 ccmhttp 200 0 02008-07-25 08:52:53 W3SVC1 172.16.1.1 CCM_POST /ccm_system/request - 80 - 172.16.1.1 ccmhttp 500 0 0...2008-07-25 12:46:09 W3SVC1 172.16.1.1 GET /SMS_MP/.sms_aut MPLIST 80 - 172.16.1.1 SMS_MP_CONTROL_MANAGER 200 0 222008-07-25 12:46:09 W3SVC1 172.16.1.1 GET /devicemgmt selftest 80 - 172.16.1.1 SMS_MP_CONTROL_MANAGER 200 0 222008-07-25 12:51:09 W3SVC1 172.16.1.1 GET /SMS_MP/.sms_aut MPLIST 80 - 172.16.1.1 SMS_MP_CONTROL_MANAGER 200 0 222008-07-25 12:51:09 W3SVC1 172.16.1.1 GET /devicemgmt selftest 80 - 172.16.1.1 SMS_MP_CONTROL_MANAGER 200 0 222008-07-25 12:53:05 W3SVC1 172.16.1.1 CCM_POST /ccm_system/request - 80 - 172.16.1.1 ccmhttp 200 0 02008-07-25 12:53:05 W3SVC1 172.16.1.1 CCM_POST /ccm_system/request - 80 - 172.16.1.1 ccmhttp 200 0 02008-07-25 12:56:09 W3SVC1 172.16.1.1 GET /SMS_MP/.sms_aut MPLIST 80 - 172.16.1.1 SMS_MP_CONTROL_MANAGER 200 0 222008-07-25 12:56:09 W3SVC1 172.16.1.1 GET /devicemgmt selftest 80 - 172.16.1.1 SMS_MP_CONTROL_MANAGER 200 0 222008-07-25 13:01:09 W3SVC1 172.16.1.1 GET /SMS_MP/.sms_aut MPLIST 80 - 172.16.1.1 SMS_MP_CONTROL_MANAGER 200 0 222008-07-25 13:01:09 W3SVC1 172.16.1.1 GET /devicemgmt selftest 80 - 172.16.1.1 SMS_MP_CONTROL_MANAGER 200 0 22I hope I didn't miss important lines to post. I searched for "error" and "warning" but there's nothing to find in the whole file.I hope you're able to locate the problem.Thanks for your help.Argre my new account name: cm_home

It looks like the client is unable to register because it can't determine an MP to talk to. If you look in LocationServices.log, it looks like it's going to AD, then to an SLP (which isn't resolvable through DNS) so it's stuck in kind of a limbo. This looks like it may be a misconfiguration of some kind. It's hard to say without complete logs, but I'd make sure you're using the right site code, that you have a default MP for your site, and ideally that you're publishing to Active Directory (if possible).

Thanks for your answer.I had the same idea when I saw the LocationServices.log but then I saw the ClientLocation.log with the correct MP selected.The whole logfiles are to long to post here but I'll post them in pastebin.com and give you the URLs. I hope it helps to determine the problem.Some details about the client installation:The command to install the client manually on each machine locally: Code Snippet CCMSetup.exe /source:"C:\install\System_Center_Configuration_Management_Client" /mp:172.16.1.1 /service /forcereboot SMSMP=172.16.1.1 SMSSITECODE=123 SMSSLP=172.16.1.1 FSP=172.16.1.1(172.16.1.1/16 is the IP of the SCCM with MP, SLP, DC with extended AD and SQL server.)It is my first usage of the SCCM and I always used the sitecode 123.Boundary: 172.16.0.0 (subnet where to find the clients)BITS activatedStatic IPs without DHCP so I use SNMP to discover clients.Client Discovery Method: Network Discovery (I put the ip address of each client into the SNMP Devices list.)Here are my logfiles of the client's machine:ccmsetup.log http://pastebin.com/m7460b9d7CcmExec.log http://pastebin.com/m6051304aClientIDManagerStartup.log http://pastebin.com/m6e5d2300ClientLocation.log http://pastebin.com/m704d738LocationServices.log http://pastebin.com/mc5d0e86 If you need some more information about my installation I didn't post yet or something else to solve the problem, please let me know.Thanks for helping me!cm_home

First off, please forgive me for not reading the entire thread. I just came acrossan SCCM client in one of my customers' environments that had the following errors in ClientIDManagerStartup.log, similar to the ones in your post: Failed to send registration request. Error: 0x8000000a Client is not registered. Sending registration request... If this is a single machine you are having issues with, I would recommend trying a WMI rebuild. Rebuilding WMI is something I onlytry as a last resort.1. Stop the "Windows Management Instrumentation" service on the problematic machine.2. Delete the file and the folder (and its contents) in \windows\system32\wbem\repository3. Start the "Windows Management Instrumentation" service4.Connect to WMI on the remote machine by running WBEMTEST from your own machine, and connecting to WMI namespace \\remotemachine\root\cimv25. Watch that the file and folder (and contents) that you deleted in step 2 are automatically re-created6.Start the "SMS Agent Host" service and watch the logs. The SCCM client will attempt to repair itself in 5 minutes.Again, sorry if I'm completely off-base, but this WMI rebuild did the trick for my single malfunctioning machine.Nick.

Hey,I have tried the steps that you said about rebuilding WMI. But I still got the error:RegTask: Client is not registered. Sending registration request... ClientIDManagerStartup 2010/1/7 13:32:25 3344 (0x0D10)RegTask: Failed to send registration request message. Error: 0x80040231 ClientIDManagerStartup 2010/1/7 13:33:26 3344 (0x0D10)RegTask: Failed to send registration request. Error: 0x80040231 ClientIDManagerStartup 2010/1/7 13:33:26 3344 (0x0D10)Error initializing client registration (0x80040222). ClientIDManagerStartup 2010/1/7 14:41:37 3344 (0x0D10)This issue troubled me for a long time. Could you please help to fix it? Thanks anyway.Jack Zhou

Did you happen to find a solution to this issue? I'm having the same problem on over 1,000 systems, it must be a misconfiguration on some level. Thank you.

This is most likely WebDAV configuration issues... According to the error below I assume that you are using Server 2003, HTTP ERROR: URL=http://w2k3xpedev.SCCMDomain.local/ccm_system/request, Port=80, Protocol=http, SSLOptions=0, Code=12007, Text=ERROR_WINHTTP_NAME_NOT_RESOLVED Have you allowed WebDAV in IIS under Web Service Extensions? I just noticed that this thread is from 2008!!! moeflam, can you please specify the OS that you use and add some log files with the error you get. Thanks, Asher

hi, having the same problem i also browse the IIS Logs and it gives this error W3SVC1 IP Address CCM_POST /ccm_system/request - 80 - IP Adress ccmhttp 500 0 0

Asher is on the money, check out: http://msdn.microsoft.com/en-us/library/cc431377.aspx (for Server 2008 SCCM O.S.) In my case I also had to open firewall ports, then I re-started the client and it showed in the All Systems collection.

I had the same problem before... double check the webdave setting ,it should work fine