In-Place Upgrade to TFS 2010 on existing hardware Not deploying new hardware Databases too large to...

11
TFS 2010 Upgrade Overview Bryan Krieger Principal Program Manager Microsoft Corporation

Transcript of In-Place Upgrade to TFS 2010 on existing hardware Not deploying new hardware Databases too large to...

Page 1: In-Place Upgrade to TFS 2010 on existing hardware Not deploying new hardware Databases too large to move Scaling-out, not up Not deploying new hardware.

TFS 2010 Upgrade OverviewBryan KriegerPrincipal Program ManagerMicrosoft Corporation

Page 2: In-Place Upgrade to TFS 2010 on existing hardware Not deploying new hardware Databases too large to move Scaling-out, not up Not deploying new hardware.

Upgrade: StrategiesIn-Place

Upgrade to TFS 2010 on existing hardware

• Not deploying new hardware • Databases too large to move• Scaling-out, not up

• Backup existing SQL databases

• Uninstall existing Team Foundation Server

• Upgrade to SQL Server 2008• Upgrade to Windows

SharePoint Services 3.0 SP1 or later

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

MigrationUpgrade to TFS 2010 on new hardware

• Testing upgrade• Upgrading to 64-bit OS• Moving to a larger capacity

server

• Backup existing SQL databases

• Install necessary TFS pre-reqs

• Restore SQL databases on new hardware

• Configure SharePoint and SQL Reporting to connect to restored databases

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

ImportUpgrade TFS 2005/2008 data after installing TFS 2010

• Consolidating multiple Team Foundation Servers

• Install TFS2010 instance• Backup existing SQL

databases• Restore SQL databases on

new hardware• Run tfsconfig.exe import• Configure SharePoint and

ReportingNote: Data is imported into a new Team Project Collection

What?

Why?

Steps

Page 3: In-Place Upgrade to TFS 2010 on existing hardware Not deploying new hardware Databases too large to move Scaling-out, not up Not deploying new hardware.

Upgrade: FlowMigratio

n

Backup TFS Data

Backup TFS Data

In-Place

Uninstall TFS

Upgradepre-reqs

Install pre-reqs

Copy and Restore TFS

Data

Install TFS 2010

Select Upgrade from Previous Version Wizard

Input Wizard Data

Configure and Upgrade

Import

Backup TFS Data

Copy and Restore TFS

Data

Run Import Command

Manually configure WSS and Reporting

Install and Config: Proxy & Build Services

Opti

onally

Page 4: In-Place Upgrade to TFS 2010 on existing hardware Not deploying new hardware Databases too large to move Scaling-out, not up Not deploying new hardware.

Upgrade: Prerequisites

TFS 2005/2008

• Windows Server 2003 (x86) with SP1 or later

• Windows Server 2003 R2 (x86)• Windows Server 2008 (x86)

• SQL Server 2005• SQL Server 2008

• Windows SharePoint Services 2.0• Windows SharePoint Services 3.0

TFS 2010

• Windows Server 2003 (x86) with SP2 or later• Windows Server 2003 R2 (x86) or later• Windows Server 2008 (x86 & x64) with SP2 or

later • Windows Server 2008 R2 (x64) • Windows 7 (x86 & x64) • Windows Vista® (x86 & x64) SP2 or later (all

editions except Starter Edition)

• SQL Server 2008• SQL Server 2008 R2 (future release)

• Windows SharePoint Services 3.0 with SP1 or later

• Microsoft Office SharePoint Server 2007• Microsoft Office SharePoint Server 2010 (future

release)

Note: SQL Server 2005 and Windows SharePoint Services 2.0 are not supported platforms for TFS 2010

Page 5: In-Place Upgrade to TFS 2010 on existing hardware Not deploying new hardware Databases too large to move Scaling-out, not up Not deploying new hardware.

Compatibility: ClientsTeam Foundation Server Version

Clients TFS 2010 TFS 2008 TFS 2005

VS / TE 2010

VS / TE 2008 * *

VS / TE 2005 * *

MSSCCI 2010

MSSCCI 2008

