Since almost everyone wanted to upgrade TFS V1 to use WSS 3.0, Microsoft added two guides to MSDN in which they explain how to update. In this guide I'll explain how to update your Reporting Services to your WSS 3.0 site as well. This will give you the ability to completely shut down the old TFS Web Site. Only I can of emergency or an update you can restart it temporarily again.

To take advantage of one site instead of two you can configure SSRS on the WSS 3.0 site.

  1. Configure SSRS using the Reporting Services Configuration Manager. You can find this by clicking Start, pointing to All Programs, pointing to Microsoft SQL Server 2005 -> Configuration Tools, and clicking Reporting Services Configuration

  2. Create and Configure Virtual Directories
    The report server and Report Manager are ASP.NET applications accessed through URLs. Each URL includes a virtual directory that you specify in the Reporting Services Configuration tool.

    Select Report Server Virtual Directory and click New..

    • For Website Select SharePoint v3
    • For Virtual Directory leave the suggested name
    • Click Ok

      Select Reports Virtual Directory and click New..

    • For Website Select SharePoint v3
    • For Virtual Directory leave the suggested name
    • Click Ok
  3. Change the Web Service Identity
    Select ReportServer application Pool for both Virtual Web Servers

  4. Click Apply and OK
  5. Change the permissions of your SharePoint v3 Web site.
    e.g. C:InetpubwwwrootwssVirtualDirectories81
    NETWORK SERVICE Account(Read & Execute)
  6. To update the registry key for SQL Report Server
    • On the Team Foundation application-tier server, click Start, click Run, type regedit, and then click OK. Registry Editor opens.
    • In Registry Editor, expand HKEY_LOCAL_MACHINE, expand Software, expand Microsoft, expand Visual Studio, expand 8.0, expand Team Foundation, and then click ReportServer.
    • Right-click Key and then click Modify.
    • In the Edit String dialog box, in Value data, change the value to reflect the https address of your Team Foundation application-tier server, and then click OK. For example, if the name of your application-tier server is Contoso1, you would change the value of the data from:




    • Close Registry Editor.
  7. Modify the sample XML below, substituting the entries for [protocol], [WSS Server 3.0], [port] with those of the new WSS 3.0 instance. Typically protocol will refer to http or https, whereas the port number will be the port number you specified for the new Web application during previous steps.

                    <Url>[protocol]://[WSS Server 3.0]:[WSS 3.0 admin port]/ ReportServer/ReportService.asmx
                    <Name> BaseReportsUrl</Name>
                    <Url>[protocol]://[ WSS Server 3.0]:[port]/Reports</Url>

  8. Save your changes to the sample as SSRS_registration.xml making sure that the file can be accessed by the Team Foundation Server application tier computer.
  9. Open a Command Prompt window on the Team Foundation Server application tier computer and execute the following commands (substituting your Team Foundation Server data tier machine name for myDTserver in the TFSReg.exe command here):

    iisreset /stop

    cd “%programfiles% Microsoft Visual Studio 2005 Team Foundation ServerTools”

    TFSReg.exe SRSS_registration.xml myDTserver

    iisreset /start

  10. Confirm that the changes have been made successfully. To do this, follow these steps:

    Check that the service interface changes that you made through running TfsReg.exe are present in the resulting XML.

  11. Team Explorer cache. Team Explorer, which is the add-in within Visual Studio 2005 which provides integration with Team Foundation Server functionality, receives the WSS URL from Team Foundation Server. This value is cached with a default cache timeout of 7200 seconds (two hours). If you are performing this update with sufficient downtime before clients will begin connecting again, then no further action is required. However, if clients will need to connect to the team project portals before the cache time has expired, then you may wish to manually invalidate the cache. To do so, each client should close all open instances of Visual Studio 2005 then delete the following folder: ““%USERPROFILE%Local SettingsApplication DataMicrosoftTeam Foundation1.0”

