Team Foundation Server 2013 Update 3 (aka TFS 2013.3) was released on August 4th, 2014. In 4ward we upgraded TFS on all the major and minor versions from 2010 to 2013, and this week we updated our TFS 2013.2 architecture to TFS 2013.3.
So in this post I’ll show you how to do an in-place upgrade of Team Foundation Server 2013 Update 3.
For a Single-Server TFS 2013 topology like mine it was an easy and fast enough process. The Upgrade wizard restore the previous configuration settings, so the only things you have to insert are the passwords for the service accounts. If you want to see the previous posts on TFS upgrade, you can go here:
- Upgrading TFS 2010 to 11 Beta
- Upgrading TFS 11 Beta to TFS 2012 RC (Release Candidate)
- Upgrading TFS 2012 RC to RTM (Release to Manufacturing)
- Upgrading TFS 2012 to 2012.1 (Update 1)
- Upgrading TFS 2012.1 to 2012.2 (Update 2)
- Upgrading TFS 2012.2 to 2012.3 (Update 3)
- Upgrading TFS 2012.3 to 2013 (Migration upgrade to new hardware)
- Upgrading TFS 2013 to TFS 2013 Update 2 (2013.2)
Before upgrading, you have to check the System Requirements for Team Foundation Server.
Preparing for Installation
If you have a MSDN Subscription, you can download, under the “Visual Studio” category, the Team Foundation Server 2013 Update 3 ISO image (en_visual_studio_team_foundation_server_2013_with_update_3_x86_x64_dvd_4900391.iso) or the Web Installer (en_visual_studio_team_foundation_server_2013_with_update_3_x86_x64_web_installer_4900363.exe). Before to go on, my recommendation is to perform the following tasks:
- Run a Complete Health Check with the Best Practice Analyzer Tool for Team Foundation Server in order to prevent or troubleshoot problems in the actual TFS deployment;
- Write down the actual TFS configuration (you can take some screenshots on TFS Administration Console) and make sure to have all the service accounts credentials for TFS;
- Send an email to warning about the upgrading process because the system will be offline while the Upgrade is applied!
- Download all the Windows Updates and Microsoft Updates and reboot the system if necessary;
- Stop all the services and application pools:
- Stop the TFS services like TfsJobAgent, TFSBuildServiceHost, etc. by using the “TFSServiceControl quiesce” command (you can find it under “C:\Program Files\Microsoft Team Foundation Server 12.0\Tools”);
- Double-check that TFS isn’t reachable from Visual Studio and Web Access.
- Perform a full backup for each database used by TFS. There are two way to do this operation:
- By using the Database BackUp Tool when the Upgrade wizard asks to do it (recommended);
- By using SQL Server Management Studio (you must also synchronize the backups to the same point in time, see how to manually back up Team Foundation Server).
- Are you using a virtual machine? If so, take a snapshot so you can always rollback the system if something goes wrong.
Install TFS 2013 Update 3
Run the Visual Studio Team Foundation Server 2013 Update 3 installation (tfs_server.exe): Accept the licence terms and click on Install Now: it would take about 15 minutes to complete the installation (depending the system performance). It could be necessary to restart the machine to continue with the installation: If you are doing an in-place upgrade, the Upgrade Wizard opens automatically at the end of the installation process: Make sure the SQL Server Instance is ok. ATTENTION: The schema of your database will be updated to the new format and the operation is not reversible without a backup! So you can take a full backup now by clicking the link to the Database Backup Tool: Select the databases to backup and the destination folder and click on Backup Now. The process was very quick for me (3 minutes to backup about 25 Gb). Now you have a current full backup of TFS databases: you can close the tool and go straight Insert the password for the TFS service account and click on Test link to validate the credentials: Because the Application Tier caches a lot of resources on a local folder (usually under C:\Program Files\Microsoft Team Foundation Server 12.0\Application Tier\Web Services\_tfs_data), you can configure a different path for this directory and make sure you have enough disk space. Keep the flag to configure Reporting for TFS: Most of these screenshot are just “click next, next, next” because I am doing an in-place upgrade. So check if everything is ok, like the Reporting Services Instance, the Report Server URL and the Report Manager URL. Insert the Password for the report reader account: My deployment use a separate server for SharePoint, and I don’t want to modify the current settings, so go on… Take a look at the Review page to check if everything is ok: The Readiness Check validates that everything is available: I have a yellow warning on the disk space on file cache location: the disk would have at least 50GB of available free space. Anyway you can skip it: if needed, you can always open the TFS Administration Console and change the File Cache Folder under Application Tier settings. After Configuration, you have to start the Project Collection upgrade: The process takes only about 2 minutes to upgrade our Project Collections: At the end you can close the Upgrade Wizard and the Configuration Center: From the TFS Administration Console you can see that the version number is updated (12.0.30723.0): Take a few minutes to check that everything works correctly:
- Open Visual Studio and connect to TFS by using the Team Explorer window;
- Perform a Get Latest;
- Modify a test file and check in;
- Queue a new build and verify if it has successfully run;
- Check the Reporting Services;
- Open the TFS Web Access:
Final tasks: don’t miss to update the Build Server, the SharePoint Extensions on the remote machine and the Agents for Visual Studio (Test Controllers and Test Agents). Now you’re ready to go! Do you need a support to adopt Visual Studio ALM? We can help you! Contact us: email@example.com