* A compatibility hotfix (GDR) is required when connecting from Team Explorer 2005 or Team Explorer 2008 to TFS 2010.For more information, see: http://go.microsoft.com/fwlink/?LinkID=166482 http://go.microsoft.com/fwlink/?LinkId=166481

Page 6: In-Place Upgrade to TFS 2010 on existing hardware Not deploying new hardware Databases too large to move Scaling-out, not up Not deploying new hardware.

Compatibility: TFS Components Team Foundation Server Version

Component TFS 2010 TFS 2008 TFS 2005

Team Foundation Proxy 2010

Team Foundation Proxy 2008

Team Foundation Proxy 2005

SharePoint Extensions 2010 n/a*

SharePoint Extensions 2008 n/a*

TFS 2010 Build Services

TFS 2008 Build Agents

TFS 2005 Build Machines

* Off box SharePoint not officially supported in TFS 2005

Page 7: In-Place Upgrade to TFS 2010 on existing hardware Not deploying new hardware Databases too large to move Scaling-out, not up Not deploying new hardware.

Microsoft Confidential7

Compatibility: Team Build

− Build Services must match TFS version− TFS 2010 and TFS 2008 Agents can exist

SxS− TFS 2010 Build Controller cannot manage

a TFS 2008 Agent− TFS 2010 can build VS 2005 and VS

2008 solutions / projects− TFS 2008 can build VS 2010

solutions / projects when configured to use MSBuild 4.0

Page 8: In-Place Upgrade to TFS 2010 on existing hardware Not deploying new hardware Databases too large to move Scaling-out, not up Not deploying new hardware.

Microsoft Confidential8

Compatibility: Reports

− Standard reports replaced with new set of reports covering Agile and CMMI

− Previous customized reports require updating and are still available: http://<servername>/Reports/<projectname>/

Page 9: In-Place Upgrade to TFS 2010 on existing hardware Not deploying new hardware Databases too large to move Scaling-out, not up Not deploying new hardware.

Microsoft Confidential9

Enabling Features on Existing Projects− No changes made to process related

features− Upgraded projects work as before except…

− Teams can enable new process related features when ready:− Version 5.0 MSF Process Templates− Team Lab− Dashboards

− See Administration Guide: “Updating an Upgraded Team Project to Access New Features”(http://go.microsoft.com/fwlink/?LinkId=187509)

Page 10: In-Place Upgrade to TFS 2010 on existing hardware Not deploying new hardware Databases too large to move Scaling-out, not up Not deploying new hardware.

Microsoft Confidential10

Useful Links:− TFS Installation Guide download:

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

− TFS Administration Guide - Updating an Upgraded Team Project to Access New Features:http://go.microsoft.com/fwlink/?LinkId=187509

− Beta2/RC to RTM Upgrade Guide: http://blogs.msdn.com/bkrieger/archive/2010/03/31/team-foundation-server-2010-upgrade-guide-from-beta2-or-rc-to-rtm-release.aspx

− TFS Rangers supplemental upgrade guide:http://vs2010upgradeguide.codeplex.com/wikipage

− Upgrade custom reports to work with TFS 2010: http://www.socha.com/blogs/john/2009/05/upgrading-visual-studio-team-foundation.html

− Upgrade TFS 2008 build definitions to TFS 2020:http://blogs.msdn.com/jimlamb/archive/2009/11/03/upgrading-tfs-2008-build-definitions-to-tfs-2010.aspx

− Client compatibility:http://blogs.msdn.com/teams_wit_tools/archive/2009/10/19/compatibility-matrix-for-2010-beta-2-team-foundation-server-to-team-explorer-2008-and-2005.aspx

− VSTS 2008 Forward Compatibility Update: http://go.microsoft.com/fwlink/?LinkId=166481

− VSTS 2005 Forward Compatibility Update: http://go.microsoft.com/fwlink/?LinkID=166482

Page 11: In-Place Upgrade to TFS 2010 on existing hardware Not deploying new hardware Databases too large to move Scaling-out, not up Not deploying new hardware.

© 2010 Microsoft Corporation. All rights reserved. Microsoft, Visual Studio, the Visual Studio logo, and [list other trademarks referenced] are trademarks of the Microsoft group of companies.

 The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation.  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 provided after the date of this presentation. 

MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED, OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.