TFS 2010 Upgrade Guidance-V1.4

TFS 2010- Supplemental Upgrade Guidance

Bijan Javidi, Pramod Vasanth, Matthew Mitrik

Microsoft Corporation

Visual Studio ALM Rangers

This content was created as part of a Ranger project. Visual Studio ALM Rangers is a special group

with members from the Visual Studio Product Group and Microsoft Services. Their mission is to

provide out of band solutions for missing features or guidance.


Copyright 2009 Microsoft Corporation Page | 2

The information contained in this document represents the current view of Microsoft Corporation on

the issues discussed as of the date of publication. Because Microsoft must respond to changing market

conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft

cannot guarantee the accuracy of any information presented after the date of publication.

This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS,

IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS DOCUMENT.

Microsoft grants you a license to this document under the terms of the Creative Commons

Attribution 3.0 License. All other rights are reserved.

2009 Microsoft Corporation.

Microsoft, Active Directory, Excel, Internet Explorer, SQL Server, Visual Studio, and Windows are

trademarks of the Microsoft group of companies.

All other trademarks are property of their respective owners.



Table of Contents 1 Introduction .......................................................................................................................................... 6

1.1 A Few Words about Team Project Collections .............................................................................. 6

2 Part I – Upgrade Planning ..................................................................................................................... 7

2.1 Choosing between Upgrade and Migration .................................................................................. 7

2.1.1 Upgrade ................................................................................................................................. 7

2.1.2 Migration ............................................................................................................................... 7

2.1.3 Server Move .......................................................................................................................... 7

2.2 Upgrade Process ........................................................................................................................... 8

2.2.1 In-Place Upgrade ................................................................................................................... 8

2.2.2 Migration Upgrade ................................................................................................................ 8

2.2.3 Upgrading Projects from Multiple TFS 2008 servers into one TFS 2010 server ................. 10

2.2.4 Splitting a Team Project Collection into Multiple Collections ............................................ 12

2.2.5 Moving reports after a Team Project Collection move ....................................................... 12

2.2.6 Updating Team Project Portal for an existing Team project............................................... 13

3 Part II – Questions and Answers (Q&A) .............................................................................................. 15

3.1 How to join a Workgroup Edition of TFS 2010 to a Domain? ..................................................... 16

3.2 Can we upgrade TFS 2008 severs when SQL Mirroring is enabled? ........................................... 17

3.3 How to recover the system if upgrade fails midway?................................................................. 17

3.4 Can I use a TFS2008 Process Template to create team projects in TFS 2010? ........................... 18

3.5 How can I enable Agile Workbooks in upgraded Projects? ........................................................ 18

3.5.1 Enabling the Product Backlog Workbook ........................................................................... 18

3.5.2 Enabling the Iteration Backlog Workbook .......................................................................... 18

3.6 How can I enable Test Case Management in upgraded project? ............................................... 19

3.7 How can I enable Branch Visualization in upgraded projects? ................................................... 19

3.8 How can I enable Lab Management in upgraded projects? ....................................................... 20

3.9 What is the WITAdmin command line utility used for? .............................................................. 21

3.10 Where is the custom reports placed post upgrade? .................................................................. 21

3.11 Will my TFS2008 reports work post upgrade? ............................................................................ 22

3.12 Can I add a new Database to my existing TFS 2010 farm? ......................................................... 22

3.13 How to resolve the error encountered when bringing cloned TPC online? ............................... 22



3.14 Can I move TPC Database from one Database server to another Database Server? ................. 23

3.15 How to enable the TFS reports if the WSS server is upgraded to MOSS server? ....................... 23

3.16 How to Move Team Projects from one Team Project Collection to another? ........................... 24

4 References .......................................................................................................................................... 25



Acronyms

This guide uses the following common acronyms:

ACRONYM DESCRIPTION

TFS Microsoft Visual Studio Team Foundation Server. Microsoft change management software for software development. Components include work item tracking, source code control, policy support and notifications, and report generating capabilities.

WIT Work Item Template

WSS

Microsoft Windows SharePoint Services

