Screenshots from a successful team project creation.

You updated to TFS 2008, but since the upgrade process doesn't touch your already installed WSS you are responsible for upgrading it yourself.

Official Guidance:

• Upgrading SharePoint Products and Technologies for Team Foundation Server

Step 1: Run Prescan.EXE

Resulting log file:

Resulting XML file:

Step 2: Install WSS 3.0

Step 3a: Upgrade (invoked automatically by setup)

(Be aware: if you do not use the same port as your TFS is configured to talk to today you need to change the TFS registration using TFSAdminUtil afterwards!)

Step 3b: Still Upgrade (not in the web browser)

Step 4: Finalization (manual step)

Step 5: Uninstall WSS 2.0 (manual step)

Step 6: Install & configure TFS Extensions for WSS (located on the TFS media)

Step 7: Verify success by creating a new team project

Screenshots from a successful Power Tools installation

Step 1: Installing Windows PowerShell

Step 2: Installing TFS Power Tools

Screenshots of a successful Team System Web Access (TSWA) installation.

Requires: Team Explorer 2008 to be installed.

Open TSWA to verify it's working:

Screenshots from a successful Team Build installation

Screenshots of a successful TFS 2008 singe-tier installation.

Step 1: Installing IIS

Step 2: Installing SQL Server 2005

And verify it's working:

Apply SQL Server 2005 SP2:

Step 3: Installing TFS 2008

After uninstalling TFS 2005 (services) from a standby TFS application tier the SQL Server Reporting Services were not available, i.e. browsing http://server/reports and http://server/reportserver/ resulted in a 404 error.

Workaround:

Run the Reporting Services Configuration Tool and recreate both virtual directories and re-configure the identities.

(Thanks to Daniel Hackel who administers this environment.)

I you received:

TF220064: An error occurred while the Setup program was querying the settings from the server that is running SQL Server Reporting Services. This error is most likely caused by your account not having the required administrative permissions on the server that is running Reporting Services. Click Next to try again. For more information about this error, see the installation logs. For more information about the installation logs, see “Troubleshooting Installation for Team Foundation” in the Team Foundation Installation Guide.

Cause:

You probably use FQDN names for your reporting services server as explained here.

Workaround:

Change URI for the ReportsService to use a NETBIOS name instead of a fully qualified domain name (FQDN) - and revert it back after successful setup.

(Special thanks to Daniel Hackel who administers this environment and had to go all the upgrade trouble as well.)

When trying to upgrade to TFS 2008 you receive the following error message on your primary AT shortly after starting the setup program

"Setup has detected that the specified database server is already in use by another Team Foundation Server (services) computer. Click OK to configure this computer as a stand-by Team Foundation Server (services) computer. Click Cancel to specify a different database server."

Cause:

You are using a fully qualified domain name (FQDN) to reference your Team Foundation Server application tier.

Workaround:

1. Remove the FQDN (run the ActiveAT command with the NETBIOS name), i.e. change it back to the regular NETBIOS name.
2. Apply the TFS 2008 upgrade.
3. Re-apply the FQDN.

Enjoy TFS 2008!

(Thanks to Daniel Hackel who adminsters this environment.)

In TFS 2005 subfolders of your team build type folder were copied recursively to the build temp directory. In TFS 2008 only the contents w/o recursion is copied.

To change this behavior, Aaron tells us, you need to modify the following line

<add key="ConfigurationFolderRecursionType" value="Full" />

in the TfsBuildService.exe.config on your build machine.

Enjoy!

If you want Team Explorer to integrate with your existing Visual Studio IDE you need at least the Standard Edition of Visual Studio (according to the comparison sheet that Microsoft published).

Note on VSTS licensing:

Keep in mind that only the Team Editions (as well as Team Suite) comes with a client access license (CAL). You will need to buy a CAL for each user that accesses TFS using VS Std. or VS Pro.

Note for VS Express users:

You can use TFS and VS Express Edition, but Team Explorer will not integrate with the IDE but rather live in a separate Mini-Visual Studio (which will call itself 'Standard Edition').

If you can't connect to your TFS anymore one reason might be that the trial expired.

To find you how many days you have left of the trial and to extend the trial you need the TFS Version Detection utility.

Starting 10 days before expiration you'll see the "Extend Trial" button...

... which will give you additional 30 days.