I have 4 sites - One Primary and the rest Secondary\Child sites. SCCM clients have been pushed to all the sites and have got installed properly without any 'Major' :-) issues. The problem now is; in one of the Sites' clients, the 'Components' tab in the installed client just shows all of the components installed. It doesn't show 'enabled' for some of the components like Software Updates etc. As a result of this only the Machine and User Policy are visible in the 'Actions' tab. This has resulted in the client not looking for\installing the Software updates or New Advertisements, though it has been pushed from the Primary site. I strongly would assume that this is a Site configuration issue. But I checked all the configuration options for all the sites bit-by-bit, option-by-option and found no differences or changes in the same. I did notice the 'Client Agents' not available on all the Secondary Sites as that would be transcended from the Primary Site.

You kind off reversed result and cause here. You only have 2 actions, which means the clients can't find/contact their management point. Hence they can't receive policy to enable the components. Check whether these clients received the correct sitecode. Seems like an assignment issue to me if all clients in the site have this problem Kim

Sounds like a site configuration issue. Clients apperantly are not getting policy. Please refer to the troubleshooting Client issuestopics for starters. http://technet.microsoft.com/en-us/library/bb693982.aspx As for your second observation, starting with ConfigMgr 2007 RTM, clientscan no longer beassigned to Secondary Sites so there are no Client Agents available.

Hi Kim, All the assigned clients have their corresponding MP's configured and is pointing to the correct one. The site code also looks good. Upon manually initiating 'Discover' for the Configuration Manager Site from the client-end; site code comes up fine. Furthermore, all parameters in the General tab for the clients in all the sites are same. The ccmsetup log also comes up clean with no issues after comparison. Clientlocation logs also seems to be fine. Still the issue persists. Saj

Hi Jeff - Still looking for clues from the link. Issue seems to be a bit strange. I really don't want to delete\repair the whole site. Trying to work the way around. I see the whole difference in the Client assignment method in 2007 as opposed to 2003\2.0. A bit confusing at first; but Ok now. Saj

what you're ccm client componenet dcm confifiguration management state [Enable/Disable/Installed]? whats you're dcm.log says? sanka

DCM State; along with all the other components, currently shows in the client component tab as 'Installed'. It should be enabled I guess as all the other sites' clients have it enabled. I couldn't find DCM.log on either the client or on the site Server. Saj

Do a repair for the component and discover the site code and do a machine policy retrival.then check the DCM.log in the client ccm\logs folder sanka

I had done all of those earlier with no joy. There is no DCM.log in the client logs. DCMAgent.log is available. Also I do see a missing line entry for one of the tasks in the said clients' DCMAgent.log. "CDCMSDK::GetAssignedBaselines" - This entry is available on all the clients in the other sites; but not in any of the clients in the issue site. Also as I had mentioned earlier; this really seems to be a Site issue rather than a single client issue as the whole sites' clients are affected. Saj

is you're CAS.log says like this. "GetLogonUserSid failed at GetTokenSids 0x800704dd"if it dispalys like this try to repair the CCM POLICY AGENT sanka

CAS Log says - "CacheConfig::InitializeFromWmi - GetSWDistSiteSettings failed with 0x80004005. Default site settings will be used Software Distribution Site Settings for the client are missing from WMI." Saj

Seems like client is cannot to find the management point.whats you're clientlocation.log says?repair the CCM framework,CCM policy,& software distribution agent too.by doing these kindsrepair we have to identify.i know that you have done lots of repairs still no joy. sanka

It can actually locate the MP. Location logs also are fine. Please view the reply that I had posted to Kim. Cheers...! Saj ClientLocation.log - "Current Management Point is %SiteServer Name% with version 5931 and capabilities: <Capabilities SchemaVersion="1.0"></Capabilities>."

This is turning out be as a challenge to me now. Did you guys find anything? Cheers... Saj

I am getting the "GetLogonUserSid failed at GetTokenSids 0x800704dd" error in my log. The sms server reports that these clients no longer have the advanced client installed - any help? Thanks!

Saj shall we try the client installation manually,if you are ok? sanka

Hey Sanka - I did try that too in one of the PC's... Still the same result.. And as I reiterate again; this is not just one or two clients, but a whole site... We are talking numbers in hundreds.... Saj

