Upgrading from Team Foundation Server Beta 3 Refresh to the Release to Manufacturing Version (RTM) of Team Foundation Server

Upgrading from Team Foundation Server Beta 3 Refresh to the Release to Manufacturing Version (RTM) of Team Foundation Server

  • Comments 1

Upgrading from Team Foundation Server Beta 3 Refresh to the Release to Manufacturing Version (RTM) of Team Foundation Server

Introduction

Upgrading from Team Foundation Server Beta 3 Refresh to Team Foundation Server RTM involves many steps that include backing up data, running utilities to update your installation, and performing some manual steps to complete the process. When you upgrade, we recommend that you use the same user accounts that you used to install Team Foundation Server Beta 3 Refresh.

This guide provides steps and guidance for completing each of these procedures on single-server and dual-server deployments in addition to guidance for verifying the success of the upgrade process.

Important   Read this guide carefully before you try to upgrade your installation of Team Foundation Server. Make sure that you follow the steps as they are listed in this guide. Performing upgrade tasks out of order or skipping steps can cause the upgrade to fail.

For additional guidance, information, and assistance, visit the Microsoft Web site (http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=68&SiteID=1).

Changes to Team Foundation Server Between Beta 3 Refresh and RTM

There have been several changes to Team Foundation Server between Beta 3 Refresh and the RTM version. Most of these changes will be handled gracefully during the upgrade process, but some of the changes will affect customizations that you have made to Team Foundation Server in Beta 3 Refresh. If you want to keep these customizations, you must import them manually. These steps are documented in the Incorporating Customizations from Team Foundation Server Beta 3 Refresh into Team Foundation Server RTM section.

Additionally, your custom reports will probably not work with the new warehouse cube structure. You must modify them to account for these changes. The most significant of these changes occurs in the work item measure group. In Team Foundation Server Beta 3 Refresh, most work item attributes were separate dimensions. In Team Foundation Server RTM, they are combined into a single work item dimension.

There will be two versions of the MSF for Agile Software Development and MSF for CMMI Process Improvement templates available on your Team Foundation Server after the upgrade, with very similar names. The new process template versions that have been updated with changes for Team Foundation Server RTM, have the version number (4.0) after their names so that you can tell what version of the process template you are about to use. For example, after you upgrade, you will have both the MSF for Agile Software Development and the MSF for Agile Software Development – 4.0 templates available on your Team Foundation Server.

Work items have also changed to use display names in various fields instead of user account names or aliases. Because of this change, you must update any work item queries that used aliases to search for work items.

Any work item changed e-mail alerts created by users will be nonfunctional after the migration from Team Foundation Server Beta 3 Refresh to Team Foundation Server RTM. Users must manually re-create their alerts after the upgrade. For more information about how to re-create project alerts, see Incorporating Customizations from Team Foundation Server Beta 3 Refresh into Team Foundation Server RTM later in this document.


 

Contents

 

Upgrading from Team Foundation Server Beta 3 Refresh to the Release to Manufacturing Version (RTM) of Team Foundation Server 1

Introduction. 1

Changes to Team Foundation Server Between Beta 3 Refresh and RTM... 1

Contents. 3

Before You Start Your Upgrade. 5

Step 1: Verify That You Have Team Foundation Server Beta 3 Refresh Installed. 5

Step 2: Connect Team Explorer to Your Team Foundation Server Beta 3 Refresh Deployment 6

Step 3: Create New Projects on Team Foundation Server 6

Step 4: View and Add Work Items in the New Project 8

Step 5: Delete the Test Projects from Team Foundation Server 8

Step 6: Check In Any Customized Reports Into Source Control 9

Step 7: Close Visual Studio and Team Foundation Components. 9

Single Server Deployment 10

Step 1: Download the Upgrade Software and Run the TFSUpgrade Tool 10

Step 2: Uninstall Team Foundation Server Beta 3 Refresh and Team Explorer 10

Step 3: Back Up Team Foundation Server Databases. 11

Step 4: Run the TFSUpgrade Tool 12

Step 5: Install the SQL Server Update From the Product Media. 12

Step 6: Verify that the SQL Server FullText Search Service is Started. 13

Step 7: Run the TFSUpgradeAT Tool to Update Windows SharePoint Server Database Names  13

Step 8: Install the ASP.NET Update From the Product Media. 14

Step 9: Install Team Foundation Server RTM... 14

Step 10: Update the Team Foundation Reporting Warehouse. 15

Step 11: Install Team Explorer 16

Step 12: Upgrade the Build Types for All Projects. 16

Step 13: Upload Default Reports for All Projects. 16

Dual Server Deployment 18

Step 1: Download the Upgrade Software and Run the TFSUpgrade Tool 18

Step 2: Uninstall Team Foundation Server Beta 3 Refresh and Team Explorer 18

Step 3: Enable Network Traffic for SQL Server and Reporting Services Administration Between the Team Foundation Application Tier and the Team Foundation Data Tier in Dual-Server Installations. 19

Step 4: Back Up the Encryption Key for Reporting Services. 20

Step 5: Back up Team Foundation Server Databases. 21

Step 6: Run the TFSUpgrade Tool 22

Step 7: Run the TFSUpgradeAT Tool to Update Windows SharePoint Server Database Names  22

Step 8: Install SQL Report Server on the Team Foundation Application-Tier Server 23

Step 9: Install the SQL Server Update On the Team Foundation Data-Tier Server 24

Step 10: Verify that the SQL Server FullText Search Service is Started. 24

Step 11: Restore the Reporting Services Encryption Key from Team Foundation Server Beta 3 Refresh  25

Step 12: Delete the Reporting Services Application Pools From Internet Information Services (IIS) 27

Step 13: Install the ASP.NET Update From the Product Media. 27

Step 14: Remove SQL Report Server from the Team Foundation Data Tier Server 27

Step 15: Install Team Foundation Server RTM... 28

Step 16: Update the Team Foundation Reporting Warehouse. 30

Step 17: Install Team Explorer 31

Step 18: Upgrade the Build Types for All Projects. 31

Step 19: Upload New Default Reports for All Projects. 31

Updating Team Foundation Build Servers. 33

Step 1: Uninstall Team Foundation Build. 33

Step 2: Install Team Foundation Build. 33

Updating Team Foundation Server Proxy. 35

Step 1: Back up the Team Foundation Server Proxy Proxy.Config File. 35

Step 2: Uninstall Team Foundation Server Proxy. 35

Step 3: Install the ASP.NET Update From the Product Media. 35

Step 4: Install Team Foundation Server Proxy. 35

Step 5: Restore the Team Foundation Server Proxy Proxy.Config File. 36

Verifying the Success of Your Upgrade. 38

Connect Team Explorer to Team Foundation Server 38

Create New Projects on Team Foundation Server 38

Add a User or Group to a Project-Level Group. 40

Configure Permissions for Default Groups in Windows SharePoint Services and Reporting Services  41

View and Add Work Items in the New Project 41

Add a Solution to Source Control for the New Project 42

Run A Build On A Build Type and Verify Build Reports. 44

Incorporating Customizations from Team Foundation Server Beta 3 Refresh into Team Foundation Server RTM    46

Work Item Types. 46

Work Item Tracking Queries. 47

Project Alerts. 47

Reports. 47

 


Before You Start the Upgrade

Before you start to upgrade the Team Foundation Server Beta 3 Refresh deployment to Team Foundation Server RTM, you should perform some maintenance and verification tasks to make sure that your current deployment is fully functional and ready for migration. Although these steps are not mandatory, taking the time to follow these steps will help reduce the potential for problems during migration.

Step 1: Verify That You Have Team Foundation Server Beta 3 Refresh Installed

There are two different upgrade paths supported for Team Foundation Server RTM:

·         Upgrading from Team Foundation Server Beta 3 Refresh to Team Foundation Server RTM.

·         Upgrading from Team Foundation Server Release Candidate (RC) to Team Foundation Server RTM.

These two upgrades have different guides and different steps. For this guide, you should make sure that you have Team Foundation Server Beta 3 Refresh installed on the server.

 

To verify that you have Team Foundation Server Beta 3 Refresh installed

1.      On the Team Foundation application-tier server, open the drive:\%PROGRAMFILES%\Microsoft Visual Studio 2005 Team Foundation Server\Web Services\Services\Bin folder.

2.      Right-click the Microsoft.TeamFoundation.dll file and then click Properties.

3.      Click the Version tab and review the version number.

·         If the version number is 8.0.50727.43, you have Team Foundation Server Beta 3 Refresh installed. Continue with the steps in this guide.

·         If the version number is 8.0.50727.127, you have Team Foundation Server RC installed. Do not continue with the steps in this guide. You must follow the steps in Upgrading from Team Foundation Server Release Candidate (RC) to the Release to Manufacturing Version (RTM) of Team Foundation Server (also included with the upgrade software) to upgrade from Team Foundation Server RC to Team Foundation Server RTM.

·         If the version number does not match either of the two numbers that were discussed earlier, you have another version of Team Foundation Server installed. Upgrade from this version to Team Foundation Server RTM is not supported. For more information, go to the Microsoft Web site (http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=68&SiteID=1).

Step 2: Connect Team Explorer to Your Team Foundation Server Beta 3 Refresh Deployment

To make sure that your Team Foundation Server Beta 3 Refresh deployment is available to Team Foundation clients, such as Team Explorer, connect Team Explorer to your current Team Foundation Server.

 

To connect to a Team Foundation Server

1.      Start Microsoft Visual Studio 2005.

2.      On the Tools menu, click Connect to Team Foundation Server.

The Connect to Team Foundation Server dialog box appears.

3.      In the Connect to a Team Foundation Server list, select the Team Foundation Server you want to use.

4.      If any team projects exist on this Team Foundation Server, select the ones that you want to use.

5.      Click OK.

Step 3: Create New Projects on Team Foundation Server

After verifying that you can connect to your Team Foundation Server, create two new team projects, one using the MSF for Agile Software Development process template, and the other using the MSF for CMMI Process Improvement process template. After upgrade, there will be two new versions of these process templates available on your Team Foundation Server in addition to these older versions. Verifying that the old process templates work in the Project Creation Wizard before upgrading will help in troubleshooting any potential problems after migration.

Your custom process templates, if any, will also appear in the Project Creation Wizard process template list as usual. If you have custom process templates, you should also create a new project on your Team Foundation Server for each customized process template.

 

To create a team project

1.      Open Team Explorer.

2.      On the File menu, click New Team Project.

The New Team Project wizard appears.

Note   If you are not using the Project Management environment settings, on the File menu, point to New, and then click Team Project.

Note   If you have not connected to a Team Foundation Server, you will be prompted to connect to one now.

3.      Under What is the name of the team project? on the Specify the Team Project Settings page, type a name for the team project that team members can easily associate with the software product. This name is what all team members will use to connect to the team project.

4.      Under Which process template should be used to create the team project? on the Select a Process Template page, select a process template.

