• State Verified Answer
  • Locked Locked
  • Replies 4 replies
  • Subscribers 20 subscribers
  • Views 5025 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Migrate users only, not groups

DJ
over 6 years ago

I have a group that wants to migrate only the users and workstations from Source to Target. They then want to build new servers and groups in the Target instead of migrating "junk" to the new domain. I've advised them it is best to clean up their groups (junk) prior to migration and migrate the groups with the users. But they figure they can simply rely on Sidhistory for gaining access to Source domain resources w/o bothering with group migration. They are not using synchronization (migration only).

This seems like a lot of extra work to me but they really want to go this route. Are there any gotchas to this approach of migrating users only and leaving groups behind; besides of course the extra work of manually building and permissioning new servers in the target with new groups?

 

  • 0 over 6 years ago
    There shouldn't be any gotchas to this approach from a technical standpoint. Once the users are migrated you will still need to use RUM to process the workstations and move them to the new domain.
  • 0 over 6 years ago
    Thank Chris. This is very helpful. What about when a new employee comes on board during the migration? Won't they have to create them in the source, add them to source groups, then migrate them?
  • +1 over 6 years ago
    The issue is. If access to the source resource is controlled through a source group that is not migrated to the target w/sidhistory there will be no access granted to the target user account via sidhistory. They have flawed logic.

    You must migrate (or merge) the source groups and membership to the target with sidhistory in order for the target users to have access to the source resources.

    If that is their plan and they want to maintain access, they will have to do all of this group work prior to the first user being migrated. That means manually creating the groups, memberships and permissions prior.

    New employees can be created wherever they need to be created to have access to the needed resources.
  • 0 over 6 years ago
    You know Jeff, the issue you articulated literally dawned on me just after a discussion I had with them. It's so obvious now that's it's a little embarrassing. Thanks for verifying what my gut's been screaming at me for days.