Joe Sango's Blog

Wednesday, September 21, 2005

VSTS Beta 2 Installation Redux.

With TFS beta 3 a sniff away now, I thought I would give a quick recap and offer a few hints for a successful beta 2 installation procedure.
I recently deployed another fresh install of TFS beta 2, Sql Server 2005 and VS 2005 Team Suite beta 2 over a duel server config (instead of the popular single machine deployment). Some folk are still having a bit of trouble here and there with their installs and they might come across similar problems with beta 3 so what a good time to share!

First and foremost, go and grab the install guide (if you haven't already got it :P).
Walkthroughs for both single and duel machine installs are covered. It’s a good, straight forward guide so follow it close.

This is the specific config I used with relatively no headaches.

2 clean vpc’s both with Windows 2003 Server SP1 with latest security updates installed.

Data Tier

  • DNS (Domain Controller)
  • Active Directory
  • IIS 6
  • SQL Server 2005
  • TFS (Data Tier Only)

App Tier and Client Tier

  • IIS 6
  • WSS 2.0 SP1
  • TFS (App Tier Only)
  • Word 2003
  • Excel 2003
  • Project Pro 2003
  • Team Suite Beta 2

Now, as you may or may not have read around the VSTS community blogs and forums, installing the DC and Active Directory first on the Data Tier before installing IIS, will save you a great deal of certain heart ache down the track. So install the AD/DNS server role BEFORE the App server role!!
Another “gotchya” area seems to be the setup of domain user account’s required for TFS. Specifically the setup account (domain\TFSSETUP) used to install TFS. Make sure that it's part of the domain admin group in AD and the admin group locally on both tiers.
A lot of setup errors also come from SQL Reporting Services issues so be sure to check that out.
That’s the data tier.

Now, first thing you should do when you start the app/client tier is add it to the domain you created and check you have connectivity between the boxes. If you copy over VPC images to create separate machines, be wary of the fact that both machines will have the same unique ID (SID) and will not talk to each other. Further explanation and fix here and another here.

The other main thing to watch out for when installing the rest of the app tier is when WSS 2.0 is installed, you have to exclude SQL Server Reporting Services from WSS management. It mentions this in the walkthrough single server deployment but not the duel server deployment section. I initially hadn’t excluded them so consequently, I was getting errors when trying to create new team projects and accessing the reports after installation was complete. Using the STSADM.EXE tool on the app tier for exclusion rectified this.
From the install guide:
STSADM.EXE -o addpath -url http://localhost/Reports -type exclusion
STSADM.EXE -o addpath -url http://localhost/ReportServer -type exclusion

All that’s left is the client tier and following the install guide for this makes it dead easy.
Hopefully with a bit of luck, you will have VSTS running smoothly without any major dramas and you will be well on your way to collaboration! Hey, I’m an optimist! ;P

If anyone is having any other significant problems during an install, feel free to drop me a line and I will help out as much as I can. Same goes for when Beta 3 lands!

Good luck all! :)

0 Comments:

Post a Comment

<< Home