Team Explorer includes process templates based on the Microsoft Solutions Framework (MSF). By default, two process templates are available: MSF for Agile Software Development, and MSF for CMMI Process Improvement. Your team or organization might provide additional process templates. You can see a description for each process template by selecting the template and reading the text in The following describes the process template in more detail.

Note   If you want to use a process template that does not appear on the list, you must first upload the template to the Team Foundation Server.

5.      Complete the Specify the Setting for the Project Portal page:

·         What is the title of the team project portal?   If you want a project portal name different from the team project name, type a name that is easily identified by all team members. The site title is part of the home page of the project portal.

·         What is the description of the team project portal?   Enter a description for the project portal. The description is displayed on the home page of the project portal.

The project portal is a team Web site (using Windows SharePoint Services) that stores and versions team project-related documents.

6.      Complete the Specify Source Control Settings page by selecting one of three options, and then click Next:

·         You can select Create an empty source control folder. Specify a name for the folder.

·         You can select Create a new source control branch. Specify from which folder to branch.

·         Or you can select Do not create a source control branch at this point.

7.      On the Confirm Team Project Settings page, review the choices and values that you specified. If the information is correct, click Finish. Otherwise, click Previous to make changes.

The New Team Project wizard creates your new team project.

Note   It may take several minutes for the wizard to finish.

8.      On the Team Project Creation Status page, view the status messages and status bar that describes what the wizard is doing.

9.      On the Team Project Created page, select Launch the process guidance for more information about how to run the team project if you want to read more details about the work items, roles, activities, and other aspects of the team process.

10.  Click Close.

11.  The new team project displays in Team Explorer. If the wizard encounters a problem when it is creating the new team project, you will see an error message describing the problem and suggesting corrective action.

12.  Repeat these steps to create a test project using each process template you intend to use in production projects.

Step 4: View and Add Work Items in the New Project

By using the same administrative account you used to create the new projects, verify that you can view and create work items in the project.

 

To view work items for a project

1.      Open Team Explorer and connect to the Team Foundation Server, if you must.

2.      In the Explorer pane, expand each test project you created.

3.      In the Explorer pane, expand the Work Items folder, and verify that the Team Queries and My Queries folders exist.

4.      In the Explorer pane, expand the Team Queries folder, and double-click the All – All Work Items query.

5.      Verify that work items appear in the query results pane. Work items are automatically created with each new project.

 

To add work items for a project

1.      Open Team Explorer.

2.      On the Team menu, click Add Work Item, and then pick the work item type from the list.

Note   As you use Team Foundation, it automatically adds your most recently used work items to the top of the Team menu for easy access.

3.      Complete the work item form by filling in all required fields.

Required fields are indicated by yellow shading.

4.      On the File menu, click Save All to save the work item.

Step 5: Delete the Test Projects from Team Foundation Server

After you create and verify the new projects, delete the test projects from Team Foundation Server.

 

To delete a project from Team Foundation Server

1.      Open a Command Prompt window. To open a command prompt, click Start, click Run, type cmd, and then click OK.

2.      Change directories to the Team Foundation Server tools directory. By default, these tools are installed in drive:\Program Files\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies.

3.      At the command prompt, type the following, where projectname is the name of the Team Foundation Server project you want to delete and servername is the name of the Team Foundation Server:

TFSDeleteProject /Server:servername projectname

4.      Monitor the command prompt for any error messages when the command is running.

5.      Repeat these steps for every test project you want to remove.

Note   For more information about the TFSDeleteProject command, see the help for Team Foundation Server command-line utilities in Administering Team Foundation Server.

Step 6: Check In Any Customized Reports Into Source Control

Check in any customized reports that you might want to keep into source control. These reports will be backed up and available to you for modification after the upgrade is finished.

Note   Customized reports from Team Foundation Server Beta 3 Refresh will not work in Team Foundation Server RTM without manual customization. For more information, see the Incorporating Customizations from Team Foundation Server Beta 3 Refresh into Team Foundation Server RTM section, later in this document.

 

To check in customized report files into source control

1.      Open Team Explorer.

2.      In the View menu, click Other Windows, and then select Source Control Explorer.

Note   Depending on your preference settings when you installed Team Explorer, Source Control Explorer might be on the same menu as Other Windows.

3.      In Source Control Explorer, click the solution where you want to add the report file.

4.      On the File menu, click Source control, and then select Add To Source Control.

The Add to Source Control dialog box is displayed.

5.      In the Exclude box, type the file name extensions that you do not want to have added. You can enter multiple file type extensions by using commas and wildcard characters; for example, *.pdb, *.obj, *.res.

6.      Click Add Files.

7.      In the Add to Source Control dialog box, locate and select the report file that you want to add to source control, and then click OK.

8.      In the Add to Source Control dialog box, click OK.

Step 7: Close Visual Studio and Team Foundation Components

Before you start the upgrade, make sure that you are not running Visual Studio or any Team Foundation components, such as Team Explorer, on the Team Foundation Server.


Single Server Deployment

Step 1: Download the Upgrade Software and Run the TFSUpgradeRTM Tool

The first step to upgrading your Team Foundation Server Beta 3 deployment to Team Foundation Server RTM is to download the upgrade software and resolve any potential upgrade conflicts.

 

To download the upgrade software and run the TFSUpgradeRTM tool to scan for any upgrade issues:

1.      Download the upgrade software from the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkID=60341) or install it from the upgrade media.

2.      At the command prompt, change directories to the directory where you installed the upgrade software. To make sure that you have the correct directory, type dir at the command-line and make sure that the TFSUpgradeRTM.exe tool is listed.

Note   If you see the command TFSUpgrade.exe instead, you have a Release Candidate (RC) version of the Team Foundation Server software instead of the RTM version. Obtain a RTM version of the Team Foundation Server software, or if you want to upgrade to the RC version, know that the steps in this guide are not designed for the RC version and will differ slightly in some areas.

3.      Type the following at the command line, where servername is the name of your Team Foundation Server:

TFSUpgradeRTM.exe servername /verify

4.      When you are prompted to confirm if you want to run this command, click Yes.

5.      Follow the instructions that appear on the screen to resolve any reported issues.

Note   Depending on your configuration, you might see an error message that prompts you to run the witfields command-line utility. The witfields command-line utility is located by default in drive\Program Files\Visual Studio8\Common7\IDE on any computer where you have installed Team Explorer. For more information, see witfields in Administering Team Foundation Server.

Step 2: Uninstall Team Foundation Server Beta 3 Refresh and Team Explorer

Use Add or Remove Programs to uninstall Team Foundation Server and Team Explorer on the Team Foundation Server.

Note   Depending on your configuration, you might not have Team Explorer installed on your Team Foundation Server. If it is installed, you must uninstall it.

 

To uninstall Team Foundation Server Beta 3 Refresh

1.      Click Start, click Settings, click Control Panel, and then click Add or Remove Programs.

2.      Select Microsoft Visual Studio 2005 Team Foundation Server.

3.      Click Change/Remove.

4.      In the setup dialog box, select Uninstall, and then click Next.

5.      Click OK on the confirmation dialog box.

6.      Click Finish when completed.

 

To uninstall Team Explorer

1.      Click Start, click Settings, click Control Panel, and then click Add or Remove Programs.

2.      Select Microsoft Visual Studio 2005 Team Explorer.

3.      Click Change/Remove.

4.      In the setup dialog box, select Uninstall, and then click Next.

5.      Click OK on the confirmation dialog box.

6.      Click Finish when completed.

Step 3: Back Up Team Foundation Server Databases

The procedure for backing up Team Foundation Server databases in Beta 3 Refresh differs from the procedure for backing up Team Foundation Server databases in Team Foundation Server RTM. The procedure for backing up Beta 3 Refresh databases is located online at http://blogs.msdn.com/vstsue/articles/500334.aspx. You should examine this document for any late-breaking changes.

 

If you have already created a backup maintenance plan, you can use the latest incremental and full backups for restoration. If not, follow the steps in this section to create a full backup of the following databases:

·         ReportServer

·         ReportServerTempDB

·         STS_Config

·         STS_servername_# (where servername is the name of the server and # is a number)

·         TfsActivityLogging

·         TfsBuild

·         TfsIntegration

·         TfsVersionControl

·         TfsWarehouse

·         TfsWorkItemTracking

·         TfsWorkItemTrackingAttachments

 

To create a full backup plan and run a full backup on a Team Foundation Server

1.      On the Team Foundation Server, open SQL Server Management Studio. To open SQL Server Management Studio, click Start, click All Programs, click Microsoft SQL Server 2005, and then click SQL Server Management Studio.

2.      Select Database Engine for the Server type. Select the appropriate server name and authentication scheme for the server. Provide a valid user name and password if it is required by your SQL Server, and then click Connect.

3.      Expand the Management node, right-click Maintenance Plans, and select Maintenance Plan Wizard.

4.      On the Maintenance Plan Wizard welcome page, click Next.

5.      On the Select a Target Server page, provide a name for this maintenance plan.

6.      Select the appropriate server and authentication scheme for your SQL Server. Provide a user name and password if it is required by your SQL Server, and then click Next.

7.      On the Select Maintenance Tasks page, select Back Up Database (Full), and then click Next.

8.      On the Select Maintenance Task Order page, click Next.

9.      On the Define Back Up Database (Full) Task page, from the Databases drop-down list where it says Select one or more, select the databases listed earlier in this section, and then click OK.

10.  On the Define Back Up Database (Full) Task page, select the desired destination options for your back up. See the SQL Server 2005 Books Online for detailed information about the options on this dialog box. (Select the Maintenance Plan Wizard dialog box and press F1 for help specific to the dialog box.) Make sure that the backup files are stored on another secure computer, and not the computer that you are about to upgrade. Click Next.

11.  On the Select Plan Properties page, click Change.

12.  On the New Job Schedule page, in Name, provide a name for the back up job. Change the Schedule type to One Time, and leave Enabled selected. Leave Date set to the current date and time. Click OK, and then click Next.

13.  On the Select Report Options page, optionally select the desired report distribution options. Click Next.

14.  Click Finish to complete creating the Maintenance Plan. The backup will start immediately after clicking Finish.

15.  When the backup finishes, click Close.

Note   Make sure that the database backup has completed before continuing on to Step 4.

Step 4: Run the TFSUpgradeRTM Tool

After uninstalling Team Foundation Server Beta 3 Refresh, you must rerun the TFSUpgradeRTM tool on your single-server deployment without the /verify option. This will upgrade your databases..

 

To run the TFSUpgradeRTM tool

1.      Open a Command Prompt window. To open a command prompt, click Start, click Run, type cmd, and then click OK.

2.      At the command prompt, change directories to the directory where you installed the upgrade software.

3.      Type the following at the command line, where servername is the name of your Team Foundation Server:

TFSUpgradeRTM.exe servername

Step 5: Install the SQL Server Update from the Product Media

You must install an update for SQL Server (KB914595) before you install Team Foundation Server RTM or you might experience problems with your computer memory. The update can be found on the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=62015) and can also be found on the Team Foundation Server product media.

 

