Hello. My environment is SCCM 2007 SP2 with R2 and MDT 2010 integration. I am experiencing an issue with machines being migrated from Windows XP to Windows 7. The problem is that after migrating a machine it is still in collections for packages only meant for Windows XP machines. I thought when a machine was built, the SCCM client is installed again. It would receive a new GUID and resource ID. Since the GUID is new, it would not be in any collections as a direct member. The old resource would be marked as obsolete and no package would install. However, this is not what I am experiencing with my USMT task sequence. I have my USMT task sequence configured to run the below steps. Once the steps are run, the machine reboots into the boot image and proceeds with the rest of the build. I have to run a command-line step for USMT. Currently, we do not have an SMP. This will be look at in the future but cannot be used now. 1. Use Toolkit 2. Gather (using a customsettings.ini with settings for our environment) 3. Run command-line (run scanstate with the switches relevant for our environment) 4. Reboot (into boot image). Before running the task sequence, I checked the GUID and compared it to the one after the machine is migrated to Windows 7. The GUIDs are the same. Since they are the same, the direct membership rules for the collections are still valid and the Windows XP packages start to install. I looked at the conflicting records settings and it is configured to automatically handle. Is there something that I am missing? Does anyone know how the SCCM client is keeping the same GUID after the migration. Thanks for the help. I feel like I am missing something simple.