Again you're just a few clicks a way for creating a single web site which contains WSS 3.0 and Reporting Services.



This blog describes how you can setup your Team Foundation Server environment using a FQDN. For a full explanation about what a FQDN is, you can read my previous post about Hosting Reporting Services on a fully qualified domain name (FQDN). Since TFS is based on Reporting Services, as well on WSS it's also advisable to read my last post about Hosting SharePoint on a fully qualified domain name (FQDN).

For this example I will modify the host file to use sharepoint.mikeglaser.com for SharePoint and Reporting Services and teamfoundation.mikeglaser.com for TFS as a FQDN. On Windows-based computers, this file can be found in the systemrootSystem32DriversEtc folder. Trough Microsoft Internet Information Services (IIS) you configure the sites, so their only accessible through sharepoint.mikeglaser.com and teamfoundation.mikeglaser.com. This can be done by changing the default identification and adding the FQDN as a host header value.

As you can see in the picture I'm using WSS V3 for TFS. How to setup a configuration like this, you can read on my blog in the Upgrade TFS V1 to WSS 3.0 Guide.

After configuring SharePoint and Reporting Services to use a FQDN it's now time to configure TFS. To use TFS with the newly created host header names, there are several steps to fulfill.

Step 1 Configure Team Foundation Server to use a FQDN SharePoint Server

Microsoft wrote an excellent article about setting up a Remote SharePoint Server. In my case it doesn't have to be a remote server, but just a server with a FQDN. Besides this I don't like TFSReg, it's to complex for such a simple job. Instead a hack my way in SQL Server directly. The table tbl_service_interface of the TfsIntegration database to be precise. I'll change all URL's to use sharepoint.mikeglaser.com instead of the name of mine server.

Warning: WSSAdminService is a separate Web Site and doesn't have to have the same FQDN as the SharePoint Web Site.

Step 2 Fix the Reporting Web parts and lists on the Team Foundation Server portal sites

TFS adds an aspx file (tfsredirect.aspx) to the layouts folder of WSS which can be found in %Program Files%Common FilesMicrosoft Sharedweb server extensions60TEMPLATELAYOUTS or %Program Files%Common FilesMicrosoft Sharedweb server extensions12TEMPLATELAYOUTS, depending on which version of WSS you're running. This file request the registry where the Report Server can be found. Open the registry and browse to HKEY_LOCAL_MACHINESOFTWAREMicrosoftVisualStudio8.0TeamFoundationReportServer hive. Change the content of 'key' to use your FQDN of Reporting Services.

Step 3 Modify web.config of Team Foundation Server

Before each services on TFS starts it check the web.config of the root website on which URL TFS is running. A strange way to build a config like this, because each services is running on the TFS web site. Either way open the web.config of TFS, which can be found in %Program Files%Microsoft Visual Studio 2005 Team Foundation ServerWeb Services. Change the TFSNameUrl key and use your FQDN (e.g. http://teamfoundation.mikeglaser.com:8080) instead.

Step 4 Clear Team Foundation client cache

Before opening Team Explorer, make sure you clean the cache of it. Else you can't connect to the new FQDN environment and red cross marks will appear in your Documents and Reports sections.

Open the local settings from the current user. Within the application data of Microsoft open the Team Foundation folder and clear the cache in 1.0 folder. To do so, just remove the cache folder or the folder beneath it.

Step 5 Open your Team Explorer and connect to the new Team Foundation Server

Add the new FQDN (e.g. teamfoundation.mikeglaser.com) to the list of servers and connect to your preferred team project. Make sure all sections are connecting to a new FQDN site.


As you can see again it's not that hard to use a FQDN with Team Foundation Server, but you gotta know how. As I hope to show you in my last couple of posts, it's easy and advisable to setup FDQN's for your environments. This way you can easily add lots of web site and applications on machine only. Besides you don't have to setup IIS environments all over the place.


Technorati tags: ,