Installing TFS
• Installing TFS is an arduous task that requires attention to detail and patience.
- Rushing through an installation will invariably cause the installation to fail due to a missed hot fix or
service pack.
- It can also be caused by tools being installed in the wrong order.
• When installing TFS, always download the latest installation guide.
- Perform a Google search for:
“Visual Studio 2005 Team Foundation Installation Guide”.
• This class won’t go into every detail about installing TFS; rather, it cover the most important pieces on
installing TFS.
- Always read the install documentation carefully and follow these instructions religiously.
• Install a fresh Windows 2003 R2 installation with the drive being formatted with NTFS.
- At minimum, you need Standard or Enterprise edition of Windows 2003 (not KN edition – intended for
Korea).
- Please note that the R2 edition has hot fixes and service packs preinstalled.
- R2 saves time and ultimately drive space because hot fixes and service packs need to downloaded before
they are installed.
• The server can be installed within its own workgroup or it can be added to a domain.
- When added to a domain, the domain must support native mode for Windows 2000 or Windows 2003.
- This means that the domain will not support Window NT 4 Server domain controllers.
• You need to on whether to install TFS in a single-server or dual-server deployment.
- This decision is based on the number of users who will be using your TFS installation.
• If your TFS installation will have over 400 users (that’s a lot!), you should use a dual server installation.
- In this case, SQL 2005 is installed on a separate machine.
- If less than 400, then consider using a single-server installation, which is much easier to install.
- Mind you, when you have a larger group of users (over 100), you’ll need to significantly scale up the
hardware to meet steeper requirements.
- For example, 2 GB of RAM with 30GB of free hard drive space; the more RAM and HDD space – the
better!
• Have an email server available to TFS.
- Whether it is Microsoft Exchange, the free hMailServer, or some other SMTP server, TFS runs best
when it can send notifications to team members.
• With dual server installation, getting the TFS server to authenticate against the database can be a real
hassle.
- Installation will take much longer, too.
- You may want to bring in Microsoft to help you with the installation.
• Don’t plan on installing other pieces of software on this server.
- Other software may install other functionality that may be incompatible with TFS.
• After installing Windows 2003, install IIS 6.0 and do not install FrontPage Server Extensions (FPSEs).
- FPSE’s are often used by Visual Studio or other tools (like FrontPage) for authoring web sites.
- They add extra security constraints not compatible with your TFS installation.
• Create necessary user accounts (TFSSETUP, TFSSERVICE, TFSREPORTS) with administrative
privileges.
- These accounts are extremely important for the functionality of TFS.
- Memorize these account names and record their passwords somewhere.
- For higher security, you may want to use different account names; hackers can read installation docs as
well as you can.
• Install SQL Server 2005 Standard or higher with Service Pack 1.
- Step through the installation wizard carefully, following the steps outlined in the installation, and install
SP1 to avoid having to install SQL 2005 hot fixes.
- SQL Server 2005 SP1 increases security and performance!
• Install WSS (Windows SharePoint Services) using the Server Farm option and do not configure it after
installation!
- WSS, not to be confused with SharePoint Portal Server, is free for Windows 2003 users as a separate
40+ MB download.
- It is used for the portal sites of the projects.
• Reboot the machine and defragment the hard drive.
- This ensures that installation has been completed, all Windows services are running and the hard drive is
running at optimum performance.
• Once completed, install TFS using the TFSSETUP account you created.
- During installation you are prompted for the other two accounts that you created earlier.
• Test you installation by navigating the Web browser on that server to:
http://localhost:8080/services/v1.0/Registration.asmx
- By invoking GetRegistrationEntries, you ensure that the portal is up and running.
- Notice that TFS uses port 8080 access to its Web services.
- Be sure clients can access this port, (not blocked by any firewalls) along with the other ports listed in
the installation instructions.
• If you are going to install Team Foundation Build, do so before installing TFS SP1.
- This course goes into greater detail later on about how to use Team Foundation Build.
• Install the Quiescence GDR hot fix, which allows TFS to shut down without losing data.
- This is a necessary (often overlooked) requirement for installing TFS SP1.
- TFS SP1 requires all server pieces to be shut down during its installation.
• Install TFS SP1.
- It should go smoothly without any trouble.
• Install Team Explorer off the TFS CD.
- Please note that the TFSSETUP account that you are logged in under grants access to TFS for you.
- Team Explorer gives you a user interface for projects, work items etc.
• Install Visual Studio 2005 SP1 to update Team Explorer.
- This grants your client (albeit, you’re on the server machine) new
• Installing TFS is an arduous task that requires attention to detail and patience.
- Rushing through an installation will invariably cause the installation to fail due to a missed hot fix or
service pack.
- It can also be caused by tools being installed in the wrong order.
• When installing TFS, always download the latest installation guide.
- Perform a Google search for:
“Visual Studio 2005 Team Foundation Installation Guide”.
• This class won’t go into every detail about installing TFS; rather, it cover the most important pieces on
installing TFS.
- Always read the install documentation carefully and follow these instructions religiously.
• Install a fresh Windows 2003 R2 installation with the drive being formatted with NTFS.
- At minimum, you need Standard or Enterprise edition of Windows 2003 (not KN edition – intended for
Korea).
- Please note that the R2 edition has hot fixes and service packs preinstalled.
- R2 saves time and ultimately drive space because hot fixes and service packs need to downloaded before
they are installed.
• The server can be installed within its own workgroup or it can be added to a domain.
- When added to a domain, the domain must support native mode for Windows 2000 or Windows 2003.
- This means that the domain will not support Window NT 4 Server domain controllers.
• You need to on whether to install TFS in a single-server or dual-server deployment.
- This decision is based on the number of users who will be using your TFS installation.
• If your TFS installation will have over 400 users (that’s a lot!), you should use a dual server installation.
- In this case, SQL 2005 is installed on a separate machine.
- If less than 400, then consider using a single-server installation, which is much easier to install.
- Mind you, when you have a larger group of users (over 100), you’ll need to significantly scale up the
hardware to meet steeper requirements.
- For example, 2 GB of RAM with 30GB of free hard drive space; the more RAM and HDD space – the
better!
• Have an email server available to TFS.
- Whether it is Microsoft Exchange, the free hMailServer, or some other SMTP server, TFS runs best
when it can send notifications to team members.
• With dual server installation, getting the TFS server to authenticate against the database can be a real
hassle.
- Installation will take much longer, too.
- You may want to bring in Microsoft to help you with the installation.
• Don’t plan on installing other pieces of software on this server.
- Other software may install other functionality that may be incompatible with TFS.
• After installing Windows 2003, install IIS 6.0 and do not install FrontPage Server Extensions (FPSEs).
- FPSE’s are often used by Visual Studio or other tools (like FrontPage) for authoring web sites.
- They add extra security constraints not compatible with your TFS installation.
• Create necessary user accounts (TFSSETUP, TFSSERVICE, TFSREPORTS) with administrative
privileges.
- These accounts are extremely important for the functionality of TFS.
- Memorize these account names and record their passwords somewhere.
- For higher security, you may want to use different account names; hackers can read installation docs as
well as you can.
• Install SQL Server 2005 Standard or higher with Service Pack 1.
- Step through the installation wizard carefully, following the steps outlined in the installation, and install
SP1 to avoid having to install SQL 2005 hot fixes.
- SQL Server 2005 SP1 increases security and performance!
• Install WSS (Windows SharePoint Services) using the Server Farm option and do not configure it after
installation!
- WSS, not to be confused with SharePoint Portal Server, is free for Windows 2003 users as a separate
40+ MB download.
- It is used for the portal sites of the projects.
• Reboot the machine and defragment the hard drive.
- This ensures that installation has been completed, all Windows services are running and the hard drive is
running at optimum performance.
• Once completed, install TFS using the TFSSETUP account you created.
- During installation you are prompted for the other two accounts that you created earlier.
• Test you installation by navigating the Web browser on that server to:
http://localhost:8080/services/v1.0/Registration.asmx
- By invoking GetRegistrationEntries, you ensure that the portal is up and running.
- Notice that TFS uses port 8080 access to its Web services.
- Be sure clients can access this port, (not blocked by any firewalls) along with the other ports listed in
the installation instructions.
• If you are going to install Team Foundation Build, do so before installing TFS SP1.
- This course goes into greater detail later on about how to use Team Foundation Build.
• Install the Quiescence GDR hot fix, which allows TFS to shut down without losing data.
- This is a necessary (often overlooked) requirement for installing TFS SP1.
- TFS SP1 requires all server pieces to be shut down during its installation.
• Install TFS SP1.
- It should go smoothly without any trouble.
• Install Team Explorer off the TFS CD.
- Please note that the TFSSETUP account that you are logged in under grants access to TFS for you.
- Team Explorer gives you a user interface for projects, work items etc.
• Install Visual Studio 2005 SP1 to update Team Explorer.
- This grants your client (albeit, you’re on the server machine) new
TFS Installation
Table of Contents
Copyright (c) 2008. Intertech, Inc. All Rights Reserved. This information is to be used exclusively as an
online learning aid. Any attempts to copy, reproduce, or use for training is strictly prohibited.
online learning aid. Any attempts to copy, reproduce, or use for training is strictly prohibited.
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
Courseware
Training Resources
Tutorials