Guys, no clues still??? Site is now in production mode...

are you pretty sure that ccmsetup folder has copied sucessfully?check the logs inside in it sanka

Yup, ccmsetup folder is in there... I have compared logs from machines in the other sites... They all look Ok... Do you recommend any particular log to check??? Saj

yer ccmsetup.log.what it says? sanka

Saj [DP] wrote: And as I reiterate again; this is not just one or two clients, but a whole site... We are talking numbers in hundreds.... Are you sure that this client agent(DCM) is enabled for this particular site? Please double check the site settings (Site management -> Sitecode -> Site settings -> Client Agents -> Desired configuration management client agent). This would only apply if you have more than one primary site.

Hi Sanka - ccmsetup.log shows a successful installation with all the parameters looking good. No errors have been located. The machine could locate the MP and also send the status message to the FSP. Looks like all client installations are fine in the Site. Definitely not a client-based issue. Rgds, Saj

Hi Torsten - DCM is enabled in the Primary Site. There is no 'Client Agents' configurable option in any of the Child\Secondary sites under the Site Management. This was a query that was actually raised during the early stages of this thread and I understand that starting with SCCM2007; the said feature will be transcended down from the Primary site. Cheers...! Saj

whats u're CAS log says.paste here the content. sanka

saj we cant see client agents in the secondary site console,all the setting have to configure on the primary site,did you create the proxy management points,FSP for secondary sites?can you find out from a client which has installed DCM log file. sanka

Hi Sanka - I had earlier posted the log on the CAS.log for your same query. Reposting it again - CAS Log in the client says - "CacheConfig::InitializeFromWmi - GetSWDistSiteSettings failed with 0x80004005. Default site settings will be used Software Distribution Site Settings for the client are missing from WMI." Also DCMAgent.log was listed earlier and commented on a missing entry. Reproducing the earlier post again [for the benefit of staying in the same page and not to scroll back ] Saj [DP] wrote: I had done all of those earlier with no joy. There is no DCM.log in the client logs. DCMAgent.log is available. Also I do see a missing line entry for one of the tasks in the said clients' DCMAgent.log. "CDCMSDK::GetAssignedBaselines" - This entry is available on all the clients in the other sites; but not in any of the clients in the issue site. Also as I had mentioned earlier; this really seems to be a Site issue rather than a single client issue as the whole sites' clients are affected. Saj Cheers again mates... Saj PS. FSP's are also configured on all Child\Secondary sites...

Saj [DP] wrote: "CacheConfig::InitializeFromWmi - GetSWDistSiteSettings failed with 0x80004005. Default site settings will be used Software Distribution Site Settings for the client are missing from WMI." That means that your client was not able to get policies from the management point. Any errors in ccmexec.log, clientlocation.log and locationservices.log on the client? Is the proxy MP at the secondary site working? But Kim and Jeff already mentioned that in theiranswers!

check are there any errors for proxy management point.i know you have done this before.try to enable software distribution component under component.and do repair.then check execmgr.log sanka

Yup, that's logically rightly said Tortsen. But unfortunately all the logs look fine; as I had earlier replied to Kim's & Jeffs' queries, and the Site MP & FSP looks good too. Please find excerpts from the client logs below - ClientLocation.log - "Current Management Point is %SiteServer Name% with version 5931 and capabilities: <Capabilities SchemaVersion="1.0"></Capabilities>." LocationServices.log - "Attempting to retrieve default management point from ADLocationServices7/28/2008 11:23:18 AM2440 (0x0988)Retrieved Default Management Point from AD: %FQDN ServerName% LocationServices7/28/2008 11:23:18 AM2440 (0x0988)Persisting the default management point in WMILocationServices7/28/2008 11:23:18 AM2440 (0x0988)Persisted Default Management Point Location locallyLocationServices7/28/2008 11:23:18 AM2440 (0x0988)Unknown task LSProxyMPModificationTask in non-quarantine - ignoring.LocationServices7/28/2008 11:23:18 AM2944 (0x0B80) Attempting to retrieve proxy MP from ADLocationServices7/28/2008 11:23:18 AM2440 (0x0988)Current AD site of machine is%SiteName% LocationServices7/28/2008 11:23:18 AM2440 (0x0988) Retrieved Proxy Management Point from AD: %FQDN ServerName%" Regards, Saj

Guys - After a very long fight, endless hours on tech. docs & following multiple leads on suspicions raised on many of the points mentioned in the thread for the services\tasks running - we were able to resolve this issue. It was a small change that made a huge difference. Phew...! I deleted the Host (A) record of the said Site Server's address and re-created it again. Voila...! All clients in the said SCCM site started getting the policies and commenced installing the application packages. I was also surprised after getting this issue resolved. Site MP was working, FSP was getting the status messages from clients, clients were able to contact the MP and send status messages to the FSP, no visible error on connectivity issues, logs displaying healthy status on all the ones that we have checked (except the policy errors), site parameters were fine, no SCCM configuration change was done on either the Primary or Secondary site - but one suspicion remained which we all have failed to address - IIS services on the Site Server and the FQDN for contacting the same. I could understand that this was critical in getting the policies across to all the clients, provided the connection target protocol used is http. Any failure to contact the IIS\http services on the Site Server will render failure on the clients to receive the policy status, policy messages, application package messages etc; though the client has, and is still able to contact the Site MP by IP using the installation configuration details. Well, that's what I feel might have caused the issue and the logic behind the resolution, though this is open for debate on other alternative possibilities too. Anyways, I'll wait for more suggestions on this matter before this thread is closed. Meanwhile; I have another issue which I'll start as a new thread Appreciate all you guys who have put in their comments & suggestions in helping me out to resolve this matter. Your points did definitely make me explore all possible avenues and did throw a good deal of knowledge in how the SCCM works. Cheers...! Saj

Saj [DP] wrote: Ok, I guess that's it on this one. Closing this thread now... Cheers...! Sajith

Hi Saj- I am facing similar kind of issue as you faced. I have1 Primarysites. SCCM clients have been pushed to all the sites and have got installed with some issues. The problem now is; in one of the Sites' clients, the 'Components' tab in the installed client just shows all of the components installed. It doesn't show 'enabled' for all of the components like Software Updates etc. As a result of this only the Machine and User Policy are visible in the 'Actions' tab. This has resulted in the client not looking for\installing the Software updates or New Advertisements, though it has been pushed from the Primary site. My LocationServices.log says: <![LOG[Retrieved Default Management Point from AD: sccmserver.corp.plex.com]LOG]!><time="09:46:24.069+420" date="09-03-2009" component="LocationServices" context="" type="1" thread="3912" file="lsad.cpp:2543"><![LOG[Persisting the default management point in WMI]LOG]!><time="09:46:24.069+420" date="09-03-2009" component="LocationServices" context="" type="1" thread="3912" file="lsad.cpp:3850"><![LOG[Failed to reset certificate request times. (0x80041002)]LOG]!><time="09:46:24.147+420" date="09-03-2009" component="LocationServices" context="" type="3" thread="3912" file="lssecurity.cpp:4231"><![LOG[Current AD site of machine is Default-First-Site-Name]LOG]!><time="09:46:24.225+420" date="09-03-2009" component="LocationServices" context="" type="1" thread="3912" file="lsad.cpp:457"><![LOG[Retrieved local Management Point from AD: sccmserver.corp.plex.com]LOG]!><time="09:46:24.225+420" date="09-03-2009" component="LocationServices" context="" type="1" thread="3912" file="lsad.cpp:3790"><![LOG[The 'Certificate Store' is empty in the registry, using default store name 'MY'.]LOG]!><time="09:46:24.256+420" date="09-03-2009" component="LocationServices" context="" type="1" thread="3912" file="ccmcert.cpp:204"><![LOG[Refreshed security settings over AD]LOG]!><time="09:46:24.412+420" date="09-03-2009" component="LocationServices" context="" type="1" thread="3912" file="lsad.cpp:4797"><![LOG[No security settings update detected.]LOG]!><time="09:46:24.412+420" date="09-03-2009" component="LocationServices" context="" type="1" thread="3912" file="lssecurity.cpp:4350"><![LOG[Unknown task LSProxyMPModificationTask in non-quarantine - ignoring.]LOG]!><time="09:46:24.412+420" date="09-03-2009" component="LocationServices" context="" type="2" thread="3204" file="scheduledcleanupendpoint.cpp:404"><![LOG[Attempting to retrieve default management point from AD]LOG]!><time="10:25:20.929+420" date="09-03-2009" component="LocationServices" context="" type="1" thread="368" file="lsad.cpp:2537"><![LOG[Retrieved Default Management Point from AD: sccmserver.corp.plex.com]LOG]!><time="10:25:21.694+420" date="09-03-2009" component="LocationServices" context="" type="1" thread="368" file="lsad.cpp:2543"><![LOG[Persisting the default management point in WMI]LOG]!><time="10:25:21.694+420" date="09-03-2009" component="LocationServices" context="" type="1" thread="368" file="lsad.cpp:3850"><![LOG[Persisted Default Management Point Location locally]LOG]!><time="10:25:21.710+420" date="09-03-2009" component="LocationServices" context="" type="1" thread="368" file="lsad.cpp:3863"><![LOG[Attempting to retrieve local MP from AD]LOG]!><time="10:25:21.757+420" date="09-03-2009" component="LocationServices" context="" type="1" thread="368" file="lsad.cpp:3778"><![LOG[Retrieved local Management Point from AD: sccmserver.corp.plex.com]LOG]!><time="10:25:21.866+420" date="09-03-2009" component="LocationServices" context="" type="1" thread="368" file="lsad.cpp:3790"><![LOG[The 'Certificate Store' is empty in the registry, using default store name 'MY'.]LOG]!><time="10:25:22.053+420" date="09-03-2009" component="LocationServices" context="" type="1" thread="368" file="ccmcert.cpp:204"><![LOG[Retrieved SLP [SCCMSERVER] from Registry]LOG]!><time="10:41:44.059+420" date="09-03-2009" component="LocationServices" context="" type="1" thread="2848" file="lsad.cpp:2255"><![LOG[Attempting to retrieve SLPs from AD]LOG]!><time="10:41:44.059+420" date="09-03-2009" component="LocationServices" context="" type="1" thread="2848" file="lsad.cpp:2261">SMSCliui.log says:![LOG[Site is in mixed mode. Internet tab will not be displayed.]LOG]!><time="09:56:12.746+420" date="09-03-2009" component="smscliui" context="" type="1" thread="3388" file="clicfgdlg.cpp:5848"><![LOG[Current Assigned Site: ABC]LOG]!><time="09:56:23.697+420" date="09-03-2009" component="smscliui" context="" type="1" thread="3388" file="clicfgdlg.cpp:1477"><![LOG[Perform Action: Request & Evaluate Machine Policy - {8EF4D77C-8A23-45c8-BEC3-630827704F51}. Message sent, id={5A81B31E-045E-42FB-AE46-894DCEC7CFD8}]LOG]!><time="09:56:31.425+420" date="09-03-2009" component="smscliui" context="" type="1" thread="3740" file="ccmclientaction.cpp:164"><![LOG[SMS Site code has not been changed.]LOG]!><time="09:56:35.883+420" date="09-03-2009" component="smscliui" context="" type="1" thread="3388" file="clicfgdlg.cpp:2042"><![LOG[The schedule remains disabled]LOG]!><time="09:56:35.883+420" date="09-03-2009" component="smscliui" context="" type="1" thread="3388" file="clicfgdlg.cpp:5559"><![LOG[CCliCfgDcmPage::FreeCallback - Detection Job is null.]LOG]!><time="09:56:35.883+420" date="09-03-2009" component="smscliui" context="" type="1" thread="3388" file="clicfgdlg.cpp:3792"><![LOG[Common Client Agent Settings for the client are missing from WMI.]LOG]!><time="09:56:38.824+420" date="09-03-2009" component="smscliui" context="" type="3" thread="3076" file="softdistpolicy.cpp:1400"><![LOG[Software Distribution Site Settings for the client are missing from WMI.]LOG]!><time="09:56:38.824+420" date="09-03-2009" component="smscliui" context="" type="3" thread="3076" file="softdistpolicy.cpp:1299"><![LOG[Failed to open to WMI namespace '\\.\root\ccm\Policy' (80041003)]LOG]!><time="09:56:43.846+420" date="09-03-2009" component="smscliui" context="" type="3" thread="3076" file="wminamespace.cpp:231"><![LOG[Could not connect to \\.\root\ccm\Policy]LOG]!><time="09:56:43.862+420" date="09-03-2009" component="smscliui" context="" type="3" thread="3076" file="policyagent.cpp:157"><![LOG[Failed to ConnectSettings for ICcmPolicyAgent in CSoftwareDistPolicyMgr::GetUserPolicyNamespace]LOG]!><time="09:56:43.862+420" date="09-03-2009" component="smscliui" context="" type="3" thread="3076" file="softdistpolicy.cpp:3016"><![LOG[Failed to connect to user policy name space]LOG]!><time="09:56:43.862+420" date="09-03-2009" component="smscliui" context="" type="2" thread="3076" file="softdistpolicy.cpp:2345"><![LOG[Failed to open to WMI namespace '\\.\root\ccm\Policy' (80041003)]LOG]!><time="09:56:48.884+420" date="09-03-2009" component="smscliui" context="" type="3" thread="3076" file="wminamespace.cpp:231"><![LOG[Could not connect to \\.\root\ccm\Policy]LOG]!><time="09:56:48.884+420" date="09-03-2009" component="smscliui" context="" type="3" thread="3076" file="policyagent.cpp:157"><![LOG[Failed to ConnectSettings for ICcmPolicyAgent in CSoftwareDistPolicyMgr::GetUserPolicyNamespace]LOG]!><time="09:56:48.884+420" date="09-03-2009" component="smscliui" context="" type="3" thread="3076" file="softdistpolicy.cpp:3016"><![LOG[Failed to connect to user policy name space]LOG]!><time="09:56:48.884+420" date="09-03-2009" component="smscliui" context="" type="2" thread="3076" file="softdistpolicy.cpp:2345"><![LOG[Software Distribution Site Settings for the client are missing from WMI.]LOG]!><time="09:56:48.899+420" date="09-03-2009" component="smscliui" context="" type="3" thread="3076" file="softdistpolicy.cpp:1299"><![LOG[Advertising 0 scripts in RAP]LOG]!><time="09:56:48.899+420" date="09-03-2009" component="smscliui" context="" type="1" thread="3076" file="rapprograms.cpp:363"><![LOG[Common Client Agent Settings for the client are missing from WMI.]LOG]!><time="09:56:48.915+420" date="09-03-2009" component="smscliui" context="" type="3" thread="3076" file="softdistpolicy.cpp:1400"><![LOG[Common Client Agent Settings for the client are missing from WMI.]LOG]!><time="09:56:57.457+420" date="09-03-2009" component="smscliui" context="" type="3" thread="3076" file="softdistpolicy.cpp:1400"><![LOG[Site is in mixed mode. Internet tab will not be displayed.]LOG]!><time="09:57:09.690+420" date="09-03-2009" component="smscliui" context="" type="1" thread="3700" file="clicfgdlg.cpp:5848"><![LOG[Current Assigned Site: ABC]LOG]!><time="09:57:58.565+420" date="09-03-2009" component="smscliui" context="" type="1" thread="3700" file="clicfgdlg.cpp:1477"><![LOG[SMS Site code has not been changed.]LOG]!><time="09:57:59.863+420" date="09-03-2009" component="smscliui" context="" type="1" thread="3700" file="clicfgdlg.cpp:2042"><![LOG[The schedule remains disabled]LOG]!><time="09:57:59.863+420" date="09-03-2009" component="smscliui" context="" type="1" thread="3700" file="clicfgdlg.cpp:5559"><![LOG[CCliCfgDcmPage::FreeCallback - Detection Job is null.]LOG]!><time="09:57:59.863+420" date="09-03-2009" component="smscliui" context="" type="1" thread="3700" file="clicfgdlg.cpp:3792"><![LOG[Site is in mixed mode. Internet tab will not be displayed.]LOG]!><time="10:08:06.345+420" date="09-03-2009" component="smscliui" context="" type="1" thread="2320" file="clicfgdlg.cpp:5848"><![LOG[Current Assigned Site: ABC]LOG]!><time="10:08:21.334+420" date="09-03-2009" component="smscliui" context="" type="1" thread="2320" file="clicfgdlg.cpp:1477"><![LOG[CCliCfgDcmPage::FreeCallback - Detection Job is null.]LOG]!><time="10:08:24.038+420" date="09-03-2009" component="smscliui" context="" type="1" thread="2320" file="clicfgdlg.cpp:3792"><![LOG[Common Client Agent Settings for the client are missing from WMI.]LOG]!><time="10:20:05.724+420" date="09-03-2009" component="smscliui" context="" type="3" thread="2452" file="softdistpolicy.cpp:1400"><![LOG[Software Distribution Site Settings for the client are missing from WMI.]LOG]!><time="10:20:05.724+420" date="09-03-2009" component="smscliui" context="" type="3" thread="2452" file="softdistpolicy.cpp:1299"><![LOG[Failed to open to WMI namespace '\\.\root\ccm\Policy' (80041003)]LOG]!><time="10:20:10.738+420" date="09-03-2009" component="smscliui" context="" type="3" thread="2452" file="wminamespace.cpp:231"><![LOG[Could not connect to \\.\root\ccm\Policy]LOG]!><time="10:20:10.738+420" date="09-03-2009" component="smscliui" context="" type="3" thread="2452" file="policyagent.cpp:157"><![LOG[Failed to ConnectSettings for ICcmPolicyAgent in CSoftwareDistPolicyMgr::GetUserPolicyNamespace]LOG]!><time="10:20:10.738+420" date="09-03-2009" component="smscliui" context="" type="3" thread="2452" file="softdistpolicy.cpp:3016"><![LOG[Failed to connect to user policy name space]LOG]!><time="10:20:10.738+420" date="09-03-2009" component="smscliui" context="" type="2" thread="2452" file="softdistpolicy.cpp:2345"><![LOG[Failed to open to WMI namespace '\\.\root\ccm\Policy' (80041003)]LOG]!><time="10:20:15.738+420" date="09-03-2009" component="smscliui" context="" type="3" thread="2452" file="wminamespace.cpp:231"><![LOG[Could not connect to \\.\root\ccm\Policy]LOG]!><time="10:20:15.738+420" date="09-03-2009" component="smscliui" context="" type="3" thread="2452" file="policyagent.cpp:157"><![LOG[Failed to ConnectSettings for ICcmPolicyAgent in CSoftwareDistPolicyMgr::GetUserPolicyNamespace]LOG]!><time="10:20:15.738+420" date="09-03-2009" component="smscliui" context="" type="3" thread="2452" file="softdistpolicy.cpp:3016"><![LOG[Failed to connect to user policy name space]LOG]!><time="10:20:15.738+420" date="09-03-2009" component="smscliui" context="" type="2" thread="2452" file="softdistpolicy.cpp:2345"><![LOG[Software Distribution Site Settings for the client are missing from WMI.]LOG]!><time="10:20:15.738+420" date="09-03-2009" component="smscliui" context="" type="3" thread="2452" file="softdistpolicy.cpp:1299"><![LOG[Advertising 0 scripts in RAP]LOG]!><time="10:20:15.738+420" date="09-03-2009" component="smscliui" context="" type="1" thread="2452" file="rapprograms.cpp:363"><![LOG[Common Client Agent Settings for the client are missing from WMI.]LOG]!><time="10:20:15.753+420" date="09-03-2009" component="smscliui" context="" type="3" thread="2452" file="softdistpolicy.cpp:1400"><![LOG[Common Client Agent Settings for the client are missing from WMI.]LOG]!><time="10:20:33.501+420" date="09-03-2009" component="smscliui" context="" type="3" thread="2452" file="softdistpolicy.cpp:1400"><![LOG[Site is in mixed mode. Internet tab will not be displayed.]LOG]!><time="10:20:40.718+420" date="09-03-2009" component="smscliui" context="" type="1" thread="680" file="clicfgdlg.cpp:5848"><![LOG[Perform Action: Request & Evaluate Machine Policy - {8EF4D77C-8A23-45c8-BEC3-630827704F51}. Message sent, id={F7EF9DE3-4730-4C65-8386-1117036B3F62}]LOG]!><time="10:20:43.624+420" date="09-03-2009" component="smscliui" context="" type="1" thread="2216" file="ccmclientaction.cpp:164"><![LOG[Current Assigned Site: ABC]LOG]!><time="10:20:47.905+420" date="09-03-2009" component="smscliui" context="" type="1" thread="680" file="clicfgdlg.cpp:1477"><![LOG[CCliCfgDcmPage::FreeCallback - Detection Job is null.]LOG]!><time="10:20:50.373+420" date="09-03-2009" component="smscliui" context="" type="1" thread="680" file="clicfgdlg.cpp:3792">Looking at the above log it looks like there was a problem with WMI connection issue. so i repaired it and try to reinstall the client. But no joy :(. Seems like policy issue. I am not able to figure out where i am missing.

Hi there, what do you mean by I deleted the Host (A) record of the said Site Server's address and re-created it again. Voila...! All clients in the said SCCM site started getting the policies and commenced installing the application packages. Can you tell me the exact way, cause i m a really beginner in this point and i have the same problems on my agentclients too... Thank you very much! Andi

Does anyone know the answer?! I really appriciate it! Andi

Hi I also have the same problem, any more suggestions would be welcome

Which issues are you talking about exactly? Have you already checked all those solutions above? Any errors in the logs? Is the MP working?

Hi Our setup is in native mode, and one primary site. We use Client Push Method. Client installs correctly and reports to the SCCM server that its installed. However, the client components show as installed, not enabled. We've checked the following URL: https://Server.domain/sms_mp/.sms_aut?MPlist Below is the output: - <MPList> - <MP Name="Server" FQDN="Server.domain"> <Version>6487</Version> - <Capabilities SchemaVersion="1.0"> <Property Name="SSL" Version="1" /> </Capabilities> </MP> </MPList> We've also checked https://Server.Domain/sms_mp/.sms_aut?MPcert It returns a long certificate string I dont want to publish online. Are there any logs, or additional info i can post?

We had exactly the same issue as described in this post, however, I will rephrase it for the benefits of others, and also include what was done to fix this: Problem: Newly installed clients not getting all Actions populated in the control panel applet, as a result the CCM had all the components set to installed. The environment is ConfigMgr 2007 SP2, MDT2010, Single Primary Site, and 2 secondary sites - ClientIDManagerStartup.log: RegTask: Failed to send registration request message. Error: 0x8007000e ClientIDManagerStartup 09/01/2011 18:23:14 2944 (0x0B80) RegTask: Failed to send registration request. Error: 0x8007000e ClientIDManagerStartup 09/01/2011 18:23:14 2944 (0x0B80) - CCMExec.log: HandleRemoteSyncSend failed (0x8007000e). CCMEXEC 09/01/2011 18:23:14 2944 (0x0B80) CForwarder_Sync::Send failed (0x8007000e). CCMEXEC 09/01/2011 18:23:14 2944 (0x0B80) CForwarder_Base::Send failed (0x8007000e). CCMEXEC 09/01/2011 18:23:14 2944 (0x0B80) - Checking if the MP is working fine. MPControl.log shows: CWmi::Connect(): ConnectServer(Namespace) failed. - 0x8004100e SMS_MP_CONTROL_MANAGER 09/01/2011 18:01:23 5944 (0x1738) CMPControlManager::WriteToCCMSettings(): pWmi->Connect() failed - 0x8004100e SMS_MP_CONTROL_MANAGER 09/01/2011 18:01:23 5944 (0x1738) MPStart(): WriteToCCMSettings() failed - 0x8004100e SMS_MP_CONTROL_MANAGER 09/01/2011 18:01:23 5944 (0x1738) SMS_MP_CONTROL_MANAGER failed to start with 0x8004100e SMS_MP_CONTROL_MANAGER 09/01/2011 18:01:23 5944 (0x1738) Uninstalled MP and client from the server, and reinstalled same. Verified that MP works now, as well as the client. - The existing client however was still unable to talk to the MP, but the error changed: CForwarder_Base::Send failed (0x80040309). CCMEXEC 09/01/2011 18:23:14 2944 (0x0B80) - LocationServices.log: Attempting to refresh certificate information from AD LocationServices 09/01/2011 19:42:36 3824 (0x0EF0) Failed to update certificate information from AD LocationServices 09/01/2011 19:42:36 3824 (0x0EF0) Failed to validate thumbprint with error 0x80070057. LocationServices 09/01/2011 19:42:36 3824 (0x0EF0) Failed to verify the mp thumbprint with error '0x80040304'. LocationServices 09/01/2011 19:42:36 3824 (0x0EF0) - Restarted SMS Services on the Site Server, and monitored the SiteComp.log to make sure that MP got updated in AD. - Restarted the SMS Agent Host service, and the client now started receiving the policies. Cheers

MP at fault. See post. We had exactly the same issue as described in this post, however, I will rephrase it for the benefits of others, and also include what was done to fix this: Problem: Newly installed clients not getting all Actions populated in the control panel applet, as a result the CCM had all the components set to installed. The environment is ConfigMgr 2007 SP2, MDT2010, Single Primary Site, and 2 secondary sites - ClientIDManagerStartup.log: RegTask: Failed to send registration request message. Error: 0x8007000e ClientIDManagerStartup 09/01/2011 18:23:14 2944 (0x0B80) RegTask: Failed to send registration request. Error: 0x8007000e ClientIDManagerStartup 09/01/2011 18:23:14 2944 (0x0B80) - CCMExec.log: HandleRemoteSyncSend failed (0x8007000e). CCMEXEC 09/01/2011 18:23:14 2944 (0x0B80) CForwarder_Sync::Send failed (0x8007000e). CCMEXEC 09/01/2011 18:23:14 2944 (0x0B80) CForwarder_Base::Send failed (0x8007000e). CCMEXEC 09/01/2011 18:23:14 2944 (0x0B80) - Checking if the MP is working fine. MPControl.log shows: CWmi::Connect(): ConnectServer(Namespace) failed. - 0x8004100e SMS_MP_CONTROL_MANAGER 09/01/2011 18:01:23 5944 (0x1738) CMPControlManager::WriteToCCMSettings(): pWmi->Connect() failed - 0x8004100e SMS_MP_CONTROL_MANAGER 09/01/2011 18:01:23 5944 (0x1738) MPStart(): WriteToCCMSettings() failed - 0x8004100e SMS_MP_CONTROL_MANAGER 09/01/2011 18:01:23 5944 (0x1738) SMS_MP_CONTROL_MANAGER failed to start with 0x8004100e SMS_MP_CONTROL_MANAGER 09/01/2011 18:01:23 5944 (0x1738) Uninstalled MP and client from the server, and reinstalled same. Verified that MP works now, as well as the client. - The existing client however was still unable to talk to the MP, but the error changed: CForwarder_Base::Send failed (0x80040309). CCMEXEC 09/01/2011 18:23:14 2944 (0x0B80) - LocationServices.log: Attempting to refresh certificate information from AD LocationServices 09/01/2011 19:42:36 3824 (0x0EF0) Failed to update certificate information from AD LocationServices 09/01/2011 19:42:36 3824 (0x0EF0) Failed to validate thumbprint with error 0x80070057. LocationServices 09/01/2011 19:42:36 3824 (0x0EF0) Failed to verify the mp thumbprint with error '0x80040304'. LocationServices 09/01/2011 19:42:36 3824 (0x0EF0) - Restarted SMS Services on the Site Server, and monitored the SiteComp.log to make sure that MP got updated in AD. - Restarted the SMS Agent Host service, and the client now started receiving the policies.

I deleted the Host (A) record of the said Site Server's address and re-created it again. Voila...! All clients in the said SCCM site started getting the policies and commenced installing the application packages. I found this thread after running into the same problem. I just wanted to say that this also fixed my problem. A dynamic DNS entry was created for the SCCM server and the locationservices.log was reporting "Failed to resolve 'SMS_SLP' to IP address from WINS" when trying to discover the site which indicated to me that it couldn't resolve DNS. I removed the dynamic entry, added a static Host (A) record for the SCCM server, uninstalled and reinstalled the client and it worked like a charm.

Hi i have this issue, when i install with osd the sccm client i have this state on the client If i force the reset of the policy after few minutes it's ok, what's the problem? Thanks