On Cloud Computing, Integration Technology, Mobility, RFID, ERP etc...
Sr, Program Manager at Microsoft and MBA from UNC Chapel Hill.My small world includes my beautiful wife Swati and our awesome twin boyz Arni and Abhi.
In my previous posts around TFS and Windows SharePoint Services I explained how you could use WSS3.0 or WSS2.0 with TFS. In many companies you already have a corporate SharePoint Farm. You may want to use that with TFS so you don't have to maintain 2 different sets of portals. This post tries to explain how you could achieve this.
There is a circular relationship between TFS, WSS and Reporting. What do I mean?
Sharing same SharePoint Farm for multiple TFS Instances:
To achieve this we require every TFS instance to have its own Managed path. You can create managed paths using the WSS admin site. As shown in the diagram below TFS_001 TFS Instance should have its unique managed path for e.g. TFS001. Similarly for TFS_002 you should have TFS002.
Following are steps you can use to setup this environment
Note: You can run this tool again for 2nd TFS server by running <TFSInstallDirectory>\tools\TFSWSSConfig
Note: This post is relevant only to Dual server configurations of TFS.
Many customers have asked me if TFS Setup account needs to be Administrator on TFS Data Tier. For Orcas the answer is "NO". Let me provide some details on this topic.
In VS 2005 we had a DT SKU that was installed on DT machine. Therefore you had to be administrator to install the DT SKU. Based on tons of feedback we got from our customers we removed that SKU in Orcas and now you just have 1 SKU or installer for both single server and dual server setup. The advantage is you do not need to be administrator to install TFS in dual server environment. You still need to be a SQL Administrator so we can create TFS databases.
Following are tasks we perform as TFS Setup on the Data Tier machine.
Hope this provides some more understanding around TFS Setup account.