1. Uninstall TFS Beta2 or RC

2. Install TFS 2010 RTM release

3. Select the "Upgrade from Previous Version" wizard

(Note: Always be sure to have a good backup copy of your TFS databases and system)

To check on your license type and expire date open the TFS Administration Console on the TFS server and on the right hand side of the first node you will see the license information

Scenario 1:  For the first 2 hours after the upgrade, check-ins will fail from any Visual Studio client.  On Visual Studio 2010 clients check-ins will work after waiting 2 hours after the upgrade completes.  On Visual Studio 2005 and Visual Studio 2008 clients you must stop and restart the Visual Studio client after the 2 hour window to enable check-ins to work again.  An alternative workaround (if you do not want to wait the 2 hours) is to delete the client side cache directory and restart Visual Studio. See below for instructions for deleting the client side cache directory.

Scenario 2: If customers have a configuration that uses a TFS Proxy server, Visual Studio 2005 and Visual Studio 2008 clients will fail to take advantage of the proxy and go directly to Team Foundation Application Tier until their client side cache directory is recreated.   The workaround is to delete the client side cache directory and restart Visual Studio. 

(Note: If you are using either TFS Proxy Server from TFS 2005 or TFS 2008 you must also restart the proxy server after the upgrade completes on the TFS 2010 Application Tier.   We do recommend that you upgrade proxy servers to the TFS 2010 RTM version.)

To delete the client side cache directory on the client machine:

1.       Exit Visual Studio

2.       Open a command window and navigate to the folder: "%localappdata%\Microsoft\Team Foundation\”  (Note: For Windows Server 2003 navigate to \Documents and Settings\<user>\Local Settings\Application Data\Microsoft\Team Foundation folder)

3.       For Visual Studio 2010 clients navigate to the sub folder: “3.0” and delete the sub folder “cache” and its contents

Or

For Visual Studio 2008 clients navigate to the sub folder: “2.0” and delete the sub folder “cache” and its contents

Or

For Visual Studio 2005 clients navigate to the sub folder: “1.0” and delete the sub folder “cache” and its contents

4.       Restart Visual Studio and connect to TFS.

With the release of Team Foundation Server (TFS) 2010 you may wonder where to start when thinking about TFS upgrade guidance.  The BEST place to start is by downloading the latest TFS Installation Guide which not only includes information about installing TFS but also includes details on TFS Upgrade.

You can download the latest Install Guide for Team Foundation here.  For TFS Upgrade guidance, start with the section labeled: "Scenario: Upgrading Team Foundation Server".

Excerpt from the Install Guide for Team Foundation:

Additional Upgrade Guidance Information

• If you are upgrading TFS from a pre-release version of TFS 2010 (Beta2 or RC) you can read this post: Team Foundation Server 2010 Upgrade Guide from Beta2 or RC to RTM.
• Finally, the Visual Studio ALM Rangers also produced a supplemental upgrade guide which contains information on issues that users may encounter during upgrade.  Most of this information has either been integrated into the RTM release or into the TFS Install Guide and Administration Guide.  However, you may still want to review the document.

This deck is meant to provide an overview on Upgrade strategies, flow and some compatibility information.  It is a work in progress and I will update periodically.

For more information on TFS upgrade please see this post: TFS Upgrade Guide.

TFS 2010 Upgrade Overview.pptx

With the Visual Studio 2010 RTM family of products, including Team Foundation Server 2010, due to be released soon, here is some TFS upgrade guidance to help you prepare to upgrade from either Beta2 or RC to the RTM release.  This is supplemental information above and beyond the Upgrade information contained in the TFS Installation Guide.   You can download the document from the link below.

If you using Visual Studio Lab Management please also see their blog for the Lab Management Upgrade Guidance.  During the Beta phase the TFS Rangers also produced a supplemental upgrade guide which contained information on issues that users may have encountered during upgrade.  Most of this information has either been integrated into the RTM release or into the TFS Install and Administration guides.  However, you may still want to review the document.

