Client not getting Site Code
Hello, I am having a problem with a client picking up a site code for one of my secondary servers. I have other clients discovering the site code just fine. IN the LocationServices.log file on the client i see this : Current AD site of machine is HSB LocationServices 4/4/2012 1:07:55 PM 3480 (0x0D98) Failed to connect to AD LocationServices 4/4/2012 1:07:55 PM 3480 (0x0D98) Attempting to retrieve SLPs from AD LocationServices 4/4/2012 1:07:55 PM 3480 (0x0D98) Failed to connect to AD LocationServices 4/4/2012 1:07:55 PM 3480 (0x0D98) Failed to resolve 'SMS_SLP' to IP address from WINS LocationServices 4/4/2012 1:08:04 PM 3480 (0x0D98) LSGetSLP : Failed to resolve SLP from WINS, is it published LocationServices 4/4/2012 1:08:04 PM 3480 (0x0D98) LSGetAssignedSiteFromSLP : Unable to get the list of SLPs LocationServices 4/4/2012 1:08:04 PM 3480 (0x0D98) Won't send a client assignment fallback status point message because the last assignment error matches this one. LocationServices 4/4/2012 1:08:04 PM 3480 (0x0D98) This client is on an old VLan compared to most other clients but dont appear to be having an issue with them. Old Vlan is a 128.1.128.x address, and new is 10.150.x.x address. I am sorry but I dont know what other info to post. I have reinstalled the client and repaired WMI. Neither have worked. I am not sure what else to check or do for this client. I did read another post but seemed more server related and AD Schema related then my problem.
April 4th, 2012 3:12pm

I am having a problem with a client picking up a site code for one of my secondary servers. What does "pick up site code" mean? Clients can't be assigned to secondary sites at all.Torsten Meringer | http://www.mssccmfaq.de
Free Windows Admin Tool Kit Click here and download it now
April 4th, 2012 4:26pm

Right, i get that sorry for the bad explanation. Under the "Advanced" tab on the client there is no Site Code. Should be RC1. When I click Discover it fails and when I manually enter it fails.
April 4th, 2012 4:30pm

Check that your secondary site truly is published in Active Directory under System\System Management\SMS-YOURSECSITECODE. If you can't see it in Active Directory users and computers go to view and select advanced features. I'd also check the boundary settings for the sites. Mats Hellman | My Blog: http://www.nixadmins.net| Twitter: Mats_Hellman | LinkedIn Mats Hellman |
Free Windows Admin Tool Kit Click here and download it now
April 5th, 2012 3:16am

Also, there could be some boundary conflict or overlapping issues? have a look at locationservices.log for more details (if verbose and debug logging is enabled then you will get more details in the log file).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.
April 5th, 2012 3:20am

I concur with Anoop also, I've seen a few sites with the same problems you are describing caused by overlapping boundaries. Let us know what you find.Mats Hellman | My Blog: http://www.nixadmins.net| Twitter: Mats_Hellman | LinkedIn Mats Hellman |
Free Windows Admin Tool Kit Click here and download it now
April 5th, 2012 3:30am

Also, did you extend the schema properly?Sabrina TechNet Community Support
April 9th, 2012 5:49am

is there a site system with a server locator point on the site where the boundary is defined in which your machine resides? the IP-range or subnet must be in an AD-site that is defined in your site boundary or directly added as a boundary and traffic must be possible and allowed between them
Free Windows Admin Tool Kit Click here and download it now
April 10th, 2012 10:55am

I need to check the schema still. I know the IP range is fine because other clients in the same range are working.
April 10th, 2012 10:57am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics