Thank you for being patient. If you’ve followed my blog, you’ve seen that we’ve struggled a bit with some issues we introduced in our initial Update 1 release. A few weeks ago, we released a patch and quickly pulled it back as we found some people with install issues. Stung with humiliation, we have spent the last few weeks working hard to make sure we had a good patch that would really work for people. We’ve learned a lot from the process – including that our patching infrastructure that we build in TFS 2012 was not as robust as we thought it was. We are rolling all of these learnings into Update 2 and we expect/hope it will be a much smoother release.
You can download the final Update 1 patch here: http://www.microsoft.com/en-us/download/details.aspx?id=36392
The KB article is here: http://support.microsoft.com/kb/2803625
Please read the installation instructions in the KB article carefully. In our testing, we have found a few potholes that you need to avoid – locked DLLs, etc. Fixing these things were beyond the risk profile we could put into the patch and will be addressed in Update 2. None of the issue lead to dead-ends. If you do get hit by one of them (and at this point we’ve had MANY people both internally and externally successfully install the patch) there are ways to recover.
You must install Update 1 before you install this patch. There’s nothing that will happen installing Update 1 – even if you happen to be unlucky and hit the worst bugs, that this patch won’t correct. The KB article also includes a list of all of the issues that this cumulative update addresses.
Last thing, please don’t give me a hard time about the name Yes, I know it’s confusing, long, and any other adjective that you care to add on. It’s Cumulative Update 1 for Team Foundation Server 2012 Update 1. We’re gradually moving away from the Update # nomenclature for the major updates. I believe Update 2 will be called TFS 2012.2. And then any patches we have to provide on that, god forbid, would be Cumulative Update 1 for Team Foundation Server 2012.2. I think that would be a little less confusing. Yes, it might be even better if it were 2012.2.1 but I celebrate the small victories some days
As always, please let us know if you have any issues or feedback. With this, I think Update 1 has been put to bed and we are focusing on putting the finishing touches on Update 2 and having a better upgrade experience for everyone.
Thank you for your patience and I apologize profusely for any inconvenience,