Hi，
Thanks for posting here.
Generally speaking, this scenario you need to have reference to the TFS environment move steps which is detailed described below due to the tfs server moving is related to cross domain.
https://msdn.microsoft.com/en-us/library/ms404883(v=vs.120).aspx
My concern is that if you want to maintain the old domain in the new server. For example, the old 5 domains are o_domain1, o_domain2,...o_domain5. And the new 5 domains are
n_domain1,...,n_domain5. After moving, you will still use o_domain1/user1 for the new server. Or you need to map the old domain to the new domain, but the same user can still have his old history. I mean o_domain1/user1 can also get history with n_domain1/user1
on the new server.
If you don't need to map, you need to build the trust relationship between the old domain with the new server domain.
If you need to map domain, you need to also match the old user SID to the new user SID with TFSConfig Identities command.
May
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.
