See all of the top support solutions for our most common issues here
When using System Center Configuration Manager 2007 some clients may be assigned to the incorrect sitecode. You may also see entries similar to those below in the locationservices.log file:
Note that in the example above, the client should have been assigned to site P01 but was instead assigned to site P04.
This can occur if Active Directory references more than one site with the same site boundary.
Remove or correct the site that contains objects using the same boundaries. To identify sites using the same boundaries, run ldifde -f output.txt from a command prompt and search the text file for the related boundary (ADSite1 in the example above).
In many cases this situation occurs because a site is deleted instead of being deinstalled. Doing this leaves the AD objects behind which results in a duplicate boundary if another site is later added that contains the boundary used in the previously deleted site.
How to Verify Site Information is Published to Active Directory Domain Services: http://technet.microsoft.com/en-us/library/bb693614.aspx
How to Publish Configuration Manager Site Information to Active Directory Domain Services: http://technet.microsoft.com/en-us/library/bb680711.aspx
How to Stop Publishing Site Information to Active Directory Domain Services: http://technet.microsoft.com/en-us/library/bb680429.aspx
For the latest version of this article see the following Knowledge Base article:
KB2002059 - Some clients may be assigned to the wrong sitecode in System Center Configuration Manager 2007
J.C. Hornbeck | System Center Knowledge Engineer