The CCMSetup key currently only has CCMSetupStampHigh and CCMSeupStampLow values. I searched the client registry for the old site code, but did not find it anywhere.
Date: Wed, 13 Aug 2014 08:55:33 -0700 From: [email protected] Subject: Re: [mssms] Site assignment issue after migration To: [email protected] locally maybe? Hkey_Local_Machine\Software\Policies\Microsoft\Ccmsetup\SetupParameters Sherry Kissinger On Wednesday, August 13, 2014 10:50 AM, Rick <[email protected]> wrote: We are finishing up on a SCCM 2007 to SCCM 2012 migration. About 10% of the clients (spread across a number of boundaries) are reporting in 2012 as Client equals NO. Upon checking those computers, the 2012 client appears to be installed properly. The Control Panel applet shows the correct 2012 site code, has a GUID, has the correct components enabled and remote control is working. But, when digging into the LocationServices.log on a client it includes "Assigning to site 'old2007sitecode'." The SCCM 2007 servers are still online, but client installation, AD publishing and AD Discovery are disabled. The boundaries have been deleted. We removed the old objects in the System Management OU (and the SCCM 2012 objects are published). The SRV record for the 2007 MP has been deleted from DNS. Any ideas on where this assignment to SCCM 2007 is coming from? Thanks in advance for the help!
