TFS 在域更改后删除重复的用户 [英] TFS Delete duplicated users after domain change

问题描述

我们刚刚将 TFS 2013.3 服务器迁移到新域.

We've just migrated our TFS 2013.3 server to a new domain.

一切似乎都按计划进行 - 我迁移了服务器，然后成功迁移了身份，但不是将用户身份更改为他们的新域帐户，而是刚刚添加了新帐户，所以现在每个人在系统中两次.

It all appeared to go to plan - I migrated the server and then migrated the Identities successfully, but instead of changing user identities to their new domain accounts, it has just added new accounts so now everybody is in the system twice.

总的来说，我已经能够减轻这种症状，但它破坏了 Web Access 中的用户容量 - 每个用户的名称出现两次，并且只有当两个名称都出现时，他们的容量图才能正确显示分配给它们的容量值相同.即使我们尝试这种糟糕的解决方法，一个用户也根本无法获得容量图.

In general I've been able to mitigate the symptoms of this, but it has broken user capacities in Web Access - each user's name appears twice, and their capacity graph only shows correctly if both names have the same capacity value assigned to them. One user does not get a capacity graph at all even if we attempt this awful workaround.

我可以轻松地从 [Tfs_Configuration.dbo.tbl_Identity] 和/或 [tbl_TeamConfigurationCapacity] 中删除旧用户，但我不知道这样做是否安全，或者对这些条目的引用可能存在于数据库.(不应该再有任何信息链接到这些用户，因为他们都已迁移，但如果删除这些行会损坏数据库，这对我没有帮助).我可能只需要对 VM 进行快照并尝试看看会发生什么，因为这是一个完整的演示.

I could easily delete the old users from [Tfs_Configuration.dbo.tbl_Identity] and/or [tbl_TeamConfigurationCapacity] but I have no idea if this would be a safe thing to do, or what references to these entries might exist elsewhere in the database. (There shouldn't be any information linked to these users any more, as they have all been migrated, but that won't help me if deleting these rows corrupts the database). I may just have to snapshot the VM and give it a try to see what happens, as this is a complete showstopper.

非常感谢任何帮助.

推荐答案

我想我可能已经解决了这个问题.万一它帮助下一个人，...

I think I may have got around the problem. In case it helps the next guy, ...

• Identities 表记录了所有已知用户(在旧域和新域上).这意味着人们在工作项的分配给"等位置出现两次(如果他们的显示名称相同，则很难区分旧域用户名和新域用户名).但是，如果您设置 TFS 组以便只有新域用户在其中，那么您可以编辑工作项的工作项类型模板，并在分配对象"字段上设置允许值"规则以仅允许人员进入组(例如 [global]\Team Foundation Server Users)，则只有当前有效的用户名出现在分配给"下拉列表中.

• The Identities table records all known users (on the old and new domain). This means people appear twice in places like "Assigned to" on work items (and if their display names are the same, it's hard to differentiate the old and new domain usernames). However, if you set up your TFS groups so that only your new domain users are in them, then you can edit the work item type Templates for your work items and set the Allowed Values rule on the Assigned-To field to only allow people in the groups (e.g. [global]\Team Foundation Server Users), then only the currently valid usernames appear in the Assigned-to drop-downs.

容量页面中的问题是因为每次迭代都存储了创建时相关用户的列表.因此，经过几次迭代(当您到达下一个尚未使用"的条目时)，旧条目将消失.在中间的迭代中，您似乎必须两次输入容量值(在用户名的两个实例上)，但确保任何假期预订仅分配给两个实例之一，然后容量图似乎工作正常.

The problem in the capacities page is because each iteration stores a list of the relevant users at the time it was created. So after a few iterations (when you reach the next one that has not yet been "used"), the old entries will disappear. In the intervening iterations you seem to have to enter the capacity value twice (on both instances of the user's name) but make sure that any holiday bookings are only assigned to one of the two instances, and then the capacity graphs seem to work ok.

所以看起来过滤掉不需要的用户，然后等待几次迭代就足以解决问题.很高兴知道是否有任何方法可以清理数据库并清除所有不需要的用户引用.

So it looks like filtering out the unwanted users and then just waiting for a couple of iterations will be enough to clean away the problems. It'd still be nice to know if there is any way to ever clean up the database and flush out all the unwanted user references though.

这篇关于TFS 在域更改后删除重复的用户的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！