A Microsoft Web-based team collaboration environment that provides the ability to create and access virtual workspaces for managing documents, discussions, lists, surveys and other important contextual information, such as team member status and presence.

TPC

Team Project Collection

A Team Project Collection is a group of related Team Projects. TFS 2010 now hosts Team Project Collection and not just Team Projects.



1 Introduction Welcome to the Visual Studio Team Foundation Server (TFS) 2010 Supplemental Upgrade Guide. This

guide is intended as a supplement to the Upgrade information found in the TFS Install and

Administration guides (http://go.microsoft.com/fwlink/?LinkId=127730 )

Part I of this guide reviews the process of planning for upgrade, with recommendations about structural

changes and the upgrade process.

Part II is a library of questions and answers similar to KB articles, covering areas like Upgrading Work

Item Templates, Upgrading Reports, and using Enterprise TFS Management (ETM). We refer to TFS 2008

for the scenarios, but the concepts mentioned, apply to TFS 2005 as well. This part is designed to grow

with time with frequent posts to Codeplex.

1.1 A Few Words about Team Project Collections One TFS 2010 feature that is discussed throughout this paper is the Team Project Collection (TPC). For

users familiar with TFS 2005 and 2008, a TPC is roughly equivalent to a server instance, and users

connect to a TPC in much the same way they connect to a TFS 2005 or 2008 server. Team Project

Collections contain Team Projects, encapsulating all of the associated data, permissions, settings, etc.

into a single database that can be backed up and restored independent of other TPCs. One of the

primary reasons for adding TPCs in TFS 2010 is to provide a better encapsulation mechanism for Team

Projects, and as a result, they are very much a central part of the upgrade and migration scenarios

discussed in this whitepaper.

To learn more about Team Project Collections in TFS 2010, visit the MSDN article on Organizing Your

Server with Team Project Collections.

http://go.microsoft.com/fwlink/?LinkId=127730

http://msdn.microsoft.com/en-us/library/dd236915(VS.100).aspx




2 Part I – Upgrade Planning

2.1 Choosing between Upgrade and Migration Before addressing the scenarios related to TFS 2010 Upgrade, we need to understand the differences

between TFS Upgrade and TFS Migration.

2.1.1 Upgrade

An upgrade refers to the process by which an existing TFS server is moved from one version to a newer

version. Upgrades are always fully supported and are tested in many configurations before being

released. In an upgrade, data on the server is transformed at the database level, and all data and

metadata are preserved.

There are also multiple flavors of upgrades: In-Place and Migration-Based. An in-place upgrade is

defined as an upgrade that when completed, will use the same set of hardware that is running the

current TFS version. A migration-based upgrade is defined as an upgrade involving a second set of

hardware, which will host the new version of TFS, when the process is complete. Section -2.2 below

summarizes the upgrade process .A detailed explanation of the upgrade process can be found in the

Team Foundation Installation Guide for Visual Studio 2010

(http://go.microsoft.com/fwlink/?LinkId=127730 ).

2.1.2 Migration

A migration refers to the process of replaying actions from one system into another. One of the key

differences, as compared to an upgrade, is that a migration is a lower fidelity data transfer. In TFS, only

version control and work item tracking data can be migrated between servers – build data, reports, and

numerous other pieces of metadata are not migrated. In general, available migration tools have

significantly less quality control and testing than the upgrade process, and most available tools have

limited support (as they are released out of band).

In the case of a migration, the data transformations are done using only the public APIs, which are

limited in providing only certain pieces of information while moving data. The result of these limitations

is that some data is lost or distorted in the process of migration. Examples of this are artifact IDs

(changeset numbers, work item IDs), date-time stamps, area paths, and iteration paths.

2.1.3 Server Move

Another term included here is Server Move, which is used to describe the process of changing the

hardware associated with a server. During a server move, the version of TFS is not changed. While a

server move is neither an upgrade nor a migration, they are often performed before or after an

upgrade, and are often confused with migration. More details on TFS 2010 move scenarios can be

found in the TFS Administration Guide.

http://go.microsoft.com/fwlink/?LinkId=127730



2.2 Upgrade Process With Team Foundation Server 2010, you now have two options for upgrading from a previous version of

TFS namely, In-place upgrade and Migration upgrade.

2.2.1 In-Place Upgrade

With In-place upgrade, you can perform an upgrade on the same hardware that was running the

previous version of Team Foundation Server. The following illustration shows an In-place upgrade, which

results in a single environment after upgrade:

Figure 1: In-place Upgrade

If you use an in-place upgrade, you will have a single Team Foundation Server 2010 environment after

upgrade. The previous environment that was on your system will be deleted.

2.2.2 Migration Upgrade

If you want to run both the new Team Foundation Server environment and the old environment

simultaneously, you should migrate to new hardware. You might run two environments simultaneously

to test the upgrade on your data before moving to the new version. After being restored on the new

hardware, the existing data is autonomous and can be upgraded to create a different environment, even

as your clients continue to use the old environment. Figure 2 "Migration Upgrade" shows a migration

upgrade, which creates two environments simultaneously running side-by-side on different computers

after the upgrade.



Figure 2: Migration Upgrade

The Team Foundation Server upgrade process can be broadly grouped as a two-step process. As a first

step, the upgrade process scans the environment and runs verification steps to ensure the environment

has all the prerequisites for the upgrade and verifies the configuration. Once the verification is

complete, in the second step the process upgrades the server to TFS 2010. Figure-3 below illustrates

some of the verifications done before the upgrade starts

Figure 3: Verifications before upgrade

WMI Available Memory

Firewall OS Version SQL Instance

SQL DB SQL Admin Role SQL Full Text

Search SQL Service SQL Version

SQL Agent Service

TCP/IP Communication

enabled

Front Page installation

Analysis service OLAP

Reporting Service SharePoint site

accessablity TFS2008 DBs



Once all the checks have been successfully completed, the process upgrades the data from the previous

version of TFS to TFS2010. Figure-4 below illustrates some of the steps followed during this Upgrade

process

Figure-4: Upgrade Process

Once the upgrade process completes, the previous instance of TFS will be upgrade to TFS2010.

2.2.3 Upgrading Projects from Multiple TFS 2008 servers into one TFS 2010 server

Scenario Overview:

Consolidating multiple instances of TFS2008 into a single TFS2010

Details:

Team Foundation Server 2010 provides wizards, for the upgrade process from an earlier version.

Add TFS2010 related Solutions to

SharePoint

Create DBs used by TFS 2010

Add Roles to DB and provide access

to TFS Service account

Create new Data Warehouse

Add roles to Application tier

Add Exception to Firewall

Verify ASP.Net Framework

Create new Application Pool

for TFS

Add Performance Counters

Install and register TFS 2010 Services

Create Default TeamProject

Collection

Upgrade TFS2008 DB



Below are the steps to migrate multiple instance of TFS2008 into a single TFS 2010 instance.

1) Run the upgrade wizard on the first TFS2008 instance (TFS2008-A) and upgrade to TFS2010

(Server-A) either using in place upgrade or using Migration based upgrade. After this process,

you will have one Team Project (say Collection1) containing all the Team projects of the

migrated TFS2008 instance.

2) For the subsequent TFS2008 instances (TFS 2008-B), you can either perform an In-Place upgrade

