Tim Elhajj

Off the Microsoft stack!

Run the TFS Upgrade Wizard


Run TFS Upgrade Wizard

How to run the TFS upgrade wizard

First you install TFS, then you run the upgrade configuration wizard. If you moved TFS to new hardware, you have to change the URL for TFS.

Tip[6]Tip: After you install TFS, the configuration tool appears automatically. If for some reason you don’t see it, you can access it from the Start menu. Launch Team Foundation Server Administration Console, choose Application Tier, and then choose Configure Installed Features.

Required Permissions

To perform this procedure, you must be a member of the Administrators security group on Windows server. If you’re using the basic upgrade path, these are the only permissions you need.

If you plan to configure reporting, you must also be a member of the Administrators security group on the server that is running SQL Server Reporting Services. If you plan to configure SharePoint Products, you must be a member of the Farm Administrators group on the SharePoint Products administration site. If you did not install the Database Engine that will host the configuration database or a database administrator manages the instance of SQL Server that you are using, you must be a member of sysadmin Server role in SQL Server.

To run the TFS installer on the new hardware
  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 configuration wizard
  1. In the Team Foundation Server Configuration tool, choose Upgrade, and then choose Start Wizard.
    The Team Foundation Server Upgrade wizard appears.
  2. Read the Welcome screen and then perform one of the following actions:
    • If your data is already hosted on the SQL Server instance that you will use as the data tier, choose Next. This is the best option for an in-place upgrade, using the same hardware.
    • If you need to restore your data to the SQL Server instance that you will use as the data tier, choose Click here to launch the Database Restore Tool. This is the best option for a migration upgrade to new hardware.
      1. In Target SQL Server Instance, enter the SQL Server instance you will use as the data tier and choose Connect.
      2. Choose Browse to navigate to the file share where you stored the backups of your TFS data. The service account for the instance of SQL Server you identified in the first step must have read access to the file share.
      3. Choose the network share you identified in the previous step. The Database Restore Tool displays the database backups stored on the file share.
      4. Select the check boxes for the databases you want to restore to the SQL Server you identified in the first step. If you’re restoring a report server or have backups with database names the match database names on the target SQL Server, choose Overwrite the existing database(s) and then choose Restore.
        The Database Restore Tool restores your data and displays progress reports.
      5. Choose Close, and then choose Next.
      6. If you did not restore the SQL Server Reporting Services databases to new hardware, you can skip steps G through R below and continue with step 3 of the TFS upgrade wizard. If you restored SQL Server Reporting Services databases, before moving to step 3 of the TFS upgrade wizard, you must launch the Report Server Configuration tool and restore the original reporting database and its encryption key to your new instance of SQL Server Reporting Services.
      7. Leave the TFS upgrade wizard running and choose Start, All Programs, Microsoft SQL Server R2, Configuration Tools, and then Reporting Services Configuration Manager.
      8. In Reporting Services Configuration Connection, specify the name of the server, and then choose Connect.
      9. On the Database page, choose Change Database.

        The Report Server Database Configuration Wizard appears.
      10. On the Action page, choose Choose an existing report server database and then choose Next.
      11. In Server Name, type the name of the SQL server you used in the TFS Database Restore Tool to restore your report server databases and choose Next.
        Choose Test Connection to test the connection.
      12. Choose the report server database you restored with the TFS Database Restore Tool and then choose Next.

        If you haven’t changed the name, the default database name is ReportServer.
      13. On the Credentials page, choose Next.
      14. On the Summary page, review the information and then choose Next.
        The wizard configures the database and displays progress reports.
      15. On Encryption Keys page, choose Restore.

        The Restore Encryption Key window opens.
      16. In File Location, specify the location of the backup file for the encryption key. In Password, specify the password you used when you backed up the encryption key, and then choose OK.
        The status of the restoration appears in Results.
      17. On the Report Manager URL page, use the hyperlink in URL to launch the Report Manager site.
        The report manager site appears.
      18. Close Reporting Services Configuration Manager and continue with step 3 of the TFS upgrade wizard.
  3. Type the name of the SQL Server instance that hosts the data from an earlier version of Team Foundation Server, and choose List Available Databases.
    The wizard lists deployments of Team Foundation Server that you can upgrade. If multiple 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, and then choose Next.
  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 optionally choose Test.
  6. Under Authentication Method, choose NTLM or Negotiate (Kerberos), and then choose Next.
    • 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 that authentication fails, NTLM authentication is used.
  7. Select the Configure Reporting for use with Team Foundation Server check box to use reporting and then choose Next.

    1. Enter the name of the server that is running SQL Server Reporting Services in Reporting Services Instance and choose Populate URLs.
      The URLs for the report server and its management site appear in the drop-down lists for Report Server URL and Report Manager URL.
    2. Make sure the URLs that you want to use for Team Foundation Server appear in the drop-down lists and then choose Next.
    3. Type the name of the server that is running the Database Engine and Full-Text Search to host the warehouse database, and then choose List Available Databases.
      The wizard lists available warehouse databases that you can upgrade. Choose the database that you want to upgrade, and then choose Next.
      You can choose Test to test the connection to SQL Server.
    4. Enter the name of the server that is running SQL Server Analysis Services in SQL Analysis Services Instance and choose Next.
      To test the connection to SQL Server, you can optionally choose Test.
    5. 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 in step 5 and you want to use a different account in this step, you must select the Use a different account than the Team Foundation Server service account for the Reporting Services report reader account check box.
      You can choose Test to test the user account and password combination.
  8. Select the Configure SharePoint for use with Team Foundation Server check box to configure SharePoint Products and choose Next.
  9. On the SharePoint Products Settings page, perform one of the following steps:
    • Choose 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 have the new TFS extensions for SharePoint installed and configured. If your old portal is on the server you are upgrading, the new extensions are configured automatically.
    • Choose Use an existing server farm for SharePoint, enter the URL for the SharePoint web application and the SharePoint Administration site, and then choose Next. To test the connection to each of these URLs, you can choose Test.
      You typically use this option to migrate to a new portal, which must contain your migrated data for SharePoint Products.
  10. On the Review page, review your settings, and choose Next.
    The wizard validates your configuration.
  11. Choose Configure.
    The wizard applies configuration settings.
  12. Choose Next.
    Your data is upgraded; Progress reports appear and show the status of each component.
  13. Choose Next.
  14. Read the final summary screen, and then choose Close twice; once in the wizard and then again in the configuration tool.
    noteNote: If the upgrade fails, see the detailed log files by choosing Click here to open a complete log on the summary screen. After you resolve any outstanding issues that are identified in the log file, you can resume the upgrade by using the Team Foundation Administration Console. On the Status tab in Team Project Collections, choose Create Collection, and then choose Rerun job.

