安装 Team Foundation Server
设置 TFS 2008 工作组版新实例的最佳实践是什么？
具体来说，限制如下：
- 必须安装在现有的 Windows Server 2008 64 位
- TFS 应用程序层仅是 32 位
我是否应该在 Windows Server 2008 或 2003 的虚拟实例中安装 SQL Server 2008、Sharepoint 和应用程序层（我是已经在运行 Hyper-V），还是使用主机操作系统上的数据库和虚拟机中的应用程序层来分割各层？
编辑：显然，不建议拆分图层
What are the best practices in setting up a new instance of TFS 2008 Workgroup edition?
Specifically, the constraints are as follows:
- Must install on an existing Windows Server 2008 64 bit
- TFS application layer is 32 bit only
Should I install SQL Server 2008, Sharepoint and the app layer in a virtual instance of Windows Server 2008 or 2003(I am already running Hyper-V) or split the layers with a database on the host OS and the app layer in a virtual machine?
Edit: Apparently, splitting the layers is not recommended
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
关于 TFS，您必须牢记的一件重要事情是，它喜欢将机器全部留给自己。 因此，如果您必须在 Hyper-V 上创建一个单独的实例，请使用经过验证的 Windows Server 2003 平台和 SQL Server 2005。
不过，我确信 Microsoft 已经做得很好，使其可以在 Windows Server 2008 和 SQL Server 2008 下运行通过这个较新的安装，您不会获得任何附加功能，并且目前尚未在野外得到验证。
因此，我的建议是坚持使用已知的内容，直到 TFS 的下一个版本发布。
另外，绝对不建议拆分层，尤其是在工作组版本中，您只能拥有 5 个许可用户。 这 5 个用户永远不会超出服务器的需求。 另外，我的建议是如果不需要，不要更新 Sharepoint。 在我的环境中，我们并没有真正使用 Sharepoint，所以我不理会它。 根据我的经验，Sharepoint 通常是 TFS 的大部分问题的根源。
One critical thing you has to keep in mind about TFS, is that it likes to have the machine all to it self. So if you have to create a separate instance on Hyper-V do it using the proven Windows Server 2003 platform with SQL Server 2005.
I am sure Microsoft has done a great job getting it to work under Windows Server 2008 and SQL Server 2008, however you don't get any additional features with this newer install and it is currently unproven in the wild.
So my recommendation is to stick with what is known until the next release of TFS comes out.
Also splitting the layers is definitely not recommended, especially in the workgroup edition where you will only be allowed to have 5 licensed users. Those 5 users will never exceed the server's needs. Also my recommendation is to not update Sharepoint if you don't need to. In my environment, we don't really use Sharepoint all that much, so I left it alone. Sharepoint is usually, in my experience, where most of the problems come from with TFS.
仅当超过 450 个用户时才需要进行分层。
我还建议将构建服务器放在完全独立的机器上。 文件系统的构建非常密集。 当 SQL Server 完全控制文件系统时，它的性能最佳 - 因此在同一台计算机上构建和 TFS 可能会在执行构建时产生性能问题。
也许可以通过适当的调整和单独的物理驱动器来缓解这种情况 - 但我认为从长远来看，使用一些旧硬件会更简单 - 或者在单独的主机上为您的构建启动一个小型虚拟机
Splitting the layers is only needed for more than 450 users.
I would also recommend having the Build Server on a completely seperate machine. Building is very file system intensive. SQL Server performs best when it has complete control of a file system - so having build and TFS on the same machine may create performance issues while builds are executing.
Perhaps this can be alleviated with proper tuning and seperate physical drives - but I'd think in the long run it would be a lot simpler to just either use some old hardware - or spin up a small virtual machine on a seperate host for your builds
我刚刚将我们的团队从 TFS 2005 升级到 TFS 2008。最困难的部分是将 SharePoint 2.0 升级到 3.0，所以如果您还没有安装 TFS 2008，我会确保首先执行此操作。我们还有其他一些困难，但它们要么与 SharePoint 升级有关，要么与我们使用售后策略包 - Scrum for TeamSystem 相关。 我们使用的是 SQL Server 2005，所以我无法解决 SQL Server 2008。至于分层，我们也没有这样做，因为我们在 Windows Server 2003 上运行，所有内容都在主机操作系统下运行。
I just upgraded our team to TFS 2008, from TFS 2005. The hardest part was upgrading SharePoint 2.0 to 3.0, so I would make sure to do that first, if you have not already installed TFS 2008. We had a couple of other difficulties, but they were all either related to the SharePoint upgrade, or to the fact that we were using an aftermarket Policy package - Scrum for TeamSystem. We are on SQL Server 2005, so I cannot address SQL Server 2008. As for splitting the layers, we did not do this either, as we are running on Windows Server 2003 and everything ran under the host OS.
这是我安装 TFS 2008 SP1 的秘诀。
在这种情况下没有域控制器，我们只是几个用户。 如果我再做一次，我会考虑更改我们的环境以使用活动目录域。
安装所有内容后，未生成报告。 找到此论坛帖子帮助解决了问题。
按顺序做事非常重要，下载安装指南并严格执行。 直到安装 SP1 后我才忘记安装 Team System Explorer，结果遇到了各种各样的问题。 再次安装 SP1 解决了这个问题。
This is my recipe for installing TFS 2008 SP1.
There is no domain controller in this scenario, we are only a couple of users. If I was to do it again, I would consider changing our environement to use a active directory domain.
After installing everything, reports were not generated. Found this forum post that helped resolve the problem.
It is very important to do things in order, download the installation guide and follow it to the letter. I forgot to install the Team System Explorer until after installing SP1 and ventured into all sorts of problems. Installing SP1 once more fixed that.