on the server and then move the TPC to the consolidated TFS (TFS 2010 Farm) Or as a safer

option, you could first upgrade to another intermediary TFS 2010 Server-B (Migration Upgrade),

before moving the TPC from the intermediary server to TFS2010 Farm.

Figure 5: Upgrading multiple TFS2008 servers

Alternatively, you can upgrade one server, and then "import" other TFS 2008 (instances) databases into

the TFS 2010 server. They will be upgraded during the import process. Brian Harry’s Blog post below

explains how to do this.

http://blogs.msdn.com/bharry/archive/2009/10/21/upgrading-from-tfs-2005-2008-to-tfs-2010.aspx

Section 2.2.5 provides the steps to move the Reports.

http://blogs.msdn.com/bharry/archive/2009/10/21/upgrading-from-tfs-2005-2008-to-tfs-2010.aspx



2.2.4 Splitting a Team Project Collection into Multiple Collections

Scenario Overview:

Splitting a Team Project Collection into multiple collections based on business requirements like

improved manageability.

Details:

TFS 2010 does not directly support this process. To achieve the desired result, you have to follow an

alternative approach of restoring the Team Project collections, using the Detach and Attach Team

Project Option. You have to use different names and then delete the not needed team projects from

each new Team Project Collection.

The following link provides the steps required for this process: http://msdn.microsoft.com/en-

