Team Foundation Server Installation Guide
Prerequisites and Requirements
To successfully deploy Team Foundation Server, you must meet the OS requirements mentioned below. Hardware recommendation are listed below, please remember these are just a recommendation. As always, larger companies need better hardware. Sooner or later you might need more than one server to allocate the load.
OS Requirements:
- All x86 version of Server 2003 R2 SP2
- Server 2008 SP2
- Server 2008 R2 RTM
- Server 2008 R2 SP1
Note that Team Foundation Server do not support the Windows Server 2008 R2 server core OS.
Hardware Requirements:
Network port requirements:
Tier and service |
Protocol |
Port |
Application tier – Web Services |
HTTP/HTTPS |
8080/443* |
Application tier – Windows SharePoint Services Administration |
HTTP |
17012* (if it was installed with Team Foundation Server); otherwise randomly generated |
Application tier – Windows SharePoint Services and Reporting Services |
HTTP Windows Management Instrumentation (WMI) service (required during installation to specify and verify the URLs for reporting services) |
80* Dynamic port |
Build computer – remote access from application-tier server |
SOAP over HTTP |
9191* |
Data tier |
MS-SQL TCP |
1433* |
Team Foundation Server Proxy - client to proxy |
HTTP |
8081* |
Team Foundation Server Proxy - proxy to application tier |
HTTP/HTTPS |
8080/443* |
Client tier - Reporting Services |
HTTP |
80* |
Client tier - Web services |
HTTP/HTTPS |
8080/443* |
Application tier to build controller |
SOAP over HTTP |
9191* |
Application tier to build agent |
SOAP over HTTP |
9191* |
Build controller to application tier |
HTTP/HTTPS |
8080/443 |
Build agent to application tier |
HTTP/HTTPS |
8080/443 |
Test controller to application tier |
HTTP/HTTPS |
8080/443* |
Application tier to test controller |
.NET remoting |
6901* |
Application tier to Domain Name System (DNS) |
DNS Dynamic Update |
|
Application tier – Virtual Machine Manager |
HTTP |
8100 |
Test controller to test agent |
.NET remoting |
6910* |
Test agent to test controller |
.NET remoting |
6901* |
Build controller to build agent |
SOAP over HTTP |
9191 |
Lab agent to lab agent in an isolated environment |
TCP sockets |
9050 |
Build agent to build controller |
SOAP over HTTP |
9191 |
Virtual Machine Manager Administrator Console – Virtual Machine Manager |
HTTP |
8100 |
Virtual Machine Manager– Virtual Machine Manager hosts |
Windows Remote Management (WinRM) to perform actions Background Intelligent Transfer Service (BITS) to transfer data |
80 to perform actions 443 to transfer data |
Virtual Machine Manager– Virtual Machine Manager library server |
WinRM to perform actions BITS to transfer data |
80 to perform actions 443 to transfer data |
Application tier – Virtual Machine Manager hosts |
Distributed Component Object Model/Windows Management Interface (DCOM/WMI) communication to transfer data |
135 Dynamic ports in the range 49152 to 65535. |
Client tier – Virtual Machine Manager hosts |
Host-based connection to the virtual machine. For more information about host-based connections, see How to: Connect to a Virtual Environment. |
2179 to perform host-based connections. |
Install Team Foundation Server
- Depending on OS you are running, run either the x86 or the x64 setup.exe from the Team Foundation Server DVD. This DVD ISO can be downloaded on VL website or MSDN site.
- On the firstWelcome page, click “Next”.
- On the License Terms, read the terms of the license carefully and then click Next.
- CheckTeam Foundation Server, and click Install.
- Once completed reboot the server
Once installed, let’s configure it:
- Click Start>All Programs>Microsoft Team Foundation Server 2010>Team Foundation Administration Console. You will see The Team Foundation Administration Console
- Choose Application Tier> click Configure Installed Features. You will see the Team Foundation Server Configuration tool.
Configure Team Foundation Server using SQL Express
- Start Team Foundation Server Configuration tool, choose Basic>Start Wizard.
- Ignore the welcome screen and click next.
- Click SQL Express to host the configdb on an instance of SQL Server Express, click next. Test the connectivity.
- Then validates your configuration.
- Click Configure and then close.
