Bringing you news, technical articles, and other useful content about Visual Studio ALM and Team Foundation Server
More videos »
Given the new, faster release cadence of updates for TFS 2012, there has been great demand for improvements to the upgrade process; namely, to minimize any manual steps it requires of the user. So in Update 2 we have done work to automatically preserve a deployment’s application tier settings for in-place upgrades. Anyone upgrading to Update 2 from a previous version of TFS 2012 will see their settings persisted right away; those upgrading from TFS 2010 will not immediately benefit from this feature in Update 2 but can expect us to start preserving their settings in all future in-place upgrades, even between major releases.
It means that when you install Update 2 and launch the upgrade wizard, you should see all your old settings pre-populated there. With the exception of entering account passwords, you can expect to be able to click Next-->Next-->Next all the way through to completion (however, you’re not off the hook for verifying what we’ve populated!). It also means that we will now persist any SSL bindings and custom ports you had configured for TFS and will do our best to keep changes you made to the AT’s web.config file.
Before you run your in-place upgrade, you should know these 3 things.
We hope these improvements make the upgrade experience much better for everyone. Since the updates are now one of the main ways we service TFS, this is a feature we hope to continue refining in the future. If you notice any strange behavior or settings we’ve missed, we’d like to hear about it. Comment below or send mails to TFCARE at Microsoft dot com.
Thank you guys! This really really really improves the install experience. This was my number 1 ask, having to enter the service account credentials & settings every time was a pain.
Ah, good old Next -> Next -> Next. :)
Will we have to re-enter the build\test service accounts for the build controller and test controllers when we upgrade to Update 2?
@Scott - Yes you will. We aren't persisting build or test settings yet, tt's on our backlog for our future releases. But even then if there is a password associated with these accounts the user would need to enter that (for security reasons).
I installed Update 2 CTP 4 and now I am unable to start the build service/controller/agent which were working before the upgrade. I documented the issue here... social.msdn.microsoft.com/.../4e4f3b0c-b41f-4ce7-86be-c17c2b19b5f5
can you take a look and let me know if this is a know issue or where I can go to get assistance with this issue.
Hi Steven - I've forwarded the link to your Forums post to the Build leads. They should be able to help you get that working again.
Actually, when I want to upgrade my TFS SharePoint Extensions from Update1.Patch2 to Update2, on the dedicated sharepoint servers. I got only this:
TF400638 : Team Foundation Server SharePoint Extensions has been detected. You cannot install Team Foundation Server while Team Foundation Server SharePoint Extensions is installed.
Okay I see. I have to upgrade that extension separately lol.
@Allen, in your SharePoint machine if you have TFS SharePoint Extensions 2012 RTM or 2012 Update 1 you will see that message if you are using the TFS Server 2012 Update 2 setup. You should use the TFS SharePoint Extensions 2012 Update 2 setup.