Team Foundation Server doesn't require Project Server, but if you want to use it, you must use a supported version. The version that you use has to have the Team Foundation Server extension for Project Server installed.
Tip |
---|
If multiple servers are running Project Server in a web farm, you must install these extensions on every application-tier server in that farm. For Project Server 2010, you must install the extensions on any web-tier servers in the farm, too. |
Supported versions, editions |
|
Authentication | NTLM is the recommended authentication. In SharePoint Server 2010, new authentication modes were introduced to SharePoint Products, but Team Foundation Server requires a web application that uses Windows-classic authentication. In SharePoint Server 2013, Microsoft deprecated Windows classic-authentication in favor of claims-based authentication. TFS 2012 supports both, but for claims-based authentication, the authentication provider must be NTLM. TFS 2012 only supports NTLM-based claims. |
¹ If you upgrade to Project Server 2013 from a Project Server 2010 installation that has been added to TFS, you have to perform a few extra steps to maintain the connection between TFS and Project Server. For more information, see this topic: Upgrade Microsoft Project Server 2010 to Microsoft Project Server 2013
² For its database backend, Project Server 2007 must use either SQL Server 2005 or SQL Server 2008 to work with Team Foundation Server.
Should you add Project Server to your current team project portal site?
Project Server is an extension of SharePoint Products. You can easily run Project Server on the same SharePoint Products farm you use for Team Foundation Server. If you run Project Server this way, you need to install both the Team Foundation Server extensions for SharePoint Products and the extensions for Project Server on the same server. Team Foundation Server recommends you use a web application running on port 80 for integration with SharePoint Products and you can use this same web application to host the Project Server projects. For example, the URL for team portal sites and Microsoft Project Web App (PWA) sites both hosted on a web application on port 80 might look something like these:
http://MOSS2010Server/sites/DefaultCollection/TFSProject
http://MOSS2010Server/pwa/EnterpriseProject
You can also run Project Server on its own SharePoint farm, separate from any farm where you might host team project portal sites. This would give you two SharePoint Products farm integrations in a single Team Foundation Server deployment.
Tip |
---|
Team Foundation Server has no topology requirements for Project Server. For performance reasons, we recommend you run Project Server on a server other than Team Foundation Server. If you want to set up a sandbox integration of Project Server and Team Foundation Server, you could install all the products on a single server for demonstrations or test purposes. |