If built in Domain Users group is migrated and renamed or merged into another group with different name, Primary Group for all future migrated users will reflect this renamed group and not Domain Users group of target domain.
Example:
Domain Users is merged into MyGroup on the target. All migrated users on the source have Domain Users specified as Primary Group. Now when migrating users and looking on the target MyGroup is specified as Primary Group for all such users.
The behavior is by design.
*Caution*
By making the change below, any users migrated after this change will no longer be a member of the 'merged' Domain Users group in Target. They will only be a member of the default Domain Users group.
1. Go to DSA server
2. Run regedit
3. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\AeDSACtrl_[ComputerName]Config\AD_Target_Part
4. Create new string value "DefaultWellKnownRIDs"
5. Set value to "513" which is Domain Users group RID. It is also possible to add more RIDs like "513,512,515" if described scenario involves groups other than Domain users.
This will change Migration Manager behavior going forward. In order to change Primary Group for the existing users that already have it set incorrectly on the target, you can do this through a number of different ways.
1. Modify it for single User with ADUC (Active Directory Users and Computers). Right click on the User and go to Properties|Member Of, select required group and click on "Set Primary Group" button.
2. Re-migrate all users again after the above registry modification was made.
3. Using ADModify or script to set the value of PrimarygroupID for all target users to the value of "513"
4. Migrate all affected users with an import file and include PrimarygroupID attribute with the value "513". More details can be found in the following article:
Renaming and merging (matching) users and groups during migration using an import file
Additionally without the DefaultWellKnownRIDs registry key in place, a users primary group when builtin will change in the target once that group has been migrated and renamed
Windows Registry:
Quest does not provide support for problems that arise from improper modification of the registry. The Windows registry contains information critical to your computer and applications. Make sure you back up the registry before modifying it. For more information on the Windows Registry Editor and how to back up and restore it, refer to Microsoft Article ID 256986 "Description of the Microsoft Windows registry": http://support.microsoft.com/default.aspx?kbid=256986
