Installing the December CTP Release of Visual Studio Team System

Article
01/04/2007

David C. Bost
Solution Partners, Inc.

February 2005

Summary: Use this step-by-step guide to install and configure the latest release of Team System in a virtual environment using Virtual PC 2004. (26 printed pages)

**Requirements **Windows XP with Virtual PC 2004 or Windows Server 2003 with Virtual Server 2005

Introduction
Setting Up Virtual PC for the Team Foundation Tiers
Setting Up the Team Foundation Data Tier
Setting Up the Team Foundation Application Tier
Setting Up the Team Foundation Client Tier
Setting Up Visual Studio with Team Foundation Functionality
Additional Resources

Introduction

This guide provides a step-by-step process of how to install and configure the December CTP release in a virtual environment using Virtual PC 2004. Virtual PC 2004 provides the ability to install the multiple-tiers on a single physical server. The December CTP release requires a minimum of two machines. One machine will host the Team Foundation data tier components, and the other machine is responsible for hosting the application tier components. The virtual environment gives you the ability to install the multiple tiers on one physical machine. It must be noted that this guide is purely for creating a testing and evaluation environment of Team Foundation.

The guide begins by creating a base Virtual Machine (VM) image to use in the creation of the three virtual machines representing each tier of Team Foundation—the Data tier, the Application tier, and the Client tier. From there, the guide steps through the process of creating an Active Directory domain to support Team Foundation Server, as well as the process of installing the necessary components for each Team Foundation tier.

In a virtual environment, such as Virtual PC, the operating system that hosts the Virtual PC is called the host. The virtual machines are referred to as guests. With two separate virtual machines required, the host machine will require a significant amount of memory to share across the guest virtual machines. A single host machine is not required to host the three guest virtual machines. All that is required is that each virtual machine is allowed to communicate with one another over the network.

If the host operating system is Windows XP, then Virtual PC 2004 can be used as the virtual environment. For Windows Server 2003, use Virtual Server 2005. This guide presents the steps to using Virtual PC 2004 on Windows XP, but the steps for Virtual Server 2005 are easily transferable. This guide is not intended to be a substitute for reading the Virtual PC and Virtual Server documentation. You may find additional information on how to install and administer each product by visiting the following links:

Setting Up Virtual PC for the Team Foundation Tiers

**Requirements **Windows XP with Virtual PC 2004 or Windows Server 2003 with Virtual Server 2005

There are three separate tiers that make up Microsoft Visual Studio Team System—the Data tier, the Application tier, and the Client tier. Due to incompatibilities between the builds of .NET 2.0 used by Microsoft SQL Server 2005 Beta 2 and the December CTP release of Visual Studio Team System, the Data tier and Application tier must be installed on separate computers. In our virtual environment, we will define two different guest virtual machines (VM). One guest VM hosts the Data tier where the other guest VM hosts both the Application tier and the Client tier.

**Note **The client tier can optionally be installed in its own virtual machine. If you plan on installing all the tiers on one host machine, it is recommended to install the Application tier and Client tier on the same guest virtual machine. This is only a recommendation for purposes of evaluation Visual Studio Team System and is not a recommendation for a production environment.

The guest virtual machines defined for the Data tier and Application tier must be installed with Windows Server 2003 (Enterprise or Standard editions). To setup a virtual environment to host the multiple tiers of Team Foundation, the following Virtual Machines are recommended:

Virtual Machine	Purpose
Data Tier	Host the Team Foundation data tier components along with SQL Server 2005. This virtual machine will also serve as our Active Directory server.
Application Tier	Host the Team Foundation application tier components. This virtual machine has the option of also hosting the Team Foundation client components.
Client Tier (optional)	Host the Team Foundation client tier components including Visual Studio 2005.

The Team Foundation installation guide recommends 1 GB of memory available for both the Team Foundation data tier and the application tier. When creating your virtual machines, you have the option to specify the amount of memory available to the virtual machine. If the host machine doesn't have enough memory to share with the virtual machines, you can either spread the virtual machines on other available host machines or decrease the memory settings for your virtual machines. Please note that decreasing the available memory for the Team Foundation servers may have a negative effect on performance. One of the benefits of a virtual environment is the ability to modify memory requirements after the virtual machine has been created.

It is recommended that if you run all of the virtual machines on a single host machine that the host machine has at least 2 GB of memory installed with the following memory configurations defined for the guest virtual machines:

