Hi there! We are using USMT 4.0 to migrate from XP to Win7 (64bit). USMT is be default migrating local group membership. So if the user to be migrated was member of the local Administrators group, it will be member of the local Administrators group on the destination machine, too. And that happens even though we are changing the user's domain and name during migration. How can we stop the migration of local group memberships? I tried the following section in config.xml, but that doesn't have the expected effect. But I might just do something stupid, as that <ProfileControl> component is hardly described in MSDN. <ProfileControl> <localGroups> <mappings> <exclude> <pattern>*</pattern> </exclude> </mappings> </localGroups> </ProfileControl> Does anybody have any ideas how to deal with it? Thanks, Christian

Hi Christian, I'm trying to accomplish the same thing and wondered if you got any further with this? We have users in Administrators and Power Users and I need to stop them being migrated across too. Cheers Simon

i hope this help http://social.technet.microsoft.com/Forums/en-US/configmgrosd/thread/aa52c134-8d58-4d8e-876e-3431453a9553Thanks Uday Kiran, Senior Consultant Cyquent Technology Consultants, Dubai Please Mark as answer if it helps you

No, not really. That's just for including / excluding individual users from the capture / restore. It has nothing to do with excluding users from local groups prior to or post migration. I think I might end up just writing a bit of VB to remove them post migration. Cheers Simon

In a refresh scenario I delete unwanted profiles prior to running USMT.

Hi Jim, well, it's an old thread but still a very useful answer! Didn't know about the changeGroup tag, which solved our issue nicely. Thanks a lot, Christian

As a follow up, I tried the following: <ProfileControl> <localGroups> <mappings> <changeGroup from="Administrators" to="JunkUsers" appliesTo="AllUsers"> <include> <pattern>*</pattern> </include> </changeGroup> </mappings> </localGroups> </ProfileControl> So far in my testing, since JunkUsers does not exist as a group on the target PC, the users were removed from Administrators and not added to anything...exactly what I wanted to accomplish. --Jim