Here is what the logs say on these machines where the SCCM client will not complete the install. ccmsetup.log: Installation succeeded clientlocation: Assiged to site US3: locationservices.log: LSVerifySiteVersion : Verified Client Version '4.00.6487.2000' is not greater than Site Version '4.00.6487.0000'. Client can be assigned to site <US3>. smscliui.log: wszMonikerName Elevation:Administrator!new:{9967A433-A640-4A56-8C3D-D8E8F95FF8F3}, error: 0x0 cas.log: Software Distribution Site Settings for the client are missing from WMI.: CacheConfig::InitializeFromWmi - GetSWDistSiteSettings failed with 0x80004005. Default site settings will be used In Control Panel I can click the Advanced Tab and pick "Discover" My machine finds the US3 site and says it was successful. Yet the client is broken and not working. Under the Actions Tab all I see are "machine policy retrieval & evaluation cycle" & "user policy retrieval & evaluation cycle" Our boundaries are based on AD Site Name. I confirmed with our AD dudes that the IP address range for this office is correct. The gateway and subnet mask are all correct. We have about 4,000 other machines off of site US3 and they are all fine, up and running. it is just this 1 office that all machines are Non-clients and we can't deploy anything to them. I've Googled the cas.log error but have not found a fix yet. Any hints would be great. mqh7

How were the client agents on these systems deployed? Are the clients stuck in provisioning mode: http://blogs.technet.com/b/configurationmgr/archive/2010/09/13/solution-after-a-configmgr-2007-osd-task-sequence-completes-the-client-may-not-automatically-pull-down-policy.aspx ? Have you checked ClientIDManagerStartup.log on one of these clients?Jason | http://blog.configmgrftw.com | Twitter @JasonSandys

More on this. On one of the failed machines I uninstalled the client and then rebooted. I tried to reinstall the client and I kept getting an error in the ccmsetup.log that it could not access the source location. I granted Domain Computers read access and it still did not work. So I took all the source (the Client folder) and created a new share on the same server. I then pointed to that share and from a CMD windows ran the ccmsetup.exe and this looked good. The ccmsetup.log file started showing a healthy install. In showed the downloaded steps and then it said installation completed successfully. but, when I look at the config manager icon in control panel it still only shows the "machine policy retrieval & evaluation cycle" & "user policy retrieval & evaluation cycle" and nothing else. After the partial install the logs have this: no errors and it does show the correct MP server name. clientinstall.log clientIDmanager.log RegTask: Failed to send registration request message. Error: 0x80040231 policyevaluator.log Failed to trigger Machine settings update (80070057) ccmexec.log HandleRemoteSyncSend failed (0x80040231). CCMEXEC 5/9/2012 1:34:46 PM 1400 (0x0578) CForwarder_Sync::Send failed (0x80040231). CCMEXEC 5/9/2012 1:34:46 PM 1400 (0x0578) CForwarder_Base::Send failed (0x80040231). CCMEXEC 5/9/2012 1:34:46 PM 1400 (0x0578) I checked and our MP does have the correct TrustedRootKey reg setting. So we're not sure what causes this. And it only happens in 1 office. The rest of the machines off this MP work fine. mqh7

good article, thanks. I did what it said since I did have the wrong data in those reg keys. I re-ran the ccmsetup.exe and I now have all of my sccm log files. I even see the Internet Tab on the ConfigMgr icon in control panel. But I still only see the same 2 things on the Action Tab. All the logs look fine except for exemgr. It has this: Common Client Agent Settings for the client are missing from WMI. how do you fix that to complete your client install? mqh7

That indicates that the client was not able to retrieve policies yet. Check clientidmanagerstartup.log, locationservices.log, clientlocation.log and ccmexec.log (given that the MP is working fine)Torsten Meringer | http://www.mssccmfaq.de

I don't know all of the reasons why clients get stuck in provisioning mode. IME, it happens when deploying systems using OSD and you are installing the Cisco VPN client. I think there's a fix for this very specific cause of the issue, but I don't rememeber what it is (sorry).Jason | http://blog.configmgrftw.com | Twitter @JasonSandys

I have done the following. Deleted the cert from the local machine deleted the SCCM client deleted the CCM and CCMSETUP folders reboot then I ran this: net stop winmgmt /y %SYSTEMDRIVE% CD %windir%\system32\wbem rd /S /Q repository net start winmgmt for /f %%s in ('dir /b /s *.dll') do regsvr32 /s %%s for /f %%s in ('dir /b *.mof') do mofcomp %%s reboot again Then I deleted the machines from the SCCM DB. then I logged into the machine, and ran the ccmsetup.exe SMSSITECODE=US3 the client does a partial install. the ccmexec.log has this over and over [CCMHTTP] HTTP ERROR: URL=http://sccmserver/ccm_system_windowsauth/request, Port=80, Protocol=http, SSLOptions=0, Code=0, Text=CCM_E_BAD_HTTP_STATUS_CODE CCMEXEC 5/10/2012 1:05:22 PM 560 (0x0230) Raising event: instance of CCM_CcmHttp_Status { DateTime = "20120510170522.050000+000"; HostName = "sccmserver"; HRESULT = "0x8004027e"; ProcessID = 4072; StatusCode = 400; ThreadID = 560; }; CCMEXEC 5/10/2012 1:05:22 PM 560 (0x0230) HandleRemoteSyncSend failed (0x80040231). CCMEXEC 5/10/2012 1:05:22 PM 560 (0x0230) CForwarder_Sync::Send failed (0x80040231). CCMEXEC 5/10/2012 1:05:22 PM 560 (0x0230) CForwarder_Base::Send failed (0x80040231). CCMEXEC 5/10/2012 1:05:22 PM 560 (0x0230) I've repeated this several times and no matter what the client does not fully install. I don't know what else to try.mqh7

Hi, Looking through the thread I can see that you have 4000 machines where the client is working. It also appears that you are using Native Mode. The machines having the issue are not talking to the Management Point. That CAS log error is nothing to worry about because it will remain until the client gets it's configuration information from the MP. That always happens before the initial MP interaction is complete, even on a "good" client. In that 1 location where things are not working you might troubleshoot by having someone from the network group (if that isn't you wearing a different hat :-) ) help with tracing the traffic and look for where things are going awry. I've seen those 0x80040231 errors at a location that would not work even when many other locations did. I would suspect that something is not communicating. Are you using CRL for your certs? If so, can the machines in the problematic location access the CRLDP? Even if the cert is fine and working for everyone else, if the machines in the 1 office can't access the CRLDP the certs will not work for them and you'll end up with a situation where they can't get policy. This might be something to look at. You should be able to test by manually accessing the CRLDP from IE on one of the affected machines. I hope something here is helpful.John DeVito