• State Verified Answer
  • Locked Locked
  • Replies 8 replies
  • Answers 1 answer
  • Subscribers 19 subscribers
  • Views 12519 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

Migrating file/print/app servers first

eric_bergstrom
over 7 years ago

 Hello all-

Theoretical question regarding resource processing with the RUM.

Typically on any migration project, we've brought over the users and groups first, processed workstations and servers, move workstations then, after all users now log into the target, move servers.

My customer has a requirement to move some app and file/print servers BEFORE migrating users and computers. As long as all the source users are copied/matched to the target and SIDHistory is brought over, the only potential issue I can see is any perms/ACLs based on Domain Local groups or maybe Built In groups as the RUM appends ACLs, not overwrites.

SQL and SharePoint are special. I'm not too concerned about that. Those really should wait until the end as it's an perms replace.

Anything I'm missing here? I'm walking into a migration project already in flight and I know I'll be asked this question.

Regards,

Eric

Parents
  • 0 over 7 years ago
    If you run SQL Processing wizard with a custom map file, you can just process these users, then if you move the server, as long as you have a good two way trust in place, they can still access.
    Luke
Reply
  • 0 over 7 years ago
    If you run SQL Processing wizard with a custom map file, you can just process these users, then if you move the server, as long as you have a good two way trust in place, they can still access.
    Luke
Children
No Data