Virtual Machine	Recommended Memory Allocation
Application/Client Tier	900 MB
Data Tier	600 MB

On a host machine with 2 GB of memory available, 500 MB will be allocated for the host OS. It is possible to allocate less memory for the guest virtual machines, but doing so can lead to unpredictable results.

Creating the Virtual Machines

The Team Foundation data and application tiers require Windows Server 2003. In a virtual environment, you can create a base operating system along with the necessary service packs applied and then copy that image to reuse for each of the tiers. This saves you from having to do a complete operating system install for each tier.

Setting Up a Base Virtual Machine

The following steps guide you through creating a base virtual machine for the Team Foundation tiers.

Create a Virtual Machine in Virtual PC. Select Windows Server 2003 as the operating system and keep the recommended settings in the wizard.
Install Windows Server 2003 with all of the defaults in the Virtual Machine.
After Windows Server 2003 setup has completed, run the Virtual Machine.
In the Virtual Machine, visit Windows Update and install all the items in the Critical Updates and Service Packs group.
In the Virtual Machine, download the Sysprep tool to a local folder. The Sysprep tool download package can be found at https://support.microsoft.com/kb/838080.
Extract the cab file and run sysprep.exe, which should result in a dialog box similar to the one shown in Figure 1.

Figure 1. System Preparation Tool dialog box

Verify that Don't reset grace period for action is unchecked and then click Reseal.

**Note **This virtual machine will serve as our base image in which you will duplicate the virtual hard disk file (.vhd) to use for the different Team Foundation tiers. Because the tiers will be joining a domain, each of the operating systems requires a unique Security Identifier (SID). Sysprep is a tool that triggers the operating system to perform a mini-setup when it's first loaded to modify settings, such as computer name, SID generation, and other configuration details.
After the virtual machine shuts down, close the Virtual PC Console.
Open the folder where the base virtual machine image is located.
Copy the base virtual machine's virtual hard disk file (.vhd) and name it TFDATA.vhd.
Make another copy of the base virtual machine's virtual hard disk file (.vhd) and name it TFAPP.vhd.
If you plan on creating a virtual machine for the client tier, copy the base virtual machine's virtual hard disk file (.vhd) and name it TFCLIENT.vhd.
Open the Virtual PC Console and create the virtual machines representing each of the tiers. On the Virtual Hard Disk Options page, Select an existing virtual hard disk and then provide the location of the respective virtual hard disk file.
The Virtual PC Console should resemble the dialog box in Figure 2.

Figure 2. Virtual PC Console dialog box

When you launch each of the tiers, the operating system will step you through a mini-setup process to generate a new Security Identifier and various other configuration details. Note that:

Virtual Machines have the ability to share the network card of the hosting machine. Once the tiers have been defined in the Virtual PC Console, use the Settings option to modify the networking requirements for each tier.
For this guide, each virtual machine must be able to communicate with one another over a TCP/IP network. For the purposes of simplicity, this guide does not incorporate a DHCP server. Each of the setup guides incorporates a static IP address assignment.

Setting Up the Team Foundation Data Tier

For this guide, the data tier serves two purposes. The one obvious purpose is to host the Team Foundation data components. The data components require that SQL Server 2005, SQL Reporting Services, and Internet Information Services be installed. The second purpose of the data tier is to host our Active Directory server. If you have access to another Active Directory outside of your virtual machines, you may use that as well. If you do decide to use an Active Directory instance outside of the virtual machines, you may skip the Add Active Directory to the Data Tier step.

**Data Tier Prerequisites **Windows Server 2003 Enterprise Edition or Standard Edition, Internet Information Server (IIS) v6.0, and Microsoft SQL Server 2005

Add Active Directory to the Data Tier

From the Virtual PC Console, click on the Data Tier virtual machine to highlight it, and then click Start.

**Note **If you haven't already run the data tier after the sysprep process, you will be required to go through a short setup wizard.
Install Active Directory and DNS on the data tier.

**Note **For help in installing active directory and DNS, please review Configuring Your Server as a Domain Controller.

Team Foundation Server User Accounts

The Team Foundation setup requires two Windows 2003 Active Directory domain accounts be created. These accounts are defined in the table below.

User logon name	Description
TFSSETUP	Used to run the Team Foundation server setup. This account has administrative access on each of the tiers.
TFSSERVICE	Used to run the services and application pools required by Team Foundation.

