Sunday, December 2, 2007

Update your old Team Project portals to use the new WSS 3.0 look and feel

I am by no mean an expert on Windows Sharepoint Services, but never the less we wanted to upgrade to WSS3.0 when we switched to using TFS 2008 and this proved to have some quirks that needed some sorting out.

After you have upgraded you TFS 2005 installation you need to upgrade the WSS 2.0 installation manually (this is not part of an upgrade). To do this you can read the following post, it refers to the Beta version of TFS 2008 but the procedure is the same.

You'll need the prescan tool to perform the upgrade as well. You can find more details about this in the documentation section Upgrading SharePoint Products and Technologies for Team Foundation Server

Once you have upgraded your sharepoint installation you will notice that the old projects doen't quite look as slick as any new project portals you create...


As you can see below the new sites created have alot of new navigational features that will make your users life easier such as the sites section on the quicklaunch and the top bar (the tabs) is handled more correctly and it has a slicker look (atleast in my opinion)...


To get around this you need to do the following steps (this is a solution that works for companies that have a not to large number of Team Project portals since it involves some manual steps):

Step 1: Navigate to your portals site settings and then from the look and feel menu select the option Reset to site definition (as shown in the picture):


make sure that you reset all the pages in your site


This will make the site look like a newely created project portal, unfourtunately it will also break a few things that you'll need to fix manually.


As you can see the Process Guidance link and the Reports link have dissapeared. Also the Team System logo on the top of the page has vanished (this I have no clue on how to fix at the moment).

Step 2: Navigate to the site settings of your site and under the look and feel section select the Top Link Bar and remove all links that are not subsites (Home, Documents and Lists, Create, Site Settings and Help).


Step 3: Navigate to the site settings of your site and under the look and feel section select the Quick Launch and remove all none wanted links (typically Pictures, Lists, Discussions and Surveys).


Step 4: Recreate the Process Guidance section in the Quick Launch sidebar

/sites/[YOURSITE]/Process%20Guidance/ProcessGuidance.html


Step 5: Recreate the Reports section in the Quick Launch sidebar
/sites/[YOURSITE]/_layouts/tfsredirect.aspx?IsReport=0


Step 6: Then add the links to the reports you had previously, for example to add the Bug Rates report.
/sites/[YOURSITE]/_layouts/tfsredirect.aspx?IsReport=1&ReportName=Bug+Rates&ShowToolbar=1


That is it, please comment if there are better ways todo this I'd love to get some pointer on how to do this easier (I guess you could do it by scripting?).

Finally if you have a bunch of highly customized templates that you are using you can find more information about how to covert them to WSS 3.0 in the Upgrade Toolkit for Windows SharePoint Services Sites and Templates Guide which was pointed out to me by the nice folks at Microsoft.

3 comments:

  1. Great help!

    How could one do this for 100+ projects ?

    Can't find anything about converting EXISTING TFS project portals that were created using WSS 2.0 style templates to the WSS 3.0 style for a large number of projects.

    Thanks
    J

    ReplyDelete
  2. Great article!

    For the record, I found an MSDN article which is great for guiding you through the upgrade process from WSS 2.0 to 3.0, and (I think) replaces Sudhir Hasbe's blog entry:

    http://msdn.microsoft.com/en-us/library/cc507614.aspx

    Stuart

    ReplyDelete
  3. Sorry for not answering until now, I have been preparing for going on parternity leave from work. We recently did our conversions by hand but we did not have that many. I think you should be able to do this in an more automated fashion creating a program utilizing the sharepoint object model but I am in no way certain. Sorry for not being able to help more.

    Peter

    ReplyDelete