us/library/dd936158(VS.100).aspx

2.2.5 Moving reports after a Team Project Collection move

Scenario Overview:

The Cloning process using the Detach-Attach method, which we explained in 2.2.3, does not copy the

reports to the cloned Team Project Collection. We have to manually move the reports to the new Team

Project Collection report location.

Details:

Moving reports, while moving a team project collection, is entirely optional. The following list

summarizes the steps for moving reports:

1. Save reports for each project (http://msdn.microsoft.com/en-us/library/ms157214.aspx)

2. Detach TPC per steps detailed in link


3. Attach TPC to new deployment (Same Server or a different server).

4. Upload reports to the folders (one by one)

http://msdn.microsoft.com/en-us/library/ms156300.aspx

5. In report manager, edit the properties of each report to hook up to the data source.

6. Reconnect the SharePoint Web app, if you use SharePoint.

7. In Team Explorer, right-click the name of the project, point to Team Project Settings, and then

click Portal Settings. Make sure that the Reports and dashboards refer to data for this team

project, and check box is selected for each team project portal, if not already checked.

8. Verify that all of your reports that you moved are working as expected.








2.2.6 Updating Team Project Portal for an existing Team project

Scenario Overview:

Updating the Portal URL for an existing Team Project if the portal infrastructure was not ready when the

Project was created

Details:

TFS 2010 upgrade process can be configured to upgrade the TFS2008 systems to TFS2010, even if

WSS/MOSS infrastructure is not ready. Post upgrade, you can also create Team projects while skipping

the option for creating the Team Project Portal.

Once the WSS/MOSS portal is made available, you have to install Team Foundation Server Extensions for

SharePoint Products and Technologies on the server that is running SharePoint Products and

Technologies. Refer the following link for detailed steps

http://msdn.microsoft.com/en-us/library/bb552177(VS.100).aspx

Following are the steps to connect the Portal to an existing Team project, once the portal has been

upgraded.

Step1: Right Click on the Team project and select “Team project Settings” and Then Select “Portal

Settings”

Step 2: In the following form (Figure below) Select “Enable team Project Portal” and Click “Configure

URL”. Alternatively you can also select “Use a Web Site” to connect to a non-SharePoint Site.

Figure 8: Project Portal Settings




Step3: After clicking the “Configure URL” option in the Step 2, you see a form to select the Web

application, which needs to be first configured in TFS Admin Console refer

http://msdn.microsoft.com/en-us/library/ee462861(VS.100).aspx, and provide the relative path.

Figure 9: Specify Portal Settings

Step4: Once the inputs have been provided, click on OK to finish the configuration.

By following the above steps, you can connect a portal to an existing TFS 2010 Team Project.

http://msdn.microsoft.com/en-us/library/ee462861(VS.100).aspx



3 Part II – Questions and Answers (Q&A)

This section addresses common situations that teams might encounter during the upgrade process, with

corresponding recommended workarounds. The scenarios outlined here should allow teams to quickly

understand the different options available to them. The scenarios also provide the necessary framework

for a team to adopt an upgrade process, which addresses their needs better. It’s important to note that

while these scenarios deliver a solution to a specific situation, it is indeed possible and quite likely, to

come up with an equally valid different approach to address the scenario.

This part is designed to grow with time as more upgrade challenges surface. We appreciate your posts

to the Community tab, which we plan to harvest as a good source for future Q&A entries.



3.1 How to join a Workgroup Edition of TFS 2010 to a Domain?

You can find very detailed information about this topic in Microsoft TechNet and other sites. It is

intentionally to the point and brief. The real world scenario might be more involved and might require

more administrator knowledge and privileges.

Below are the steps to be followed to bring a TFS 2010 workgroup instance inside a domain. It is

intentionally to the point and brief.

1. Stop the following services, app pools and web sites:

Services:

1. Visual Studio Team Foundation Build (VSTFBUILD)

2. Visual Studio Team Foundation Background Job Agent (TFSJobAgent)

3. Stop SQL SERVER(TfsInstance)

4. SQL SERVER agent

5. If you have configured reporting with TFS, you need to stop SQL SERVER Reporting

Services, SQL SERVER Analysis Services

Websites:

1. Team Foundation Server

2. Team Foundation Server Proxy

3. Default website

4. Sharepoint central administration v3

App pools:

1. "Microsoft Team Foundation Server Application Pool",

2. "Microsoft Team Foundation Server Proxy Application Pool"

2. Backup Tfs databases:

1. Tfs_<label>Configuration,

2. Tfs_<label>Warehouse (if reporting configured)

3. Tfs collections

Following link provides the steps to Backup TFS 2010 Database


3. Join machines to the domain

http://technet.microsoft.com/en-us/default.aspx




4. Once in the new domain, you will need to update the accounts used for TFS operations

1) Update the TFS by running the command:

