Checklist: Upgrade Team Foundation Server By Using More Than One Server
You can use this checklist to upgrade to Visual Studio Team Foundation Server 2010. To benefit most from this checklist, you must have a deployment of Team Foundation Server that includes more than one server, or you must want to upgrade your deployment at the same time as you migrate it to different hardware. If you have a single-server deployment and you want to upgrade it in place, use Checklist: In-Place Upgrade of Team Foundation Server on a Single Server.
The tables in this topic contain tasks and links. The links provide either procedural or conceptual information for you to perform the associated task. You should perform the tasks from top to bottom unless you are directed to skip a task.
Preparation
The following tasks prepare the existing installation of Team Foundation Server for either of the following tasks:
a migration upgrade (use different hardware).
an in-place upgrade with more than one server (use the same or different hardware).
Tasks
Detailed instructions
Check for the latest installation guide. Download the current version of this guide. If there are late-breaking updates for upgrade procedures, you can find them in the latest version of this guide.
For the latest version of the Team Foundation Server installation guide, see the Microsoft Web site:
Back up your data. On your existing Team Foundation Server installation, back up your data. The upgrade tool deletes your old database during the upgrade. If you migrate to new hardware, you will use this data on the new hardware. If you plan to do an in-place upgrade, you can use this data as a snapshot of your Team Foundation Server installation, immediately before the upgrade.
NoteBack up your web.config file to preserve some settings, such as e-mail alerts and public URL settings. You will have to manually add these settings by using the upgrade wizard, and you can use the information in web.config as a reference. Open the folder that the Team Foundation Server Web application uses, and copy the file to a different location. You might want to rename the file. (For example, if this Web application uses port 80, save the file as Web.config80.)For the latest information about backing up Team Foundation Server, see the Microsoft Web site:
How to: Back Up a Team Foundation Server (Visual Studio Team System 2008 Team Foundation Server)
How to: Back Up a Team Foundation Server (Visual Studio 2005 Team Foundation Server)
Check for supported hardware and software. Verify that the operating system on every server where you will install Team Foundation Server meets Team Foundation Server requirements. Verify that the hardware is capable of running Team Foundation Server and all prerequisite server software. Review the language requirements for Team Foundation Server.
Check for required permissions and user accounts. Verify that the account you will use to install Team Foundation Server is a member of the Administrators security group on the servers where you will install Team Foundation Server.
Determine the service accounts you will use during Team Foundation Server and SQL Server installation (if you require a new installation of SQL Server).
Check for supported environment settings. To use Team Foundation Server on multiple servers, you must have an Active Directory domain that meets requirements of Team Foundation Server.
If you have a firewall between the server where you want to run Team Foundation Server and any clients that must connect to Team Foundation Server, verify that the ports required by Team Foundation Server are open.
If Windows Firewall is on and configured to allow exceptions, the installation wizard for Team Foundation Server creates exceptions for Team Foundation Server.
If Windows Firewall is configured to disallow exceptions or you are using a different firewall, you must specify the ports manually before you can install Team Foundation Server.
Set up Internet Information Services (IIS). If you are moving Team Foundation Server to new hardware that is running Windows Server 2003, you must install IIS. Otherwise, IIS is installed and configured for you, but a warning message appears during installation. If you want to avoid the warning message, you must install IIS on the server where you will install Team Foundation Server. If IIS has already been installed, you can verify that IIS is configured to work with Team Foundation Server.
Set up SQL Server. Either install SQL Server 2008 on the server where you will host the Database Engine and Full Text Search features or verify that an existing installation meets Team Foundation Server requirements. If you are doing an in-place upgrade and were using SQL Server 2005 you must upgrade to SQL Server 2008.
Review the Team Foundation Server collation requirements. Determine the collation settings your organization requires for its data and ensure that those settings meet the requirements of Team Foundation Server. If these settings are not consistent across all SQL Server instances added to Team Foundation Server, you may get unexpected results in reports.
Set up Reporting. If you want to use reporting, you must either install SQL Server Reporting Services and SQL Server Analysis Services or verify that an existing installation meets Team Foundation Server requirements.
You can use the following guidelines for setting up SQL Server for reporting during an upgrade:
You do not have to use the same report server that you used with your earlier version of Team Foundation Server.
You do not have to use the same SQL Server instance for the report server as the one that you used for the Database Engine.
You can even use multiple servers to host the report server.
However, your report server cannot be shared with other applications. Team Foundation Server requires a dedicated report server. If your report server is not on the same server as Team Foundation Server, you must add the account that you used to install Team Foundation Server to the Administrators security group on the report server. This enables setup to configure the report server to work with Team Foundation Server.
SQL Server Collation Requirements for Team Foundation Server
How to: Add the Service Account for Team Foundation Server to the Report Server
For information about how to upgrade SQL Server, see the following page on the Microsoft Web site:
Verify SQL Server. Verify that you have configured all instances of SQL Server to meet the minimum requirements of Team Foundation Server.
Prepare Portal Server.If you are using Windows SharePoint Services 2.0 and want to add a portal server to your new installation of Team Foundation Server, you must upgrade to Windows SharePoint Services 3.0, Microsoft Office SharePoint Server 2007, or Microsoft SharePoint Server 2010.
You cannot install Windows SharePoint Services 3.0 when you upgrade Team Foundation Server. You must use your existing portal or point to an existing SharePoint Products site that meets requirements.
You can also take any one of these optional steps with your portal server:
You can also upgrade Windows SharePoint Services 3.0 to Microsoft Office SharePoint Server 2007. For more information, see the following page on the Microsoft Web site: Upgrading SharePoint Products and Technologies for Team Foundation Server.
You can migrate your portal to new hardware. For more information, see the following page on the Microsoft Web site: Redirect SharePoint Products to Use a New Content Database.
You can skip setting up a portal server when you upgrade Team Foundation Server. If you skip this step and then add a portal later, you must manually link all of your team projects to the portal.
For the more information, see the following pages on the Microsoft Web site:
Team Foundation Server Administrator Fills out Worksheet. For a remote installation of SharePoint Products, multiple administrators may want to exchange information to configure Team Foundation Server. To help facilitate communication, the administrator for Team Foundation Server should print Worksheet: Team Foundation Server and SharePoint Products Collaboration and add the information that the administrator for SharePoint Products requires. The administrator for Team Foundation Server should then hand off the worksheet and the installation media for Team Foundation Server to the administrator for SharePoint Products to complete the rest of the tasks in this checklist.
If you are the administrator for both Team Foundation Server and SharePoint Products, you can skip this step, but you should read the following important caveats before you continue:
If you are using Microsoft Office SharePoint Server 2007 or SharePoint Server 2010, you must perform the steps in "Configure Settings for Dashboard Compatibility" later in this topic before dashboards will function correctly.
If you are doing an in-place upgrade and SharePoint Products is already installed on the same server as Team Foundation Server, the upgrade wizard installs the Team Foundation Server extensions for Windows SharePoint Services for you. You must skip "Install and Configure Extensions" later in this topic.
Install and provision SharePoint Products. If Windows SharePoint Services 3.0 is already installed on the same server as Team Foundation Server, you can skip all the way to "Verify local SharePoint Products." If Microsoft Office SharePoint Server 2007 or SharePoint Server 2010 is already installed, skip to "Configure Settings for Dashboard Compatibility."
You can install SharePoint Products with the recommended settings for Team Foundation Server. After you install SharePoint Products, you must use the SharePoint Central Administration site to create a Web application that has the following characteristics:
uses port 80
uses NTLM for authentication
has a unique name that also indicates the port number
NoteIf you specify a different port number than 80, users must include it as part of the address for Team Foundation Server to operate correctly.
For more information about how to create a Web application, see the following pages on the Microsoft Web site:
For information about Windows SharePoint Services 3.0, see Create a Web application.
For information about Microsoft Office SharePoint Server 2007, see Create or extend a Web application.
For information about Microsoft SharePoint Server 2010, see Create a Web application that uses Windows-classic authentication (SharePoint Server 2010).
Configure Microsoft Office SharePoint Server 2007 or SharePoint Server 2010. If you are using Microsoft Office SharePoint Server 2007 or SharePoint Server 2010, perform the required configurations for dashboard compatibility. If you are using Windows SharePoint Services 3.0, skip to the next step.
Install and Configure Extensions. If SharePoint Products is already installed on the same server as Team Foundation Server, the upgrade wizard installs the Team Foundation Server extensions for Windows SharePoint Services for you. You can skip to "Verify local SharePoint Products."
Verify that the installation of SharePoint Products meets the minimum requirements for Team Foundation Server, and then install and configure Team Foundation Server Extensions for Windows SharePoint Services.
Add the service account of Team Foundation Server to Farm Administrators group. Add the account of the person who will install the application tier to the Farm Administrators group. Use the printed worksheet to locate the account name for the service account of the Team Foundation Server (TFSSERVICE) and the account of the person who is installing Team Foundation Server.
How to: Verify SharePoint Products for Team Foundation Server
How to: Install Team Foundation Server Extensions for Windows SharePoint Services
How to: Configure Team Foundation Server Extensions for Windows SharePoint Services
How to: Add the Service Account for Team Foundation Server to the Farm Administrators Group
Administrator for SharePoint Products Fills out Worksheet. The Team Foundation Server administrator requires specific information about the installation of SharePoint Products to finish the Team Foundation Server configuration. The administrator for SharePoint Products should print Worksheet: Team Foundation Server and SharePoint Products Collaboration. The administrator for SharePoint Products must add the information that is required by the Team Foundation Server administrator and then hand off the worksheet to the Team Foundation Server administrator.
Verify local SharePoint Products. If SharePoint Products is on the same server as Team Foundation Server, verify that the installation of SharePoint Products meets the minimum requirements for Team Foundation Server.
Add the service account of Team Foundation Server to the Farm Administrators group. Add the account of the person who will upgrade the application tier to the Farm Administrators group.
Uninstall the previous version of Team Foundation Server. If you are doing an in-place upgrade, you must uninstall Team Foundation Server. If you are migrating to different hardware, you can skip this step.
Restore your data. If you are doing an in-place upgrade and your data is already in place on an instance of SQL Server 2008, you can skip this step. Otherwise, on the instance of SQL Server that will host the configuration database, you can restore the data from Team Foundation Server that you backed up at the start of this checklist.
NoteYou must not rename any database that you are restoring.For the more information about how to restore data from Team Foundation Server, see the following page on the Microsoft Web site:
How to: Restore Data for Team Foundation Server to a Different Server (Team System 2008 Team Foundation Server)
NoteThe previous link offers a dozen steps, but you are required to perform only the procedures that are associated with step 3, "Restore the Databases." The upgrade for Team Foundation Server performs the rest of the steps that are required to restore your Team Foundation Server environment.How to: Move Your Team Foundation Server from One Hardware Configuration to Another (Visual Studio 2005 Team Foundation Server)
Team Foundation Server Upgrade
Perform the following tasks to upgrade Team Foundation Server.
Tasks |
Detailed instructions |
---|---|
Install Team Foundation Server. If you are upgrading from Visual Studio 2005 Team Foundation Server, you should delete the old Team Foundation Server Web sites from Internet Information Services (IIS) before you perform this procedure. |
|
Update and configure Team Foundation Server. This update will prevent an issue caused by a specific pattern of version control operations that affects the upgrade of version control labels and merges. To download this update, see the following page on the Microsoft Web site: KB2135068 - Labeled items and merge targets missing after upgrade to TFS2010. For more information, see the following page on the Microsoft Web site: After an upgrade to TFS 2010, labels are missing items, or merge relationships are missing. After you complete the installation and apply the update for version control, upgrade your server by using the Team Foundation Server Configuration tool. Once the upgrade completes, you might have to perform a bind operation on your version control projects in Visual Studio. If you changed the URL for your team collection by migrating the AT to a new server or by changing settings in IIS, then your version control projects might not work as you’d expect until you do a bind operation. |
|
Final configuration of Microsoft Office SharePoint Server 2007 or SharePoint Server 2010. If you installed Microsoft Office SharePoint Server 2007 or SharePoint Server 2010, you must configure the enterprise application definition that you created for Team Foundation Server. If you are using Windows SharePoint Services 3.0 or did not configure SharePoint Products, you can skip this step. |