**Note **These are sample names. If you choose to provide different names, be sure to substitute those names where appropriate in the rest of the document.

Creating the Team Foundation Domain Accounts

Click the Start button, point to All Programs, point to Administrative Tools, and then click Active Directory Users and Computers.
Click the + next to the domain name (TEAMSYSLAB.com) to expand it.
Right-click the Users folder, point to New, and then click User.
Type TFS for the first name and Setup for the last name.
Type TFSSETUP in the User logon name box.
Click Next.
Provide a password for Password and Confirm password.
Set the password options as shown in the following table.

Option Check box state

User must change password at next logon Cleared

User cannot change password Selected or cleared

Password never expires Selected

Account is disabled Cleared
Click Next, and then click Finish.
Repeat steps 3 through 9 to create the TFSSERVICE user account. Use Service for the last name and TFSSERVICE for the user logon name.

Option	Check box state
User must change password at next logon	Cleared
User cannot change password	Selected or cleared
Password never expires	Selected
Account is disabled	Cleared

Adding the Team Foundation Domain Accounts to the Local Administrators Group

For this release, the TFSSETUP and TFSSERVICE accounts need to be added to the local Administrators group of the data tier. The following steps outline how to add the new user accounts to the Administrators group.

**Note **Adding users to the local Administrators group on a domain controller is different than a non-domain controller machine. If you didn't create the Active Directory domain controller on the data tier, your steps will vary. You may access the local Administrators group on a non-domain controller machine by selecting Start -> Administrative Tools -> Computer Management -> Local Users and Groups -> Groups.

In the left pane of the Active Directory Users and Computers window, click the Builtin folder.
In the right pane, double-click the Administrators group.
Click the Members tab, and then click Add.
Click Advanced, and then click Find Now.
Select the TFS Service and TFS Setup users while holding down the Ctrl key while clicking each name. Click OK while the accounts are highlighted.
Click OK in the Select Users, Contacts, Computers, or Groups dialog to add the Team Foundation accounts to the Administrators group.
Click OK to close the Administrators Properties sheet.

Install Internet Information Services on the Team Foundation Data Tier Using the Configure Your Server Wizard

Follow these steps to install the Internet Information Server (IIS) 6.0 on the Team Foundation Server data tier.

Click the Start button, point to All Programs, point to Administrative Tools, and then click on 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, select Application Server (IIS, ASP.NET), and then click Next.
On the Application Server Options page, select Enable ASP.NET, and then click Next.
On the Summary of Selections page, click Next.

**Note **You may be prompted for your Windows Server 2003 installation media.
Click Finish to complete the wizard.
Visit Windows Update and install all the items in the Critical Updates and Service Packs group.

Install Microsoft SQL Server 2005 on the Team Foundation Data Tier

Follow these steps to install Microsoft SQL Server 2005 on the Team Foundation Server data tier.

Locate and run the installation file (Setup.msi) in the root folder of the SQL Server 2005 installation media.
On the End User License Agreement page, review the license agreement. If you accept the terms and conditions, select I accept the licensing terms and conditions and click Next.
On the SQL Server Component Update page, click Install. After the components are installed successfully, click Finish.
After the Microsoft SQL Server 2005 Installation Wizard starts, click Next.
On the System Configuration Check page, check the status of the required actions and follow the guidance on this page until all actions achieve Success status. After all actions achieve Success status, click Continue to start the installation.

**Note **It may take a few moments for the installer to start.
On the Registration Information page, fill in the registration information and click Next.
On the Components to Install page, select all of the components on this page, and then click Next.
On the Instance Name page, select Default Instance, and then click Next.
On the Service Account page, select Use the Local System account, select Auto-start service, and then click Next.
On the Authentication Mode page, select Mixed Mode, type a password for the sa login, and then click Next.
On the Collation Settings page, make no changes to the default options, and click Next. Select Yes when a message appears stating, "SQL collation cannot be used for Analysis Services. Do you want to use best match collation Latin1_General_CI_AS for Analysis Services?"
On the Report Server Virtual Directories page, keep the default directory settings, and then click Next.
On the Report Server Database Setup page, keep the default settings, and then click Next.
On the Report Server Delivery Settings page, type the location of an SMTP server through which SQL Server 2005 can relay e-mail messages and the address from which the messages should appear to be sent, and then click Next.
On the Error Reporting page, you can optionally select Automatically send fatal error reports to Microsoft, and then click Next. If no Internet connectivity is available in the guest virtual machine, than do not select this option.
On the Ready to Install page, review the installation settings, and then click Install.

