{"id":38,"date":"2013-04-07T19:35:32","date_gmt":"2013-04-07T18:35:32","guid":{"rendered":"http:\/\/www.vosseburcht.com\/?p=38"},"modified":"2013-04-07T19:35:32","modified_gmt":"2013-04-07T18:35:32","slug":"team-foundation-server-2012-update-2-installation","status":"publish","type":"post","link":"https:\/\/vosseburchttechblog.azurewebsites.net\/index.php\/2013\/04\/07\/team-foundation-server-2012-update-2-installation\/","title":{"rendered":"Team Foundation Server 2012 Update #2 installation"},"content":{"rendered":"

I decided to upgrade our production instance of Team Foundation Server 2012 with Update #2 fairly fast after its release since we are starting a new sprint on monday and we have been waiting for some of the new features.<\/p>\n

I had done some research beforehand, and Update #1 installation went without any problems whatsoever so I felt fairly confident that it would be quite easy this time around as well. Ofcourse I checked if all my automatic back-ups had run, and that was the case.<\/p>\n

I started the installation and file copied fine, but then\u00a0I started the upgrade wizard and was greeted by the message described in the following connect bug report: http:\/\/connect.microsoft.com\/VisualStudio\/feedback\/details\/780985<\/a><\/p>\n

Luckily I had my documentation in order and could use the work around no problem. But no “Next, next, next” installation as promised. Also this bug was reported\u00a0in CTP #4 and didn’t get fixed for the RTM…. BAD MICROSOFT<\/p>\n

So before you upgrade, make sure you write down the settings you need for the upgrade procedure:<\/p>\n

– SQL server name
\n– Analysis server name
\n– Reporting server name
\n– Reporting server accounts<\/p>\n","protected":false},"excerpt":{"rendered":"

I decided to upgrade our production instance of Team Foundation Server 2012 with Update #2 fairly fast after its release since we are starting a new sprint on monday and we have been waiting for some of the new features. I had done some research beforehand, and Update #1 installation went without any problems whatsoever […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[7],"tags":[20],"_links":{"self":[{"href":"https:\/\/vosseburchttechblog.azurewebsites.net\/index.php\/wp-json\/wp\/v2\/posts\/38"}],"collection":[{"href":"https:\/\/vosseburchttechblog.azurewebsites.net\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/vosseburchttechblog.azurewebsites.net\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/vosseburchttechblog.azurewebsites.net\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/vosseburchttechblog.azurewebsites.net\/index.php\/wp-json\/wp\/v2\/comments?post=38"}],"version-history":[{"count":0,"href":"https:\/\/vosseburchttechblog.azurewebsites.net\/index.php\/wp-json\/wp\/v2\/posts\/38\/revisions"}],"wp:attachment":[{"href":"https:\/\/vosseburchttechblog.azurewebsites.net\/index.php\/wp-json\/wp\/v2\/media?parent=38"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/vosseburchttechblog.azurewebsites.net\/index.php\/wp-json\/wp\/v2\/categories?post=38"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/vosseburchttechblog.azurewebsites.net\/index.php\/wp-json\/wp\/v2\/tags?post=38"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}