TFS 2010 中的服务帐户是什么？
我是 TFS 2010 的新手。我已将我的 PC 设置为服务器。我需要将客户端计算机与该服务器连接。我已在 TFS 控制台中添加了一个服务帐户。客户端计算机与此帐户连接。
现在，我的问题是，服务帐户是否用于连接客户端与服务器？
谁能解释一下这个帐户的用途吗？
我还需要知道如何找到（或设置）TFS 管理员？
I am very new in TFS 2010. I have setup my PC as server. I need to connect the client machine with this server. I have added a Service Account in TFS console. The client machine are connected with this account.
Now, my question is that, is the Service Account is intended to connect the client with server?
Can anyone explain me the purpose of this account?
Also I need to know, how to find(or setup) the TFS admin?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
您指的是安装指南中的“TFSSERVICE”服务帐户吗？该帐户用于运行与 TFS 相关的各种服务，例如 TFS 任务计划程序。它应该具有机器上可能的最低权限。
客户端不应使用服务帐户连接到服务器，他们应该使用自己的帐户，您授予该帐户对 TFS 中相关存储库的访问权限。如果您将所有客户端连接到服务帐户，您如何知道谁签入了每个变更集？
您可能会在此处找到安装使用指南。请参阅标题为“安装 Team Foundation 组件所需的帐户”的部分。
如果您使用域，则应该能够按照本文了解权限在 TFS 中的工作原理。您可以从 Visual Studio 中的“团队资源管理器”窗格向资源分配权限。
如果您在工作组中使用 TFS，则情况会略有不同，因为您需要为用户设置本地帐户。请参阅本文。
Are you referring to the "TFSSERVICE" service account from the installation guide? That account is used to run various services related to TFS, for example the TFS Task Scheduler. It should have the minimum privileges possible on the machine.
The client should not connect to the server with a service account, they should be using their own account which you grant access to the relevant repositories in TFS. If you connect all clients with the service account, how will you know who checked in each changeset?
You might find the installation guide of use which can be found here. See section entitled "Accounts Required for Installation of Team Foundation Components".
If you are using a domain, you should be able to follow the instructions in this article for how permissions work in TFS. You can allocate permissions to resources from the Team Explorer pane within Visual Studio.
If you're using TFS in a workgroup then it's a little different as you need to set up local accounts for your users. See this article.