**Note **The installation wizard may disappear for a moment.
On the Setup Progress page, you can monitor the installation status of each component. After setup is finished, click Next.
Click Finish to exit the wizard.
When a message appears that states, "The requested operation is successful. Changes will not be effective until the system is rebooted.", click OK and then restart the computer.

**Note **Depending on system configuration, it may take few minutes for this message to appear after the exiting the installation wizard. If the message does not appear after five minutes, restart the computer.
After the computer restarts, log on as the Administrator, click Start, point to Microsoft SQL Server 2005, and then click SQL Server Management Studio.
Connect to the SQL Server instance you just installed.

**Tip **The Connect to Server dialog box should contain the needed connection information. Click Connect to join using this default information.
In Object Explorer, right-click the server object, and then click Properties from the context menu.
In the Server Properties window, select the Autostart Services page.
Select the SQL Server Agent check box (it should be checked already by default).
Select the Security page.
Click Failed Logins Only, and then click OK.
Close SQL Server Management Studio.

Install Team Foundation Server on the Data Tier

Follow these steps to install the Team Foundation data tier components.

Log on to the data tier using the Team Foundation Server setup account (Domain\TFSSETUP) account.
Click Start, point to Control Panel, point to Administrative Tools, and then click Services.
Verify that the following services are running with a status of Started:
- SQL Server (MSSQLSERVER)
- SQL Server Agent (MSSQLSERVER)
- Analysis Services (MSSQLSERVER)
Start the Visual Studio 2005 Team Foundation Data Tier installation from the autorun page, or locate and run the installation file (Setup.msi) in the \vstf\dt folder on the installation media. Then the Visual Studio Team Foundation Setup Wizard starts.
On the Welcome to Setup page, click Next.
On the End-User License Agreement and Product Key page, review the license agreement. If you accept the terms and conditions, select I accept the terms of the License Agreement, and then click Next.
On the Team Foundation Web Services Application Pool Identity page, type the Windows domain account you created for the Team Foundation Server service account (Domain\TFSSERVICE) in the Account name text box, and then click Next.
On the Ready to Install page, click Install.
On the Installing Components page, you can monitor the installation of the Team Foundation data tier components.
On the Setup Completed Successfully page, click Exit.

Setting Up the Team Foundation Application Tier

The application tier is responsible for hosting the Team Foundation application tier components.

**Application Tier Prerequisites **Windows Server 2003 Enterprise Edition or Standard Edition, Internet Information Server (IIS) v6.0, and Microsoft Windows Sharepoint Services 2.0

Add the Application Tier to the Active Directory Domain

From the Virtual PC Console, click on the Data Tier virtual machine to highlight it, and then click Start.

**Note **If you haven't already ran the data tier after the sysprep process, you will be required to go through a short setup wizard.
Log on to the application tier virtual machine using the local Administrator account.
Click the Start button, point to Control Panel, point to Network Connections, and then click Local Area Connection.
In the Local Area Connection Status dialog, click the Properties button.
Under the This connection uses the following items section, click Internet Protocol (TCP/IP), and then click the Properties button.
Select Use the following IP address, and then type 10.0.0.3 for the IP address. Press the tab key twice, and then type 10.0.0.1 for the Default gateway. Type 10.0.0.2 (the DNS server created on the data tier) for the Preferred DNS server, and then click OK.
On the Local Area Connection Properties dialog, click Close.
On the Local Area Connection Status dialog, click Close.

**Tip **To verify you can communicate with the data tier, open a command prompt and ping the data tier by its machine name. If the data tier isn't responding, verify that the data tier virtual machine is running.
Click the Start button, point to Control Panel, click System.
Click the Computer Name tab, and then click the Change button.
In the Computer Name Changes dialog, select the Domain option under Member of.
Type your Active Directory domain name in the Domain text box, and then click OK.
You will be prompted to provide a login with permission to join the domain. Type the domain administrator's login (Domain/Administrator) and password, and then click OK.
Click OK to close the welcome message. Click OK when prompted with the You must restart this computer for the changes to take effect message.
Click OK to close the System Properties dialog, and then click Yes on the System Settings Change message to restart the application tier.

