2

We manage all our site security via AD group memberships. We are currently in the process of folding four AD domains into a fifth domain that already exists. Our farm is in one of those four domains but it will not be moving due - we'll handle that when we migrate to SP2013.

Given those considerations, does Move-SPUser essentially function as a user merge tool in that scenario? We have some users with two or even three logins to the site, and my hope is that we can use Move-SPUser to merge them all in order to preserve author/editor metadata on SP objects.

Assume we are moving domains B and C to A. User Bob has potentially created content on B\Bob and C\Bob. We can use Move-SPUser to migrate B\Bob to A\Bob. What happens if we then migrate C\Bob to A\Bob? Does all the existing content associated with A\Bob get "Unknown User"? Or do the IDs all get overwritten?

Improve this question

1 Answer 1

Reset to default
1

I'm sorry, but if you are planning to have a "catch-all" procedure, that is not really healthy. I would recommend you plan your accounts migration procedure in such way that you avoid such transitive operations. Is a "last-one in" operation, so content associated with prior account should be updated to consider the new account (SID included - there is an option for that in the command).

Basically, if you migrate B\Bob to A\Bob, and C\Bob to A\Bob - than A\Bob is what user shall use in the future to access content.

Improve this answer
2
  • Unfortunately the SIDs are changing and that's out of my hands, so I have to run -IgnoreSID with Move-SPUser. Commented Feb 18, 2013 at 18:20
  • Yes, that is true, and SID are usually automatically handled by the AD DS. Commented Feb 18, 2013 at 18:23

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.