To install the SQL Server Update

1.      On the Team Foundation data-tier server, click Start, point to All Programs, point to Microsoft SQL Server 2005, point to Configuration Tools, and then click SQL Server Configuration Manager.

2.      In the Explorer pane, click SQL Server 2005 Services.

3.      Right-click SQL Server Browser, and then click Stop.

4.      On the Team Foundation Server installation media, locate the SQLServerKB folder.

Note   On Team Foundation Server Release Candidate (RC) media, this folder is named KB912838. If you see this folder, you have an RC version of the Team Foundation Server media. Obtain a RTM version of the media to upgrade to Team Foundation Server RTM.

5.      Locate the executable file (.exe) for the operating system and language, such as AS2005-KBnnnnnn-x86-ENU.exe, and then double-click the file to start the Hotfix Installer.

6.      In the Hotfix Installer, accept the End User License Agreement, complete the pages to install the hotfix, and then click Finish.

7.      In SQL Server Configuration Manager, right-click SQL Server Browser, and then click Properties.

8.      On the Service tab, locate Start Mode, and select Automatic.

9.      On the Log On tab, click Start.

Note   If Start is not enabled on the Log On tab, click the Service tab, set the Start Mode to Disabled, and then again select Automatic to explicitly update the Start Mode.

Step 6: Verify that the SQL Server FullText Search Service is Started

Unlike Team Foundation Server Beta 3 Refresh, Team Foundation Server RTM depends on the SQL Server FullText Search service. You must make sure that this service is started and set to Automatic, or an upgrade might fail.

 

To verify that the SQL Server FullText Search service is started

1.      On the Team Foundation Server, open SQL Server Configuration Manager.

2.      In the Explorer pane, click SQL Server 2005 Services.

3.      Review the list of services for SQL Server FullText Search (MSSQLSERVER). Make sure that State is listed as Running and that the Start Mode is listed as Automatic. If the state is not Running or the start mode is not listed as Automatic, do the following:

1.      To start the SQL Server FullText Search service, right-click the service and then click Properties. On the Log On tab, click Start, and then click OK.

Note   If Start is not enabled on the Log On tab, click the Service tab, set the Start Mode to Disabled, and then again select Automatic to explicitly update the Start Mode.

2.      To change the Start Mode of the SQL Server FullText Search service, right-click the service and then click Properties. On the Service tab, locate Start Mode, select Automatic, and then click OK.

Step 7: Run the TFSUpgradeAT Tool to Update Windows SharePoint Server Database Names

Before you can install Team Foundation Server RTM, you must run the TFSUpgradeAT tool to update Windows SharePoint Server database names.

 

To run the TFSUpgradeAT tool

1.      At the command prompt, change directories to the directory where you installed the upgrade software.

2.      Type the following at the command line:

TFSUpgradeAT.exe

Step 8: Install the ASP.NET Update from the Product Media

You must install an update for ASP.NET before you install Team Foundation Server RTM or the installation will fail. The update is included on the Team Foundation Server product media in the KB913393 folder and can also be downloaded from the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=62733).

Step 9: Install Team Foundation Server RTM

