Ok, so here's the situation: I have been tasked with rebuilding SCCM for a customer. They had so many issues from a previous implementation, that they just wanted a "do-over". I uninstalled all sites, and removed all references from AD. I have a script removing all clients. I deleted the System Mangement containing and recreated with ADSIEDIT, then applied the correct permissions. I have rebuilt the VM with a new name (same IP) onto 2008 R2. I installed SCCM (all roles on 1 server for now), successfully extnded the schema. I set all boundaries using site/services. Everything looks good. I went to push the first client as a test and the site assignment failed. I get the following in the location services log: LSRefreshSiteCode: Group Policy Updated the Assigned Site Code <HOU>, which is different than the exisitng assigned Site Code <>. Would try to re-assign the site. LocationServices 4/23/2010 10:01:39 AM 3956 (0x0F74) Sending Fallback Status Point message, STATEID='500'. LocationServices 4/23/2010 10:01:39 AM 3956 (0x0F74) Processing GroupPolicy site assignment. LocationServices 4/23/2010 10:01:39 AM 3956 (0x0F74) Assigning to site 'HOU' LocationServices 4/23/2010 10:01:39 AM 3956 (0x0F74) LSVerifySiteVersion : Verifying Site Version for <HOU> LocationServices 4/23/2010 10:01:39 AM 3956 (0x0F74) LSGetSiteVersionFromAD : Failed to retrieve version for the site 'HOU' (0x80004005) LocationServices 4/23/2010 10:01:39 AM 3956 (0x0F74) Attempting to retrieve SLPs from AD LocationServices 4/23/2010 10:01:39 AM 3956 (0x0F74) Failed to resolve 'SMS_SLP' to IP address from WINS LocationServices 4/23/2010 10:01:49 AM 3956 (0x0F74) LSGetSLP : Failed to resolve SLP from WINS, is it published LocationServices 4/23/2010 10:01:49 AM 3956 (0x0F74) LSGetSiteVersionFromSLP : Unable to get the list of SLPs LocationServices 4/23/2010 10:01:49 AM 3956 (0x0F74) LSVerifySiteVersion: Failed to get Site Version from AD and SLP LocationServices 4/23/2010 10:01:49 AM 3956 (0x0F74) Sending Fallback Status Point message, STATEID='608'. LocationServices 4/23/2010 10:01:49 AM 3956 (0x0F74) "HOU" is the previous site code from the old implementation. The new site code should be "S01". I don't know how it keeps trying to use the old HOU or where it's even coming from. I have even put this computer in an OU with all policy blocked to make sure that was not it. I am runing out of ideas. PLEASE HELP. Thanks! xtiyu32n

Hi, the old site code is stored in a registry key on client machines and I think it still exists. So, to reassign a client to new site, you should use the GPO deployment method to update the registry key on machines. See this link : http://technet.microsoft.com/en-us/library/bb633010.aspx Thanks.Bechir Gharbi. MCSA, MCSE M+S, MCITP Server/Enterprise Administrator, MCT, MCTS Configuration Manager/Forefront (Time Zone : GMT+1)

That's right. I just found the SMS key and when I deleted it and repushed, it found the right site. Thanks!xtiyu32n

Could you tell me the exact location of this registy key please? I'm having similar issues and would like to try this as a troubleshooting step as well?