We have SCCM 2007 SP2 installed with no problems however we have installed two new win7 pc's and installed CCM client as normal. Checked that installs on these client can see site server in control panel which they do but they do not appear in the collections console anywhere. Where can one check and force these cleints to appear? We have firewall turned off clients appear in DNS and can respond to ping and RDP.

Have you already updated the collection membership and refreshed the console? Any errors in LocationServices.log, ClientLocation.log and ccmexec.log?Torsten Meringer | http://www.mssccmfaq.de

LocationServices.log below Failed to reset certificate request times. (0x80041002) LocationServices 17/01/2012 09:30:38 3364 (0x0D24) Attempting to retrieve local MP from AD LocationServices 17/01/2012 09:30:38 3364 (0x0D24) Current AD site of machine is Reform LocationServices 17/01/2012 09:30:38 3364 (0x0D24) Retrieved local Management Point from AD: DUNSRV030.BRJNT.LOCAL LocationServices 17/01/2012 09:30:38 3364 (0x0D24) The 'Certificate Store' is empty in the registry, using default store name 'MY'. LocationServices 17/01/2012 09:30:38 3364 (0x0D24) Refreshing client operational settings over AD LocationServices 17/01/2012 09:30:38 3364 (0x0D24) Refreshed security settings over AD LocationServices 17/01/2012 09:30:38 3364 (0x0D24) No security settings update detected. LocationServices 17/01/2012 09:30:38 3364 (0x0D24) Refreshing the Management Point List for site BK1 LocationServices 17/01/2012 09:30:38 3364 (0x0D24) Retrieved management point encryption info from AD. LocationServices 17/01/2012 09:30:38 3364 (0x0D24) Raising event: instance of CCM_CcmHttp_Status { DateTime = "20120117093038.665000+000"; HostName = "DUNSRV030.BRJNT.LOCAL"; HRESULT = "0x00000000"; ProcessID = 1124; StatusCode = 0; ThreadID = 3364; }; LocationServices 17/01/2012 09:30:38 3364 (0x0D24) Refreshing trusted key information LocationServices 17/01/2012 09:30:38 3364 (0x0D24) Raising event: instance of CCM_CcmHttp_Status { DateTime = "20120117093038.712000+000"; HostName = "DUNSRV030.BRJNT.LOCAL"; HRESULT = "0x00000000"; ProcessID = 1124; StatusCode = 0; ThreadID = 3364; }; LocationServices 17/01/2012 09:30:38 3364 (0x0D24) Persisting the management point authentication information in WMI LocationServices 17/01/2012 09:30:38 3364 (0x0D24) Persisted Management Point Authentication Information locally LocationServices 17/01/2012 09:30:38 3364 (0x0D24) Attempting to retrieve default management point from AD LocationServices 17/01/2012 09:55:30 2324 (0x0914) Retrieved Default Management Point from AD: DUNSRV030.BRJNT.LOCAL LocationServices 17/01/2012 09:55:30 2324 (0x0914) Persisting the default management point in WMI LocationServices 17/01/2012 09:55:30 2324 (0x0914) Persisted Default Management Point Location locally LocationServices 17/01/2012 09:55:30 2324 (0x0914) Attempting to retrieve local MP from AD LocationServices 17/01/2012 09:55:30 2324 (0x0914) Current AD site of machine is Reform LocationServices 17/01/2012 09:55:31 2324 (0x0914) Retrieved local Management Point from AD: DUNSRV030.BRJNT.LOCAL LocationServices 17/01/2012 09:55:31 2324 (0x0914) The 'Certificate Store' is empty in the registry, using default store name 'MY'. LocationServices 17/01/2012 09:55:31 2324 (0x0914) Refreshing client operational settings over AD LocationServices 17/01/2012 09:55:31 2324 (0x0914) Refreshed security settings over AD LocationServices 17/01/2012 09:55:31 2324 (0x0914) No security settings update detected. LocationServices 17/01/2012 09:55:31 2324 (0x0914) Attempting to retrieve default management point from AD LocationServices 17/01/2012 13:09:16 3072 (0x0C00) Retrieved Default Management Point from AD: DUNSRV030.BRJNT.LOCAL LocationServices 17/01/2012 13:09:17 3072 (0x0C00) Persisting the default management point in WMI LocationServices 17/01/2012 13:09:17 3072 (0x0C00) Persisted Default Management Point Location locally LocationServices 17/01/2012 13:09:17 3072 (0x0C00) Attempting to retrieve local MP from AD LocationServices 17/01/2012 13:09:17 3072 (0x0C00) Current AD site of machine is Reform LocationServices 17/01/2012 13:09:17 3072 (0x0C00) Retrieved local Management Point from AD: DUNSRV030.BRJNT.LOCAL LocationServices 17/01/2012 13:09:17 3072 (0x0C00) The 'Certificate Store' is empty in the registry, using default store name 'MY'. LocationServices 17/01/2012 13:09:18 3072 (0x0C00) Refreshing client operational settings over AD LocationServices 17/01/2012 13:09:18 3072 (0x0C00) Refreshed security settings over AD LocationServices 17/01/2012 13:09:18 3072 (0x0C00) No security settings update detected. LocationServices 17/01/2012 13:09:18 3072 (0x0C00) Attempting to retrieve default management point from AD LocationServices 17/01/2012 13:37:56 3056 (0x0BF0) Retrieved Default Management Point from AD: DUNSRV030.BRJNT.LOCAL LocationServices 17/01/2012 13:37:57 3056 (0x0BF0) Persisting the default management point in WMI LocationServices 17/01/2012 13:37:57 3056 (0x0BF0) Persisted Default Management Point Location locally LocationServices 17/01/2012 13:37:57 3056 (0x0BF0) Attempting to retrieve local MP from AD LocationServices 17/01/2012 13:37:57 3056 (0x0BF0) Current AD site of machine is Reform LocationServices 17/01/2012 13:37:57 3056 (0x0BF0) Retrieved local Management Point from AD: DUNSRV030.BRJNT.LOCAL LocationServices 17/01/2012 13:37:57 3056 (0x0BF0) The 'Certificate Store' is empty in the registry, using default store name 'MY'. LocationServices 17/01/2012 13:37:57 3056 (0x0BF0) Refreshing client operational settings over AD LocationServices 17/01/2012 13:37:57 3056 (0x0BF0) Refreshed security settings over AD LocationServices 17/01/2012 13:37:57 3056 (0x0BF0) No security settings update detected. LocationServices 17/01/2012 13:37:57 3056 (0x0BF0)

ccmexec.log on client Failed in WinHttpSendRequest API, ErrorCode = 0x2ee7 CCMEXEC 19/01/2012 08:45:09 3056 (0x0BF0) [CCMHTTP] HTTP ERROR: URL=http://DUNSRV030.BRJNT.LOCAL/ccm_system_windowsauth/request, Port=80, Protocol=http, SSLOptions=0, Code=12007, Text=ERROR_WINHTTP_NAME_NOT_RESOLVED CCMEXEC 19/01/2012 08:45:12 3056 (0x0BF0) Raising event: instance of CCM_CcmHttp_Status { DateTime = "20120119084512.339000+000"; HostName = "DUNSRV030.BRJNT.LOCAL"; HRESULT = "0x80072ee7"; ProcessID = 2036; StatusCode = 0; ThreadID = 3056; }; CCMEXEC 19/01/2012 08:45:12 3056 (0x0BF0) HandleRemoteSyncSend failed (0x80040231). CCMEXEC 19/01/2012 08:45:12 3056 (0x0BF0) CForwarder_Sync::Send failed (0x80040231). CCMEXEC 19/01/2012 08:45:12 3056 (0x0BF0) CForwarder_Base::Send failed (0x80040231). CCMEXEC 19/01/2012 08:45:12 3056 (0x0BF0) SystemTaskProcessor::QueueEvent(PowerChanged, 0) CCMEXEC 19/01/2012 08:45:14 2040 (0x07F8) SystemTaskProcessor::QueueEvent(PowerChanged, 0) CCMEXEC 19/01/2012 08:45:14 2040 (0x07F8) SystemTaskProcessor::QueueEvent(PowerChanged, 0) CCMEXEC 19/01/2012 08:45:14 2040 (0x07F8) SystemTaskProcessor::QueueEvent(PowerChangedEx, 0) CCMEXEC 19/01/2012 08:45:14 2040 (0x07F8) SystemTaskProcessor::QueueEvent(NetworkChangedRaw, 1) CCMEXEC 19/01/2012 08:45:17 5768 (0x1688) SystemTaskProcessor::QueueEvent(NetworkChanged, 1) CCMEXEC 19/01/2012 08:46:08 5768 (0x1688) New CCM (user, session) is: (S-1-5-21-2087721824-771572039-1847928074-10769,1). CCMEXEC 19/01/2012 08:46:16 2980 (0x0BA4) SystemTaskProcessor::QueueEvent(NetworkChanged, 1) CCMEXEC 19/01/2012 08:46:17 5768 (0x1688) SystemTaskProcessor::QueueEvent(Logon, 0) CCMEXEC 19/01/2012 08:46:23 2980 (0x0BA4) SystemTaskProcessor::QueueEvent(NetworkChanged, 1) CCMEXEC 19/01/2012 08:51:08 5768 (0x1688) SystemTaskProcessor::QueueEvent(NetworkChanged, 1) CCMEXEC 19/01/2012 08:51:16 4004 (0x0FA4)

Failed in WinHttpSendRequest API, ErrorCode = 0x2ee7 CCMEXEC 19/01/2012 08:45:09 3056 (0x0BF0) [CCMHTTP] HTTP ERROR: URL=http://DUNSRV030.BRJNT.LOCAL/ccm_system_windowsauth/request, Port=80, Protocol=http, SSLOptions=0, Code=12007, Text=ERROR_WINHTTP_NAME_NOT_RESOLVED CCMEXEC 19/01/2012 08:45:12 3056 (0x0BF0) Have you seen that part of log?Torsten Meringer | http://www.mssccmfaq.de

I see it now. Any clues on how to fix or further investigate error?

Well the message says that the client cannot resolve the name of the MP. It's clearly a name resolution problem. You can start with ping and nslookup.Torsten Meringer | http://www.mssccmfaq.de

The client can ping the site server no problem, in config settings on the client the site code is clearly shown. Will try to reinstall client. Thanks

The client can ping the site server no problem, in config settings on the client the site code is clearly shown. Will try to reinstall client. Thanks Have you tried to ping using FQDN or shorname? Shortname is the one you need to test.Anoop C Nair - @anoopmannur MY BLOG: http://anoopmannur.wordpress.com User Group: ConfigMgr Professionals This posting is provided AS-IS with no warranties/guarantees and confers no rights.

Have you tried to ping using FQDN or shorname? Shortname is the one you need to test. No, FQDN: "[CCMHTTP] HTTP ERROR: URL=http://DUNSRV030.BRJNT.LOCAL/ccm_system_windowsauth/request, Port=80, Protocol=http, SSLOptions=0, Code=12007, Text=ERROR_WINHTTP_NAME_NOT_RESOLVED CCMEXEC 19/01/2012 08:45:12 3056 (0x0BF0)"Torsten Meringer | http://www.mssccmfaq.de

you can also try these 2 URLS on client to see if client talks with MP. do you see any errors on site system status from site server component staus ? http://MPservername/SMS_MP/.sms_aut?mplist http://MPservername/SMS_MP/.sms_aut?mpcertPlease click on "vote as Helpful" if you feel this post helpful to you. Eswar Koneti | My Tech blog: eskonr.com | Linkedin: Eswar Koneti

yes works fine now showing in console but show no client approved NO

showing in console but shows no client approved NO

yes works fine now showing in console but show no client approved NO How is it started working now ? May be you can start troubleshooting from the below blog post. Also you can give try by initiating Discovery Data collection Cycle from configmgr applet in control panel and wait for some time to check whether client is Showing YES or not. http://blogs.technet.com/b/configurationmgr/archive/2009/08/10/troubleshooting-issues-where-clients-are-not-reporting.aspxAnoop C Nair - @anoopmannur MY BLOG: http://anoopmannur.wordpress.com User Group: ConfigMgr Professionals This posting is provided AS-IS with no warranties/guarantees and confers no rights.

yes works fine now showing in console but show no client approved NO How is it started working now ? May be you can start troubleshooting from the below blog post. Also you can give try by initiating Discovery Data collection Cycle from configmgr applet in control panel and wait for some time to check whether client is Showing YES or not. http://blogs.technet.com/b/configurationmgr/archive/2009/08/10/troubleshooting-issues-where-clients-are-not-reporting.aspxAnoop C Nair - @anoopmannur MY BLOG: http://anoopmannur.wordpress.com User Group: ConfigMgr Professionals This posting is provided AS-IS with no warranties/guarantees and confers no rights.