Review the latest instructions for Team Foundation Server installation in a single-server deployment in the Help file TFSInstall.chm, available on your installation media, and also available online at the Microsoft Web site (http://go.microsoft.com/fwlink/?linkid=40042).

 

To install Team Foundation Server RTM in a single-server deployment

1.      Complete all Team Foundation Server upgrade prerequisites detailed earlier in steps 1 through 8.

2.      Log on to Windows using the Team Foundation Server Setup account; for example, Domain\TFSSETUP.

3.      On the Autorun page that appears after you insert the installation media, click Install Team Foundation Server, and then click Single-Server Installation.

If the Autorun page does not appear, locate and run the autorun file (autorun.exe) in the root folder on the installation media.

The Visual Studio Team Foundation Server Setup wizard starts.

4.      On the Welcome to Setup page, click Next.

5.      On the Microsoft Software License Terms 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.

6.      On the Destination Folder page, accept the default destination folder and then click Next.

7.      On the System Health Check page, the setup wizard will scan the system for conditions that could cause setup to fail, or cause issues later during server operation. After the system scan is completed, setup will report the status of the system health check. If the system health check finds any issues, you can click a link to review a report about specific warnings and blocks. Warnings should be addressed before continuing with setup, but should not prevent setup from completing. Blocks must be addressed before continuing with setup. If the system health check did not find any blocks, click Next. Otherwise, click Cancel and run setup again after fixing any blocking issues.

8.      On the Service Logon Account page, in the Account Name box, type the Windows domain user account you created for the Team Foundation Server Service account (for example, Domain\TFSSERVICE), type the password in the Password box, and then click Next.

9.      On the Reporting Logon Account page, type the account information for the Team Foundation Server Reporting account (for example, Domain\TFSREPORTS), and then click Next.

Note   This account should not be the same as the Team Foundation Server Setup or Service accounts.

10.  On the Specify Alert Settings page, select Enable Team Foundation Alerts, and type the following information:

·         In the SMTP server box, type the name of the server that you will use to send e-mail notifications.

·         In the From e-mail address box, type the name of the e-mail address from which notifications appear to come, and then click Next.

11.  On the Ready to Install page, click Install.

12.  On the Installing Components page, you can monitor the installation of Team Foundation Server.

Note   During installation, you might be prompted to restart the computer. Click Restart Now and setup will continue after the computer restarts and you log on again.

13.  On the Setup Completed Successfully page, click Finish.

Step 10: Update the Team Foundation Reporting Warehouse

To make sure that the reporting warehouse is updated immediately after installation, verify that the TFSServerScheduler service is running and then manually update the reporting warehouse.

Note   In large Team Foundation Server deployments, updating the warehouse can take several hours.

 

To verify that the TFSServerScheduler service is running

1.      On the Team Foundation Server, click Start, point to Administrative Tools, and then click Services.

2.      In the Services window, locate TFSServerScheduler, and confirm that the Status column says Started.

If the service is not started, right-click TFSServerScheduler, and then click Start.

 

To manually update the Team Foundation Reporting Warehouse

1.      On the Team Foundation Server, open Internet Explorer.

2.      Open http://localhost:8080/Warehouse/v1.0/warehousecontroller.asmx.

3.      Click GetWarehouseStatus, and then click Invoke.

Wait for the service to idle. The service should return Running Adapters, ProcessingOlap, and then idle. The four possible return states are as follows:

·         Idle   The warehouse is not processing.

·         RunningAdapters   The adapters are applying schema changes or pulling data into the warehouse.

·         ProcessingOlap   The warehouse is processing schema changes or data changes in the OLAP cube.

·         Blocked   The warehouse is blocked.

4.      Open http://localhost:8080/Warehouse/v1.0/warehousecontroller.asmx.

5.      Click Run and then click Invoke.

This starts the processing of the warehouse. The service returns True or False whether it has started processing (asynchronously).

Note   You can repeat step 3 to monitor the processing.

6.      To verify, you can repeat step 2 to validate data.

Step 11: Install Team Explorer

To install Team Explorer and connect it to the Team Foundation Server, follow the instructions in the Help file TFSInstall.chm, available on the installation media, and also available online at the Microsoft Web site (http://go.microsoft.com/fwlink/?linkid=40042). You can install Team Explorer on the Team Foundation Server itself or on any computer that meets its requirements.

Step 12: Upgrade the Build Types for All Projects

You must upgrade the build types for all projects you want to upgrade from Team Foundation Server Beta 3 Refresh to Team Foundation Server RTM.

 

To upgrade the build type for all projects

1.      On the computer where you installed Team Explorer, at the command prompt, change directories to the directory where you installed the upgrade software.

2.      At the command prompt, run the TFSBuildUpgrade tool by typing in the following, where servername is the name of your Team Foundation Server:

TFSBuildUpgrade.exe servername

Step 13: Upload Default Reports for All Projects

Team Foundation Server process templates and reports have changed from Beta 3 Refresh to RTM. Even if you were using the reports included in the product without any customized changes, you still must manually upload the reports that come with Team Foundation Server RTM before you can use them. You must upload the default reports for all projects you want to upgrade from Team Foundation Server Beta 3 Refresh to Team Foundation Server RTM. Follow these steps for each project you want to upgrade.

Note   Customized reports from Team Foundation Server Beta 3 Refresh will not work in Team Foundation Server RTM without manual customization. You must manually modify any custom reports before you can upload them to Team Foundation Server RTM. For more information, see the Incorporating Customizations from Team Foundation Server Beta 3 Refresh into Team Foundation Server RTM section that is shown here.

Important   You must upgrade the default reports for all process templates you intend to use in Team Foundation Server that include reports for the original process templates that were included with Team Foundation Server Beta 3 Refresh.

 

To upgrade the default reports for a project

1.      Open Team Explorer or Visual Studio 2005 with Team Explorer.

2.      On the Tools menu, click Connect to Team Foundation Server.

3.      In the Connect to Team Foundation Server dialog box, select the Team Foundation Server you installed in Step 9.

Note   If the drop-down list is empty, click Servers to manually enter the settings for the Team Foundation Server you installed in Step 9.

4.      Under Team projects, select one or more team projects from the list. Team projects with a check mark next to them will display in Team Explorer.

5.      Click OK.

6.      On the Team menu, point to Team Foundation Server Settings, and then click Process Template Manager.

The Process Template Manager lists each process template installed on the Team Foundation Server.

7.      Click Download.

8.      Download a new version of the process template that contains the reports you want to use in Team Foundation Server RTM and save it to a specified folder. If you want to use more than one process template, make sure that you download the new version of each process template you want to use.

Note   After you upgrade, both the old process template versions you used in Team Foundation Server Beta 3 Refresh and the new versions of the process templates (designated with a “-v4.0” at the end of the process template name) will be available. Make sure that you use the new versions of the process templates after you upgrade.

9.      Click Close to close the Process Template Manager.

10.  At the command prompt, change directories to the directory where you installed the upgrade software.

11.  At the command prompt, run the TFSUploadReports tool by typing the following, where projectname is the name of the project you want to upgrade, servername is the name of your Team Foundation Server, drive is the drive where the templates are stored, templatepath is the path of the template directory, and templatedirectory is the name of the directory where the stock report templates are stored:

TFSUploadReports.exe /s servername /p projectname /t drive:\templatepath\templatedirectory

12.  Repeat these steps for each project in which you want to use default reports.


Dual Server Deployment

Step 1: Download the Upgrade Software and Run the TFSUpgradeRTM Tool

The first step to upgrading your Team Foundation Server Beta 3 deployment to Team Foundation Server RTM is to download the upgrade software to the Team Foundation data-tier server and resolve any potential upgrade conflicts.

 

To download the upgrade software and run the TFSUpgradeRTM tool on the Team Foundation data-tier server to scan for any upgrade issues

1.      Download the upgrade software from the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkID=60341) or install it from the upgrade media.

2.      At the command prompt, change directories to the directory where you installed the upgrade software. To make sure that you have the correct directory, type dir at the command-line and make sure that the TFSUpgradeRTM.exe tool is listed.

Note   If you see the command TFSUpgrade.exe instead, you have a Release Candidate (RC) version of the Team Foundation Server software instead of the RTM version. Obtain a RTM version of the Team Foundation Server software, or if you want to upgrade to the RC version, know that the steps in this guide are not designed for the RC version and will differ slightly in some areas.

3.      Type the following at the command line, where servername is the name of your Team Foundation Server data-tier server:

TFSUpgradeRTM.exe servername /verify

4.      When you are prompted to confirm if you want to run this command, click Yes.

5.      Follow the instructions that appear on the screen to resolve any reported issues.

Note   Depending on your configuration, you might see an error message that prompts you to run the witfields command-line utility. The witfields command-line utility is located by default in drive\Program Files\Visual Studio8\Common7\IDE on any computer where you have installed Team Explorer. For more information, see witfields in Administering Team Foundation Server.

Step 2: Uninstall Team Foundation Server Beta 3 Refresh and Team Explorer

Use Add or Remove Programs to uninstall Team Foundation Server and Team Explorer on your application-tier server and your data-tier server.

Note   Depending on your configuration, you might not have Team Explorer installed on your Team Foundation application-tier server or your Team Foundation data-tier server. If it is installed, you must uninstall it.

 

To uninstall Team Foundation Server Beta 3 Refresh

1.      On the Team Foundation application-tier server, click Start, click Settings, click Control Panel, and then click Add or Remove Programs.

2.      Select Microsoft Visual Studio 2005 Team Foundation Server.

3.      Click Change/Remove.

4.      In the setup dialog box, select Uninstall, and then click Next.

5.      Click OK on the confirmation dialog box.

6.      Click Finish when completed.

7.      On the Team Foundation data-tier server, click Start, click Settings, click Control Panel, and then click Add or Remove Programs.

8.      Select Microsoft Visual Studio 2005 Team Foundation Server.

9.      Click Change/Remove.

10.  In the setup dialog box, select Uninstall, and then click Next.

11.  Click OK on the confirmation dialog box.

12.  Click Finish when completed.

 

To uninstall Team Explorer

1.      On the Team Foundation application-tier server, click Start, click Settings, click Control Panel, and then click Add or Remove Programs.

2.      Select Microsoft Visual Studio 2005 Team Explorer.

3.      Click Change/Remove.

4.      In the setup dialog box, select Uninstall, and then click Next.

5.      Click OK on the confirmation dialog box.

6.      Click Finish when completed.

7.      On the Team Foundation data-tier server, click Start, click Settings, click Control Panel, and then click Add or Remove Programs.

8.      Select Microsoft Visual Studio 2005 Team Explorer.

9.      Click Change/Remove.

10.  In the setup dialog box, select Uninstall, and then click Next.

11.  Click OK on the confirmation dialog box.

12.  Click Finish when completed.

 

Step 3: Enable Network Traffic for SQL Server and Reporting Services Administration Between the Team Foundation Application Tier and the Team Foundation Data Tier in Dual-Server Installations

If you have a dual-server installation and you have a firewall or router configured to control network traffic between the two servers, you must enable network traffic for SQL_SERVICES and Reporting Services Administration between the two servers after you remove Team Foundation Server Beta 3 Refresh, as this port will have been automatically closed. By default, the network port for SQL_SERVICES traffic is 1433, but check to make sure that you did not specify another port during installation.

Note   As an alternative to the procedures in the following section, you can choose to turn off Windows Firewall on the Team Foundation application-tier server and the Team Foundation data-tier server for the duration of the upgrade. For more security, leave Windows Firewall enabled and instead enable the network ports as described in the procedures.

 

To verify the port for SQL_Services

1.      On the Team Foundation data-tier server, click Start, point to All Programs, point to Microsoft SQL Server 2005, point to Configuration Tools, and then click SQL Server Configuration Manager.

2.      In the Explorer pane, expand SQL Server Native Client Configuration, and then click Client Protocols. Double-click TCP/IP and write down the port number listed next to Default Port. This will be the port number for which you must enable network traffic or the upgrade will fail.

To open the network port for SQL_SERVICES and Reporting Services Administration

1.      Open a Command Prompt window on the Team Foundation data-tier server. To open a Command Prompt window, click Start, click Run, type cmd, and then click OK.

2.      At the command line, type the following:

netsh firewall set service RemoteAdmin enable

Note   You must restart your computer after changing this setting.

3.      Open a Command Prompt window on the Team Foundation application-tier server. To open a Command Prompt window, click Start, click Run, type cmd, and then click OK.

4.      At the command line, type the following, where port is the SQL Server port number:

netsh firewall set portopening TCP port SQL_PORT ENABLE ALL

For example, if you have enabled Windows Firewall on the Team Foundation application-tier server, and you used the default SQL Server port, you would type the following at the command line:

netsh firewall set portopening TCP 1433 SQL_PORT ENABLE ALL

For more information about Windows Firewall and the netsh command-line utility, see Help and Support.

Note   After you have successfully upgraded to Team Foundation Server RTM, do not forget to restore your original firewall settings.

Step 4: Back Up the Encryption Key for Reporting Services

You must have a back up of this key in order to complete an upgrade of a dual-server installation of Team Foundation Server Beta 3 Refresh to Team Foundation Server RTM. In a dual-server deployment, you must use the RSKEYMGMT command.

 

To back up the encryption key using the RSKEYMGMT command

1.      On the Team Foundation data-tier server, open the Command Prompt window and locate the RSKEYMGMT tool. By default, the tool is located in the installation directory as follows: drive:\Program Files\Microsoft SQL Server\90\Tools\Binn.

2.      Use the -e, -f, and -p options of the RSKEYMGMT tool to create a backup file that is password protected for the encryption key.

For example, the following command line extracts the key, creates a file named MyRSKeyBackUp, and specifies a password to encrypt or decrypt the key.

RSKEYMGMT -e -f c:\mybackups\MyRSKeyBackUp.snk -p StrongPassword

Note   For more information about the RSKEYMGMT tool, use the /? option. For example, you can run RSKEYMGMT /? in a Command Prompt window.

Step 5: Back up Team Foundation Server Databases

The procedure for backing up Team Foundation Server databases in Beta 3 Refresh is located online at http://blogs.msdn.com/vstsue/articles/500334.aspx. Examine this document for any late-breaking changes.

 

If you have already created a backup maintenance plan, you can use the latest incremental and full backups for restoration. If not, follow these steps to create a full backup of the following databases:

·         ReportServer

·         ReportServerTempDB

·         STS_Config

·         STS_servername_# (where servername is the name of the server and # is a number)

·         TfsActivityLogging

·         TfsBuild

·         TfsIntegration

·         TfsVersionControl

·         TfsWarehouse

·         TfsWorkItemTracking

·         TfsWorkItemTrackingAttachments

 

To create a full backup plan and run a full backup on a Team Foundation Server:

1.      On the Team Foundation Server data-tier server, open SQL Server Management Studio. To open SQL Server Management Studio, click Start, click All Programs, click Microsoft SQL Server 2005, and then click SQL Server Management Studio.

2.      Select Database Engine for the Server type. Select the appropriate server name and authentication scheme for the server. Provide a valid user name and password if it is required by your SQL Server, and then click Connect.

3.      In SQL Server Management Studio, expand the Management node, right-click Maintenance Plans, and then select Maintenance Plan Wizard.

4.      On the Maintenance Plan Wizard welcome page, click Next.

5.      On the Select a Target Server page, provide a name for this maintenance plan.

6.      Select the appropriate server and authentication scheme for your SQL Server. Provide a user name and password if it is required by your SQL Server, and then click Next.

7.      On the Select Maintenance Tasks page, select Back Up Database (Full), and then click Next.

8.      On the Select Maintenance Task Order page, click Next.

9.      On the Define Back Up Database (Full) Task page, from the Databases drop-down list where it says Select one or more, select the databases listed earlier, and then click OK.

10.  On the Define Back Up Database (Full) Task page, select the desired destination options for your back up. See the SQL Server 2005 Books Online for detailed information about the options on this dialog box. (Select the Maintenance Plan Wizard dialog box and press F1 for help specific to the dialog box.) Make sure that the backup files are stored on another secure computer, and not the computer that you are about to upgrade. Click Next.

11.  On the Select Plan Properties page, click Change.

12.  On the New Job Schedule page, in Name, provide a name for the back up job. Change the Schedule type to One Time, and leave Enabled selected. Leave Date set to the current date and time. Click OK, and then click Next.

13.  On the Select Report Options page, optionally select the desired report distribution options. Click Next.

14.  Click Finish to complete creating the Maintenance Plan. The backup will start immediately after clicking Finish.

15.  When the backup is completed, click Close.

Note   Make sure that the database backup has completed before continuing on to Step 6.

Step 6: Run the TFSUpgradeRTM Tool

After uninstalling Team Foundation Server Beta 3 Refresh, you must rerun the TFSUpgradeRTM tool on your Team Foundation data-tier server.

 

To run the TFSUpgradeRTM tool

1.      At the command prompt, change directories to the directory where you installed the upgrade software.

2.      Type the following at the command line, where servername is the name of your Team Foundation data-tier server:

TFSUpgradeRTM.exe servername

Step 7: Run the TFSUpgradeAT Tool to Update Windows SharePoint Server Database Names

Before you can install Team Foundation Server RTM, you must run the TFSUpgradeAT tool on the Team Foundation application-tier server to update Windows SharePoint Server database names.

 

To run the TFSUpgradeAT tool

1.      Download the upgrade software from the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkID=60341) or install it from the upgrade media.

2.      On the Team Foundation application-tier server, at the command prompt, change directories to the directory where you installed the upgrade software.

3.      Type the following at the command line:

TFSUpgradeAT.exe

Step 8: Install SQL Report Server on the Team Foundation Application-Tier Server

When configuring Team Foundation Server for a dual-server deployment, you must install SQL Report Server on the computer that you want to serve as the Team Foundation application-tier server for Team Foundation Server RTM.

 

To install SQL Report Server on the Team Foundation Application Tier Server

1.      On the Team Foundation application-tier server, log on to Windows using the Team Foundation Server Setup account; for example, Domain\TFSSETUP.

2.      On the Autorun page that appears after you insert the installation media, under Install, click Server components, tools, Books Online, and samples.

If the Autorun page does not appear, locate and run the autorun file (splash.hta) in the Servers folder on the installation media.

The Microsoft SQL Server 2005 Setup wizard starts.

3.      On the End User License Agreement page, review the license agreement. If you accept the terms and conditions, select I accept the license terms and conditions, and then click Next.

4.      On the Installing Prerequisites page, click Install. After the required components are installed successfully, click Next.

The Microsoft SQL Server Installation Wizard starts.

5.      Click Next to start the System Configuration Check.

6.      On the System Configuration Check page, verify the status of any required actions, such as required system restarts and follow the guidance on this page until all actions achieve Success status. After all actions achieve Success status, click Next to start installation.

