Upgrade team-foundation-server-2012-the-ultimate-upgrade-guide
Upcoming SlideShare
Loading in...5
×
 

Upgrade team-foundation-server-2012-the-ultimate-upgrade-guide

on

  • 1,221 views

 

Statistics

Views

Total Views
1,221
Views on SlideShare
1,221
Embed Views
0

Actions

Likes
0
Downloads
3
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Upgrade team-foundation-server-2012-the-ultimate-upgrade-guide Upgrade team-foundation-server-2012-the-ultimate-upgrade-guide Document Transcript

  • Upgrade Team Foundation Server 2012: The Ultimate Upgrade Guide© August 2012 by Tim ElhajjAll rights reserved under the International and Pan-American Copyright Conventions. No partof this book may be reproduced or transmitted in any form or by any means, electronic ormechanical, including photocopying, recording, or by any information storage and retrievalsystem, without permission in writing from the publisher.
  • Upgrade Team Foundation Server 2012: The UltimateUpgrade GuideTim ElhajjCopyright 2012 by Tim ElhajjSmashwords EditionFirst EditionWarning: the unauthorized reproduction or distribution of this copyrighted work is illegal.Criminal copyright infringement, including infringement without monetary gain, isinvestigated by the FBI and is punishable by up to 5 years in prison and a fine of $250,000.Visit us online:http://elhajj.wordpress.com
  • ContentsIntroductionUpgrade RequirementsServer UpgradeOne: Double CheckTwo: SQL Server Set upThree: SharePoint Set upFour: Fix up new hardwareFive: Run TFS upgrade wizardUpgrade Automated buildsAdd New Features to Team ProjectsContact View slide
  • IntroductionUse this guide to upgrade to Team Foundation Server 2012.You’ll find step-by-step guidance here that covers the most popular upgrade tasks, includingin-place upgrades and upgrades that involve moving to new hardware. Direction on what todo with SharePoint, whether it’s running on the same server as TFS or somewhere else. We’llalso walk through upgrade of a build machine, as well as adding new features to yourupgraded team projects. View slide
  • Upgrade RequirementsReview the requirements listed here and then choose a server upgrade path. You canupgrade from any of the following earlier releases:Team Foundation Server 2012, including the developer preview, BETA, or RC releasesTeam Foundation Server 2010, with or without Service Pack 1Team Foundation Server 2008 with Service Pack 1New prerequisite requirementsSQL Server: Before you start your upgrade, you might have to upgrade SQL Server to meetnew Team Foundation Server requirements. SQL Server 2008 is no longer supported. SQLServer 2008 R2 and SQL Server 2012 are supported.This guide assumes you’re using SQL Server 2008 R2 for your backend database and reportserver and offers specific instruction on it.SharePoint: If you have a portal server, you can continue to use the same one withoutupgrading it. We support all of the previously supported versions of SharePoint, includingWindows SharePoint Services 3.0, Office SharePoint Server 2007, SharePoint Foundation, orSharePoint Server 2010.This guide assumes your portal is Windows SharePoint Services 3.0 and offers specificinstruction on it.What about skipping reporting or SharePoint during upgrade?Only if you no longer plan to use reporting or SharePoint should you simplify yourdeployment by not adding these features. Otherwise, keep these two features duringupgrade. The upgrade configuration automatically links upgraded projects to the portal andreporting features. If you add a portal or reporting after you upgrade, you cannot easilycreate these links between all your upgraded projects and the portal.Less common upgrade tasksIf you are not using a Team Foundation Server farm and no one on your team uses ProjectServer, you can probably skip this section.Upgrading a Team Foundation Server farmIf you have a scaled out Team Foundation Server deployment that you want to upgrade, youshould uninstall the old version of Team Foundation Server from each application tier. Withthe previous version uninstalled, install TFS 2012 on one of the application tiers and run theupgrade as you would for a standalone deployment. Select any application tier in the farmthat you like; it doesn’t matter. Once the upgrade completes, install Team Foundation
  • Server 2012 on the remaining application tiers using the Add an Application Tier wizard. Thisreassembles the farm and completes the farm upgrade.For more information, see this topic on MSDN: How to: Create a Team Foundation ServerFarm (High Availability)Upgrading the TFS Extensions for Project ServerIf you have integrated Project Server with your TFS deployment and you upgrade TFS, yourteam projects should continue to work as before, but you won’t have access to any newfeatures until you install the new TFS Extensions for Project Server. You should uninstall theold extensions from Project Server and then install the latest version of the extensions on allthe servers where it was previously installed. The version of the extensions you use forProject Server should always match the version of Team Foundation Server you’re running.For more information, see this topic on MSDN: How to: Add Project Server to TeamFoundation Server
  • Server UpgradeWhether you’re planning to use the same hardware or moving to a new machine, we havethe steps you’ll need in the next five sections. We cover all possible options, includingupgrades from TFS basic or express, which requires a brief visit to Microsoft Update beforeupgrade to make sure you succeed.You may not have to do all five steps above. If you’re not planning to move TFS to a newmachine, for example, you can skip the steps for setting up SQL Server and restoring yourdata. New for this version of TFS, the backup of your TFS data can be done from within theTFS upgrade wizard.
  • One: double check requirementsVerify that the operating system and hardware meet the requirements for the newversion of Team Foundation Server. New for this version of TFS, you must use a 64-bit serverif you use a server operating system.Determine the service account you will use for Team Foundation Server. By default, TFS usesNetwork Service. In most cases, you should use the same account you used for the previousinstallation or consider using Network Service.Theres more information on MSDN: System Requirements for Team Foundation Server, orAccounts Required for Installation of Team Foundation Server.Visit Microsoft Update.If youre using SQL Server Express for TFS, use Microsoft Update to make sure that SQL ServerExpress has the latest service pack (SP). Similar to Windows Update, Microsoft Update is forMicrosoft software other than operating systems. Use the Windows Update Control Panel toopt into Microsoft Update and check for updates.If youre running SQL Server Express 2008 with either SP2 or SP3, the TFS upgradewizard will be able to automatically upgrade your installation of SQL Server Express duringTFS upgrade. If you don’t have SharePoint and aren’t moving TFS to new hardware, you canskip ahead to step 5, Run the TFS upgrade wizard.Tip: If you dont know if youre using SQL Express, look at the Application Tier node in theTFS administration console. Scroll down to Data Tier Summary and look forSQLServerExpress to confirm.
  • Two: set up SQL ServerSet up SQL Server on the new hardware. If you’re going to reuse the same hardware orcontinue using SQL Server Express, you can skip to the next section, Set up SharePoint.How to setup SQL ServerFirst you install and configure SQL Server 2008 R2 for Team Foundation Server withreporting. If you’re using SQL Server 2008 R2 Enterprise edition, you have to update tocumulative update package 1 for SQL Server 2008 R2 Service Pack 1 (or a later version) toaddress a SQL Server issue with table compression.After you complete the install, you configure Windows Server to recover analysis services onfailure.Tip: Make sure the default collation settings in SQL Server match the existing settings fromthe SQL Server instance that you’re migrating from. There’s more information about this onMSDN: SQL Server Collation Requirements for Team Foundation ServerRequired PermissionsTo perform these procedures, you must be a member of the Administrators security group onWindows Server.
  • To install Database Engine, Analysis Services and Reporting Services1. Launch setup.exe on the SQL Server DVD.2. On the SQL Server Installation Center page, choose Installation, and then choose Newinstallation or add features to an existing installation.3. On the Setup Support Rules page, choose OK.4. On the Product Key page, type your product key or specify a free edition and then chooseNext.5. On the License Terms page, accept the license agreement and choose Next.6. On the Setup Support Files page, choose Install.7. On the Setup Support Rules page, choose Next.
  • Tip: A Windows Firewall warning might appear here, but you can safely ignore thiswarning. TFS automatically adds an exception for Windows Firewall during upgrade.8. On the Setup Role page, choose SQL Server Feature Installation and then choose Next.9. On the Feature Selection page, select the check boxes for the following components andthen choose Next:
  • Database Engine Services (required for Team Foundation Server)Full-Text Search (required for Team Foundation Server)Analysis Services (required for reporting)Reporting Services (required for reporting)Management Tools – Basic (Management Tools -Complete automatically selects itselfwhen you click Basic and this is fine)10. On the Installation Rules page, choose Next.11. On the Instance Configuration page, choose Default instance. If you choose Namedinstance, type the name of the instance. Choose Next.
  • 12. On the Disk Space Requirements page, choose Next.13. On the Server Configuration page, choose Use the same account for all SQL Serverservices, and enter NT AUTHORITYNETWORK SERVICE in Account Name for every service.If you do specify a domain account, enter its password in Password.If you use NT AUTHORITYNETWORK SERVICE, leave Password blank.
  • If you choose Use the same account for all SQL Server services, you might still haveto manually enter account information for some services.14. In the Startup Type column, verify that Automatic appears for all services that you canedit, and then choose Next.15. On the Database Engine Configuration page, choose Windows authentication mode,choose Add Current User, and then choose Next.16. On the Analysis Services Configuration page, choose Add Current User, and then chooseNext.17. On the Reporting Services Configuration page, choose Install the native mode defaultconfiguration, and then choose Next.
  • 18. (Optional) On the Error and Usage Reporting page, specify whether to send informationabout errors and then choose Next.19. On the Installation Rules page, choose Next.20. On the Ready to Install page, review the list of components to be installed, and thenchoose Install.The Installation Progress page shows the status of each component.21. On the Complete page, choose Close.
  • Update SQL Server 2008 R2 Enterprise editionIf you’re using SQL Server 2008 R2 Enterprise edition, you have to update to cumulativeupdate package 1 for SQL Server 2008 R2 Service Pack 1 (or a later version) to address a SQLServer issue with table compression. If you’re using SQL Server 2008 R2 Standard edition orSQL Server 2012, you don’t have to update SQL Server.Configure Analysis Services to recover on failureYou should configure the Windows service for Analysis Services to restart itself if it fails.To configure Analysis Services to recover1. Open the Services control panel (Start >Administrative tools >Services).2. Right-click the Windows service for SQL Server Analysis Services (MSSQLSERVER), and thenchoose Properties. If you are using a named instance of Analysis Services, the instance nameappears in parenthesis.
  • 3. Choose Recovery.4. In the First failure list, choose Restart the Service.5. In the Second failure list, choose Restart the Service.6. In the Subsequent failures list, choose Restart the Service, and then choose OK.
  • Three: set up SharePointIf you don’t skip the portal setup (if you skip portal set up, go to back up and restore ifyou’re moving to new hardware or run the TFS upgrade wizard), you have two options forhow to deal with SharePoint:Option 1: You can continue to use the same SharePoint site you used with TFS 2010, if youperform a few procedures to update SharePoint. First you have to uninstall the oldTFS extensions for SharePoint, and then install the new version of the extensions. Youalso want to make sure the service account that you will use on the upgraded TeamFoundation Server is a member of the Farm administrators group.Option 2: New for this version of TFS, you can install SharePoint Foundation using the TFSextensions for SharePoint wizard. The TFS wizard will install a fresh copy of SharePoint usingthe installation of SQL Server you just set up, and then configure the TFS extensions for thenew installation of TFS. After you install SharePoint, you’ll detach its content database toprepare for the migration of the data from your previous SharePoint installation in step 4,Backup and restore data.How to Set Up SharePointThe steps for both options appear below. Skip the uninstall section if you’re going to installSharePoint on the new hardware. Likewise, you can skip the section for detaching thecontent database if you’re going to reuse your existing SharePoint.
  • Required PermissionsTo perform these procedures, you must be a member of the Administrators security group onWindows Server and a member of the Farm Administrators group in Windows SharePointServices 3.0.Uninstall the old TFS extensions (if necessary)On the SharePoint site you were using with TFS 2010, uninstall the TFS Extensions forSharePoint (the uninstall screen for TFS 2008 looks different, but the process is exactly thesame). If you’re installing SharePoint on the new hardware, you can skip this step.If SharePoint and the previous version of TFS were on the same computer, you have touninstall the entire TFS application tier. In the new upgraded TFS deployment, yourSharePoint server will be on a different server than the TFS application tier, and the onlyTFS component on the SharePoint server will be the TFS extensions for SharePoint.
  • Install the new TFS extensions (and possibly SharePoint)Run the TFS installation program from the product DVD and then use the ConfigureExtensions for SharePoint Products wizard. New for this version of TFS, you can use the TFSExtensions for SharePoint wizard to install SharePoint Foundation. If you already have acompatible version of SharePoint installed when you run the wizard, it will only install theTFS extensions.To run the Team Foundation Server installer1. Insert the Team Foundation Server DVD in the drive and launch the tfs_server.exe file tobegin the installation.2. On the license terms dialog box, accept the license terms and then choose Install Now.If you want to install Team Foundation Server to a specific location in the file system,choose the browse button (…) next to the default install location.To configure Team Foundation Server Extensions for SharePoint Products1. In the Team Foundation Server Configuration tool, choose Configure Extensions forSharePoint Products and then choose Start Wizard.The Team Foundation Server SharePoint Extensions Configuration wizard appears.
  • 2. Read the Welcome screen, and choose Next.3. If SharePoint Products is already installed, skip to step 4. If SharePoint weren’t installed,you’d take these letter steps A - D:A. Choose the big Install SharePoint Foundation 2010 button.B. Once the install completes, choose Next.C. Type the name of the SQL Server or named instance that will host theconfiguration databases for SharePoint Foundation 2010 and choose Next.D. Type a user account and password for the service account for SharePointFoundation 2010 and then choose Next.4. On the Review page, review the settings and choose Next.The wizard validates your configuration.5. Choose Configure.The wizard applies configuration settings. This process might take several minutes.6. Choose Next.7. Choose Close.8. Choose Close.The Team Foundation Server Administration Console appears.
  • Add the TFS service account to the Farm Administrators groupIf you’re using the same SharePoint site from your previous deployment, you may alreadyhave the TFS service account in the Farm Administrators group. If so, you can skip this step.Otherwise, you should follow the steps below to ensure the service account that you will usefor TFS is added to the Farm Administrators group on SharePoint.How do you know if this step is necessary? Here are two potential scenarios that wouldrequire you to perform this step.If you’re planning to change the account you’re using for the TFS service accountduring TFS upgrade, you should add the new account to the Farm Administratorsgroup.If you are using Network Service and you’re planning to migrate the TFS applicationtier to new hardware, you should add the name of the new hardware followed by a $symbol (DomainServerName$) to the Farm Administrators group.To add the service account for TFS to the Farm Administrators group for SharePointFoundation (pictured)1. In a web browser, open the SharePoint 2010 Central Administration site.2. Under Security, choose Manage farm administrators group.3. Choose New.4. In the Users/Groups box, enter the name of the service account for Team FoundationServer.
  • If you’re using Network Service, add the server name followed by a $ symbol. Forexample, domainservername$.5. Choose OK.To add the service account for TFS to the Farm Administrators group in WindowsSharePoint Server 3.0 or Office SharePoint 2007 (not pictured)1. In a web browser, open the SharePoint Central Administration site.2. Choose the Operations tab.3. Under Security Configuration, choose Update farm administrator’s group.4. In Groups, choose Farm Administrators.5. Choose New.6. In the Users/Groups box, enter the name of the service account for Team FoundationServer.If you’re using Network Service, add the server name followed by a $ symbol. Forexample, domainservername$.7. Choose OK.Detach the SharePoint content databaseOnly do this step if you’ve installed a fresh copy of SharePoint Foundation and you intend tomigrate your content database from a previous installation of SharePoint. Otherwise, skipthis step.
  • When you installed SharePoint, a brand new content database was created for SharePoint.You need to detach that database to prepare for the migration of the data from yourprevious SharePoint installation in step 4, Back up and Restore Data.To detach the content database1. In a web browser, open the SharePoint 2010 Central Administration site.2. Under Application Management, choose Manage Content Databases.3. Choose WSS_Content.Note: WSS_Content is the default name. Your installation might use a custom name forthis database.The Manage Content Database Settings page opens.4. Select the Remove content database check box, and then choose OK.Note: This step detaches the database but does not delete any content.5. In the warning dialog box that appears (pictured), choose OK.6. In Manage Content Database Settings, choose OK to confirm your changes.
  • Four: back up and restore dataThis step is only necessary if you’re moving TFS to new hardware. If you’re going to usethe same hardware, you can back up your data when you run the TFS upgrade wizard. Skipto step 5, run the TFS upgrade wizard.How to back up and restore TFS data to new hardwareIf you haven’t installed TFS on the new hardware yet, you’ll want to do that now. New forthis version of TFS, you can use custom backup and restore tools to manage your data. Firstyou’re going to back up your data, including the encryption key on the report server youused with the previous version of TFS. Next, you’re going to restore your data to the SQLServer instance you set up in step 2. With the restore complete, you’ll use the SQL ServerReporting tool to restart the report server database, restore its encryption key, and thenverify access to the report server. If you installed SharePoint, you’ll use a SharePointcommand line tool to attach and upgrade your content database.Required PermissionsTo perform this procedure, you must be a member of the Administrators security group onWindows server of the new hardware and the old.
  • If you plan to configure reporting, you must also be a member of the Administratorssecurity group on the server that is running SQL Server Reporting Services. If you plan toconfigure SharePoint Products, you must be a member of the Farm Administrators group onthe SharePoint Products administration site. If you did not install the Database Engine thatwill host the configuration database or a database administrator manages the instance ofSQL Server that you are using, you must be a member of sysadmin Server role in SQL Server.Back up your dataIf you haven’t installed TFS on the new hardware yet, you’ll want to do that now to accessthe custom backup and restore tools. You’re going to back up all of your TFS data, includingthe encryption key for the report server.Tip: Migrating from Windows SharePoint Services 3.0? Your SharePoint site must be runningat service pack 2 or higher to migrate the content database to SharePoint Foundation on thenew hardware. If you’re not at service pack 2 or higher, you should update SharePointbefore you back up your data.To run the Team Foundation Server installer
  • 1. Insert the Team Foundation Server DVD in the drive and launch the tfs_server.exe file tobegin the installation.2. On the license terms dialog box, accept the license terms and then choose Install Now.If you want to install Team Foundation Server to a specific location in the file system,choose the browse button (…) next to the default install location.To back up the encryption key for reporting services1. Launch Reporting Services Configuration Manager.For example, on Windows Server 2008 R2, you would choose Start, All Programs, MicrosoftSQL Server, Configuration Tools, and then choose Reporting Services ConfigurationManager.The Reporting Services Configuration Connection dialog box opens.2. Specify the name of the report server you used with the previous version of TFS and thenchoose Connect.3. In the navigation bar on the left side, choose Encryption Keys, and then choose Backup.The Encryption Key Information dialog box opens.4. In File Location, specify the location where you want to store a copy of this key.Consider storing this key on the new hardware, so that it’s easily accessible when yourestore the Reporting Services databases.5. In Password, specify a password for the file.
  • Don’t forget the password! You’ll need it later on to restore the Reporting Servicesdatabases.6. In Confirm Password, specify the password for the file again.7. Choose OK.To back up your databases1. Launch TFSBackup.exe.The TFSBackup.exe tool is in the Tools folder where you installed Team FoundationServer.The default location is C:Program FilesMicrosoft Team Foundation Server11.0Tools.2. In Source SQL Server Instance, enter the name of the SQL Server instance that hosts theTFS databases you want to back up and choose Connect.3. In Select databases to backup, choose the databases to back up.Need help? List of TFS 2010 databases on MSDN; List of TFS 2008 databases on MSDN.4. In Backup Databases to, enter the name of a network share that is configured with read/write access for Everyone, or accept the default location in the file system of the SQL Serveryou connected to in step 2.Note: If you want to overwrite backups stored in this network location, you can chooseOverwrite existing database backups at this location.5. Choose Backup Now.The Backup tool reports progress on each database being backed up.6. Choose Close.
  • Restore your dataNow that you’re data is backed up on from the old hardware, you can restore it to the SQLServer on the new hardware.To restore your TFS data1. Launch TFSRestore.exe.The TFSRestore.exe tool is in the Tools folder where you installed Team FoundationServer. The default location is C:Program FilesMicrosoft Team Foundation Server11.0Tools.2. In Target SQL Server Instance, enter the SQL Server instance you will use as the data tierand choose Connect.3. Choose Add Share and enter the UNC path to the network share that is configured withread/write access to Everyone where you stored the backups of your TFS data. For example,servernamesharename.
  • If the backup files are located on the file system of the server that is runningTFSRestore.exe, you can use the drop down box to select a local drive.Note: The service account for the instance of SQL Server you identified at the start of thisprocedure must have read access to this share.4. In the left hand navigation pane, choose the network share or local disk you identified inthe previous step.The TFS Restore Tool displays the database backups stored on the file share.5. Select the check boxes for the databases you want to restore to the SQL Server youidentified at the start of this procedure.Important: For SharePoint, you must only restore the WSS_Content database. Do notrestore the WSS_AdminContent or WSS_Config databases. You want the new SharePointFoundation versions of these databases, not the ones from the previous version of SharePointor from a SharePoint installation running on any other server.6. Choose Overwrite the existing database(s) and then choose Restore.The Database Restore Tool restores your data and displays progress reports.7. Choose Close.Fix up the report serverTo restart the Reporting Services database and restore its encryption key1. Launch the Report Server Configuration tool and restore the original reporting databaseand its encryption key to your new instance of SQL Server Reporting Services.For SQL Server 2008 R2, choose Start, All Programs, Microsoft SQL Server R2,Configuration Tools, and then Reporting Services Configuration Manager.2. In Reporting Services Configuration Connection, specify the name of the server where youinstalled Reporting Services for TFS 2012 and choose Connect.3. On the Database page, choose Change Database.The Report Server Database Configuration Wizard appears.4. On the Action page, choose Choose an existing report server database and then chooseNext.5. In Server Name, type the name of the SQL server you used in the TFS Database RestoreTool to restore your report server databases and choose Next.Choose Test Connection to test the connection.
  • 6. Choose the report server database you restored with the TFS Database Restore Tool andthen choose Next.If you haven’t changed the name, the default database name is ReportServer.7. On the Credentials page, choose Next.8. On the Summary page, review the information and then choose Next.The wizard configures the database and displays progress reports.9. On Encryption Keys page, choose Restore.The Restore Encryption Key window opens.10. In File Location, specify the location of the backup file for the encryption key. InPassword, specify the password you used when you backed up the encryption key, and thenchoose OK.The status of the restoration appears in Results.11. On the Scale-out Deployment page, choose the previous report server from the scale-outdeployment status page and choose Remove Server.12. On the Report Manager URL page, use the hyperlink in URL to launch the Report Managersite.The report manager site appears. Your report server has been restored.13. Choose Exit to close Reporting Services Configuration Manager.Fix up the SharePoint ServerTo run the STSADM command line tool for SharePoint1. Open a Command Prompt as an administrator on the new hardware that is runningSharePoint Foundation.2. Change directories to this location:Drive:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions14binWhere Drive is the drive letter.3. In the command prompt, type the following command:stsadm.exe -o addcontentdb -url http://WSSServerName/sites -databasenamecontentdatabase -databaseserver SQLServerName
  • Where: WSSServerName is the name of the SharePoint server; contentdatabase is the nameof the content database; SQLServerName is the name of the SQL Server that hosts thecontent database.4. In the command prompt, type the following command:stsadm.exe -o addpermissionpolicy -url http://WSSServerName -userloginDomainUserName -permissionlevel "full control"Where: WSSServerName is the name of the SharePoint server; DomainUserName is the username and domain of the account used to run the TFS SharePoint configuration wizard andinstall SharePoint.
  • Five: run TFS upgrade wizardRun the Team Foundation Server install from the product DVD and then use the UpgradeConfiguration wizard to upgrade your installation.How to Upgrade TFSFirst you install TFS, then you run the upgrade configuration wizard. If you moved TFS tonew hardware, you have to change the URL for TFS after the upgrade wizard finishes.Tip: After you install TFS, the configuration tool appears automatically. If for some reasonyou don’t see it, you can access it from the TFS administration console. Launch TFSadministration console from the Start menu. In the admin console, choose Application Tier,and then choose Configure Installed Features.Required PermissionsTo perform this procedure, you must be a member of the Administrators security groupon Windows server. If you’re using the basic upgrade path, these are the only permissionsyou need.If you plan to configure reporting, you must also be a member of the Administratorssecurity group on the server that is running SQL Server Reporting Services. If you plan toconfigure SharePoint Products, you must be a member of the Farm Administrators group onthe SharePoint Products administration site. If you did not install the Database Engine thatwill host the configuration database or a database administrator manages the instance ofSQL Server that you are using, you must be a member of sysadmin Server role in SQL Server.Uninstall the previous version of TFS (if necessary).Use Control Panel to completely uninstall the previous version of Team Foundation Server.
  • Tip: If youre upgrading from a prerelease version of TFS 2012, you dont have to uninstallthe old version of TFS. You can skip this step.Install TFS 2012 and run the upgrade wizardTo run the TFS installer on the new hardware1. Insert the Team Foundation Server DVD in the drive and launch the tfs_server.exe file.2. On the license terms dialog box, accept the license terms and then choose Install Now.If you want to install Team Foundation Server to a specific location in the file system,choose the browse button (…) next to the default install location.To run the TFS configuration wizard1. In the Team Foundation Server Configuration tool, choose Upgrade, and then choose StartWizard.
  • The Team Foundation Server Upgrade wizard appears.2. Read the Welcome screen and choose Next.3. Type the name of the SQL Server instance that hosts the data from an earlier version ofTeam Foundation Server, and choose List Available Databases.The wizard lists deployments of Team Foundation Server that you can upgrade. Ifmultiple deployments are listed, choose the one that you want to upgrade.4. Select the By checking this box, I confirm that I have a current backup check box, andthen choose Next.If you need to do a backup, you can choose Click here to launch the Database Backup Tool,follow the steps below, then continue with the TFS upgrade wizard.The TFS Database Backup Tool displays the databases it finds on the SQL Serverinstance specified in SQL Server Instance.A. In Select databases to backup, choose the databases to back up.Need help? List of TFS 2010 databases on MSDN; List of TFS 2008 databases on MSDN.B. In Backup Databases to, accept the default location or enter another.Note: If you want to overwrite backups stored in this network location, you canchoose Overwrite existing database backups at this location.C. Choose Backup Now.
  • The Backup tool reports progress on each database being backed up.D. Choose Close.5. Choose Use a system account to use Network Service as the service account for TFS.If you use a user account, you must type its password.To test the user account and password combination, you can choose Test.6. Under Authentication Method, choose NTLM or Negotiate (Kerberos), and then chooseNext.If you choose NTLM, NTLM authentication is used. This option is the default setting.If you choose Negotiate (Kerberos), Kerberos authentication is attempted first. If thatauthentication fails, NTLM authentication is used.7. If you’re upgrading from TFS 2008, you can specify a Port or Virtual Directory or you canaccept the default values. If you’re upgrading from any other version of TFS, you must skipto the next step. On client operating systems, you must skip to step 10. You cannotconfigure SharePoint Products or the reporting feature of Team Foundation Server on aclient operating system.8. Select the Configure Reporting for use with Team Foundation Server check box to usereporting and then choose Next.
  • A. Enter the name of the server that is running SQL Server Reporting Services inReporting Services Instance and choose Populate URLs.The URLs for the report server and its management site appear in the drop-down listsfor Report Server URL and Report Manager URL.B. Make sure the URLs that you want to use for Team Foundation Server appear in thedrop-down lists and then choose Next.
  • C. If you’re upgrading from TFS 2008, skip to the next step. Otherwise, type thename of the server that is running the Database Engine and Full-Text Search to hostthe warehouse database, and then choose List Available Databases.The wizard lists available warehouse databases that you can upgrade. Choose thedatabase that you want to upgrade, and then choose Next.You can choose Test to test the connection to SQL Server.D. Enter the name of the server that is running SQL Server Analysis Services in SQLAnalysis Services Instance and choose Next.To test the connection to SQL Server, you choose Test.E. Enter the name and the password of the report reader account and choose Next.
  • If you specified a user account for the service account of Team Foundation Server instep 5 and you want to use a different account in this step, you must select the Use adifferent account than the Team Foundation Server service account for theReporting Services report reader account check box.Choose Test to test the user account and password combination.9. Select the Configure SharePoint for use with Team Foundation Server check box toconfigure SharePoint Products and choose Next.
  • On the SharePoint Products Settings page, choose one of the following optoins:* Use current SharePoint settings to retain your settings for SharePoint Products,and then choose Next.You typically use this option to continue to use the existing portal, which must havethe new TFS extensions for SharePoint installed and configured. If your old portal ison the server you are upgrading, the new extensions are configured automatically.* Use an existing server farm for SharePoint, enter the URL for the SharePoint webapplication and the SharePoint Administration site, and then choose Next. To testthe connection to each of these URLs, you can choose Test.You typically use this option to migrate to a new portal, which must contain yourmigrated data for SharePoint Products.10. If you’re upgrading from TFS 2008, accept the default values for project collection nameand description or optionally enter a new name and description and then choose Next. Ifyou’re upgrading from any other version of the product, skip to the next step.11. On the Review page, review your settings, and choose Next.The wizard validates your configuration.12. Choose Configure.The wizard applies configuration settings.
  • 13. Choose Next.Your data is upgraded; Progress reports appear and show the status of eachcomponent.14. Choose Next.15. Read the final summary screen, and then choose Close twice; once in the wizard andthen again in the configuration tool.Note: If the upgrade fails, see the detailed log files by choosing Click here to open acomplete log on the summary screen. After you resolve any outstanding issues that areidentified in the log file, you can resume the upgrade by using the Team FoundationAdministration Console. On the Status tab in Team Project Collections, choose CreateCollection, and then choose Rerun job.Update the URL for TFSIf you used the advanced upgrade path, you moved TFS to new hardware and now youmust update the server URL on the TFS application tier and in the TFS extensions forSharePoint. If you used the standard or basic upgrade paths, you can ignore both of theseprocedures.To update the URL for TFS on the TFS application tier1. On the TFS application tier, open the administration console for Team Foundation Server.2. In the navigation bar, choose Application Tier, and then click Change URLs.The Change URLs window opens.3. In Notification URL, type the URL for the new application-tier server, and then chooseOK.To update the URL for TFS application tier in the TFS Extensions for SharePoint1. On the server running SharePoint, open the administration console for Team FoundationServer.2. In the navigation bar, choose Extensions for SharePoint Products, select the SharePointWeb Application and then choose Modify access.The Change URLs window opens.3. In URL for Team Foundation Server, type the URL for the new application-tier server, andthen choose OK.
  • Upgrade Automated BuildsAfter you upgrade the application tier, you might want to install the new build service. Youcan’t use the TFS 2010 build service with Team Foundation Server 2012, but you can installthe new build service side-by-side on the same server as the TFS 2010 build service.
  • One: Double Check RequirementsVerify that the operating system and hardware meet the requirements for TeamFoundation Build Service. New for this version of TFS, the build service requires a 64-bitserver, if you use a server operating system. You can also use Windows 7 or Windows 8 clientoperating systems. Vista is no longer supported. If your team is building Windows apps,you’ll need to install the build service on Windows 8.By default, Team Foundation Build Service uses Network Service for its service account.There’s more information on MSDN: System Requirements for Team Foundation BuildService, Accounts Required for Installation of Team Foundation Server, and Build and Test aWindows App Using Team Foundation Build.
  • Two: Install the Build ServiceRun the Team Foundation Server install from the product DVD and then use the buildservice configuration wizard to configure your installation. This wizard installs andconfigures Team Foundation Build Service.How to run the TFS Build wizardFirst you install the build service, then you run its configuration wizard. This procedureassumes you’re installing the new build service on a dedicated build machine which alsohosts the TFS 2010 build service, but this is not a requirement. You can install the TFS 2012build service wherever you like.Once you have the new build service installed, you can continue to build your softwareprojects with your existing build definitions and process templates, or you can create newdefinitions using the new default template, which allows you to take advantage of new buildfeatures.There’s more information on MSDN: Use Legacy Build Processes, Define a Build Process thatis Based on the Default Template, and Whats New in Team Foundation Build.Tip: If you’ve already installed TFS on the machine where you plan to run the new buildservice, then the build service is already installed, and you can skip the first procedure. Toaccess the build configuration wizard, launch Team Foundation Server AdministrationConsole, choose Build Configuration and then choose Configure Installed Features.Required PermissionsTo perform these procedure, you must be a member of the Administrators security group onWindows Server. To run the build configuration wizard, you must be a member of theProject Collection Administrators group on TFS.
  • To run the TFS installer on the new hardwareThis installs Team Foundation Server and all its components (including the build service) onyour file system, but you only need to configure the build service. You don’t have toconfigure any of components you don’t need running on this machine (for example, TFS).1. Insert the Team Foundation Server DVD in the drive and launch the tfs_server.exe file .2. On the license terms dialog box, accept the license terms and then choose Install Now.If you want to install Team Foundation Server to a specific location in the file system,choose the browse button (…) next to the default install location.To run the TFS build configuration wizard1. Choose Configure Team Foundation Build Service, and then choose Start Wizard.The Build Service Configuration wizard appears.2. Read the Welcome screen, and then choose Next.3. Choose Browse, enter the name of the upgraded TFS 2012 server, and then choose theteam project collection to which you want this build controller to connect.4. Choose Next.5. Perform one of the following steps, and then choose Next:* Choose Use the default setting and specify the number of build agents. This optiononly appears if there are no other build machines attached to the team projectcollection.
  • If you installed Team Foundation Build Service on the same server as TeamFoundation Server, the default setting for Number of build agents to run on thisbuild machine is 1 (recommended).* Choose Scale out build services, to run concurrent builds across multiple machines.If you choose this option, you have to specify the number of build agents for thismachine and then add them to a new or existing build controller. This option onlyappears if there are other build machines attached to the team project collection.If you installed Team Foundation Build Service on its own server, the default settingfor Number of build agents to run on this build machine is equal to the number ofprocessor cores on this server.* Don’t choose Replace an existing build machine or Configure later, as theseoptions enable you to replace a build machine or skip this configuration.6. Under Run Team Foundation Build Service as, choose Use a system account, and thenchoose NT AuthorityNetwork Service.If you choose Use a user account , you must enter a domain or local account nameand password. To test the user account and password, choose Test.Network Service is the default value for the service account for the build service.7. Choose Next.8. Review the information and then choose Next.The wizard validates your configuration.Tip: If you get a warning that port 9191 is already in use, you can safely ignore it. Theprevious version of the build service is using this port, but will share it with this version ofthe build service.9. Choose Configure.The wizard applies configuration settings.10. Choose Next.11. Choose Close twice, once in the wizard and then again in the configuration tool.The Team Foundation Server Administration Console appears.
  • Add New Features to Team ProjectsYou can also use a wizard to add new features to your TFS 2010 team projects.So far, you’ve been upgrading the server. That’s great. But now it’s time to upgrade some orall of the projects created on that server, if you want any of those projects to have the newfeatures available in Team Foundation Server (TFS) 2012. You might want to do this as theserver administrator, or you might want to have an administrator for the project performthis task. When you upgrade a project using the Configure Features wizard, your useraccount is automatically added to the default team created as part of upgrading the projectas an administrator for that team. That’s handy if you’re the project administrator; notnecessarily so handy if you’re the server admin who will never look at that project again.And if you have a lot of projects to upgrade, it might make more sense to share the task outto the people who will be working in those projects on a daily basis. It’s up to you to decidewho will do this work.How to run the Configure Features wizardThe Configure Features wizard helps you add features to your pre-existing projects createdin TFS 2010. It cannot be used on projects created with earlier versions of TFS. If you havenot customized your TFS 2010 team project, or only slightly customized it, the wizard canadd features automatically for you. If you have customized your team project or processtemplates extensively, you will probably not be able to use the wizard.You can use the wizard to:Analyze projects to determine if they can be automatically updated with available featuresAutomatically configure these projects with those features, such as review, feedback, andplanning tools
  • The wizard provides information about your project and the changes it will make in eachstep. Depending on how much you have customized your team project, you might need tochoose between process templates. In some cases, no automatic configuration is possible,and you must manually make the changes required to enable the features you want. Unlessyou have heavily customized your project or templates, however, the wizard will be able toupgrade your project for you, providing you access to all the neat new features for thisrelease, such as:Team and Team Page: Organize work by teams and use the team home page as aconvenient way to navigate work in Team Web AccessCode Review: Initiate and track code review requests and responses.Feedback: Initiate feedback requests and track feedback responses. Even though thisfeature set will be enabled, users will not be able to see or use it unless they have Fullpermissions in Team Web Access. For more information on MSDN, see FeaturesAccessed Through Web Permissions.My Work: Organize upcoming, ongoing, and suspended work.Planning Tools: Manage the product backlog and plan and run sprints using the backlogpage, iteration pages, capacity setting, and task board page. As with the Feedback featureset, even though all planning tools will be enabled, your users will only be able to see anduse the set that they have permissions for. For more information on MSDN, see FeaturesAccessed Through Web Permissions.Storyboard Linking: Access the latest version of storyboards by linking them to work items.Hidden Types Category: Specify the set of work item types that users should create througha form or tool, and not manually. By default this includes Code Review Request and CodeReview Response, Feedback Request and Feedback Response, and Shared Steps.Required PermissionsYou must be at least a member of the Project Administrators group to configure features fora project, or have the equivalent permissions. Team Foundation Collection administratorsand Team Foundation Administrators can do this too, but as mentioned above, the useraccount of the person running the wizard will be automatically added to the default team,so to save time and avoid confusion, it might make more sense for a project admin to runthis tool. Regular project members can’t use the Configure Features wizard.To run the Configure Features wizard1. Open Team Web Access and choose the team project you want to update. (If you’re notsure how to open a project in Team Web Access, it’s easy; just open a web browser andnavigate to the URL of your team project, using thehttp://ServerName:Port/tfs/CollectionName/ProjectName format.)
  • 2. Choose the gear icon to open the administration page, and then choose ConfigureFeatures.If Configure Features doesn’t appear, either your project has already been updated with allfeatures available, or else you don’t have the required permissions to configurefeatures. Assuming there are features to configure and you have the right permissions, theConfigure Features wizard opens and lists those features not yet configured for your teamproject:3. Choose Verify to determine if the listed features can be configured automatically for yourproject.4. After the verification process completes, choose from one of these options, depending onwhat the wizard returns:Configure: to proceed with the automatic update, disregarding any exceptions listed.Cancel: to close the wizard as you want to update a customized process templateor manually update the team project.
  • Choose a process template to continue: if you are asked to choose between two or morepotential matches, to pick the process template that best matches the template used tocreate your team project, and then proceed with the configuration process.Close: to close the wizard as it cannot perform an automatic update. You must manuallyupdate your team project as it has been customized beyond what the wizard can handle, oryou created your team project using a process template that the wizard doesn’t recognize.A successful update will return a success message.If the wizard doesn’t succeed, you will receive an error message. It’s up to you at that pointto manually resolve any errors and complete the update.For more information on MSDN, see Update a Customized Process Template to Access NewFeatures, and Update an Upgraded Team Project to Access New Features (manual updates).In most cases, congratulations, you’ve enabled features for your upgraded team project.Now you need to verify that the changes worked and add team members to your team asneeded.
  • However, if you’re using the Agile process template, or you want access to add the sharedqueries feature to your team project, there’s still a little more work to do before continuingto the next step. For more information on MSDN, see Update the Workflow for Agile TeamProjects and Add New Queries.How to verify access to New FeaturesAfter you have run the Configure Features wizard, you or a team member should verify thatthe new features appear as expected.Required Permissions:We’ll walk you through the steps for you to verify availability of these features:* The Task Board and the Storyboard tab. To verify that these features appear in TeamWeb Access (TWA), you must be a member of one of the following groups: Team FoundationAdministrators, Project Collection Administrators, or Project Administrators of the teamproject.* The Product Backlog and Iteration Backlog pages and the Feedback Request form. Thesefeatures require you to be added to the Full group for Web Access Permissions.Important: To access the Full set of features, users must be licensed for one of thefollowing MSDN subscriptions: Visual Studio Test Professional with MSDN, Visual StudioPremium with MSDN, or Visual Studio Ultimate with MSDN. Each of these MSDN subscriptionsincludes a TFS CAL for the subscriber. For more information on MSDN, see Features AccessedThrough Web Permissions.To add users to the Full group of Web Access Permissions, you must be a member of theTeam Foundation Administrators group. Unless you are a member of that group, you will notbe able to view the web access tab or make any changes.* The Code Review feature. To verify availability to request code reviews, you must be amember of the team project and have installed either Visual Studio Premium 2012 or VisualStudio Ultimate 2012.Important: If you encounter a problem in any of these steps, check if there is an answerin the Team Foundation Server Setup forum or the Team Web Access forum.Verify access to the Task Board page and the Storyboards tabTo verify that the home page appears as expected1. Open Team Web Access (TWA) and then connect to your team project using a URL thathas the following format. If TWA is already open, then refresh your browser to refresh thecache.http://MyServer:8080/tfs/TeamProjectCollectionName/MyProject
  • 2. Verify that the Activities list on the right side of the Home page appears as shown:To add Team Members and Set up IterationsThe upgrade of Team Foundation Server (TFS) created a default team for your team project,named “Your Project Name Team,” but did not add any members to it.1. From the Home page, under Members, choose the Manage all members link, and addyourself to the team. Also, add a TFS group, Windows group, or other members that belongto this team.
  • 2. Under Administration, choose the Configure schedule and iterations link.3. Select the checkbox for the iteration that you want to specify as current. For example,select the checkbox next to Iteration 1, and then choose the Set dates link for thatiteration.4. Specify the dates for the current iteration. Specify dates which will include today’s datewithin the Start Date and End Date.
  • The task board only shows work items that are assigned to the current iteration, which isdefined as that iteration whose dates include the current date.For more information on MSDN, see Define Team Areas and Iterations.To verify that the Storyboards tab and Task Board appear1. From the Home page, choose the button that corresponds to your backlog orrequirements category, depending on your process template. For example, choose from oneof the following buttons:2. Specify a Title and any other required fields.3. Choose the Storyboards tab and verify that it appears as shown.
  • 4. Select the current iteration in the Iteration field.5. Choose Save and Close.6. Choose the View board link, and verify that the Task Board page appears and displays thework item that you just created.You see only those backlog items that are assigned to the current iteration, and any tasksthat have been linked to those items.7. Choose the add task icon.8. Fill in the work item form, and then choose Save and Close.Verify access to the Backlog page and Request feedback toolTo access the Backlog page and the Request Feedback tool, you must be added to the Fullgroup to Web Access Permissions. If you are a member of the Team Foundation
  • Administrators group, go ahead and perform the following steps. Otherwise, ask a TFSadmin to add you to the Full group.To add Team Members to the Full Group1. To access the administration mode, choose the gear icon.2. Choose Control Panel.3. Choose Web Access, and then choose Full.4. Choose Add, Add Windows user or group, and then add yourself to the Full group.5. (Optional) Add a team member who meets the license requirements to the Full group.To verify access to the Backlog page
  • 1. Return to the Home page of TWA, and then refresh your browser.2. Verify that the Activities list appears like this:3. Choose View backlog, and then verify that the Product Backlog page appears similar tothe one shown in this example:The Type of backlog item shown will differ depending on the process template usedto create your team project.4. Type an entry into the Title field for a backlog item and choose the Add button. Yourentry is added to the bottom of the list.5. (Optional) To remove the items that you added for verification purposes, open each itemthat you created and change the State to Closed or Done.To verify access to Request Feedback1. Choose the Home tab.
  • 2. Choose the Request feedback link. The Feedback Request form appears as shown.Did you get an error message?
  • If error message TF400264 appears (pictured below), you’ll need to configure an SMTP serverto continue. For more information on MSDN, see Configure Email Notifications and Specifythe SMTP Server.To verify access to the Code Review FeatureYou can request a code review only from the My Work page of Team Explorer. This pageappears only if you install Visual Studio Premium 2012 or Visual Studio Ultimate 2012. Also,you will need to have some code that you have added or updated in order for the RequestReview link to become active.1. Open Team Explorer from VS Premium or VS Ultimate.If Team Explorer is already open, then choose the Refresh icon to refresh the cache.2. Choose My Work. You should see the Request Review link as shown:3. Check out some code, modify it, and then verify that you can choose the Request Reviewlink.
  • For more information on MSDN, see Day in the Life of an ALM Developer: Suspend Work, Fix aBug, and Conduct a Code Review.What Next? Last stepsWith the verify process completed, your team can get started using all the newfeatures. You can learn about them from these topics on MSDN:Agile Planning and IterationsEngage Stakeholders through Continuous FeedbackDay in the Life of an ALM Developer: Suspend Work, Fix a Bug, and Conduct a Code ReviewUpdate the Workflow for Agile Team ProjectsTo get the best experience using the Agile planning tools and task board, you will want tomanually update the workflow definitions for the user story and task work item types. If youdon’t update the workflow, then the task board provides only two states, Active andClosed, which doesn’t provide insight into progress your team makes during a sprint.You only need to perform this step if your team project is based on an Agile processtemplate. For more information on MSDN, see Update the Workflow for Agile Team Projects.To learn moreConfiguration Changes Made to Add New FeaturesChanges Made to Team Projects and Default Process Templates During Upgrade of TeamFoundation Server
  • Contacthttp://elhajj.wordpress.comPlease visit us online for information on future titles.About the authorTim Elhajj is a writer in Microsoft’s Developer Division. He currently works on TeamFoundation Server and ALM products. He has also worked on the Windows Server product.He lives in Washington State with his wife, two high-school kids, random chickens, and abunch of computers.He graduated summa cum laude from Hunter College’s School of Arts and Sciences inmidtown Manhattan. Since moving West, he’s worked at companies small and large: Onecompany made software that ran in DOS, others provided public record retrieval orcorporate expense accounting services. He’s done his time in the contract agency trenches,and he’s worked for big, recognizable companies like RealNetworks and Microsoft. Hecurrently holds the MCSE and MCSA.