Tfsconfig identities /change /account:<accountName> /fromdomain:<old domain> /todomain:<new domain>

2) Run the below command to update the TFS service account

tfsconfig accounts /change /account:<tfs service account> /password /accountType:ApplicationTier

If you use the command tfsconfig accounts /add, you will have to manually grant the service account

"Log on as a service" permission.

3) If Report Service is configured, run the command below command to update the TFS reports

tfsconfig accounts /change /account:<reporting service account> /password /accountType:ReportingDataSource

3.2 Can we upgrade TFS 2008 severs when SQL Mirroring is enabled?

You can find very detailed information about this topic in Microsoft TechNet and other sites. It is

intentionally to the point and brief. The real world scenario might be more involved and might require

more administrator knowledge and privileges.

The upgrade process involves many SQL operations and hence keeping Mirroring active will impact the

performance. Another reason for turning off the Mirroring is in case the upgrade fails midways, you can

still use the Mirrored instance for failover which may not be possible if Mirroring is kept active.

Post successful upgrade, you can back up the database and restore them on the Mirror and then re-

establish the Mirroring.

3.3 How to recover the system if upgrade fails midway? This depends on what point the Upgrade failed. As a failsafe, it’s always best to maintain a copy of the

TFS 2008 DB before starting the upgrade as TFS 2010 deletes the TFS 2008 Databases during

upgrade (Except the warehouse DB).

In case the upgrade fails during the initial upgrade steps, you can always restore the old TFS 2008 DBs

and restart the upgrade. Also, if TFS is configured and the upgrade job is running, it may be possible to

debug the failure (like simple failures: network connectivity, disk space issues) and then attempt to

restart the upgrade. To do this you go to the Administration Console and into the Team Project

Collections node, and attempt to click the “Restart” the service job related to upgrade.

http://technet.microsoft.com/en-us/default.aspx



If the Upgrade fails during the upgrade of MOSS/WSS site, you will have to manually install the

necessary site templates & features and then link the SharePoint site to the TFS 2010. Following link

provides the steps for installing Extensions for SharePoint Products: http://msdn.microsoft.com/en-

us/library/bb552177(VS.100).aspx

3.4 Can I use a TFS2008 Process Template to create team projects in TFS

2010? Yes, your existing TFS 2008 template will work fine with TFS2010. But you need to ensure that the

SharePoint project template is installed on the new SharePoint server in case you are using a new

instance of SharePoint for TFS 2010. You may encounter issues creating project in scenarios where in

there is conflict between the WorkItem Field Names of your custom fields and TFS.

3.5 How can I enable Agile Workbooks in upgraded Projects? The Agile Workbooks included in VSTS 2010 aid teams in the planning phase of their project. These

workbooks are included in the MSF for Agile Software Develop – v5.0 template and include both a

Product Backlog workbook and an Iteration Backlog workbook. There are slightly different steps

required to enable these workbooks for upgraded team projects.

3.5.1 Enabling the Product Backlog Workbook

To enable the Product Backlog Workbook for existing team projects based on the MSF for Agile Software