Please download the latest Installation Guide for Team Foundation and read the Upgrade sections for details on types of upgrades and steps to perform an upgrade to TFS 2010. (You can find an excerpt from the Install Guide here in my post: TFS Upgrade Guide)

Excerpt from document below:

While every attempt has been made to ensure a smooth upgrade process from previous versions to Microsoft Team Foundation Server (TFS) 2010, there are some specific action items you should follow when upgrading from TFS 2010 Beta2 or the TFS 2010 Release Candidate (RC) to the RTM version.  Please first download and read the most recent Team Foundation Server Installation Guide (https://go.microsoft.com/fwlink/?LinkId=127730) which contains information regarding upgrading TFS from previous versions and then read this document before starting the upgrade to RTM.  Note that some of the steps in this document are conditional based on the Beta2/RC configuration you are currently running.

The document is divided into four sections:

• Additional steps required BEFORE upgrading to RTM.
• TFS Upgrade Summary Steps.
• Additional steps required AFTER upgrading to RTM.
• Troubleshooting Upgrade failures.

TFS 2010 Beta2-RC to RTM Upgrade Guide (v1.11).docx

[Update: please see this post (Team Foundation Server 2010 Upgrade Guide from Beta2 or RC to RTM) for information on upgrading to TFS 2010 RTM version]

Now that  TFS 2010 Release Candidate (RC) has been released, we are providing this upgrade guide to help you prepare to upgrade from Beta2 to RC.  Below is an excerpt from the document which you can download below. If you using Visual Studio Lab Managment please also see their blog for the Lab Management 2010 Beta2 to RC Upgrade Guide.

[UPDATE1: Added topic in Section 2 for SharePoint extensions on SharePoint servers in a farm]

[UPDATE2: Added topic in Section 2 regarding clearing the Web Services cache directory to improve upgrade performance]

TFS 2010 Beta2 to RC Upgrade Guide (v1.02).pdf

There are two paths to choose from when upgrading to TFS 2010 Beta2:  “In-Place” upgrade and “Migration” upgrade.

Path 1: In-Place Upgrade

An In-Place upgrade is defined as an upgrade where you use the same set of hardware that is running the current TFS version.  In this scenario you will be uninstalling the current TFS version, upgrading any pre-req components such as SQL Server and SharePoint server, and then installing TFS and running the Upgrade Wizard.

Examples:

1.       Single Server - you are currently running TFS on a single server with SQL Server, SharePoint and Reporting Services/Analysis Services components.  You would uninstall TFS and then install/upgrade TFS to Beta2 using the existing SQL Server, SharePoint and RS/AS components.

2.       Multi Server - you are using separate servers for TFS, SQL Server and SharePoint.  You would uninstall TFS on the TFS Server and then install/upgrade TFS to Beta2 on that same server.

High level in-place upgrade steps (See the TFS Install guide for more details):

1.       Backup existing SQL databases

2.       Uninstall Team Foundation Server

3.       Upgrade to SQL Server 2008 (including Reporting Services and Analysis Services if using reporting)

4.       Upgrade to Windows SharePoint Services (WSS) 3.0 SP1 or later (if using portal)

5.       If using a separate SharePoint farm, uninstall existing Team Foundation Server Extensions for WSS and install TFS 2010 Extensions for WSS

6.       Run the TFS 2010 setup and select the Upgrade from Previous Version Wizard.

Path 2: Migration Upgrade

A Migration upgrade is defined as an upgrade where you using a separate duplicate set of hardware to perform the upgrade.  In this scenario you will be installing the pre-req components, copying the existing TFS related databases over and then installing TFS and running the Upgrade Wizard.

Examples:

1.       Single Server - you are currently running TFS on a single server where all components are on this same server.  For a migration upgrade you would set up a new separate server with the pre-req components (SQL Server, SharePoint, AS/RS), back up the TFS, SharePoint and Reporting databases from the existing server, restore them on the new server and then run the install/upgrade of TFS to Beta2.

2.       Multi Server – you are using separate servers for TFS, SQL Server and SharePoint.   You would setup new servers for each separate component, backup the appropriate databases, restore them to the new servers and then run the install/upgrade of TFS to Beta2.

High level migration upgrade steps (See the TFS Install guide for more details):

1.       Backup existing SQL databases (TFS, SharePoint content, Warehouse and Reporting databases)

2.       On new hardware, install necessary TFS pre-reqs including OS, IIS, SQL Server 2008, SQL Reporting Services and Analysis Services and Windows SharePoint Services.  (Note: The TFS Basic configuration will install SQL Express for you and doesn’t require Reporting Services or Windows SharePoint Services)

3.       Copy over backups from step #1 and restore databases on new hardware

4.       Configure SharePoint and SQL Reporting to connect and use these restored databases

5.       If using a separate SharePoint farm, uninstall existing Team Foundation Server Extensions for WSS and install TFS 2010 Extensions for WSS

6.       Run the TFS 2010 setup and select the Upgrade from Previous Version Wizard.

Which path to choose?

There are essentially three scenarios to choose from which will determine which upgrade path you follow:

Scenario 1: Testing Upgrade

In this scenario you want to test upgrade on a separate set of hardware while leaving the existing system running.   For this scenario you follow the Migration Upgrade path.  In addition you will also need to change the TFS database "stamp" on this new upgraded instance.  All TFS instances have a GUID that identifies them (regardless of what url you use to acces them).  Your clients will get confused if there are two TFS instances with the same GUID.  To change the TFS GUID follow these commands:

Scenario 2: Production Upgrade

In this scenario you are ready to upgrade your existing production system and plan to use the existing hardware.  For this scenario you follow the In-Place Upgrade path.  (Note that in this scenario that because you have to uninstall the existing version of TFS and the TFS 2010 upgrade is changing the existing data, “failing back” to that previous version of TFS will involve restoring the TFS databases from backup and re-installing the previous TFS version.)

Scenario 3: Production Upgrade with quick fall back plan

In this scenario you are going to move to new hardware at the same time as upgrading your production system, AND you will keeping the existing version of TFS running on the old hardware until the upgrade completes successfully.   For this scenario you follow the Migration Upgrade path.   (Note that the benefit of this scenario is that you can “fall back” and resume using the previous version of TFS on the old hardware if the upgrade fails.)

However, there is an important set of steps to add to our TFS 2010 Installation Guide.  The guide provides a checklist for performing the upgrade (see "Checklist: Upgrade from Visual Studio Team System 2008 Team Foundation Server").  Here are some additional instructions that you need to follow if you want to first copy your WSS content to another server to use in the upgrade test.   I recommend you migrate/copy the WSS content to the new server prior to running the TFS 2010 upgrade test by following these additional instructions.  You can insert these steps right after the step "Prepare Portal Server" in the Upgrade checklist.

1.    Plan your upgrade

Spend time putting together a plan for the upgrade.  TFS is a complex system and whether you have a single server installation of TFS or a distributed complex multi server deployment.  Putting together a project plan will pay dividends in the end.

2.    Prepare ahead of time

In addition to building a plan, spending time preparing for the actual upgrade is just as important as the TFS upgrade itself.   TFS sits on the “top of the stack” and depends upon several technologies working together to be successful.   Making sure to have the “pre-reqs” prepared and ready will take some time and is extremely important for a successful upgrade.   For more information on the pre-req for TFS 2010 see the TFS 2010 Installation Guide

3.    Decide on fall-back plan

While we have worked very hard to ensure a smooth upgrade, it is always important to have thought through the “fall-back” plans in the unlikely event that the upgrade is not successful.   In future posts I will discuss some of the fall-back plans as well as features we’ve built to help ensure upgrade success.

4.    Test, test, test

Finally, any upgrade of a production system (especially a server based system like TFS) should be tested beforehand.  I will also talk about several testing strategies you can employ in future posts.