Udostępnij za pośrednictwem

Configmgr Site code - Automatic Discovery Fails

  • Artykuł

I recently moved some of my Configmgr  Clients to a new domain. After moving the clients to this new domain. I noticed that a large number of my Configmgr clients were failing to report into my Primary Configmgr site.

As part of the troubleshooting this, I went to Control Panel, then accessed the  Configuration Manager application. In my case I have 32 bit OS and 64 bit OS Clients.

This is the settings from a 64 bit client.

 

  

Here is what the error looks like in the control panel

 

 

 

 I next opened the locationsservices.log to see what is causing the failure.

 Here is what is in the log

#################locationservices.log#############################################################################################

 LSGetAssignedSiteFromDirectories: Found Assigned Site Code <BAM> by Group Policy        LocationServices        5/31/2011 11:55:34 AM        8132 (0x1FC4)

LSVerifySiteVersion : Verifying Site Version for <BAM>        LocationServices        5/31/2011 11:55:34 AM        8132 (0x1FC4)

LSGetSiteVersionFromAD : Failed to retrieve version for the site 'BAM' (0x80004005)        LocationServices        5/31/2011 11:55:34 AM        8132 (0x1FC4)

Attempting to retrieve SLPs from AD        LocationServices        5/31/2011 11:55:34 AM        8132 (0x1FC4)

Retrieved SLPs from AD        LocationServices        5/31/2011 11:55:34 AM        8132 (0x1FC4)

Raising event:

 

instance of CCM_CcmHttp_Status

{

DateTime = "20110531155534.536000+000";

HostName = "CONFIGUSA1";

HRESULT = "0x00000000";

ProcessID = 5472;

StatusCode = 0;

ThreadID = 8132;

};

LocationServices        5/31/2011 11:55:34 AM        8132 (0x1FC4)

LSGetSiteVersionFromSLP : No site version  returned from SLP for site <BAM>        LocationServices        5/31/2011 11:55:34 AM        8132 (0x1FC4)

LSVerifySiteVersion: Failed to get Site Version from AD and SLP        LocationServices        5/31/2011 11:55:34 AM        8132 (0x1FC4)

Won't send a client assignment fallback status point message because the last assignment error matches this one.        LocationServices        5/31/2011 11:55:34 AM        8132 (0x1FC4)

 #################locationservices.log################################################################################################################

 So It looks like I am I have gotten a assignment site code of BAM from Group policy.   My current side code should be TOP.

 

This info was used in the domain my clients moved from.

 How to Assign Configuration Manager Clients to a Site

 Pasted from <https://technet.microsoft.com/en-us/library/bb680370.aspx>

What the above info does not include is where it sets the info in the registry.  That's what I need to remove to get a correct site code assignment for TOP.

Here is the location of that info in the registry on a 64 bit Client.  I need to remove the GPRequestedSiteAssigmentCode entry.  Notice that the registry location is HKLM\Software\Wow6432Node\Microsoft\Sms\Mobile Client.

Note: On a 32 bit Client it would be HKLM\Software\Microsoft\Sms\Mobile Client.

 

 After removing the GPRequestedSiteAssigmentCode entry.  I can now successfully retrieve the correct site code.

 Here is what my locationservices.log looks like now.

#################locationservices.log#############################################################################################

 Current AD site of machine is Default-First-Site-Name        LocationServices        5/31/2011 12:15:23 PM        8184 (0x1FF8)

LSGetAssignedSiteFromAD : Trying to Assign to the Site <TOP>        LocationServices        5/31/2011 12:15:23 PM        8184 (0x1FF8)

LSVerifySiteVersion : Verifying Site Version for <TOP>        LocationServices        5/31/2011 12:15:23 PM        8184 (0x1FF8)

LSGetSiteVersionFromAD : Successfully retrieved version '4.00.6487.0000' for site 'TOP'        LocationServices        5/31/2011 12:15:23 PM        8184 (0x1FF8)

LSVerifySiteVersion : Verified Client Version '4.00.6487.2000' is not greater than Site Version '4.00.6487.0000'. Client can be assigned to site <TOP>.        LocationServices        5/31/2011 12:15:23 PM        8184 (0x1FF8)

Site and assignment sitecode match. Verifying site version        LocationServices        5/31/2011 12:15:26 PM        8184 (0x1FF8)

LSVerifySiteVersion : Verifying Site Version for <TOP>        LocationServices        5/31/2011 12:15:26 PM        8184 (0x1FF8)

LSGetSiteVersionFromAD : Successfully retrieved version '4.00.6487.0000' for site 'TOP'        LocationServices        5/31/2011 12:15:26 PM        8184 (0x1FF8)

LSVerifySiteVersion : Verified Client Version '4.00.6487.2000' is not greater than Site Version '4.00.6487.0000'. Client can be assigned to site <TOP>.        LocationServices        5/31/2011 12:15:26 PM        8184 (0x1FF8)

 #################locationservices.log#############################################################################################

 More info here on this

https://blogs.technet.com/b/configmgr/archive/2008/06/09/details-for-obtaining-100-configmgr-client-installation-reach.aspx

 

 

 Posts in this blog are provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified in the Terms of Use.

Comments

  • Anonymous
    September 24, 2014
    i have tried above mention setp but not luck , kindly provdie any solution..
  • Anonymous
    September 15, 2015
    Thank you!!

    I've been fighting this all day. It wasn't totally clear to me but I just deleted the whole GPRequestedSiteAssigmentCode string. Once I re-ran the client, it automatically created an AssignedSiteCode string with the correct site code and began working immediately.