Over the weekend, we decided to take the plunge and upgrade the SSW TFS 2010 instance to the shiny new TFS 2012 release candidate.
Initially, there was some debate as to whether we should upgrade what is the busiest server in our environment. One call to Grant Holliday made all the difference and we quickly reached a consensus. The upgrade was going ahead and Damian Brady was the guy in the hot seat!
There are three main upgrade paths:
- Upgrade from a Basic or Express version of TFS
- Upgrade in place
- Upgrade and move to new hardware (recommended)
We chose option 3 for a few reasons. We used the opportunity to move to a SQL Server 2012 instance and change our hardware configuration a bit, but more importantly option 3 gave us the simplest rollback path; simply turn off the new server and bring the old one back up, then change any DNS settings back.
It was a very straightforward process (with a few coffee breaks):
- Before you start – getting the VMs ready
- Preparation steps – stopping the servers and backing up
- Installing and upgrading TFS 2012
- Configuring Reporting Services
The initial feedback from the test developers is extremely positive. They can’t wait to start using it!
I want to mention a couple of great blog posts. There was a series of blog posts from Tim Elhajj, and of course we could leverage off our Rules to Better TFS 2010 Migration and the related blog posts (first, second, third) from Martin Hinshelwood for ideas.
Well done to the TFS team, they’ve really done a great job in this version.
SSW may have a possible claim to fame here – we might be the first company to deploy TFS 2012 RC to live. I have not seen any blog posts about other companies migrating their live environment yet. I’m a TFS MVP and nobody on that list has posted about their migration yet. I’m expecting the punctilious Martin Hinshelwood to send us a nice scotch whisky!
For all the gory details and a step by step walkthrough, see Damian Brady’s blog post.