Note   It may take several moments for the installer to start.

7.      On the Registration Information page, complete the registration information, and then click Next.

8.      On the Components to Install page, select Reporting Services, and then click Next.

Note   If you click Advanced, do not remove any default selections.

9.      On the Instance Name page, select Default instance, and then click Next.

Important   Team Foundation Server setup will fail if you specify a named instance.

10.  On the Service Account page, select Use the built-in System account and from the list, select Network Service. In Start services at the end of setup, select Reporting Services, and then click Next.

11.  On the Report Server Installation Options page, click Next. By default, Install but do not configure the server is selected.

12.  On the Error and Usage Report Settings page, you can optionally select Automatically send Error reports for SQL Server 2005 to Microsoft or your corporate error reporting server and Automatically send Feature Usage data for SQL Server 2005 to Microsoft, and then click Next.

13.  On the Ready to Install page, you can review the list of components to be installed, and then click Install.

14.  On the Setup Progress page, you can monitor the installation status of each component. After setup has completed, click Next.

Note   Installation may appear to stall for several minutes during activation of SQL Server Reporting Services.

15.  Click Finish to exit the wizard.

Step 9: Install the SQL Server Update On the Team Foundation Data-Tier Server

You must install an update for SQL Server (KB914595) before you install Team Foundation Server RTM or you might experience problems with your computer memory. The update can be found on the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=62015) and can also be found on the Team Foundation Server product media.

 

To install the SQL Server Update

1.      On the Team Foundation data-tier server, click Start, point to All Programs, point to Microsoft SQL Server 2005, point to Configuration Tools, and then click SQL Server Configuration Manager.

2.      In the Explorer pane, click SQL Server 2005 Services.

3.      Right-click SQL Server Browser, and then click Stop.

4.      On the Team Foundation Server installation media, locate the SQLServerKB folder.

Note   On Team Foundation Server Release Candidate (RC) media, this folder is named KB912838. If you see this folder, you have an RC version of the Team Foundation Server media. Obtain a RTM version of the media to upgrade to Team Foundation Server RTM.

5.      Locate the executable file (.exe) for the operating system and language, such as AS2005-KBnnnnnn-x86-ENU.exe, and then double-click the file to start the Hotfix Installer.

6.      In the Hotfix Installer, accept the End User License Agreement, complete the pages to install the hotfix, and then click Finish.

7.      In SQL Server Configuration Manager, right-click SQL Server Browser and then click Properties.

8.      On the Service tab, locate the Start Mode and select Automatic.

9.      On the Log On tab, click Start.

Note   If Start is not enabled on the Log On tab, click the Service tab, set the Start Mode to Disabled, and then again select Automatic to explicitly update the Start Mode.

Step 10: Verify that the SQL Server FullText Search Service is Started

Unlike Team Foundation Server Beta 3 Refresh, Team Foundation Server RTM depends on the SQL Server FullText Search service. You must make sure that this service is started and set to Automatic, or the upgrade might fail.

 

To verify that the SQL Server FullText Search service is started

1.      On the Team Foundation data-tier server, open SQL Server Configuration Manager.

2.      In the Explorer pane, click SQL Server 2005 Services.

3.      Review the list of services for SQL Server FullText Search (MSSQLSERVER). Make sure that State is listed as Running and that the Start Mode is listed as Automatic. If the state is not Running or the start mode is not listed as Automatic, do the following:

·         To start the SQL Server FullText Search service, right-click the service and then click Properties. On the Log On tab, click Start, and then click OK.

Note   If Start is not enabled on the Log On tab, click the Service tab, set the Start Mode to Disabled, and then again select Automatic to explicitly update the Start Mode.

·         To change the Start Mode of the SQL Server FullText Search service, right-click the service and then click Properties. On the Service tab, locate Start Mode, select Automatic, and then click OK.

Step 11: Restore the Reporting Services Encryption Key from Team Foundation Server Beta 3 Refresh

After you install SQL Report Server, you must modify the Reporting Services encryption key so that you will be able to install, configure, and use SQL Report Server together with Team Foundation Server. You must configure SQL Report Server to connect to the SQL Report Server database catalog before you can restore the encryption key. You must restore the encryption key from the back up you made earlier.

Important   Do not back up or create a new encryption key on this SQL Server instance before you restore the encryption key you saved in Step 4.

 

To modify the Reporting Services encryption key

1.      On the Team Foundation application-tier server, click Start, click All Programs, click Microsoft SQL Server, click Configuration Tools, and then click Reporting Services Configuration.

2.      Verify that you are connecting to the correct Report Server and then click OK.

3.      In the Explorer pane, click Report Server Virtual Directory. On the Report Server Virtual Directory Settings page, click New.

4.      In Create a New Virtual Directory, click OK.

5.      On the Report Server Virtual Directory Settings page, click Apply, if Apply is active.

6.      In the Explorer pane, click Report Manager Virtual Directory. On the Report Manager Virtual Directory Settings page, click New.

7.      On the Report Manager Virtual Directory Settings page, click Apply, if Apply is active.

8.      In the Explorer pane, click Web Service Identity.

9.      On the Web Service Identity page, next to Report Server, click New. On the New Application Pool page, in Application Pool Name, type ReportServer. Click Built-in Account, select Network Service, and then click OK.

10.  On the Web Service Identity page, next to Report Manager, select ReportServer from the drop-down list.

11.  On the Web Service Identity page, click Apply.

12.  In the SQL Server Connection Dialog dialog box, click OK.

13.  In the Explorer pane, click Database Setup. On the Database Connection page, type the name of the Team Foundation data-tier server in Server Name, type ReportServer in Database, and then click Connect.

Note   Do not change the authentication type from Current User - Integrated Security.

14.  In the SQL Server Connection Dialog dialog box, click OK.

15.  On the Database Connection page, click Apply, if Apply is active.

16.  In the SQL Server Connection Dialog dialog box, click OK.

17.  In the Explorer pane, click Windows Service Identity. On the Windows Service Identity page, in the Built-in Service Account drop-down box, Network Service should be selected, but Apply is unavailable. To grant the Team Foundation application-tier server log on permissions to the SQL Server on the Team Foundation data-tier, in the Built-in Service drop-down box, select Local Service. Do not click Apply, but instead return to the Built-in Service drop-down box and re-select Network Service. When Network Service is selected and Apply is available, click Apply.

18.   In the SQL Server Connection Dialog dialog box, click OK.

19.  Restore the encryption key and remove previous instances of Report Server by doing one of the following:

If you are running SQL Report Server Enterprise Edition

1.      In the Explorer pane of Reporting Services Configuration, click Encryption Keys.

2.      In the Explorer pane, click Encryptions Keys. On the Encryption Key page, click Restore.

3.      On the Encryption Key Information page, type the password for the encryption key file in Password, type or select the backup encryption key .snk file location in Key File, and then click OK.

4.      In the Explorer pane of Reporting Services Configuration, click Initialization. On the Initialization page, select the instance ID that corresponds with the name of the Team Foundation data-tier server. Click Remove, and then click OK.

If you are running SQL Report Server Standard Edition:

1.      Close the Reporting Services Configuration tool.

2.      Click Start, click Run, type cmd, and then click OK to open a Command Prompt window.

3.      Change directories to drive:\%PROGRAMFILES%\Microsoft SQL Server\90\Tools\binn.

4.      Type the following command to view a list of Reporting Service instances:

RSKeyMgmt -l

5.      Review the list to find the name of the Reporting Service instance that corresponds with the name of the Team Foundation data-tier server. Type the following command to remove that instance, where DTInstanceID is the name of the instance that corresponds with the name of the Team Foundation data-tier server:

RSKeyMgmt –r DTInstanceID

6.      On the Team Foundation application-tier server, click Start, click All Programs, click Microsoft SQL Server, click Configuration Tools, and then click Reporting Services Configuration.

7.      In the Explorer pane, click Encryptions Keys. On the Encryption Key page, click Restore.

8.      On the Encryption Key Information page, type the password for the encryption key file in Password, type or select the backup encryption key .snk file location in Key File, and then click OK.

Step 12: Delete the Reporting Services Application Pools From Internet Information Services (IIS)

After you install SQL Report Server, you must delete the Reporting Services application pools, or installation of Team Foundation Server RTM will fail.

Warning   Failure to complete this step can cause your installation of Team Foundation Server RTM to fail.

 

To remove the Reporting Services application pools

1.      On the Team Foundation application-tier server, click Start, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.

2.      In the Explorer pane, expand the server node, expand Web Sites, and then expand Default Web Site.

3.      Right-click ReportServer, and then click Delete. On the confirmation dialog box, click Yes.

4.      Right-click Reports, and then click Delete. On the confirmation dialog box, click Yes.

5.      In the Explorer pane, expand Application Pools.

6.      Right-click ReportServer, and then click Delete. On the confirmation dialog box, click Yes.

Step 13: Install the ASP.NET Update From the Product Media

You must install an update for ASP.NET on the Team Foundation application-tier server before you install Team Foundation Server RTM, or the installation will fail. The update is included on the Team Foundation Server product media in the KB913393 folder.

Step 14: Remove SQL Report Server from the Team Foundation Data Tier Server

In Team Foundation Server RTM, SQL Report Server no longer has to be installed on the Team Foundation data-tier server. Use Add or Remove Programs to remove SQL Report Server from the Team Foundation data-tier server to complete the migration from Team Foundation Server Beta 3 Refresh.

 

To uninstall SQL Report Server from the Team Foundation Data-Tier Server

1.      On the Team Foundation data-tier server, click Start, click Settings, click Control Panel, and then click Add or Remove Programs.

2.      Select Microsoft SQL Server 2005.

3.      Click Change.

4.      In the Microsoft SQL Server 2005 Maintenance dialog box, select MSSSQLSERVER: Analysis Services, Database Engine, Reporting Services, and then click Next.

5.      In the Feature Maintenance dialog box, select Reporting Services, and then click Next.

6.      On the Welcome to the Microsoft SQL Server Installation Wizard page, click Next.

7.      On the System Configuration Check page, click Next.

8.      On the Change or Remove Instance page, click Change Installed Components.

9.      On the Feature Selection page, click Reporting Services, click Entire feature will be unavailable, and then click Next.

10.  On the Ready to Update page, click Install.

11.  On the Setup Progress page, you can monitor the progress of the Reporting Services component removal. When all products report Setup finished, click Next.

12.  On the Completing Microsoft SQL Server 2005 Setup page, click Finish.

Step 15: Install Team Foundation Server RTM