Development v4.2 process template you will need to complete the following four steps

Step 1 – Download the MSF for Agile Software Development v5.0 process template

Step 2 – Modify the Scenario work item definition

Step 3 – Create a product backlog query

Step 4 – Bind your query to the product backlog workbook

A detailed walkthrough is provided by Aaron Bjork in his blog post, on how to enable Product Backlog

workbook.

Enabling the Product Backlog Workbook on an Upgraded Team Project

http://blogs.msdn.com/aaronbjork/archive/2009/05/18/enabling-the-product-backlog-workbook-on-

an-upgraded-team-project.aspx

3.5.2 Enabling the Iteration Backlog Workbook

To enable the Iteration Backlog Workbook for existing team projects based on the MSF for Agile

Software Development v4.2 process template you will need to complete the following five steps

Step 1 – Download the MSF for Agile Software Development v5.0 process template

Step 2 – Modify the Task work item definition



http://blogs.msdn.com/aaronbjork/archive/2009/05/18/enabling-the-product-backlog-workbook-on-an-upgraded-team-project.aspx

http://blogs.msdn.com/aaronbjork/archive/2009/05/18/enabling-the-product-backlog-workbook-on-an-upgraded-team-project.aspx



Step 3 – Create an iteration backlog query

Step 4 – Bind your query to the product backlog workbook

Step 5 – Modify the workbook document properties

A detailed walkthrough is provided by Aaron Bjork in his blog post, on how to enable Iteration Backlog

workbook.

Enabling the Iteration Backlog Workbook on an Upgraded Team Project

http://blogs.msdn.com/aaronbjork/archive/2009/05/18/enabling-the-iteration-backlog-workbook-on-

an-upgraded-team-project.aspx

3.6 How can I enable Test Case Management in upgraded project? Test Case Management is one of the most exciting features to come to TFS 2010. Test Case

Management allows you to manage your testing effort seamlessly using the work item tracking

capability of TFS. To enable Test Case Management you will need to follow the following steps:

Step 1 – Obtain the new process template items

Step 2 – Add link types

Step 3 – Add new work item types

Step 4 – Deal with work item name conflicts

Step 5 – Edit existing test case work item

Step 6 – Add work item categories

Step 7 – Enhance existing work item types

Following blog post provides detailed steps and scripts to enable Test Case Management

http://blogs.msdn.com/chrispat/archive/2009/10/19/enabling-test-management-on-upgraded-

team-projects-beta-2.aspx

3.7 How can I enable Branch Visualization in upgraded projects? Branch Visualization is a feature in VSTS 2010 that allows you to not only visualize your branches but to

visually track your changes as they move through your branch hierarchy.

To use the new branching capabilities in 2010, you will need to convert your existing branched folders

into fully fledged branches. Below are the steps to enable Branch Visualization manually, but post Beta-2

this happens automatically during the upgrade.

1. Identify the branch structure you are currently using. If you would like to change your branch

structure, now may be a good time to do so, but it is not necessary.

2. Identify the folder in your solution explorer mapped to your parent (top level) branch.

http://blogs.msdn.com/aaronbjork/archive/2009/05/18/enabling-the-iteration-backlog-workbook-on-an-upgraded-team-project.aspx

http://blogs.msdn.com/aaronbjork/archive/2009/05/18/enabling-the-iteration-backlog-workbook-on-an-upgraded-team-project.aspx

http://blogs.msdn.com/chrispat/archive/2009/10/19/enabling-test-management-on-upgraded-team-projects-beta-2.aspx

http://blogs.msdn.com/chrispat/archive/2009/10/19/enabling-test-management-on-upgraded-team-projects-beta-2.aspx



3. Right click on that folder. On the context menu select “Branching and Merging” & then “Convert

Folder to Branch”. This will open a dialog for doing the conversion of a folder to a branch.

4. At the bottom of the dialog, check the “Recursively perform this conversion for all branched

child folders”.

5. Next click the “Convert” button. This will upgrade this folder to a branch. It will also walk the

branch tree and convert all folders that have been branched from this folder.

