Documente Academic
Documente Profesional
Documente Cultură
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.
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.
Page | 2
Part I Upgrade Planning ..................................................................................................................... 7 2.1 Choosing between Upgrade and Migration .................................................................................. 7 Upgrade................................................................................................................................. 7 Migration............................................................................................................................... 7 Server Move .......................................................................................................................... 7
Upgrade Process ........................................................................................................................... 8 In-Place Upgrade ................................................................................................................... 8 Migration Upgrade ................................................................................................................ 8 Upgrading Projects from Multiple TFS 2008 servers into one TFS 2010 server ................. 10 Splitting a Team Project Collection into Multiple Collections ............................................ 12 Moving reports after a Team Project Collection move ....................................................... 12 Updating Team Project Portal for an existing Team project............................................... 13
Part II Questions and Answers (Q&A) .............................................................................................. 15 3.1 3.2 3.3 3.4 3.5 How to join a Workgroup Edition of TFS 2010 to a Domain? ..................................................... 16 Can we upgrade TFS 2008 severs when SQL Mirroring is enabled? ........................................... 17 How to recover the system if upgrade fails midway?................................................................. 17 Can I use a TFS2008 Process Template to create team projects in TFS 2010? ........................... 18 How can I enable Agile Workbooks in upgraded Projects? ........................................................ 18 Enabling the Product Backlog Workbook ........................................................................... 18 Enabling the Iteration Backlog Workbook .......................................................................... 18
3.5.1 3.5.2 3.6 3.7 3.8 3.9 3.10 3.11 3.12 3.13
How can I enable Test Case Management in upgraded project? ............................................... 19 How can I enable Branch Visualization in upgraded projects? ................................................... 19 How can I enable Lab Management in upgraded projects? ....................................................... 20 What is the WITAdmin command line utility used for? .............................................................. 21 Where is the custom reports placed post upgrade? .................................................................. 21 Will my TFS2008 reports work post upgrade? ............................................................................ 22 Can I add a new Database to my existing TFS 2010 farm? ......................................................... 22 How to resolve the error encountered when bringing cloned TPC online? ............................... 22 Page | 3
Can I move TPC Database from one Database server to another Database Server? ................. 23 How to enable the TFS reports if the WSS server is upgraded to MOSS server? ....................... 23 How to Move Team Projects from one Team Project Collection to another? ........................... 24
References .......................................................................................................................................... 25
Page | 4
Page | 5
Page | 6
Page | 7
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.
Page | 8
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
Available Memory
WMI
Firewall
OS Version
SQL Instance
SQL Version
SQL Service
SQL DB
Analysis service
OLAP
TFS2008 DBs
Reporting Service
Page | 9
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
Upgrade TFS2008 DB
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. Copyright 2009 Microsoft Corporation Page | 10
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.
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 Harrys 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.
Page | 11
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/enus/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 http://msdn.microsoft.com/en-us/library/dd936138(VS.100).aspx 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. Copyright 2009 Microsoft Corporation
Page | 12
Page | 13
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.
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.
Page | 14
Page | 15
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 http://msdn.microsoft.com/en-us/library/bb552295(VS.100).aspx 3. Join machines to the domain Copyright 2009 Microsoft Corporation Page | 16
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
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 reestablish the Mirroring.
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/enus/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.
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-onan-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 Page | 18
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-onan-upgraded-team-project.aspx
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-upgradedteam-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 Cools 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-teamprojects-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; youll 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-featuresfor-existing-team-projects-in-beta2.aspx
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
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.
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 Sochas 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.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) Copyright 2009 Microsoft Corporation Page | 22
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 http://msdn.microsoft.com/en-us/library/dd936138(VS.100).aspx
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, youll 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
Page | 23
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 TPC1 TPC2 Team Projects TP-1, TP-2 TP-3, TP-4
Page | 24
http://blogs.msdn.com/bharry/
Aaron Bjorks blog
http://blogs.msdn.com/aaronbjork
Bryan Kriegers blog on TFS 2010 upgrade which includes specific topics on Beta2/RC upgrades to RTM. http://blogs.msdn.com/bkrieger/
Page | 25