Just to name some issues:
- Prerequisites (or Things You Should Install Yourself Because The TFS Setup Team Was Too Lazy To Make The Process Smooth And Automatic)
- IIS
- SQL 2005
- + Some hotfixes
- .NET 2.0
- + Some hotfixes
- SharePoint Services
- Team Foundation Server
- Visual Studio Team Foundation Server Quiescence GDR
- Visual Studio 2005 SP1
- The setup requires some 3-4 users to be already defined on the domain (that is - you don't have the option to add these during the installation process).
- TFS includes a license for SQL 2005 Standard Edition. But nobody tells you where you you can find the required Product Key. So we're now on the phone with Microsoft to figure that out...
I can understand problems related to the conversion of existing source management systems to TFS (up to some extent). But I NEVER thought ANY software could be THAT cumbersome to install. We didn't even reach the point of converting the data, and frankly if the setup is so complicated, I shiver at thinking of the complications we will encounter at converting...
2 comments:
try this, might be of help
http://blogs.msdn.com/jmeier/archive/2007/01/28/vpc-with-vstf-single-server-deployment.aspx
alik
thanks, although we wanted a concrete installation, not on a virtual image. Anyway, we're through now.
btw, according to their roadmap (see: http://blogs.msdn.com/bharry/archive/2006/11/30/team-foundation-server-roadmap.aspx) they are planning some improvements in the setup experience.
Post a Comment