Add the Team Foundation Server Domain Accounts to the Local Administrators Group on the Application Tier

Log on to the application tier virtual machine using the local Administrator account.
Point to the Start button, point to Administrative Tools, and then click Computer Management.
In the left pane, under System Tools, click the + next to Local Users and Groups, and then click on the Groups folder.
In the right pane, double-click Administrators.
In the Administrator Properties dialog, click Add.
Click Advanced.
When presented with a login screen, type in the domain's Administrator (Domain\Administrator) username and password.
Click Find Now.
Select the TFS Service and TFS Setup users while holding down the Ctrl key while clicking each name. Click OK while the accounts are highlighted.
Click OK in the Select Users, Contacts, Computers, or Groups dialog to add the Team Foundation accounts to the Administrators group.
Click OK to close the Administrators Properties sheet.

Install Internet Information Server on the Team Foundation Application Tier Using the Configure Your Server Wizard

Follow these steps to install the Internet Information Server (IIS) 6.0 on the Team Foundation Server application tier.

Click the Start button, point to All Programs, point to Administrative Tools, and then click on 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, select Application Server (IIS, ASP.NET), and then click Next.
On the Application Server Options page, select Enable ASP.NET, and then click Next.
On the Summary of Selections page, click Next.

**Note **You may be prompted for your Windows Server 2003 installation media.
Click Finish to complete the wizard.
Visit Windows Update and install all the items in the Critical Updates and Service Packs group.

Install Microsoft Windows Sharepoint Services for the Team Foundation Application Tier

Microsoft Windows Sharepoint Services are required on the Team Foundation application tier to host your project sites. Follow these steps to install Microsoft Windows Sharepoint Services on the application tier.

Download Microsoft Windows Sharepoint Services 2.0 with Service Pack 1 and save the file to a local folder on the application tier's virtual machine.
Run the downloaded self-extracting installer file (stsv2.exe).

**Note **Windows Sharepoint Services require an NTFS file system.
On the End-User License Agreement page, review the license agreement. If you accept the terms, select I accept the terms in the License Agreement, and then click Next.
On the Type of Installation page, select Typical Installation, and then click Next.
On the Summary page, click Install.

When the installation is complete, a Web browser opens and displays the home page of the Windows Sharepoint Services top-level site.
Visit Windows Update and install all the items in the Critical Updates and Service Packs group.

Install the Team Foundation Server Application Tier Components

The Team Foundation data tier components must be installed prior to installing the application tier components.

On the data tier virtual machine, verify that the SQL Server services are running.

Click Start, point to Control Panel, point to Administrative Tools, and then click Services. Verify that the following services are running with a status of Started:
- SQL Server (MSSQLSERVER)
- SQL Server Agent (MSSQLSERVER)
- Analysis Services (MSSQLSERVER)
  
  If any of these services aren't running, attempt to start them manually. The application tier setup routine requires access to these services.
Log on to the application tier using the Team Foundation Server setup account (Domain\TFSSETUP).
Start the Visual Studio 2005 Team Foundation Data Tier installation from the autorun page, or locate and run the installation file (Setup.msi) in the \vstf\at folder on the installation media.

The Visual Studio Team Foundation Setup Wizard starts.
On the Welcome to Setup page, click Next.
On the End-User License Agreement and Product Key page, review the license agreement. If you accept the terms and conditions, select I accept the terms of the License Agreement, and then click Next.
On the Destination Folder and Database Server page, keep the default installation page in the Destination folder text box. Type the name of the database tier machine name in the Database Tier Computer text box TFDATATIER), and then click Next.
On the Team Foundation Web Services Application Pool Identity page, type the Windows domain account you created for the Team Foundation Server service account (Domain\TFSSERVICE) in the Account name text box and the password in the Password text box, and then click Next.
On the Directory Security page, accept the default setting (Use open communication), and then click Next.
On the SMTP Mail Server Information page, click Next.

