Back in June, I wrote about the upgrade of the main Developer Division server to TFS 2012 RC. That post described both the scale of that server as well as the issues that we found in the process of upgrading it and the for the first week of running it (we found most all of the issues in the first week). Last month we upgraded that server to TFS 2012 RTM.

Now this past Friday, we upgraded it to the final CTP for TFS 2012 Update 1. While the CTP is not licensed for production use, we wanted to use this opportunity to find the issues that you only find in production on such a large server. We’ve been upgrading our smaller internal “dogfood” server called pioneer every three weeks with every CTP we’ve released, and of course we put the same update on tfspreview.com every three weeks. However, the developer division server scale is different with a few thousand users all working on the same project.

Just like we did with the 2012 RC, we found some issues. We are going to have these addressed for the final release of TFS Update 1, so you’ll be able to use it knowing that we have put it into production on our mission-critical server.

• Web.config settings aren’t being maintained (affected both build and version control cache directory)
• Circular group memberships are causing performance problems

Brian has listed the features in Visual Studio Update 1 and TFS Update 1.

Follow me on Twitter at twitter.com/tfsbuck