We are migrating to a new domain. The documentation for changing environment (and for the TfsConfig identities /change
) command states that the user accounts must not exist in TFS before you try and migrate them in TFS.
However, one has got in because they were migrated as a test case and added automatically via group policy.
As described in the documentation, TfsConfig identities /change
will not work for this account because the new account is already in TFS.
TfsConfig identities
shows that the SID of the new identity not a match to Windows.
None of the users queries are working (of course, because it's a new account).
To make it worse, the user has created work items. So now there are work items under two separate accounts....
My question is: Do I have any facility to clean this mess up?
I want the new identity to match Windows, the users work items to be merged under the new account and all the users queries to work...
Before I understood what had gone wrong, I posted this question because I thought that the reason the users queries were not working was a simple query configuration issue. Now I realise (assuming anything of what I said above is correct) that I have bigger problems that possibly can't be cleaned up with the available command-line tools...
UPDATE (for anyone else who makes the same mistake we did)
We moved our server into the new domain last night. Happily, the SIDs appear to have corrected themselves. The only issue now is that the user doesn't have access to their old work items. I can update all fields apart from Created By via code. Created By is read-only. This question is now solely asking:
How do I update the Created By field of a work item?
I've read a lot of posts that say never, ever, ever, update data directly in the TFS databases... But this appears to be my only option if I want to fix the users queries...