**Note **In the December CTP release, Team Foundation alerts are not available. Check the Ask Burton site (https://blogs.msdn.com/askburton/) for a future workaround.
On the Ready to Install page, click Install.
On the Installing Components page, you can monitor the installation of the Team Foundation data tier components.

**Note **The application tier may need to restart during the installation of the components. After the restart, be sure to log on as the Team Foundation Server setup account (Domain/TFSSETUP).
On the Setup Completed Successfully page, click Exit.

Setting Up the Team Foundation Client Tier

The following provides the guidance to setting up the Team Foundation client tier.

Add the Client Tier to the Active Directory Domain

Open the Virtual PC Console.
From the Virtual PC Console, click on the Client Tier virtual machine to highlight it, and then click Start.

**Note **If you haven't already ran the client tier after the sysprep process, you will be required to go through a short setup wizard.
Log on to the client tier virtual machine using the local Administrator account.
Click the Start button, point to Control Panel, point to Network Connections, and then click Local Area Connection.
In the Local Area Connection Status dialog, click the Properties button.
Under the This connection uses the following items section, click Internet Protocol (TCP/IP), and then click the Properties button.
Select Use the following IP address, and then type 10.0.0.4 for the IP address. Press the tab key twice, and then type 10.0.0.1 for the Default gateway. Type 10.0.0.2 (the DNS server created on the data tier) for the Preferred DNS server, and then click OK.
On the Local Area Connection Properties dialog, click Close.
On the Local Area Connection Status dialog, click Close.

**Tip **To verify you can communicate with the data tier, open a command prompt and ping the data tier by its machine name (TFDATATIER). If the data tier isn't responding, verify that the data tier virtual machine is running and that your network settings are correct.
Click the Start button, point to Control Panel, click System.
Click the Computer Name tab, and then click the Change button.
In the Computer Name Changes dialog, select the Domain option under Member of.
Type your Active Directory domain name in the Domain text box (TEAMSYSLAB), and then click OK.
You will be prompted to provide a login with permission to join the domain. Type the domain administrator's login (Domain/Administrator) and password, and then click OK.
Click OK to close the welcome message. Click OK when prompted with the You must restart this computer for the changes to take effect message.
Click OK to close the System Properties dialog, and then click Yes on the System Settings Change message to restart the application tier.

Install the Client Tier Prerequisites

Install on an operating system that meets the system requirements for Visual Studio 2005 as specified in the Visual Studio 2005 Readme.

**Note **If you're installing the Team Foundation client tier on the Team Foundation application tier, complete the installation of the application tier prior to installing the client tier components.
If not installing on the Windows Server 2003, download and install the Microsoft .NET Framework 1.1. You can download the Microsoft .NET Framework 1.1 at https://www.microsoft.com/downloads/details.aspx?FamilyID=262d25e3-f589-4842-8157-034d1e7cf3a3&DisplayLang=en.
Visit Windows Update and install all the items in the Critical Updates and Service Packs group.
Install Microsoft Office Excel 2003 and Microsoft Office Word 2003.

**Note **If you choose to install Microsoft Office Excel 2003 and Microsoft Office Word 2003 using a different type of installation (such as Custom Install), you must be certain to install the .NET Programmability Support feature for both Microsoft Office Excel 2003 and Microsoft Office Word 2003. This feature installs the Primary Interop Assemblies that allow programmability with the .NET Framework and is required for integration with Team Foundation.
Install Microsoft Project Professional 2003.

**Note **If you choose to install Microsoft Project Professional 2003 using a different type of installation (such as Custom Install), you must be certain to install the .NET Programmability Support feature for Microsoft Office Project for Windows. This feature installs the Primary Interop Assemblies that allow programmability with the .NET Framework and is required for integration with Team Foundation.
Visit Windows Update and install all the items in the Critical Updates and Service Packs group.
Visit Office Update and install any available updates.

Internet Explorer Enhanced Security Configuration

If you are installing the Team Foundation client tier on the same virtual machine as the Team Foundation application tier, you need to apply Windows 2000 default Internet Explorer security settings to enable Team Foundation functionality for the client. To apply Windows 2000 default Internet Explorer security settings on Windows Server 2003, you must disable Internet Explorer Enhanced Security Configuration.
Click the Start button, point to Control Panel, and then click Add or Remove Programs.
On the Add or Remove Programs dialog, click Add/Remove Windows Components.
Select Internet Explorer Enhanced Security Configuration, click the check box to clear the selection, and then click Next.
Click Finish when the wizard is completed.
Restart Internet Explorer to apply the changes.

**Note **Removing Internet Explorer Enhanced Security Configuration increases your server's exposure to potential attacks from malicious Web-based content.

Install the Team Foundation Server Client Tier: Visual Studio 2005 Team Suite

Follow this procedure to install the Visual Studio Team Suite on the client tier virtual machine.

Start the Visual Studio 2005 Team Suite installation from the autorun page, or locate and run the installation file (Setup.msi) in the \vs folder on the installation media.

The Visual Studio Team Suite Setup Wizard starts.
On the setup selection page, click Install Visual Studio 2005 Beta 2.
On the Welcome to the Microsoft Visual Studio 2005 beta 2 installation wizard page, click Next.
On the End-User License Agreement page, review the license agreement. If you accept the terms and conditions, select I accept the terms of the License Agreement, and then click Next.
On the Select features to install page, select Default, and then click Next.

**Note **If you choose to perform a Custom installation, you must be certain to select Team Foundation Client and the options page to use Team Foundation Server functionality.
On the Installing Components page, you can monitor the installation of the Team Suite components.
When the setup wizard completes installing Microsoft .NET Framework 2.0 Beta 2, click Restart Now to restart the operating system.
Log on to the client tier using the same user account you used to install the client tier components.

The setup wizard will continue installing the rest of the client tier components.
Once the installation wizard has completed, click Finish to exit the wizard.
On the Visual Studio 2005 Beta 2 Setup window, you can optionally choose to Install Product Documentation the documentation or click Exit.

Setting Up Visual Studio with Team Foundation Functionality

To create a team project, the user must have a number of security settings in place. This user, typically a project manager or architect, must be a member of the Namespace Administrators Group, a Sharepoint Administrator (to create the project site), and a Content Manager on the SQL Server 2005 Reporting server.

Create a Project Administrator Account

Follow these steps to setup a project administrator user account and set the required permissions.

Create a project administrator account (PROJADMIN) in the Active Directory.
Add the project administrator to the Namespace Administrators Group.

**Note **There are two ways to add users to the Namespace Administrators Group. The first is to use the GSSUTIL installed on the application tier. The other is to use the Team Foundation client to manage the users. To use the Team Foundation client, you must use an account that is already a member of this Namespace Administrators Group. If you used the TSSETUP domain account to install the application tier, this user is already assigned to the Namespace Administrators Group.

Using GSSUTIL on the Application Tier: Log on to the application tier using the credentials of a user account that is already a member of the Namespace Administrators application group (DOMAIN\TSSETUP). Open a command prompt and change the directory to %ProgramFiles%\Microsoft Visual Studio 2005 Enterprise Server\BISIISDIR\sdk\bin directory (for example, C:\Program Files\Microsoft Visual Studio 2005 Enterprise Server\BISIISDIR\sdk\bin).

Use the TFS Group Security Client (GSSUTIL.EXE) tool to add the project administrator account to the Namespace Administrators application group (adm:): gssutil.exe /g+ adm: n:domain\username.
Add the project administrator to the Sharepoint Administrators group.
1. Log on to the application tier using credentials of a user account that has administrative access to the application tier (Domain\TFSSETUP).
2. Open a browser window and enter https://localhost in the Address field, and click Go. This brings up the top-level site of Sharepoint Services. If the top-level site doesn't appear, review the steps to installing Sharepoint Services.
3. On the Home page, click on Site Settings.
4. On the Site Settings page, click on Go to Site Administration.
5. On the Top-level Site Administration page, click Manage site groups.
6. On the Manage Site Groups page, click on Administrator.
7. Click Add Members.
8. On the Add Users page, type the name of the project administrator account (Domain\PROJADMIN). Select Administrator in the Choose Site Groups area and then click Next.
9. Type an e-mail address in the E-mail Address box for the project administrator, and then click Finish.
Add the project administrator account (Domain\PROJADMIN) to the local Administrators group on the application tier.
Add the project administrator as a content manager for SQL Reporting Services.
1. On the data tier, log on using credentials of a user that has administrative access to the data tier (Domain\TFSSETUP).
2. Click on the Start button, point to All Programs, point to Microsoft SQL Server 2005, and then click Report Manager.
3. On the SQL Server Reporting Services Home page, click the Properties tab.
4. Click New Role Assignment.
  
  **Note **If you are running Internet Explorer in Windows Server 2003, you may need to adjust your Internet Explorer security settings for some the Reporting sites functionality to work. Adjust your security settings by selecting Tools | Options, clicking on the Security tab and then setting your security level to Medium.
5. On the New Role Assignment page, type the project administrator account (Domain\PROJADMIN) in the Group or user name box, select the Content Manager role, and then click OK.

Connect Visual Studio to Team Foundation Server

Log on to the client tier with the project administrator credentials.
Click the Start button, point to All Programs, point to Microsoft Visual Studio 2005 Beta, and then click Microsoft Visual Studio Beta 2.
If the Team Explorer tool window is not in view, select the View menu and click Team Explorer.
On the Tools menu, click Connect to Team Foundation Server...
On the Connect to Team Foundation Server dialog, click Servers.
On the Add/Remove Team Foundation Server dialog, click Add.
On the Add Team Foundation Server dialog, type the name of your application tier machine name in the Team Foundation Server Name box. Keep the defaults for Connection Details, and then click OK, as shown in Figure 3.

Figure 3. Add Team Foundation Server dialog

**Note **If you are unable to connect to the application tier, be sure the application tier virtual machine is running and all networking components have been installed. If you receive a message about not having sufficient permissions, be sure the credentials you used to log on to the client tier is a valid domain account and has been added to the Namespace Administrators group.
On the Add/Remove Team Foundation Server dialog, click Close.
The application tier will be listed in the Connect to a Team Foundation Server drop down. Highlight the application tier and click OK.

Create a Team Project

Log on to the client tier with the project administrator credentials.
Click the Start button, point to All Programs, point to Microsoft Visual Studio 2005 Beta, and then click Microsoft Visual Studio Beta 2.
If the Team Explorer tool window is not in view, select the View menu and click Team Explorer.
On the File menu, click New Team Project.
On the New Team Project page shown in Figure 4, type the project name in the Team project name box, you can optionally provide a description of the project, and then click Next.

Figure 4. New Team Project Setting Dialog box
On the Select a Process Template page, select a template from the Process template name drop down as shown in Figure 5.

Figure 5. Selecting a process template
On the Specify the Setting for the Project Portal page, type a title for the project portal site and provide a description, then click Next.

**Note **The Team project portal address box provides the URL of your project portal site as shown in Figure 6.

Figure 6. New Team Project dialog box with portal address
On Specify source control settings, click Create an empty version control folder, and then click Next.
On the Summary page, click Finish.
On the Team Project Creation Status page, you can view the progress of the project creation.

**Note **If your project isn't created successfully, choose to view the log to review which step(s) failed. A good portion of the errors encountered are possibly due to invalid security settings. Review that all the security steps for setting up a project administrator have been completed and try creating the project again. If you are running the tiers in a virtual environment you may have to increase the request timeout setting on IIS.

Team Roles

Once the project administrator has created the team project, the project administrator can assign team members to various roles. The project creation wizard creates the following default roles:

Contributor: has general read/write permissions across the project.
Reader: has read access across the project.
Project Administrator: has access to manage the project.

The following steps outline the process of assigning a developer account to the contributor role:

Create a user account in the Active Directory for the developer (Joe Developer).
Log on to the client tier with the project administrator credentials.
Click the Start button, point to All Programs, point to Microsoft Visual Studio 2005 Beta, and then click Microsoft Visual Studio Beta 2.
If the Team Explorer tool window is not in view, select the View menu and click Team Explorer.
Right-click on the team project, point to Team Project Settings, and click on Groups.

Figure 7. Project Groups dialog box
Click on the project's Contributor role to highlight it, and then click Properties.
On the Team Foundation Server Group Properties dialog, select Windows User or Group in Add member, and then click Add.
On the Select Users or Groups dialog, click Advanced, and then click Find Now.
Select the developer's domain user account and click OK.
On the Select Users or Groups dialog, click OK as shown in Figure 8**.**

Figure 8. Team Foundation Server Group Properties dialog box
Close the Team Foundation Server Group Properties dialog by clicking OK.

Additional Resources

For more information, see the following resources:

Dave Bost is the Director of Technology for Solution Partners, a Chicago-based consulting company and Microsoft Solution Provider Partner. From the earlier days of Visual Basic and COM to the present times with .NET and distributed architectures, Dave has spent the past 10 years specializing in designing and implementing Microsoft software solutions. Dave is also a frequent speaker at some of the industries leading conferences including VSLive and Microsoft's Developer Days. You can contact Dave through his blog at https://www.davebost.com/blog.