One major scenario for most of our customers who are using Visual Studio 2005 Team Foundation Server is moving to Orcas and leveraging the new features around WSS3.0. The upgrade path to this is very simple and straight forward. This post is focused on performing in-place upgrade of WSS. That means you upgrade WSS2.0 to WSS3.0 on the TFS server itself.
As I mentioned in my last post related to Upgrade. We want you to make sure you have a working Whidbey before trying to upgrade to Orcas. We don't want you to change the configuration of the server.
The steps to upgrade are as follows.
Note: You can use TFSAdminUtil to update all the different URL's for WSS. Following is the syntax for updating all WSS related attributes in TFS.
Hope this post is helpful. Please let me know your experiences.
This topic is very similar to the previous topic( http://blogs.msdn.com/sudhir/archive/2007/05/31/upgrade-2005-with-wss2-0-to-orcas-wss3-0.aspx
We have put in a lot of effort on getting our Upgrade experience right. It is not perfect but I think
Hmmmn when we try to run the Orcas TFS installer it throws an error complaining that the schema is old and that the TFS 2005 is already installed. The install guide lists upgrading from a previous version as not supported and workarounds as NONE
The Upgrade is only supported in Beta2. I am sorry for the confusion. I had mentioned in it previous posts. I guess I should add it to this one too.
As I posted before I have been updating our TFS server to 2008 Beta2, today it was the WSS from 2.0 to
In most implementations of TFS we end up having tough discussions with infrastructure and questions such
At the company i work for, we are using Team Foundation Server 2005 for Workgroup Edition, since June
Upgrading Team Foundation Server 2005 to 2008 SP1