Hi all, I'm having a few problems with a number of machines that have been migrated from a legacy domain into our new domain. This legacy domain also has an installation of SCCM in mixed mode. in the new domain we are running in native mode. what is happening is that the machines are migrated across to the new domain using the various AD migration tools that the AD team uses, the old sccm client is uninstalled. Once the machine is migrated, it picks up the PKI certifcate specific to the new SCCM environment and then tries to install the new client. Now, as far as I'm concerned, that machine is now completely migrated and should not, in any way shape or form be trying to reference the old domain or SCCM enviroment, but what is happening is the machines is contacting a valid site server to download it's install files. it checks AD and finds that it's subnet is assigned to a particular site code in the new domain and puts that in the install path so everything looks good to this point. Once the install has completed as far as the ccmsetup.log in concerned, I then take a look at the CCM folder and look specifically at the locationservices.log file and for some unexplainable reason, it still knows about or trys to find it's old site server in the old domain ! what could be causing this? is there references to the old enviroment that ccmsetup.exe /uninstall can't remove? the sccm system is still running in the old domain so we have a situation where both SCCM environments are looking at the same ip subnet and have it included in respective boundaries, but as far as I'm concerned, these machines, after migration, should know nothing about the old domain and SCCM environment it came from and should assign itself to the correct parent in the new domain. could there be conflicting boundaries even though the SCCM environments are completely segregated in differnent AD's? I have included a bit of the log file so show the problem. we are running in native mode and the AD schema is extended. The site code it should be assigning to is 404, the one referenced below is from the old domain for some reason. LSRefreshSiteCode: Group Policy Updated the Assigned Site Code <MAD>, which is different than the exisitng assigned Site Code <>. Would try to re-assign the site. LocationServices 28-10-2010 17:35:42 5840 (0x16D0) Sending Fallback Status Point message, STATEID='500'. LocationServices 28-10-2010 17:35:42 5840 (0x16D0) Processing GroupPolicy site assignment. LocationServices 28-10-2010 17:35:42 5840 (0x16D0) Assigning to site 'MAD' LocationServices 28-10-2010 17:35:42 5840 (0x16D0) LSVerifySiteVersion : Verifying Site Version for <MAD> LocationServices 28-10-2010 17:35:42 5840 (0x16D0) LSGetSiteVersionFromAD : Failed to retrieve version for the site 'MAD' (0x80004005) LocationServices 28-10-2010 17:35:42 5840 (0x16D0) Attempting to retrieve SLPs from AD LocationServices 28-10-2010 17:35:42 5840 (0x16D0) Failed to resolve 'SMS_SLP' to IP address from WINS LocationServices 28-10-2010 17:35:52 5840 (0x16D0) LSGetSLP : Failed to resolve SLP from WINS, is it published LocationServices 28-10-2010 17:35:52 5840 (0x16D0) LSGetSiteVersionFromSLP : Unable to get the list of SLPs LocationServices 28-10-2010 17:35:52 5840 (0x16D0) LSVerifySiteVersion: Failed to get Site Version from AD and SLP LocationServices 28-10-2010 17:35:52 5840 (0x16D0) Sending Fallback Status Point message, STATEID='608'. LocationServices 28-10-2010 17:35:52 5840 (0x16D0) any help would be greatly appreciated ! regards douglas

Are both domains in the same forest? What is your install command line for the client? Have you read this? http://blogs.technet.com/b/configmgrteam/archive/2009/04/09/reassigning-a-configuration-manager-client-across-hierarchies.aspx John Marcum | http://myitforum.com/cs2/blogs/jmarcum |