It is so simple to set up Visual Studio Team Foundation Server
Setting up Visual Studio Team Foundation Server is easy, here is the guide how to set up Visual Studio Team Foundation Server Single Deployment:
1. Install your machine with Window Server 2003 R2 Standard Edition
- Install Window Server 2003 R2 on blank drive
- Assigned [HOSTNAME]
- Licensing Per Device, 20 concurrent connections
- Assign password to Admin
- Set GMT
- Network Settings , select Typical
- Member of Workgroup: [WORKGROUP]
- Install all items in the Critical Updates and Service Packs group, and reboot
- Install Internet Information Services for Team Foundation Server
- Go to Control Panel > Administrative Tools > Configure Your Server Wizard
- On the Welcome to the Configure Your Server Wizard page, click Next
- On the Preliminary Steps page, click Next
- On the Server Role page, click Application server (IIS, ASP.NET) , and then click Next
- On the Application Server Options page, select Enable ASP.NET, and then click Next (Do not select FrontPage Server Extensions)
- On the Summary of Selections page, click Next
- Click Finish to complete the wizard
Reboot
Logon as Administrator
Create three user accounts Required for Team Foundation Server Setup
- TFSSETUP: Used to run Team Foundation Server Setup, must be an administrator on Team Foundation Server computers
- TFSSERVICE: Used as the service account by Team Foundation Server Windows services (Code Coverage Analysis Service and TFSSchedulerService), and the SharePoint Timer Service
- TFSREPORTS: Used as the service account by SQL Server Reporting Services data sources
Logout and logon as TFSSETUP
Install Microsoft Office (Word, Excel, Project)
Install Microsoft SQL Server 2005 Standard or Enterprise Edition as the default instance of SQL Server (MSSQLSERVER)
- Accept the terms and conditions.
- Install Prerequisites
- On the Components to Install page, select all components except Notification Services
- click Advanced
- Under Database Service, click the icon for Replication and select Entire feature will be unavailable
- Under Client Components , all other items under Client Components, click the icon and select Entire feature will be unavailable, except Management Tools
- Under Documentation, Samples, and Sample Databases, you can optionally click the icon for Books Online and select Entire feature will be unavailable
- Click Next
- On the Instance Name page, select Default instance, and then click Next ( Team Foundation Server setup fails if you specify a named instance)
- On the Service Account page, select Use the built-in System account and from the list select Local system. In Start services at the end of setup, select all services: SQL Server, SQL Server Agent, Analysis Services, Reporting Services, and SQL Browser, and then click Next.
- On the Authentication Mode page, select Windows Authentication Mode, and then click Next
- On the Collation Settings page, select the appropriate collation for your language and then click Next
- On the Report Server Installation Options page, select Install the default configuration, and then click Next
- On the Error and Usage Report Settings page, you can optionally select Automatically send Error reports for SQL Server 2005 to Microsoft or your corporate error reporting server and Automatically send Feature Usage data for SQL Server 2005 to Microsoft, and then click Next
- Click Install
Install the hotfix KB912838 for Microsoft SQL Server 2005 available on the Team Foundation Server installation media. Or you can download the Service Pack from this site https://www.microsoft.com/downloads/details.aspx?familyid=CB6C71EA-D649-47FF-9176-E7CAC58FD4BC&displaylang=en
Install the hotfix KB913393 for Microsoft .NET Framework 2.0 available on the Team Foundation Server installation media
Install Windows SharePoint Services with Service Pack 2 for use with Team Foundation Server
- On the Type of Installation page, select Server Farm,
- Do not change Window SharePoint Services at this point
Reboot your machine
Install Team Foundation Server
- on the Autorun page that appears click Install Team Foundation Server, and then click Single-Server Installation
- Accept the terms and conditions, run through the System Health Check
- On the Service Logon Account page, use the Windows domain user account you created for the Team Foundation Server Service account (for example, Domain\TFSSERVICE)
- On the Reporting Logon Account page, use the account information for the Team Foundation Server Reporting account, and then click Next
- On the Specify Alert Settings page, select Enable Team Foundation Alerts
- Click Install
Reboot your computer
Install Team Explore
- On the autorun page of the Team Foundation Server setup wizard, click Install Team Explorer and start installation
Build Service does not installed during the Team Foundation Server Installation, you have to install it separately. You can find the setup file on the Team Foundation Server installation media, locate the \build folder and run setup.exe. On the Service Account page, use the Windows domain user account you created for the Team Foundation Server Service account (for example, Domain\TFSSERVICE).
You have successfully set up the Team Foundation Server Single Deployment.
Go to this site https://www.microsoft.com/downloads/details.aspx?familyid=e54bf6ff-026b-43a4-ade4-a690388f310e&displaylang=en to download the latest Visual Studio 2005 Team Foundation Installation Guide
Comments
Anonymous
July 25, 2006
To me its ok to install TFS in Workgroups rather than in company domain, especially when its hard to get support from system administrator. But it also depend on the size of the team and resources we have. The main reason is, because we don't want to depend on our tecnical staff to manage our TFS. We can create our local user name and password with the same user name and password with domain user name. So later on when users connect to TFS, they will not be prompted with username and password. That's awesome!Anonymous
May 17, 2009
PingBack from http://www.discussweb.com/server-management/13606-team-suite-tfs-installation.html#post40801Anonymous
June 09, 2009
PingBack from http://weakbladder.info/story.php?id=4521