6. Your branches should now be shown with the branch icon in the source control explorer tree.

7. If you have any folders that had their relationship established via Baseless Merge, you will need

to use the “Reparent Branch” option from the “Branching & Merging” context menu to establish

the parent/child relationship in the branch hierarchy.

8. Repeat these steps for all remaining branch trees in your solution.0

Jamie Cool’s blog provides detailed steps on the process needed to convert your existing branched

folder.

http://blogs.msdn.com/hakane/archive/2009/05/19/enable-branch-visualization-in-upgraded-team-

projects-tfs-2010-beta1.aspx

3.8 How can I enable Lab Management in upgraded projects? If you wish to enable Lab management in upgraded projects, you need to follow the below steps

Initial steps

1. Upgrade your TFS 2008 server to 2010

2. Install Microsoft System Center Virtual Machine Manager (SCVMM) and add hosts to host

groups. You can find the steps for this in the Team Foundation Installation guide for Visual

Studio Team System 2010.

3. Install the SCVMM admin console on the TFS application tier server. You can find the steps for

this in the Team Foundation Installation guide for Visual Studio Team System 2010.

4. Enable Test Case Management in your existing Team Projects. See the steps in section 3.63.6

above for details on how to do this.

Once the prerequisite steps above have been completed, you can

Step 1 – Configure Lab Management

This involves using the Team Foundation Administration Console to provide details about the

SCVMM machine name, details about the network address and network isolation.

Step 2 – Configure Lab Management for the Project Collection hosting the upgraded projects

Each Team Project Collection that hosts upgraded Team Projects will need to be configured with

settings about VMM library shares, Host Groups, Network Isolation and DNS suffix set.

Step 3 – Configure Lab Management for upgraded Team Project(s)

http://blogs.msdn.com/hakane/archive/2009/05/19/enable-branch-visualization-in-upgraded-team-projects-tfs-2010-beta1.aspx

http://blogs.msdn.com/hakane/archive/2009/05/19/enable-branch-visualization-in-upgraded-team-projects-tfs-2010-beta1.aspx



In this final step, you will need to download a script file from VSTS Lab Management team blog

and after editing setting in the batch file; you’ll need to run it for each existing project. The

script will grant default Lab Management permissions, create Project Host groups and create

Project Library shares.

Complete details on how to enable Lab Management for upgraded team projects can be found on the

blog: http://blogs.msdn.com/lab_management/archive/2009/10/19/enable-lab-management-features-

for-existing-team-projects-in-beta2.aspx

3.9 What is the WITAdmin command line utility used for?

The witadmin command line utility allows you to create, delete, import, and export categories, global

lists, types of links, types of work items, and work item fields. In previous versions of Team Foundation

Server, tools like witimport, witexport and glimport were typically used for some of this functionality.

The witadmin utility is the more flexible successor to many of these earlier tools.

View a list of work item type definitions

From a Visual Studio command prompt type

Witadmin listwitd /collection:http://tfsserver:8080/tfs/DefaultCollection /p:MyProject

For a team project created with the MSF for Agile Software Developer – v5.0 process template, the

output from the previous command would be.

Bug Shared Steps Task Test Case User Story Issue

For a complete list of commands refer the following MSDN link

http://msdn.microsoft.com/en-us/library/ms253088(VS.100).aspx

3.10 Where is the custom reports placed post upgrade? TFS2008 and TFS2010 follow different logics for storing reports in the reports server. In TFS 2008, we

have one folder at the root level per Team project containing all the Reports. In TFS 2010, we have one

http://blogs.msdn.com/lab_management/archive/2009/10/19/enable-lab-management-features-for-existing-team-projects-in-beta2.aspx



http://msdn.microsoft.com/en-us/library/ms253088(VS.100).aspx



folder per Team Project Collection at the root, which in turn have one folder per Team Project

containing the reports.

Post upgrade, the upgrade wizard creates folder for the Team Project collection and then creates Folder

for each team project in it. But the reports are not copied from the old TFS 2008 instance. You will have

to manually move the Reports from the Old reports location to the new Report location.

3.11 Will my TFS2008 reports work post upgrade? TFS 2010 reports warehouse has a different structure than TFS 2008. Post upgrade, TFS 2010, moves the