Review the latest instructions for Team Foundation Server installation in a dual-server deployment in the Help file TFSInstall.chm, available on your installation media, and also available online at the Microsoft Web site (http://go.microsoft.com/fwlink/?linkid=40042).

 

To install Team Foundation Server RTM on the data-tier in a dual-server deployment

1.      Complete all the prerequisite upgrade steps, as described earlier.

2.      On the Team Foundation data-tier server, log on to Windows using the Team Foundation Server Setup account; for example, Domain\TFSSETUP.

3.      On the Autorun page that appears after you insert the installation media, click Install Team Foundation Server, click Dual-Server Installation, and then click Install the Team Foundation Databases Tier ONLY.

If the Autorun page does not appear, locate and run the autorun file (autorun.exe) in the root folder on the installation media.

The Visual Studio 2005 Team Foundation Server (databases) Setup wizard starts.

4.      On the Welcome to Setup page, click Next.

5.      On the Microsoft Software License Terms 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.

6.      On the Destination Folder page, accept the default destination folder and then click Next.

7.      On the System Health Check page, the setup wizard will scan the system for conditions that could cause setup to fail, or cause issues later during server operation. After you complete the system scan, setup will report the status of the system health check. If the system health check finds any issues, you can click a link to review a report about specific warnings and blocks. Warnings should be addressed before continuing with setup, but should not prevent setup from completing. Blocks must be addressed before continuing with setup. If the system health check did not find any blocks, click Next. Otherwise, click Cancel and run setup again after fixing any blocking issues.

8.      On the Service Account page, type the Windows domain user account you created for the Team Foundation Server Service account (for example, Domain\TFSSERVICE) in the Web service account name box, and then click Next.

9.      On the Ready to Install page, click Install.

10.  On the Installing Components page, you can monitor the installation of Team Foundation data-tier components.

During installation, you may be prompted to restart your computer. Click Restart Now and setup will continue after the computer restarts and you log on again using the same account.

11.  On the Setup Completed Successfully page, click Finish.

12.  On the Autorun page, click Exit.

 

To install Team Foundation Server RTM on the application-tier in a dual-server deployment:

1.      Complete all the prerequisite upgrade steps, as described earlier.

2.      On the Team Foundation application-tier server, log on to Windows using the Team Foundation Server Setup account; for example, Domain\TFSSETUP.

3.      On the Autorun page that appears after you insert the installation media, click Install Team Foundation Server, click Dual-Server Installation, and then click Install the Team Foundation Application Tier ONLY.

If the Autorun page does not appear, locate and run the autorun file (autorun.exe) in the root folder on the installation media.

The Visual Studio Team Foundation Server (services) Setup wizard starts.

4.      On the Welcome to Setup page, click Next.

5.      On the Microsoft Software License Terms 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.

6.      On the Destination Folder and Database Server page, type the following information:

·         In the Destination folder box, type the installation path, or accept the default.

·         In the Database Server box, type the name of the computer on which you installed the Team Foundation Server (databases).

Note   You must use the name of the computer, not the IP address.

7.      On the System Health Check page, the setup wizard will scan the system for conditions that could cause setup to fail, or cause issues later during server operation. After you complete the system scan, setup will report the status of the system health check. If the system health check finds any issues, you can click a link to review a report about specific warnings and blocks. Warnings should be addressed before continuing with setup, but should not prevent setup from completing. Blocks must be addressed before continuing with setup. If the system health check did not find any blocks, click Next. Otherwise, click Cancel and run setup again after fixing any blocking issues.

8.      On the Service Account page, type the account information for the Team Foundation Server Service account (for example, Domain\TFSSERVICE), and then click Next.

9.      On the Reporting Logon Account page, type the account information for the Team Foundation Server Reporting account (for example, Domain\TFSREPORTS), and then click Next.

Note   This account should not be the same as the Team Foundation Server Setup or Service accounts.

10.  On the Team Foundation Alerts page, type the following information:

·         In the SMTP server box, type the name of the server that you will use to send Team Foundation alerts.

·         In the From e-mail address box, type the name of the e-mail address for sending Team Foundation alerts, and then click Next.

11.  On the Ready to Install page, click Install.

During installation, you may be prompted to restart your computer. Click Restart Now and setup will continue after the computer restarts and you log on again.

12.  On the Setup Completed Successfully page, click Finish.

Step 16: Update the Team Foundation Reporting Warehouse

To make sure that the reporting warehouse is updated immediately after installation, verify that the TFSServerScheduler service is running and then manually update the reporting warehouse.

Note   In large Team Foundation Server deployments, updating the warehouse can take several hours.

 

To verify the TFSServerScheduler service is running

1.      On the Team Foundation application-tier server, click Start, point to Administrative Tools, and then click Services.

2.      In the Services window, locate the TFSServerScheduler, and confirm that the Status column says Started.

If the service is not started, right-click TFSServerScheduler, and then click Start.

 

To manually update the Team Foundation Reporting Warehouse

1.      On the Team Foundation application-tier server, open Internet Explorer.

2.      Open http://localhost:8080/Warehouse/v1.0/warehousecontroller.asmx.

3.      Click GetWarehouseStatus, and then click Invoke.

Wait for the service to idle. The service should return Running Adapters, ProcessingOlap, and then idle. The four possible return states are as follows:

·         Idle   The warehouse is not processing.

·         RunningAdapters   The adapters are applying schema changes or pulling data into the warehouse.

·         ProcessingOlap   The warehouse is processing schema changes or data changes in the OLAP cube.

·         Blocked   The warehouse is blocked.

4.      Open http://localhost:8080/Warehouse/v1.0/warehousecontroller.asmx.

5.      Click Run and then click Invoke.

This starts the processing of the warehouse. The service returns True or False depending on whether it has started processing (asynchronously).

6.      You can repeat step 3 to monitor the processing.

7.      To verify, you can repeat step 2 to validate the data.

Step 17: Install Team Explorer

To install Team Explorer and connect it to the Team Foundation Server, follow the instructions in the Help file TFSInstall.chm, available on the installation media and also available online at the Microsoft Web site (http://go.microsoft.com/fwlink/?linkid=40042). You can install Team Explorer on the Team Foundation Server itself or on any computer that meets its requirements.

Step 18: Upgrade the Build Types for All Projects

You must upgrade the build types for all projects you want to upgrade from Team Foundation Server Beta 3 Refresh to Team Foundation Server RTM. Follow these steps for each project you want to upgrade.

 

To upgrade the build type for all projects

1.      On the computer where you installed Team Explorer, at the command prompt, change directories to the directory where you installed the upgrade software.

2.      At the command prompt, run the TFSBuildUpgrade tool by typing in the following, where servername is the name of your Team Foundation application-tier server:

TFSBuildUpgrade.exe servername

Step 19: Upload New Default Reports for All Projects

Team Foundation Server process templates and reports have changed from Beta 3 Refresh to RTM. Even if you were using the reports included in the product without any customized changes, you still must manually upload the reports that come with Team Foundation Server RTM before you can use them. You must upload the default reports for all projects you want to upgrade from Team Foundation Server Beta 3 Refresh to Team Foundation Server RTM. Follow these steps for each project you want to upgrade.

Note   Customized reports from Team Foundation Server Beta 3 Refresh will not work in Team Foundation Server RTM without manual customization. You must manually modify any custom reports before you can upload them to Team Foundation Server RTM. For more information, see the Incorporating Customizations from Team Foundation Server Beta 3 Refresh into Team Foundation Server RTM section, later in this document.

Important   You must upgrade the default reports for all process templates you intend to use in Team Foundation Server that include reports for the original process templates that were included with Team Foundation Server Beta 3 Refresh.

 

To upgrade the default reports for a project

1.      Open Team Explorer or Visual Studio 2005 with Team Explorer.

2.      On the Tools menu, click Connect to Team Foundation Server.

3.      In the Connect to Team Foundation Server dialog box, select the Team Foundation Server you installed in Step 15.

Note   If the drop-down list is empty, click Servers to manually enter the settings for the Team Foundation Server you installed in Step 15.

4.      Under Team projects, select one or more team projects from the list. Team projects with a check mark next to them will display in Team Explorer.

5.      Click OK.

6.      On the Team menu, point to Team Foundation Server Settings, and then click Process Template Manager.

The Process Template Manager lists each process template installed on the Team Foundation Server.

7.      Click Download.

8.      Download a new version of the process template that contains the reports you want to use in Team Foundation Server RTM and save it to a specified folder. If you want to use more than one process template, make sure that you download the new version of each process template you want to use.

Note   After you upgrade, both the old process template versions you used in Team Foundation Server Beta 3 Refresh and the new versions of the process templates (designated with a “-v4.0” at the end of the process template name) will be available. Make sure that you use the new versions of the process templates after you upgrade.

9.      Click Close to close the Process Template Manager.

10.  At the command prompt, change directories to the directory where you installed the upgrade software.

11.  At the command prompt, run the TFSUploadReports tool by typing the following, where projectname is the name of the project you want to upgrade, servername is the name of your Team Foundation Server, drive is the drive where the templates are stored, templatepath is the path of the template directory, and templatedirectory is the name of the directory where the stock report templates are stored:

TFSUploadReports.exe /s servername /p projectname /t drive:\templatepath\templatedirectory

12.  Repeat these steps for each project in which you want to use some or all the default reports.


Updating Team Foundation Build Servers

If you have installed and configured any Team Foundation Build servers in your deployment, you must upgrade each of those build servers. The Beta 3 Refresh version of Team Foundation Build will not work correctly with Team Foundation Server RTM.

Step 1: Uninstall Team Foundation Build

You must uninstall the Team Foundation Server Beta 3 Refresh version of Team Foundation Build before you can upgrade to the Team Foundation Server RTM version of Team Foundation Build.

 

To uninstall Team Foundation Build

1.      On the Team Foundation Server Proxy computer, click Start, click Settings, click Control Panel, and then click Add or Remove Programs.

2.      Select Microsoft Visual Studio 2005 Team Foundation Server (build).

3.      Click Change/Remove.

4.      In the setup dialog box, select Uninstall, and then click Next.

5.      On the confirmation dialog box, click OK.

6.      Click Finish when completed.

Step 2: Install Team Foundation Build

Install Team Foundation Build on each server you want to configure as a build server.

 

To install Team Foundation Build

1.      On each server on which you want to install Team Foundation Build, log on to Windows using the same user account you used to install Team Foundation Server RTM.

2.      On the Team Foundation Server RTM upgrade media, locate the \build folder and run setup.

The Visual Studio 2005 Team Foundation Build Server Setup wizard starts.

3.      On the Welcome to Setup page, click Next.

4.      On the 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.

Note   If you do not agree to the terms and conditions, the Team Foundation Server Setup Wizard will not install Team Foundation Build.

5.      On the Destination Folder page, accept the default destination folder and then click Next.

6.      On the System Health Check page, the setup wizard scans the system for conditions that could cause setup to fail, or cause issues later during server operation. After you complete the system scan, setup reports the status of the system health check. If the system health check finds any issues, you can click a link to review a report about specific warnings and blocks. Warnings should be addressed before continuing with setup, but should not prevent setup from completing. Blocks must be addressed before continuing with setup. If the system health check did not find any blocks, click Next. Otherwise, click Cancel and run setup again after fixing any blocking issues.

7.      On the Service Account page, type the Windows domain user account you created for the Team Foundation Server Service account (for example, Domain\TFSSERVICE) in the Account Name box, type the password in the Password box, and then click Next.

Note   For this release, you must use the same Windows domain user account as the Team Foundation Server Service account.

8.      On the Ready to Install page, click Install.

Note   Setup creates program exceptions for MSBuild.exe and TeamBuildService.exe in Windows Firewall to communicate with Team Foundation Server.

9.      On the Installing Components page, you can monitor the installation of Team Build.

10.  On the Setup Completed Successfully page, click Finish.


Updating Team Foundation Server Proxy

If you have installed and configured Team Foundation Server Proxy in your deployment, you must upgrade the proxy.

Step 1: Back up the Team Foundation Server Proxy Proxy.Config File

You must make a copy of the Team Foundation Server proxy.config file before uninstalling and reinstalling Team Foundation Server Proxy.

 

To make a copy of the Team Foundation Server Proxy proxy.config file

1.      On the Team Foundation Server Proxy computer, open Windows Explorer and locate the drive:\%PROGRAMFILES%\Microsoft Visual Studio 2005 Team Foundation Server\Web Services\VersionControlProxy directory.

Note   If you installed Team Foundation Server Proxy in a different directory than the default directory, open that directory instead.

2.      Copy the proxy.config file in that directory to a portable media device or to another computer.

Step 2: Uninstall Team Foundation Server Proxy

You must uninstall the Team Foundation Server Beta 3 Refresh version of the Team Foundation Server Proxy before you can upgrade to the Team Foundation Server RTM version of the Team Foundation Server Proxy.

 

To uninstall Team Foundation Server Proxy

1.      On the Team Foundation Server Proxy computer, click Start, click Settings, click Control Panel, and then click Add or Remove Programs.

2.      Select Team Foundation Server (proxy).

3.      Click Change/Remove.

4.      In the setup dialog box, select Uninstall, and then click Next.

5.      On the confirmation dialog box, click OK.

6.      Click Finish when completed.

Step 3: Install the ASP.NET Update From the Product Media

You must install an update for ASP.NET on the Team Foundation Server Proxy computer before you install Team Foundation Server Proxy, or the installation will fail. The update is included on the Team Foundation Server product media in the KB913393 folder and can also be downloaded from the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=62733).

Step 4: Install Team Foundation Server Proxy

Install Team Foundation Server Proxy on the computer after you install the ASP.NET update.

 

To install Team Foundation Server Proxy

1.      On the Team Foundation Server Proxy computer, log on to Windows using the same user account you used to install Team Foundation Server RTM.

2.      On the Team Foundation Server RTM upgrade media, locate the \proxy folder and run setup.

The Visual Studio 2005 Team Foundation Server Proxy Setup wizard starts.

3.      On the Welcome to Setup page, click Next.

4.      On the 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.

Note   If you do not agree to the terms and conditions, the Team Foundation Server Setup Wizard will not install Team Foundation Server Proxy.

5.      On the System Health Check page, examine any warnings or blocks by clicking the report link.

·         Blocks must be addressed before setup can continue. Click Cancel and run setup again after fixing the issues.

·         Warnings should be addressed before continuing but should not prevent setup from completing. You can click Next.

·         If nothing is listed, click Next.

6.      On the Destination Folder page, accept the default destination folder, and then click Next.

7.      On the Default Cache Folder page, if you originally installed Team Foundation Server Proxy using the default paths, accept the default path and folder, and then click Next. If you used a custom path, type that path and folder, and then click Next.

8.      On the Service Account page, in the Account Name box, type the Windows domain user account you created for the Team Foundation Server Service account (for example, Domain\TFSSERVICE), type the password in the Password box, and then click Next.

Note   For this release, you must use the same Windows domain user account as the Team Foundation Server Service account.

9.      On the Ready to Install page, click Install.

10.  On the Installing Components page, you can monitor the installation of Team Foundation Server Proxy.

11.  On the Setup Completed Successfully page, click Finish. If Internet Explorer opens and the Configuring Team Foundation Server Proxy page appears, close Internet Explorer.

Step 5: Restore the Team Foundation Server Proxy Proxy.Config File

Instead of having to reconfigure Team Foundation Server Proxy after upgrade, you can use the previous Team Foundation Server proxy.config file to restore your previous settings.

 

To restore the Team Foundation Server Proxy Proxy.Config File

1.      On the Team Foundation Server Proxy computer, open Windows Explorer and locate the drive:\%PROGRAMFILES%\Microsoft Visual Studio 2005 Team Foundation Server\Web Services\VersionControlProxy directory.

Note   If you installed Team Foundation Server Proxy in a different directory than the default directory, open that directory instead.

2.      Open another instance of Windows Explorer and locate the portable media or location where you copied the previous Team Foundation Server Proxy proxy.config file.

3.      Copy the back up copy proxy.config file into the drive:\%PROGRAMFILES%\Microsoft Visual Studio 2005 Team Foundation Server\Web Services\VersionControlProxy directory.

Note   If you installed Team Foundation Server Proxy in a different directory than the default directory, copy the file to that directory instead.

4.      When you are prompted to confirm whether you want to overwrite the proxy.config file in the destination directory, click Yes.


Verifying the Success of the Upgrade

After you complete the upgrade from Team Foundation Server Beta 3 Refresh to Team Foundation Server RTM, consider performing the following tasks to verify the success of the upgrade. If you experience problems or error messages when performing these tasks, consider whether you want to contact Microsoft Support Services. For additional guidance, information, and assistance, visit the Microsoft Web site (http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=68&SiteID=1).

Connect Team Explorer to Team Foundation Server

If you have not already done this during the Team Foundation Server upgrade process, add the upgraded Team Foundation Server to Team Explorer and connect a Visual Studio 2005 client to the upgraded server.

 

To add a Team Foundation Server to the Team Explorer server list

1.      Start Microsoft Visual Studio 2005.

2.      On the Tools menu, click Connect to Team Foundation Server.

3.      On the Connect to Team Foundation Server dialog box, click Servers.

4.      On the Add/Remove Team Foundation Server dialog box, click Add.

5.      On the Add Team Foundation Server dialog box, in the Team Foundation Server Name box, type the name of the computer that hosts the Team Foundation Server application tier.

6.      In the Port Number box, specify the port to use for this connection (the default port is 8080 for HTTP) and select the corresponding protocol.

7.      Click OK to return to the Add/Remove Team Foundation Server dialog box.

8.      Click Close to return to the Connect to Team Foundation Server dialog box.

9.      If any team projects exist on this Team Foundation Server, select the ones that you want to use.

10.  Click OK.

 

To connect to a Team Foundation Server

1.      Start Microsoft Visual Studio 2005.

2.      On the Tools menu, click Connect to Team Foundation Server.

The Connect to Team Foundation Server dialog box appears.

3.      In the Connect to a Team Foundation Server list, select the Team Foundation Server you want to use.

4.      If any team projects exist on this Team Foundation Server, select the ones that you want to use.

5.      Click OK.

Create New Projects on Team Foundation Server

After you make sure that you can connect to the upgraded Team Foundation Server, create a new team project using each default process template you plan to use for production work. There will be two versions of the MSF for Agile Software Development and MSF for CMMI Process Improvement templates available on your Team Foundation Server after the upgrade, with very similar names. The new process template versions that have been updated with changes for Team Foundation Server RTM have numbers after their names so that you can tell what version of the process template you are about to use.

Note   While your custom process templates, if any, will also appear in the list, you should not try to create a project with these custom templates at this point. You will have to manually update your custom process templates before they can be used in Team Foundation Server RTM. For more information, see the section “Incorporating Customizations from Team Foundation Server Beta 3 Refresh to Team Foundation Server RTM” later in this document.

 

To create a team project

1.      On the File menu, click New Team Project.

The New Team Project wizard appears.

Note   If you are not using the Project Management environment settings, on the File menu, point to New, and then click Team Project.

Note   If you have not connected to a Team Foundation Server, you will be prompted to connect to one now.

2.      Under What is the name of the team project? on the Specify the Team Project Settings page, type a name for the team project that team members can easily associate with the software product. This name is what all team members will use to connect to the team project.

3.      Under Which process template should be used to create the team project? on the Select a Process Template page, select a default process template.

By default, two process templates are available: MSF for Agile Software Development-v4.0, and MSF for CMMI Process Improvement-v4.0. You can see a description for each process template by selecting the template and reading the text in The following describes the process template in more detail.

Note   If you want to use a process template that does not appear on the list, you must first upload the template to the Team Foundation Server.

4.      Complete the Specify the Setting for the Project Portal page:

·         What is the title of the team project portal?   If you want a project portal name different from the team project name, type a name that is easily identified by all team members. The site title is part of the home page of the project portal.

·         What is the description of the team project portal?   Enter a description for the project portal. The description is displayed on the home page of the project portal.

The project portal is a team Web site (using Windows SharePoint Services) that stores and versions team project-related documents.

5.      Complete the Specify Source Control Settings page by selecting one of three options, and then click Next:

·         Click to Create an empty source control folder and specify a name for the folder.

·         Click to Create a new source control branch and specify which folder to branch from.

·         Click Do not create a source control branch at this point.

6.      On the Confirm Team Project Settings page, review the choices and values that you specified. If the information is correct, click Finish. Otherwise, click Previous to make changes.

The New Team Project wizard creates your new team project.

Note   It may take several minutes for the wizard to finish.

7.      On the Team Project Creation Status page, view the status messages and status bar that describes what the wizard is doing.

8.      On the Team Project Created page, select Launch the process guidance for more information about how to run the team project if you want to read more details about the work items, roles, activities, and other aspects of the team process.

9.      Click Close.

10.  The new team project displays in Team Explorer. If the wizard encounters a problem when it is creating the new team project, you will see an error message describing the problem and suggesting corrective action.

11.  Repeat these steps to create a test project using each process template you intend to use in production projects.

Add a User or Group to a Project-Level Group

After you create test projects, you should try adding users or groups to these test project default groups to make sure that members of these groups can access the project correctly.

Note   Use user accounts or groups that must belong to production projects on your Team Foundation Server; as these user accounts or groups will be automatically added to the Team Foundation Valid Users group and cannot be removed.

 

To add a user account or group to a project-level group

1.      In Team Explorer, select the team project that the group is in.

2.      From the Team menu, point to Team Project Settings, and then click Group Membership.

3.      In the Project Groups dialog box, select the default group that you want to add users to, and then click Properties.

4.      In the Team Foundation Server Group Properties dialog box, on the Members tab, under Add Member, select Windows User or Group.

5.      Click Add.

6.      In the Select Users or Groups dialog box, under Enter the object names to select, enter the domain name and alias of the users whom you want to add in the following format:

domain\useralias

To add more than one user at a time, separate the entries with a semicolon (;).

7.      Click OK.

Configure Permissions for Default Groups in Windows SharePoint Services and Reporting Services

After you create your test projects and add a test user or group to each default group for the project, configure permissions for the default groups in Windows SharePoint Services and Reporting Services.

 

To configure permissions for default groups in Windows SharePoint Services

1.      In Microsoft Visual Studio 2005, open Team Explorer, and connect to Team Foundation Server.

2.      Right-click the team project node and then click Show Project Portal.

3.      Click Site Settings, click Go to Site Administration, and then click Manage Users.

4.      Click Add Users.

5.      In Step 1: Choose Users, add the user or group name that you added to the project-level group.

6.      In Step 2: Choose Site Groups, select the appropriate Windows SharePoint Services group, and then click Next.

7.      In Step 3: Confirm Users, add the e-mail address of the user or group.

8.      In Step 4: Send E-Mail, select whether to automatically send the user an e-mail, and then click Finish.

 

To configure permissions for default groups in Reporting Services

1.      Open Internet Explorer

2.      Type the following in the Address bar:

http://application-tier/Reports/Pages/Folder.aspx

where application-tier is the name of the Team Foundation application-tier report server. You can find the name of the report server by opening Team Explorer, expanding the Reports node, and viewing the properties of a report.

3.      Click the Properties tab and then click New Role Assignment.

4.      In Group or User Name, add the user or group name for the person you want to add to this group.

5.      In Role, select the appropriate Reporting Services group, and then click OK.

View and Add Work Items in the New Project

After adding test users or groups to the new projects, log on to the computer as a member of each group and verify that you can view and create work items in the project appropriate to the level of permissions of each group. Members of each default group should be able to view work items for the project.

 

To view work items for a project

1.      Open Team Explorer and connect to the Team Foundation Server.

2.      In the Explorer pane, expand each test project you created.

3.      In the Explorer pane, expand the Work Items folder and verify that the Team Queries and My Queries folders exist.

4.      In the Explorer pane, expand the Team Queries folder, and double-click the All – All Work Items query.

5.      Verify that work items appear in the query results pane. Work items are automatically created with each new project.

 

To add work items for a project

1.      Open Team Explorer.

2.      On the Team menu, click Add Work Item, and then pick the work item type from the list.

Note   As you use Team Foundation, it automatically adds your most recently used work items to the top of the Team menu for easy access.

3.      Complete the work item form by filling in all required fields.

Required fields are indicated by yellow shading.

4.      On the File menu, click Save All to save the work item.

Add a Solution to Source Control for the New Project

After verifying that work items are working correctly, add a solution to source control for the new project using one test account, and create a workspace and check out a solution file by using another test account.

 

To add a solution to source control

1.      In Solution Explorer, right-click the solution, and then click Add Solution to Source Control.

2.      In the Add Solution to Source Control dialog box (if you already have a workspace open, you do not see this dialog box; the solution is automatically added and you are not asked to provide a folder), move to where you want to add the project or solution under Team Project Location, and either accept default values, or click Make New Folder, and enter the desired folder name or change the name of the solution folder in the Type a name for the solution folder text box.

3.      Click OK.

 

To create a workspace

1.      Open Visual Studio 2005.

2.      On the File menu, select Source Control, and then click Workspaces.

3.      In the Manage Workspaces dialog box, click Add.

4.      Type a descriptive name in the Name box, enter a comment describing the new workspace in the Comment box, and provide alternative Owner and Computer name values, as necessary.

5.      Under Working Folders, in the Source Control Folder box, click the text box and then the ellipsis (…).

6.      In the Browse for Folder dialog box, select a server folder, and then click OK.

7.      Under Working Folders, in the Local Folder box, click the text Click here to enter a new working folder, click the text box, and then click the ellipsis (…).

8.      In the Browse for Folder dialog box, select a folder on your computer, and then click OK.

9.      In the Add Workspace dialog box, click OK to create the workspace.

10.  In the Manage Workspaces dialog box, click Close.

Tip   With the workspace established, right-click the project folder that has the source files that you want to get, and use the Get Latest Version command to populate your workspace with source from the server.

 

To populate the workspace with the source for your project

1.      Open Visual Studio 2005.

2.      On the View menu, click Other Windows, and then click Source Control Explorer.

3.      In Source Control Explorer, click Workspaces on the toolbar, and then click the new workspace from the list.

4.      With the new workspace selected, items that appear shaded indicate that they have not been copied to the local workspace. Locate a folder or file that you want to add to the new workspace, right-click, and then click either Get Latest Version to copy the latest version of the items, or Get Specific Version.

5.      In the Get dialog box, make sure that the file or folder you want to get is selected, and then select what type of version you want to get from the By drop-down list:

·         Changeset   Get a version based on a changeset.

·         Date   Get a version based on a date. If selected, click a date in the Date list.

·         Label   Get a version based on a label.

·         Latest Version   If selected, updates with the latest version in source control on the Team Foundation Server.

·         Workspace   Gets a version based on the workspace.

6.      (Optional) Select the Overwrite writable files that are not checked out option. If selected, files from the server will overwrite all files that do not have the read-only attribute associated with them and are not checked out. Only files on the server that are different will overwrite the files in the local workspace. By default, this option is not selected.

7.      (Optional) Select the Force get of file versions already in my workspace option. If selected, the source control server will only download files that differ from those located in the local workspace; otherwise, the server will download all files. By default, this option is selected.

8.      Click Get.

Source Control Explorer is displayed. If you chose Latest Version in step 5, the Latest column is updated with the status of Yes.

 

To check out and change a source-controlled file

1.      Open Visual Studio 2005.

2.      In Solution Explorer, highlight the item or items on which you want to work. Items that are currently checked in are designated in Solution Explorer with padlock icons. Right-click and select Check Out for Edit.

The Check Out dialog box appears.

3.      In the Check Out dialog box, make sure that the item or items on which you want to work are selected with a check mark in their respective check boxes and then select a locking option under the Lock section. The choices are as follows:

·         None - Allow shared content

·         Check Out - Prevent other users from checking out and checking in

·         Check In - Allow other users to check out but prevent them from checking in

4.      Click Check Out. Solution Explorer replaces the padlock icon with a check mark icon to indicate that the files are checked out to you.

Tip   A check mark indicates that the items are checked out with the None - Allow shared content option selected. A check mark with an exclamation point icon indicates that the items were checked out with either the Check Out - Prevent other users from checking out and checking in option or the Check In - Allow other users to check out but prevent them from checking in option selected.

 

Run A Build On A Build Type and Verify Build Reports

After you upgrade Team Foundation Server, run a build on a pre-existing build type for at least one project configured by using each process template type you use. For example, if you have projects that use MSF for Agile Software Development and projects that use MSF for CMMI Process Improvement, run two builds, one for a project that uses MSF for Agile Software Development, and one for a project that uses MSF for CMMI Process Improvement. You should also view a build report for every build and verify that all tasks finished successfully.

 

To run a build

1.      Open Visual Studio 2005.

2.      In Team Explorer, select the appropriate team project.

3.      On the Build menu, click Build TeamProjectName to display the Build dialog box, where TeamProjectName is the name of the project.

4.      Under the Build type drop-down list, select the build type that you want to run.

5.      Under Build Location, retain the default computer configured to use the build type or select a build server from the drop-down list.

6.      Under the build directory, retain the default directory configured for the build type or change the default directory that the build uses.

Note   When selecting the build directory, make sure that the directory has sufficient space to build; insufficient space leads to build failure.

7.      Click Build to start the build.

 

To view a build report

1.      Open Visual Studio 2005.

2.      In Team Explorer, locate the Team Builds node and expand the Build Summary node to display the Build Summary report. A summary appears that displays the completed and in-progress builds.

3.      In the summary report, double-click the build that you want to view. The build report displays its own tab with the name and version number of the build.

- or -

In Team Foundation Build, click the child build node associated with the build.

Note    For information about the build report, see Overview of Build Reports in Help.

4.      Verify that the build tasks listed in the summary report are marked as successful and have all the relevant information for completion date, status, quality, and so on.

5.      Double-click the build row and make sure that the detailed report for the build opens successfully and contains appropriate information.


Incorporating Customizations from Team Foundation Server Beta 3 Refresh into Team Foundation Server RTM

This section provides instructions on handling customizations which, generally, have been left untouched. You can start to use the upgraded system before these steps are completed.

Work Item Types

The work item types in existing projects do not reflect the changes that were made to Microsoft Solutions Framework work item types between Beta 3 and RTM. If you use the Microsoft Solutions Framework work item types without customization, you can select one of two ways to apply those changes.

·         Create a new project using the Microsoft Solutions Framework process template or templates that you have used in existing projects. This will update the work item types for the project.

·         Import the work item types explicitly.

1.      Download the process template(s) used on the server.

2.      Use the WITImport command-line tool to import the work item types from downloaded process templates.

 

If you have custom work item types that are derived from the Microsoft Solutions Framework work item types, you might want to update your work item types to reflect the changes that were made in Microsoft Solutions Framework. Most of the time, you can do this by reapplying the changes to the work item types and importing them.

1.      Download the Microsoft Solutions Framework process template that contains the work item types that were customized.

2.      Change the work item types from the Microsoft Solutions Framework process template to include your customizations.

3.      Use the WITImport command-line tool to import the updated work item types.

 

If your custom work item types changed the type or reportable type of a System field or a Microsoft field, you must change the reference name of that field so that it does not conflict.

1.      Use WIChangeRefName.exe to change the reference name of the conflicting field. Chose a reference name that is not in the System or Microsoft namespace.

2.      Update your work item types to refer to the new field.

3.      Use the WITImport command-line tool to import the updated work item types.

 

If you have customized field mappings for Microsoft Project integration, you must keep those in line with any changes you make to the work item types.

Work Item Tracking Queries

In Team Foundation Server Beta 3 Refresh and earlier versions, work item tracking used Active Directory or local computer account names instead of friendly names for fields such as Assigned To. Team Foundation Server RTM uses friendly names for these fields. Queries that use those fields and are set to an account name will return empty result sets until they are updated to search for display names.

Project Alerts

Any work item changed e-mail alerts created by users will be nonfunctional after the migration from Team Foundation Server Beta 3 Refresh to Team Foundation Server RTM. Users must manually re-create their alerts after the upgrade.

1.      Open Team Explorer. With a team project node selected, on the Team menu, click Project Alerts.

2.      Select the check box next to the alerts you want.

3.      For each alert, in the Send to column, add the e-mail addresses of the team members whom should receive the alert. You can use a distribution list to simplify specifying recipients.

4.      For each alert, in the Format column, select HTML or Plain text for the type of e-mail message to be sent.

5.      Click OK to save your alerts for the selected project.

Reports

In Team Foundation Server Beta 3 Refresh, most work item attributes were separate dimensions. In Team Foundation Server RTM, they are combined into a single work item dimension. The most significant of these changes occurs in the work item measure group. Therefore, any custom reports will probably not work with the new warehouse cube structure. You must download those custom reports and modify them to account for these changes before you can upload them to the server.

1.      Check out your customized reports from source control.

2.      Change the reports by using the correct dimensions.

3.      Upload the custom report to Team Foundation Server.

4.      Check in the modified custom report to source control.

 

Leave a Comment
  • Please add 7 and 3 and type the answer here:
  • Post
Page 1 of 1 (1 items)