Update the URL for TFS

If you used the advanced upgrade path, you moved TFS to new hardware and now you must update the server URL on the TFS application tier and in the TFS extensions for SharePoint. If you used the standard or basic upgrade paths, you can ignore both of these procedures.

Update the URL for TFS on the TFS application tier
  1. 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 choose OK.
Update the URL for TFS application tier in the TFS Extensions for SharePoint
  1. On the server running SharePoint, open the administration console for Team Foundation Server.
  2. In the navigation bar, choose Extensions for SharePoint Products, select the SharePoint Web Application and then click Modify access.
    The Change URLs window opens.
  3. In URL for Team Foundation Server, type the URL for the new application-tier server, and then choose OK..

Next Step: Set up a new build machine

After you upgrade the application tier, you may want to install the new build service. You can’t use TFS 2010 build service with Team Foundation Server 2012, but you can install the new build service side-by-side on the same server as the TFS 2010 build service.

6 thoughts on “Run the TFS Upgrade Wizard

  1. Great blog but when I run the upgrade wizard with TFS 2012 update 2, I don’t see the Database Restore tool available. Any advice?
    I am thinking about restoring the database directly on my new TFS server manually to get going.

  2. Hey, Brian. This page is for an early beta version of the TFS 2012. You want the new version of this page. It’s very similar, but some of the UI has changed. Go here: https://elhajj.wordpress.com/run-the-tfs-upgrade-wizard-rtm/

    Or better yet, check out the official MSDN versions of all these pages: http://msdn.microsoft.com/en-us/library/dd631898.aspx

    I developed this guide here on the blog during the TFS beta last year, but now these pages have a home on MSDN. Good luck

  3. i think that make a mistake, when aply update 3 tfs2012 start the wizard and configure the sharepoint name to other server (its correct is in other srver) but when finish the wizard upgrade, try to start the sharepoint extension wizard and this try to create a shareopint in my tfs app

    i think that my mistake was not install the sharepoint extension before the upgrade, so how could i solve that

  4. First, use this page for the reasons mentioned earlier: https://elhajj.wordpress.com/run-the-tfs-upgrade-wizard-rtm/

    You should run the extensions configuration wizard on the server that is running SharePoint. It sounds like you ran the extensions wizard on a server that didn’t have SharePoint installed (only TFS), but SharePoint is some where else in the TFS topology?

  5. hi
    i tried to explain alll steps
    i´ve 3 server 1 for app, tier,1 for data tier and 1 for sharepoint
    when i installed the update in app, set the sharepoint server in the wizard settings, im sure of that, take pictures of all windows.
    when wizard finish show all success but see a warning that tell me about sharepoint extensions

    “tf400414 sharepoint templates were not uploaded because the retained sharepintsettings point to a remote machine. Ensure sharepoint extension are installed on the remote machine.”

    my mistake, i dont have installed the extensions in sharepoint server.
    after that install sharepoint extensions in sharepoint server, all was succeded

    but when back to app tier to run wizard for sharepoint extension tell me that i tried to install sharepoint in my app tier, that is false,
    so i need to set this correct, viewing the log tell me that tried to install in my app tier so i never set that

    testing this issue, all is wrking fine, reports, source control, builds, shareponit, sharpeoint dash, create new proyect, all is workking fine

    only i need to “fix” that

    any idea please, thanks

  6. I think you’ve got it set up correctly. You can only run the SharePoint extensions wizard on the server that is running SharePoint, but it sounds like you already did that, so you’re good. I think the TFS admin console is a little confusing sometimes because it shows nodes that don’t always need to be configured in every place where TFS is installed. Your setup sounds like it’s all in good working order. Hooray!

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s