CCM 2007 clients are installing, but can not register with site or MP
Ok... I am about ready to pull what little hair I have left out... I have seen TONS of good responses from Wally, so if you are reading this, I think this will be right up your alley... We have a SIMPLE setup... One Config Manager 2007 SP1 R2 site, on one server, local SQL 2005 sp2, etc. We have ONE AD forest, schema extended. We have roughly 500 clients, a mix of XP and Vista. Some clients (69 to be exact) installed and registered without a hitch, and the rest are installed (I can go to the machine and see the config manager client in control panel, settings are right, etc) but they can not check in and register. What is happening is the ones that cant register are getting the following errors repeatedly in their logs: From the ClientIDManagerStartup.log of an affected client: <![LOG[RegTask: Client is not registered. Sending registration request...]LOG]!><time="08:21:35.360+420" date="09-24-2008" component="ClientIDManagerStartup" context="" type="1" thread="2420" file="regtask.cpp:1434"> <![LOG[RegTask: Failed to send registration request message. Error: 0x80040231]LOG]!><time="08:21:35.422+420" date="09-24-2008" component="ClientIDManagerStartup" context="" type="3" thread="2420" file="regtask.cpp:1139"> <![LOG[RegTask: Failed to send registration request. Error: 0x80040231]LOG]!><time="08:21:35.422+420" date="09-24-2008" component="ClientIDManagerStartup" context="" type="3" thread="2420" file="regtask.cpp:1314"> From the CCMExec.log of the same machine: <![LOG[[CCMHTTP] HTTP ERROR: URL=http://configmanager1.cd.local/ccm_system_windowsauth/request, Port=80, Protocol=http, SSLOptions=0, Code=0, Text=CCM_E_BAD_HTTP_STATUS_CODE]LOG]!><time="08:21:35.391+420" date="09-24-2008" component="CCMEXEC" context="" type="1" thread="2420" file="ccmhttperror.cpp:264"> <![LOG[Raising event: instance of CCM_CcmHttp_Status { DateTime = "20080924152135.406000+000"; HostName = "configmanager1.cd.local"; HRESULT = "0x8004027e"; ProcessID = 4044; StatusCode = 400; ThreadID = 2420; }; ]LOG]!><time="08:21:35.406+420" date="09-24-2008" component="CCMEXEC" context="" type="1" thread="2420" file="event.cpp:525"> <![LOG[HandleRemoteSyncSend failed (0x80040231).]LOG]!><time="08:21:35.422+420" date="09-24-2008" component="CCMEXEC" context="" type="3" thread="2420" file="forwarder_client.cpp:1308"> <![LOG[CForwarder_Sync:end failed (0x80040231).]LOG]!><time="08:21:35.422+420" date="09-24-2008" component="CCMEXEC" context="" type="3" thread="2420" file="forwarder_client.cpp:1380"> <![LOG[CForwarder_Base:end failed (0x80040231).]LOG]!><time="08:21:35.422+420" date="09-24-2008" component="CCMEXEC" context="" type="3" thread="2420" file="forwarder_base.cpp:393"> From looking at the locationservices.log I can see that the client is finding the correct domain, name and site information (configmanager1.cd.local is the FQDN of the config manager machine, cd.local is hte domain, etc). Here is where things get weird. If I go to the machine that I pulled these error logs from, and manually browse to the CCM_SYS_WINDOWSAUTH site, it prompts for credentials, just like it does on machines that are registered. So... I am totally lost, and have exhausted about a solid work week trying to fix this... Please, I beg of you... help... Gabriel Hayes
September 25th, 2008 2:21am

It could be a number of things. Check to see if you can ping the MP from the client: Checking for DNS issues. I assume this is Mixed mode server install. It is odd since you have others that are working. Are the ones that aren't in a certain department, certain subnet, certain configuration? Any commonalities?
Free Windows Admin Tool Kit Click here and download it now
September 25th, 2008 4:16am

Sorry, I should have included more... The clients CAN see the MP (for instance - http://configmanager1/sms_mp/.sms_aut?mplistshows the XML that lists the MP) and I have tried with DNS turned on and off (per the instructions I found, DNS is ONLY needed if you don't/cant extend the schema). It IS a mixed mode install (because our PKI infrastructure is not complete yet) There is no commonality that I can see between any of the issues. the clients that DONT work are in the same AD sites as those that DO work, they are the same mix of OS type (Some XP and Vista works, some XP and vista dont), similar subnets between those that do and those that dont, configuration is the "same" between those that do and dont work... Like I said, it is so totally baffling to me... I KNOW there is something I am missing, but I cant figue out what... :^( Oh, and to expand a little more, the clients that DO work, work well... I can deploy office packages, do hardware inventories, etc. Every function that we use works on those where the client works... Thanks...
September 25th, 2008 4:22am

A little more info... when browsing to the URL I listed above, here is the output: - <MPList> - <MP Name="CONFIGMANAGER1" FQDN="configmanager1.cd.local"> <Version>6221</Version> - <Capabilities SchemaVersion="1.0"> <Property Name="WOL" Version="1" /> </Capabilities> </MP> </MPList>
Free Windows Admin Tool Kit Click here and download it now
September 25th, 2008 4:30am

Some more info... The clients that are installed only have these two actions available in the config manager control panel applet: User policy Retrieval and Evaluation Cycle & Machine Policy Retrieval and Evaluation Cycle Other than that everything looks correct compared to other workign clients... So, are they not retrieveing their policies? If so, how do I figure out why they are not?
September 25th, 2008 6:50pm

Nope, they are not retrieving policy. Usualy because they can't find the site or the mp. So let's first figure out which of both it is. On the advanced tab of a non-working client check the sitecode it is assigned to.
Free Windows Admin Tool Kit Click here and download it now
September 26th, 2008 11:16pm

The error posted (0x8004027e) returns "The device will not start without a reboot". I'd try that.
September 27th, 2008 12:00am

Site code for non working client (and I assume you mean one where the client is installed, but not "checking in") is correct - CU1. The same as the clietns that are working. The MP it finds is correct to (configmanager1). The only difference that I can see in the configmanager client on the ones that are working versus not working is the actions tab only has the two policy retrieval actions, where as the working ones have the inventory, etc etc actions.
Free Windows Admin Tool Kit Click here and download it now
September 27th, 2008 12:09am

I believe that I have tried rebooting, but I will try again... more in 15 minutes... THANKS!
September 27th, 2008 12:10am

That would be because they said they couldn't register, and without being registered, they can't access the default MP in the site, and thus can't download policies. It all starts with being assigned to a site, then finding the default MP for the site, and finally registering with the site.
Free Windows Admin Tool Kit Click here and download it now
September 27th, 2008 12:15am

:^( After rebooting, I get the following in the ccmexec.log in the client: <![LOG[[CCMHTTP] HTTP ERROR: URL=http://configmanager1.cd.local/ccm_system_windowsauth/request, Port=80, Protocol=http, SSLOptions=0, Code=0, Text=CCM_E_BAD_HTTP_STATUS_CODE]LOG]!><time="14:44:39.953+420" date="09-26-2008" component="CCMEXEC" context="" type="1" thread="3116" file="ccmhttperror.cpp:264"><![LOG[Raising event: instance of CCM_CcmHttp_Status{DateTime = "20080926214439.984000+000";HostName = "configmanager1.cd.local";HRESULT = "0x8004027e";ProcessID = 1384;StatusCode = 400;ThreadID = 3116;};]LOG]!><time="14:44:39.984+420" date="09-26-2008" component="CCMEXEC" context="" type="1" thread="3116" file="event.cpp:525"><![LOG[HandleRemoteSyncSend failed (0x80040231).]LOG]!><time="14:44:40.000+420" date="09-26-2008" component="CCMEXEC" context="" type="3" thread="3116" file="forwarder_client.cpp:1308"><![LOG[CForwarder_Sync:end failed (0x80040231).]LOG]!><time="14:44:40.000+420" date="09-26-2008" component="CCMEXEC" context="" type="3" thread="3116" file="forwarder_client.cpp:1380"><![LOG[CForwarder_Base:end failed (0x80040231).]LOG]!><time="14:44:40.000+420" date="09-26-2008" component="CCMEXEC" context="" type="3" thread="3116" file="forwarder_base.cpp:393"> Any other suggestions?
September 27th, 2008 12:47am

That indicates that this computer can't authenticate with the ccm_system_windowsauth virtual directory. If some can and others can't, it must be some communications issue with this one system (or set of systems). You could check the virtual directory in IIS to see if the permissions have been changed. I recall one user had someone from their security team go in and change some permissions on the MP. When reset back, all worked again.
Free Windows Admin Tool Kit Click here and download it now
September 27th, 2008 12:56am

the settings have not been changed since install (i am the only one working on this)... can you tell me what they SHOULD be set to so I know what ot compare to?
September 27th, 2008 12:59am

What I see on mine for CCM_System_WindowsAuth is: * No anonmymous access * IUSR_SMSServer (my MP server account) * Integrated Windows Authentication enabled That's all I can offer, if that doesn't help, I'd open a case with product support. If you do, please do report the answer here for future reference.
Free Windows Admin Tool Kit Click here and download it now
September 27th, 2008 1:16am

Ok, partly because I am stubborn, but also because I want to understand what is going on, I removed and then reinstalled the MP role on my server.... I THINK that this made things better.. Before doing this, I only saw about 70 or so clients as "yes" out of about 550... not I have only about 150 that are "no"... But, I am still seeing some werid issues. Here is part of the ClientIDManagerStartup log from a client that is still marked "no" even though it is installed: <![LOG[RegTask - Executing registration task synchronously.]LOG]!><time="09:14:54.943+420" date="09-29-2008" component="ClientIDManagerStartup" context="" type="1" thread="240" file="regtask.cpp:779"><![LOG[Read SMBIOS (encoded): 3900530046003000390035003100]LOG]!><time="09:14:55.006+420" date="09-29-2008" component="ClientIDManagerStartup" context="" type="1" thread="240" file="smbiosident.cpp:118"><![LOG[Evaluated SMBIOS (encoded): 3900530046003000390035003100]LOG]!><time="09:14:55.022+420" date="09-29-2008" component="ClientIDManagerStartup" context="" type="1" thread="240" file="smbiosident.cpp:185"><![LOG[No SMBIOS Changed]LOG]!><time="09:14:55.022+420" date="09-29-2008" component="ClientIDManagerStartup" context="" type="1" thread="240" file="smbiosident.cpp:65"><![LOG[SMBIOS unchanged]LOG]!><time="09:14:55.022+420" date="09-29-2008" component="ClientIDManagerStartup" context="" type="1" thread="240" file="ccmid.cpp:919"><![LOG[SID unchanged]LOG]!><time="09:14:55.022+420" date="09-29-2008" component="ClientIDManagerStartup" context="" type="1" thread="240" file="ccmid.cpp:936"><![LOG[HWID unchanged]LOG]!><time="09:14:55.115+420" date="09-29-2008" component="ClientIDManagerStartup" context="" type="1" thread="240" file="ccmid.cpp:952"><![LOG[RegTask: Initial backoff interval: 1 minutes]LOG]!><time="09:14:56.116+420" date="09-29-2008" component="ClientIDManagerStartup" context="" type="1" thread="240" file="regtask.cpp:1830"><![LOG[RegTask: Reset backoff interval: 257 minutes]LOG]!><time="09:14:56.116+420" date="09-29-2008" component="ClientIDManagerStartup" context="" type="1" thread="240" file="regtask.cpp:1831"><![LOG[GetSystemEnclosureChassisInfo: IsFixed=TRUE, IsLaptop=FALSE]LOG]!><time="09:14:57.444+420" date="09-29-2008" component="ClientIDManagerStartup" context="" type="1" thread="240" file="ccmid.cpp:434"><![LOG[Computed HardwareID=263B5ED732FE9F2CAE7021236ED9A86EA2DC013CWin32_SystemEnclosure.SerialNumber=9SF0951Win32_SystemEnclosure.SMBIOSAssetTag= Win32_BaseBoard.SerialNumber=..CN7082144I01GH.Win32_BIOS.SerialNumber=9SF0951Win32_NetworkAdapterConfiguration.MACAddress=00:11:11:03:E6:0C]LOG]!><time="09:14:57.491+420" date="09-29-2008" component="ClientIDManagerStartup" context="" type="1" thread="240" file="ccmid.cpp:673"><![LOG[RegTask: Client is not registered. Sending registration request...]LOG]!><time="09:14:57.507+420" date="09-29-2008" component="ClientIDManagerStartup" context="" type="1" thread="240" file="regtask.cpp:1434"><![LOG[RegTask: Failed to send registration request message. Error: 0x80040231]LOG]!><time="09:14:57.569+420" date="09-29-2008" component="ClientIDManagerStartup" context="" type="3" thread="240" file="regtask.cpp:1139"><![LOG[RegTask: Failed to send registration request. Error: 0x80040231]LOG]!><time="09:14:57.569+420" date="09-29-2008" component="ClientIDManagerStartup" context="" type="3" thread="240" file="regtask.cpp:1314"><![LOG[RegTask: Client is not registered. Sending registration request...]LOG]!><time="09:15:57.591+420" date="09-29-2008" component="ClientIDManagerStartup" context="" type="1" thread="240" file="regtask.cpp:1434"><![LOG[RegTask: Failed to send registration request message. Error: 0x80040231]LOG]!><time="09:15:57.654+420" date="09-29-2008" component="ClientIDManagerStartup" context="" type="3" thread="240" file="regtask.cpp:1139"><![LOG[RegTask: Failed to send registration request. Error: 0x80040231]LOG]!><time="09:15:57.654+420" date="09-29-2008" component="ClientIDManagerStartup" context="" type="3" thread="240" file="regtask.cpp:1314"> Does anyone know what the error 0x80040231 is?
September 29th, 2008 7:19pm

A little more info... because it seems that everyone has pointed to the MP being the issue, I checked something I had not looked at before (shame on me)... I looked in the system status, and saw this under the sms_mp_control_manager logs... There is ONE of these in the logs after I reinstalled the MP... does this mean anything? MP Control Manager detected MP is not responding to HTTP requests. The http error is 12002. Possible cause: MP service is not started or not responding. Solution: Manually restart the SMS Agent Host service on the MP. Possible cause: IIS service is not responding. Solution: Manually restart the W3SVC service on the MP. For more information, refer to Microsoft Knowledge Base article 838891. KB article 838891 is pretty useless (basically says if there is a problem look at the planning documentation)... I cant see how it could be IIS or SMS not working, as the other clients are checking in... but, if I knew the answer, I wouldnt be asking you guys, huh... Thanks!
Free Windows Admin Tool Kit Click here and download it now
September 29th, 2008 7:27pm

According to Custom Error Codes for Configuration Manager 2007, 0x80040231 is Transient error that could indicate a network problem. Not sure if that helps or not! - Carol This posting is provided AS IS with no warranties and confers no rights.
September 30th, 2008 7:22am

One other source I found for that error was "no directories found", which would indicate again the virtual directory issue we discussed a while ago.
Free Windows Admin Tool Kit Click here and download it now
October 3rd, 2008 9:22pm

Well - Her eis the latest update... Since my last post, I have done nothing (other than sync the mirror on the OS disks) to the server but wait... clients that were not installing before are installing now... I am totally confused as to why they are installing, but they are... So... Thanks for the help everyone... I think that within one or two more weeks, all the clients will be installed... Now on to start building out my office deployment strategy! THANKS!
October 9th, 2008 12:43am

Still sounds like network issues to me :-)
Free Windows Admin Tool Kit Click here and download it now
October 9th, 2008 1:02am

I have been having the same problem for the last 3 weeks. I have 30 secondary sites and 3 of the sites are having that issue. the client gets installed on the workstations , but when the client tries toregisterback to theMP the following erroroccurs :<![LOG[[CCMHTTP] HTTP ERROR: URL=http://MIA-WAP-P15.WFS.COM/ccm_system_windowsauth/request, Port=80, Protocol=http, SSLOptions=0, Code=0, Text=CCM_E_BAD_HTTP_STATUS_CODE]LOG]!><time="05:59:16.155+000" date="05-29-2009" component="CCMEXEC" context="" type="1" thread="2480" file="ccmhttperror.cpp:264"><![LOG[Raising event:instance of CCM_CcmHttp_Status{DateTime = "20090528215916.155000+000";HostName = "MIA-WAP-P15.WFS.COM";HRESULT = "0x8004027e";ProcessID = 3836;StatusCode = 400;ThreadID = 2480;};]LOG]!><time="05:59:16.155+000" date="05-29-2009" component="CCMEXEC" context="" type="1" thread="2480" file="event.cpp:525"><![LOG[HandleRemoteSyncSend failed (0x80040231).]LOG]!><time="05:59:16.155+000" date="05-29-2009" component="CCMEXEC" context="" type="3" thread="2480" file="forwarder_client.cpp:1308"><![LOG[CForwarder_Sync::Send failed (0x80040231).]LOG]!><time="05:59:16.155+000" date="05-29-2009" component="CCMEXEC" context="" type="3" thread="2480" file="forwarder_client.cpp:1380"><![LOG[CForwarder_Base::Send failed (0x80040231).]LOG]!><time="05:59:16.155+000" date="05-29-2009" component="CCMEXEC" context="" type="3" thread="2480" file="forwarder_base.cpp:393">I called microsoft support and i uploaded all the logs from the primary,secondary servers and multiple workstations .. and gess what? they dont support this kind of infrastructure problems!.. i made a BIG complain and they put packet snnifers in the workstation\secondary and primary servers..the network support team issaying that is caused by KERBEROS authentication .we remove the secondary site and had the clients report directly to the primary server,we registered the SPNs for all the servers, check all IIS settings and it all looks good..but the clients are still not reporting back the the managment point. still waiting for a call back..??????????Does anybody knows how to fix this issue?
May 29th, 2009 1:14am

Why doesn't Microsoft support this problem? Is there something special with your setup? That's a basic mechanism in ConfigMgr and is supported as far as I know. It's true that registering has something to do with Kerberos authentication. It looks as if the problem is caused by "Text=CCM_E_BAD_HTTP_STATUS_CODE" in other words an issue with the MP. Have you already had a look at the IIS logfiles?
Free Windows Admin Tool Kit Click here and download it now
May 29th, 2009 9:40am

Wow, that was amazingly unhelpful...
January 24th, 2011 11:33pm

"How It Works: Automatic Client Approval in Configuration Manager 2007": http://blogs.technet.com/b/configurationmgr/archive/2010/01/20/how-it-works-automatic-client-approval-in-configuration-manager-2007.aspx
Free Windows Admin Tool Kit Click here and download it now
January 25th, 2011 3:17am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics