Ask a questionAsk a question
 

QuestionClients not showing in console

  • Thursday, July 02, 2009 10:22 AMRobert Lourenco Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hi Guys

    I still have a problem with clients that do not show up in the console.  I can see that the client is installed and pointing to the correct MP and Site etc.  No errors in the logs on the clients.  But it does not pick up that it actually has a client from the console.  This happens to about 10% of my clients.  I can use the remove tools and them and they find the agent.  But they do not report back Hardware and software data and show that they have the client in the console. 

    Boundries are fine for the particular site.  Local firewalls are not on.  Plus some machines in the same stores work fine and were deployed the same and other give this problem.  any ideas on how to resolve this without have to uninstall and reinstall the clients?

All Replies

  • Thursday, July 02, 2009 10:29 AMNeeraj55 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Are those system assigned to site?

    Paste your locationservice.log from any problem facing client.

    have you updated collection membership.
    ___________________________________________________________ Shimbesh
  • Thursday, July 02, 2009 10:43 AMRobert Lourenco Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Hi Shimbesh

    yes, they are assigned to a site.  However  i need to correct my first post.  This machine in particular is in an AD site that has not been moved from SMS 2003 to SCCM 2007.  The sms 2003 still controls the site boundary.  I am still migrating site by site/ region by region. 
    But this happens to clients that are in the correct site with the correct boundary assigned to the SCCM.  If you want I can add the location services for one of those machines.

    Here is the locationservice.log from one of the clients:

    Executing Task LSRefreshLocationsTask LocationServices 2009/07/01 12:10:12 AM 3148 (0x0C4C)
    Executing Task LSRefreshLocationsTask LocationServices 2009/07/01 01:10:13 AM 2372 (0x0944)
    Current AD site of machine is CSG_MDR LocationServices 2009/07/01 01:20:22 AM 2404 (0x0964)
    Created and Sent Location Request '{2D6B8711-CC40-43DA-A7EA-77CD423826B5}' for package {57E2DE3B-75F1-4DEC-8679-62B1A7E78B74} LocationServices 2009/07/01 01:20:22 AM 2404 (0x0964)
    Calling back with the following WSUS locations LocationServices 2009/07/01 01:20:22 AM 4048 (0x0FD0)
    WSUS Path='http://SERVERNAME.DOMAINNAME.CORP:8530', Server='SERVERNAME', Version='5' LocationServices 2009/07/01 01:20:22 AM 4048 (0x0FD0)
    Calling back with locations for WSUS request {2D6B8711-CC40-43DA-A7EA-77CD423826B5} LocationServices 2009/07/01 01:20:22 AM 4048 (0x0FD0)
    Executing Task LSRefreshLocationsTask LocationServices 2009/07/01 02:10:15 AM 3140 (0x0C44)
    Executing Task LSRefreshLocationsTask LocationServices 2009/07/01 03:10:17 AM 464 (0x01D0)
    Executing Task LSRefreshLocationsTask LocationServices 2009/07/01 04:10:20 AM 3372 (0x0D2C)
    Executing Task LSRefreshLocationsTask LocationServices 2009/07/01 05:10:21 AM 2288 (0x08F0)
    Executing Task LSRefreshLocationsTask LocationServices 2009/07/01 06:10:23 AM 1104 (0x0450)
    Executing Task LSRefreshLocationsTask LocationServices 2009/07/01 07:10:25 AM 2064 (0x0810)
    Executing Task LSRefreshLocationsTask LocationServices 2009/07/01 08:10:26 AM 2844 (0x0B1C)
    Executing Task LSRefreshLocationsTask LocationServices 2009/07/01 09:10:28 AM 3368 (0x0D28)
    Executing Task LSRefreshLocationsTask LocationServices 2009/07/01 10:10:30 AM 2680 (0x0A78)
    Executing Task LSRefreshLocationsTask LocationServices 2009/07/01 11:10:31 AM 1268 (0x04F4)
    A Fallback Status Point has not been specified.  Message with STATEID='500' will not be sent. LocationServices 2009/07/01 11:47:07 AM 1612 (0x064C)
    Processing pending site assignment. LocationServices 2009/07/01 11:47:07 AM 1612 (0x064C)
    Assigning to site 'RET' LocationServices 2009/07/01 11:47:07 AM 1612 (0x064C)
    LSVerifySiteVersion : Verifying Site Version for <RET> LocationServices 2009/07/01 11:47:07 AM 1612 (0x064C)
    LSGetSiteVersionFromAD : Successfully retrieved version '4.00.6221.0000' for site 'RET' LocationServices 2009/07/01 11:47:10 AM 1612 (0x064C)
    LSVerifySiteVersion : Verified Client Version '4.00.6221.1000' is not greater than Site Version '4.00.6221.0000'. Client can be assigned to site <RET>. LocationServices 2009/07/01 11:47:10 AM 1612 (0x064C)
    Attempting to retrieve default management point from AD LocationServices 2009/07/01 11:47:10 AM 1612 (0x064C)
    Retrieved Default Management Point from AD: SERVERNAME.DOMAINNAME.CORP LocationServices 2009/07/01 11:47:10 AM 1612 (0x064C)
    Assigning to default Management Point 'SERVERNAME.DOMAINNAME.CORP' LocationServices 2009/07/01 11:47:10 AM 1612 (0x064C)
    A Fallback Status Point has not been specified.  Message with STATEID='700' will not be sent. LocationServices 2009/07/01 11:47:10 AM 1612 (0x064C)
    Successfully processed pending site assignment. LocationServices 2009/07/01 11:47:10 AM 1612 (0x064C)
    Attempting to retrieve default management point from AD LocationServices 2009/07/01 11:47:10 AM 1612 (0x064C)
    Retrieved Default Management Point from AD: SERVERNAME.DOMAINNAME.CORP LocationServices 2009/07/01 11:47:10 AM 1612 (0x064C)
    Persisting the default management point in WMI LocationServices 2009/07/01 11:47:10 AM 1612 (0x064C)
    Persisted Default Management Point Location locally LocationServices 2009/07/01 11:47:10 AM 1612 (0x064C)
    Failed to reset certificate request times. (0x80041002) LocationServices 2009/07/01 11:47:10 AM 1612 (0x064C)
    Attempting to retrieve proxy MP from AD LocationServices 2009/07/01 11:47:11 AM 1612 (0x064C)
    Unknown task LSProxyMPModificationTask in non-quarantine - ignoring. LocationServices 2009/07/01 11:47:11 AM 640 (0x0280)
    DhcpGetOriginalSubnetMask entry point not supported. LocationServices 2009/07/01 11:47:11 AM 1612 (0x064C)
    Current AD site of machine is CSG_MDR LocationServices 2009/07/01 11:47:11 AM 1612 (0x064C)
    Current AD site of machine is CSG_MDR LocationServices 2009/07/01 11:47:11 AM 1612 (0x064C)
    Attempting to retrieve local MP from AD LocationServices 2009/07/01 11:47:11 AM 1612 (0x064C)
    Current AD site of machine is CSG_MDR LocationServices 2009/07/01 11:47:11 AM 1612 (0x064C)
    Group Policy Site Assignment key HKLM\Software\Microsoft\SMS\Mobile Client has changed, will attempt to re-assign the client. LocationServices 2009/07/01 11:47:11 AM 1612 (0x064C)
    Executing Task LSRefreshLocationsTask LocationServices 2009/07/01 11:47:18 AM 3892 (0x0F34)
    Executing Task LSTimeOutRequestsTask LocationServices 2009/07/01 11:47:18 AM 3676 (0x0E5C)
    Executing Task LSRefreshDefaultMPTask LocationServices 2009/07/01 11:47:18 AM 4040 (0x0FC8)
    Refreshing the Management Point List for site RET LocationServices 2009/07/01 11:47:18 AM 2800 (0x0AF0)
    Retrieved management point encryption info from AD. LocationServices 2009/07/01 11:47:18 AM 2800 (0x0AF0)
    Raising event:

    instance of CCM_CcmHttp_Status
    {
     ClientID = "GUID:91DCA098-3C97-4F4A-AB90-8991033BBA3B";
     DateTime = "20090701094718.780000+000";
     HostName = "SERVERNAME.DOMAINNAME.CORP";
     HRESULT = "0x00000000";
     ProcessID = 3104;
     StatusCode = 0;
     ThreadID = 2800;
    };
     LocationServices 2009/07/01 11:47:18 AM 2800 (0x0AF0)
    Refreshing trusted key information LocationServices 2009/07/01 11:47:18 AM 2800 (0x0AF0)
    Raising event:

    instance of CCM_CcmHttp_Status
    {
     ClientID = "GUID:91DCA098-3C97-4F4A-AB90-8991033BBA3B";
     DateTime = "20090701094718.905000+000";
     HostName = "SERVERNAME.DOMAINNAME.CORP";
     HRESULT = "0x00000000";
     ProcessID = 3104;
     StatusCode = 0;
     ThreadID = 2800;
    };
     LocationServices 2009/07/01 11:47:18 AM 2800 (0x0AF0)
    Persisting the management point authentication information in WMI LocationServices 2009/07/01 11:47:18 AM 2800 (0x0AF0)
    Persisted Management Point Authentication Information locally LocationServices 2009/07/01 11:47:18 AM 2800 (0x0AF0)
    Attempting to retrieve default management point from AD LocationServices 2009/07/01 11:47:19 AM 3676 (0x0E5C)
    Attempting to retrieve default management point from AD LocationServices 2009/07/01 11:47:19 AM 4040 (0x0FC8)
    Retrieved Default Management Point from AD: SERVERNAME.DOMAINNAME.CORP LocationServices 2009/07/01 11:47:19 AM 3676 (0x0E5C)
    Retrieved Default Management Point from AD: SERVERNAME.DOMAINNAME.CORP LocationServices 2009/07/01 11:47:19 AM 4040 (0x0FC8)
    Persisting the default management point in WMI LocationServices 2009/07/01 11:47:19 AM 4040 (0x0FC8)
    Unknown task LSProxyMPModificationTask in non-quarantine - ignoring. LocationServices 2009/07/01 11:47:19 AM 640 (0x0280)
    Persisted Default Management Point Location locally LocationServices 2009/07/01 11:47:19 AM 4040 (0x0FC8)
    Unknown task LSProxyMPModificationTask in non-quarantine - ignoring. LocationServices 2009/07/01 11:47:19 AM 3188 (0x0C74)
    Attempting to retrieve proxy MP from AD LocationServices 2009/07/01 11:47:19 AM 4040 (0x0FC8)
    Current AD site of machine is CSG_MDR LocationServices 2009/07/01 11:47:19 AM 4040 (0x0FC8)
    Current AD site of machine is CSG_MDR LocationServices 2009/07/01 11:47:19 AM 4040 (0x0FC8)
    Attempting to retrieve local MP from AD LocationServices 2009/07/01 11:47:19 AM 4040 (0x0FC8)
    Current AD site of machine is CSG_MDR LocationServices 2009/07/01 11:47:19 AM 4040 (0x0FC8)
    Raising event:

    instance of CCM_CcmHttp_Status
    {
     ClientID = "GUID:91DCA098-3C97-4F4A-AB90-8991033BBA3B";
     DateTime = "20090701094719.624000+000";
     HostName = "SERVERNAME.DOMAINNAME.CORP";
     HRESULT = "0x00000000";
     ProcessID = 3104;
     StatusCode = 0;
     ThreadID = 4040;
    };
     LocationServices 2009/07/01 11:47:19 AM 4040 (0x0FC8)
    The 'Certificate Store' is empty in the registry, using default store name 'MY'. LocationServices 2009/07/01 11:47:19 AM 2800 (0x0AF0)
    Attempting to retrieve default management point from AD LocationServices 2009/07/01 11:47:19 AM 3736 (0x0E98)
    Refreshing client operational settings over AD LocationServices 2009/07/01 11:47:19 AM 2800 (0x0AF0)
    Retrieved Default Management Point from AD: SERVERNAME.DOMAINNAME.CORP LocationServices 2009/07/01 11:47:19 AM 3736 (0x0E98)
    Refreshed security settings over AD LocationServices 2009/07/01 11:47:19 AM 2800 (0x0AF0)
    No security settings update detected. LocationServices 2009/07/01 11:47:19 AM 2800 (0x0AF0)
    Unknown task LSProxyMPModificationTask in non-quarantine - ignoring. LocationServices 2009/07/01 11:47:19 AM 640 (0x0280)
    Refreshing the Management Point List for site RET LocationServices 2009/07/01 11:50:13 AM 2172 (0x087C)
    Retrieved management point encryption info from AD. LocationServices 2009/07/01 11:50:13 AM 2172 (0x087C)
    Raising event:

    instance of CCM_CcmHttp_Status
    {
     ClientID = "GUID:91DCA098-3C97-4F4A-AB90-8991033BBA3B";
     DateTime = "20090701095014.114000+000";
     HostName = "SERVERNAME.DOMAINNAME.CORP";
     HRESULT = "0x00000000";
     ProcessID = 3104;
     StatusCode = 0;
     ThreadID = 2172;
    };
     LocationServices 2009/07/01 11:50:14 AM 2172 (0x087C)
    Refreshing trusted key information LocationServices 2009/07/01 11:50:14 AM 2172 (0x087C)
    Raising event:

    instance of CCM_CcmHttp_Status
    {
     ClientID = "GUID:91DCA098-3C97-4F4A-AB90-8991033BBA3B";
     DateTime = "20090701095014.208000+000";
     HostName = "SERVERNAME.DOMAINNAME.CORP";
     HRESULT = "0x00000000";
     ProcessID = 3104;
     StatusCode = 0;
     ThreadID = 2172;
    };
     LocationServices 2009/07/01 11:50:14 AM 2172 (0x087C)
    Persisting the management point authentication information in WMI LocationServices 2009/07/01 11:50:14 AM 2172 (0x087C)
    Persisted Management Point Authentication Information locally LocationServices 2009/07/01 11:50:14 AM 2172 (0x087C)
    Executing Task LSRefreshLocationsTask LocationServices 2009/07/01 12:47:15 PM 1620 (0x0654)
    Executing Task LSRefreshLocationsTask LocationServices 2009/07/01 01:47:16 PM 516 (0x0204)
    Executing Task LSRefreshLocationsTask LocationServices 2009/07/01 02:47:17 PM 500 (0x01F4)
    Executing Task LSRefreshLocationsTask LocationServices 2009/07/01 03:47:19 PM 436 (0x01B4)
    A Fallback Status Point has not been specified.  Message with STATEID='500' will not be sent. LocationServices 2009/07/01 04:38:39 PM 380 (0x017C)
    Processing pending site assignment. LocationServices 2009/07/01 04:38:39 PM 380 (0x017C)
    Assigning to site 'RET' LocationServices 2009/07/01 04:38:39 PM 380 (0x017C)
    LSVerifySiteVersion : Verifying Site Version for <RET> LocationServices 2009/07/01 04:38:39 PM 380 (0x017C)
    LSGetSiteVersionFromAD : Successfully retrieved version '4.00.6221.0000' for site 'RET' LocationServices 2009/07/01 04:38:41 PM 380 (0x017C)
    LSVerifySiteVersion : Verified Client Version '4.00.6221.1000' is not greater than Site Version '4.00.6221.0000'. Client can be assigned to site <RET>. LocationServices 2009/07/01 04:38:41 PM 380 (0x017C)
    Attempting to retrieve default management point from AD LocationServices 2009/07/01 04:38:41 PM 380 (0x017C)
    Retrieved Default Management Point from AD: SERVERNAME.DOMAINNAME.CORP LocationServices 2009/07/01 04:38:41 PM 380 (0x017C)
    Assigning to default Management Point 'SERVERNAME.DOMAINNAME.CORP' LocationServices 2009/07/01 04:38:41 PM 380 (0x017C)
    A Fallback Status Point has not been specified.  Message with STATEID='700' will not be sent. LocationServices 2009/07/01 04:38:41 PM 380 (0x017C)
    Successfully processed pending site assignment. LocationServices 2009/07/01 04:38:41 PM 380 (0x017C)
    Attempting to retrieve default management point from AD LocationServices 2009/07/01 04:38:41 PM 380 (0x017C)
    Retrieved Default Management Point from AD: SERVERNAME.DOMAINNAME.CORP LocationServices 2009/07/01 04:38:41 PM 380 (0x017C)
    Persisting the default management point in WMI LocationServices 2009/07/01 04:38:41 PM 380 (0x017C)
    Persisted Default Management Point Location locally LocationServices 2009/07/01 04:38:41 PM 380 (0x017C)
    Failed to reset certificate request times. (0x80041002) LocationServices 2009/07/01 04:38:41 PM 380 (0x017C)
    Attempting to retrieve proxy MP from AD LocationServices 2009/07/01 04:38:41 PM 380 (0x017C)
    Unknown task LSProxyMPModificationTask in non-quarantine - ignoring. LocationServices 2009/07/01 04:38:41 PM 3912 (0x0F48)
    DhcpGetOriginalSubnetMask entry point not supported. LocationServices 2009/07/01 04:38:42 PM 380 (0x017C)
    Current AD site of machine is CSG_MDR LocationServices 2009/07/01 04:38:42 PM 380 (0x017C)
    Current AD site of machine is CSG_MDR LocationServices 2009/07/01 04:38:42 PM 380 (0x017C)
    Attempting to retrieve local MP from AD LocationServices 2009/07/01 04:38:42 PM 380 (0x017C)
    Current AD site of machine is CSG_MDR LocationServices 2009/07/01 04:38:42 PM 380 (0x017C)
    Group Policy Site Assignment key HKLM\Software\Microsoft\SMS\Mobile Client has changed, will attempt to re-assign the client. LocationServices 2009/07/01 04:38:42 PM 380 (0x017C)
    Executing Task LSRefreshLocationsTask LocationServices 2009/07/01 04:38:48 PM 1352 (0x0548)
    Executing Task LSTimeOutRequestsTask LocationServices 2009/07/01 04:38:48 PM 3836 (0x0EFC)
    Executing Task LSRefreshDefaultMPTask LocationServices 2009/07/01 04:38:48 PM 3388 (0x0D3C)
    Attempting to retrieve default management point from AD LocationServices 2009/07/01 04:38:48 PM 3388 (0x0D3C)
    Retrieved Default Management Point from AD: SERVERNAME.DOMAINNAME.CORP LocationServices 2009/07/01 04:38:48 PM 3388 (0x0D3C)
    Persisting the default management point in WMI LocationServices 2009/07/01 04:38:48 PM 3388 (0x0D3C)
    Persisted Default Management Point Location locally LocationServices 2009/07/01 04:38:48 PM 3388 (0x0D3C)
    Unknown task LSProxyMPModificationTask in non-quarantine - ignoring. LocationServices 2009/07/01 04:38:48 PM 3876 (0x0F24)
    Attempting to retrieve proxy MP from AD LocationServices 2009/07/01 04:38:48 PM 3388 (0x0D3C)
    Current AD site of machine is CSG_MDR LocationServices 2009/07/01 04:38:48 PM 3388 (0x0D3C)
    Refreshing the Management Point List for site RET LocationServices 2009/07/01 04:38:48 PM 3836 (0x0EFC)
    Retrieved management point encryption info from AD. LocationServices 2009/07/01 04:38:48 PM 3836 (0x0EFC)
    Raising event:

    instance of CCM_CcmHttp_Status
    {
     ClientID = "GUID:91DCA098-3C97-4F4A-AB90-8991033BBA3B";
     DateTime = "20090701143848.709000+000";
     HostName = "SERVERNAME.DOMAINNAME.CORP";
     HRESULT = "0x00000000";
     ProcessID = 692;
     StatusCode = 0;
     ThreadID = 3836;
    };
     LocationServices 2009/07/01 04:38:48 PM 3836 (0x0EFC)
    Refreshing trusted key information LocationServices 2009/07/01 04:38:48 PM 3836 (0x0EFC)
    Raising event:

    instance of CCM_CcmHttp_Status
    {
     ClientID = "GUID:91DCA098-3C97-4F4A-AB90-8991033BBA3B";
     DateTime = "20090701143848.818000+000";
     HostName = "SERVERNAME.DOMAINNAME.CORP";
     HRESULT = "0x00000000";
     ProcessID = 692;
     StatusCode = 0;
     ThreadID = 3836;
    };
     LocationServices 2009/07/01 04:38:48 PM 3836 (0x0EFC)
    Persisting the management point authentication information in WMI LocationServices 2009/07/01 04:38:48 PM 3836 (0x0EFC)
    Persisted Management Point Authentication Information locally LocationServices 2009/07/01 04:38:48 PM 3836 (0x0EFC)
    Attempting to retrieve default management point from AD LocationServices 2009/07/01 04:38:48 PM 4052 (0x0FD4)
    Retrieved Default Management Point from AD: SERVERNAME.DOMAINNAME.CORP LocationServices 2009/07/01 04:38:48 PM 4052 (0x0FD4)
    Current AD site of machine is CSG_MDR LocationServices 2009/07/01 04:38:49 PM 3388 (0x0D3C)
    Attempting to retrieve local MP from AD LocationServices 2009/07/01 04:38:49 PM 3388 (0x0D3C)
    Current AD site of machine is CSG_MDR LocationServices 2009/07/01 04:38:49 PM 3388 (0x0D3C)
    Raising event:

    instance of CCM_CcmHttp_Status
    {
     ClientID = "GUID:91DCA098-3C97-4F4A-AB90-8991033BBA3B";
     DateTime = "20090701143849.303000+000";
     HostName = "SERVERNAME.DOMAINNAME.CORP";
     HRESULT = "0x00000000";
     ProcessID = 692;
     StatusCode = 0;
     ThreadID = 3388;
    };
     LocationServices 2009/07/01 04:38:49 PM 3388 (0x0D3C)
    The 'Certificate Store' is empty in the registry, using default store name 'MY'. LocationServices 2009/07/01 04:38:49 PM 1352 (0x0548)
    Attempting to retrieve default management point from AD LocationServices 2009/07/01 04:38:49 PM 4052 (0x0FD4)
    Refreshing client operational settings over AD LocationServices 2009/07/01 04:38:49 PM 1352 (0x0548)
    Retrieved Default Management Point from AD: SERVERNAME.DOMAINNAME.CORP LocationServices 2009/07/01 04:38:49 PM 4052 (0x0FD4)
    Refreshed security settings over AD LocationServices 2009/07/01 04:38:49 PM 1352 (0x0548)
    No security settings update detected. LocationServices 2009/07/01 04:38:49 PM 1352 (0x0548)
    Unknown task LSProxyMPModificationTask in non-quarantine - ignoring. LocationServices 2009/07/01 04:38:49 PM 3912 (0x0F48)
    Refreshing the Management Point List for site RET LocationServices 2009/07/01 04:40:43 PM 2996 (0x0BB4)
    Retrieved management point encryption info from AD. LocationServices 2009/07/01 04:40:43 PM 2996 (0x0BB4)
    Raising event:

    instance of CCM_CcmHttp_Status
    {
     ClientID = "GUID:91DCA098-3C97-4F4A-AB90-8991033BBA3B";
     DateTime = "20090701144044.039000+000";
     HostName = "SERVERNAME.DOMAINNAME.CORP";
     HRESULT = "0x00000000";
     ProcessID = 692;
     StatusCode = 0;
     ThreadID = 2996;
    };
     LocationServices 2009/07/01 04:40:44 PM 2996 (0x0BB4)
    Refreshing trusted key information LocationServices 2009/07/01 04:40:44 PM 2996 (0x0BB4)
    Raising event:

    instance of CCM_CcmHttp_Status
    {
     ClientID = "GUID:91DCA098-3C97-4F4A-AB90-8991033BBA3B";
     DateTime = "20090701144044.133000+000";
     HostName = "SERVERNAME.DOMAINNAME.CORP";
     HRESULT = "0x00000000";
     ProcessID = 692;
     StatusCode = 0;
     ThreadID = 2996;
    };
     LocationServices 2009/07/01 04:40:44 PM 2996 (0x0BB4)
    Persisting the management point authentication information in WMI LocationServices 2009/07/01 04:40:44 PM 2996 (0x0BB4)
    Persisted Management Point Authentication Information locally LocationServices 2009/07/01 04:40:44 PM 2996 (0x0BB4)
    Executing Task LSRefreshLocationsTask LocationServices 2009/07/01 05:38:44 PM 3528 (0x0DC8)
    Executing Task LSRefreshLocationsTask LocationServices 2009/07/01 06:38:46 PM 1104 (0x0450)
    Executing Task LSRefreshLocationsTask LocationServices 2009/07/01 07:38:47 PM 516 (0x0204)
    Executing Task LSRefreshLocationsTask LocationServices 2009/07/01 08:38:49 PM 1356 (0x054C)
    Executing Task LSRefreshLocationsTask LocationServices 2009/07/01 09:38:51 PM 2236 (0x08BC)
    Executing Task LSRefreshLocationsTask LocationServices 2009/07/01 10:38:52 PM 2408 (0x0968)
    Current AD site of machine is CSG_MDR LocationServices 2009/07/01 10:39:00 PM 2484 (0x09B4)
    Created and Sent Location Request '{9F1D6F0D-CCF9-465E-8DAA-9ADB510685CC}' for package {57E2DE3B-75F1-4DEC-8679-62B1A7E78B74} LocationServices 2009/07/01 10:39:00 PM 2484 (0x09B4)
    Calling back with the following WSUS locations LocationServices 2009/07/01 10:39:01 PM 2304 (0x0900)
    WSUS Path='http://SERVERNAME.DOMAINNAME.CORP:8530', Server='SERVERNAME', Version='5' LocationServices 2009/07/01 10:39:01 PM 2304 (0x0900)
    Calling back with locations for WSUS request {9F1D6F0D-CCF9-465E-8DAA-9ADB510685CC} LocationServices 2009/07/01 10:39:01 PM 2304 (0x0900)
    Executing Task LSRefreshLocationsTask LocationServices 2009/07/01 11:38:53 PM 3120 (0x0C30)
    Executing Task LSRefreshLocationsTask LocationServices 2009/07/02 12:38:55 AM 2976 (0x0BA0)
    Executing Task LSRefreshLocationsTask LocationServices 2009/07/02 01:38:56 AM 1268 (0x04F4)
    Executing Task LSRefreshLocationsTask LocationServices 2009/07/02 02:38:57 AM 3044 (0x0BE4)
    Executing Task LSRefreshLocationsTask LocationServices 2009/07/02 03:38:59 AM 2672 (0x0A70)
    Executing Task LSRefreshLocationsTask LocationServices 2009/07/02 04:39:00 AM 2800 (0x0AF0)
    Executing Task LSRefreshLocationsTask LocationServices 2009/07/02 05:39:02 AM 3140 (0x0C44)
    Executing Task LSRefreshLocationsTask LocationServices 2009/07/02 06:39:03 AM 2220 (0x08AC)
    Executing Task LSRefreshLocationsTask LocationServices 2009/07/02 07:39:04 AM 1252 (0x04E4)
    Executing Task LSRefreshLocationsTask LocationServices 2009/07/02 08:39:06 AM 1252 (0x04E4)
    Executing Task LSRefreshLocationsTask LocationServices 2009/07/02 09:39:10 AM 2172 (0x087C)
    Executing Task LSRefreshLocationsTask LocationServices 2009/07/02 10:39:12 AM 3228 (0x0C9C)
    Executing Task LSRefreshLocationsTask LocationServices 2009/07/02 11:39:13 AM 2352 (0x0930)
    Executing Task LSRefreshLocationsTask LocationServices 2009/07/02 12:39:14 PM 3400 (0x0D48)

  • Tuesday, July 07, 2009 11:15 AMNeeraj55 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hi Robert,

    "Group Policy Site Assignment key HKLM\Software\Microsoft\SMS\Mobile Client has changed, will attempt to re-assign "

    R u using SUP client installation method.

    Please let me know how u r installaing client(Method)


    As well as your client is able to locate to MP and assigning to site also.

    Just update collection and verify the system is coming with client or not.

    ___________________________________________________________ Shimbesh
  • Tuesday, July 07, 2009 1:52 PMRobert Lourenco Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hi Shimbesh

    I am not using the SUP client installation method although I am using SUP.  I am using the normal Client push installation.  So I disover the AD groups and then deploy.  The Boundries are also correct.  What I have found is that some of the agents are pointing to a site code that is incorrect.  I can only assume it is left over from the last administrators attempt to use SCCM.

    So if I manually install the client and force it to upgrade/repair the agent then some of them get fixed.  But I still have a large amount that even if I install them this way that they still do not show up in my console.  Even though the logs look fine and the remote desktop and assistance tools work.  It strange.  If these tools work the software updates however still do not work.
  • Tuesday, July 07, 2009 2:06 PMTorsten [MVP]MVPUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Remote desktop and remote assistance have nothing to do with the ConfigMgr client, because they are part of the OS.

    Have you already checked if there are boundaries left in the "system management" container?

    LocationServices.log, ClientLocation.log, ccmexec.log are the places to start troubleshooting (atfter the client was installed successfully; see cmexec.log). I haven't seen a non-working client without any errors in any of the logs.