Data of TFS 2008 instance to its new warehouse and retains the old warehouse to enable the reports to

function. But any new updates made on the Workitems will not be reflected in the Old warehouse. To

get the latest data, reports have to be modified to work with the new warehouse. Below are the

modifications you need to follow

Step 1 – Make MDX query changes

Step 2 – Make SQL Changes

Step 3 – Rename Data Sources

Step 4 – Validate Report working.

Step 5 – Change Report location

John Socha’s blog provides detailed steps on how to achieve the above steps.

http://www.socha.com/blogs/john/2009/05/upgrading-visual-studio-team-foundation.html

http://www.socha.com/blogs/john/2009/10/upgrading-team-foundation-server-2008.html

3.12 Can I add a new Database to my existing TFS 2010 farm? Yes, TFS 2010 provides us with option to specify the Database Server instance while creating a new

Team Project collection. Using this option, you can create the Team Project Collection on different

Database server. But the warehouse data of all the TPCs will reside on a single Database instance.

3.13 How to resolve the error encountered when bringing cloned TPC online? When you try to bring a cloned TPC (using Detach-attach process) online, you will get an “A duplicate

Team Project Exist” error message (as shown below)

http://www.socha.com/blogs/john/2009/05/upgrading-visual-studio-team-foundation.html

http://www.socha.com/blogs/john/2009/10/upgrading-team-foundation-server-2008.html



Figure 10: Duplicate Team Project Error

To get the TPCs online post cloning, you have to ensure that the 2 cloned TPC have unique projects. So

before bringing the TPC online, delete the projects from the 2 cloned TPCs and ensure only unique team

projects.

3.14 Can I move TPC Database from one Database server to another Database

Server? You can move a database of a Team Project Collection from one server to another server running SQL

Server 2008. You can also move a Team Project Collection from one deployment of Visual Studio Team

Foundation Server to another. Following link provides the steps to be followed to move a Team Project

Collection


3.15 How to enable the TFS reports if the WSS server is upgraded to MOSS

server? If you upgrade an existing server from WSS to MOSS, to enable the reports, you just need to enable the

MOSS dashboard features on your team project portal sites after the upgrade. The new reports are

packaged into the features in MOSS and so once you turn on the features, you’ll have the new

reports/dashboards. To enable the Dashboard in SharePoint, Navigate to

Site Actions Site Settings Site features “Active” the “Dashboards with reports for

Microsoft Office SharePoint Server”




3.16 How to Move Team Projects from one Team Project Collection to

another? We currently do not have support for merging/moving selective Team Projects between Team Project

Collections in TFS 2010. The following example scenario illustrates this situation.

After Upgrading from two TFS2008, you have two team Project Collections:

Team Project Collection Team Projects

TPC1 TP-1, TP-2

TPC2 TP-3, TP-4

It is not possible to move TP-2 and to TPC2.



4 References

VSTS Rangers Site

http://msdn.microsoft.com/en-us/teamsystem/ee358786.aspx

Team System Widgets

http://www.teamsystemwidgets.com

Videos for Team System

http://msdn.microsoft.com/en-ca/vsts2008/bb507749.aspx?wt.slv=topsectionsee

Team System Site

http://msdn.microsoft.com/en-us/teamsystem/default.aspx

Brian Harry’s blog

http://blogs.msdn.com/bharry/

Aaron Bjork’s blog

http://blogs.msdn.com/aaronbjork

Bryan Krieger’s blog on TFS 2010 upgrade which includes specific topics on Beta2/RC upgrades to RTM.

http://blogs.msdn.com/bkrieger/

http://msdn.microsoft.com/en-us/teamsystem/ee358786.aspx

http://www.teamsystemwidgets.com/

http://msdn.microsoft.com/en-ca/vsts2008/bb507749.aspx?wt.slv=topsectionsee

http://msdn.microsoft.com/en-us/teamsystem/default.aspx

http://blogs.msdn.com/bharry/

http://blogs.msdn.com/bkrieger/

TFS 2010 Upgrade Guidance-V1.4

Documents