Search
Tuesday, December 02, 2008 ..:: Home ::.. Register  Login
Blog roll

Topic search

UsersOnline
Membership Membership:
Latest New User Latest: bokonon42
New Today New Today: 0
New Yesterday New Yesterday: 0
User Count Overall: 118

People Online People Online:
Visitors Visitors: 0
Members Members: 0
Total Total: 0

Online Now Online Now:

Blogs
Jul 28

Written by: Justin James
7/28/2008 11:53 PM

Last week I wrapped up the installation of our new Team Foundation Server 2008 setup. I had previously installed it in a single-server archtecture, but we decided to go to the dual-server configuration. Why? Because I am trying to consolidate everything by purpose into different VMs on our new app server. This means that I have 1 VM for SQL server, another one for SharePoint and other collaborative applications, and so on. When I went to install TFS into this, it was an incredible headache.

For one thing, TFS requires 32 bit Windows; since this is TFS 2008, and because so many of the 2007 and 2008 Microsoft server products (Exchange, for example) require 64 bit Windows, I think that this is going to be a real problem, especially for small shops. So now I have a 32 bit Windows 2008 VM just for TFS.

The installation took forever. I went through all of the checklists, but there was always something wrong. Oddly enough, the #1 offender was SQL Server Reporting Services. The TFS installer is supposed to configure the unconfigured SSRS install, but the default install in broken. I had to delete the encryption keys (for whatever reason) to make it work, which could bite me in the rear down the road.

I then had further problems with installing the SharePoint extensions on my 64 bit SharePoint install. Apparently, the TFS disk doesn't ship with a 64 bit version of this, and the error message doesn't say anything about it, just throws a dumb, useless error message. Luckily, they made a 64 bit version a few months ago.

Over all, I must say that this install was one of the most miserable installations that I ahve ever done of a Microsoft product. I know that TFS is supposed to be "enterprise class", but many of their other "enterprise class" products are smooth sailing. I can't see what makes TFS so special that it can't be an easier installation. If Microsoft wants more shops to use it, they need to make it easy to deploy. No one can evaluate it in its current state, it requires too much work.

J.Ja

Tags:

4 comments so far...

The home server install was quite messy too

The home server install was quite messy too. That took like 10 reboots and bunch of scripts firing off.

There's a certain element inside Microsoft that seems to like these really complex procedures. I remember how crazy their Exchange disaster recovery procedure was which prompted me to write this alternate method of using disk images many years ago (http://articles.techrepublic.com.com/5100-10878_11-5054178.html).

By host on   7/29/2008 1:19 PM

Re: Misery: Team Foundation Server Dual-Server Install

Yeah, their products are getting more and more like "enterprise class software". While it is good that the feature sets are really beefing up, I always liked Microsoft products because they tended to be easier to deploy and maintain than their competitors. It seems like that has been lost. I am not sure why expanding the feature set should make installation a chore, but somehow it has. The seamless integration of the Microsoft stack is only a selling point if it is seamless, otherwise it is just another Oracle or SAP.

J.Ja

By jmjames on   7/29/2008 1:51 PM

Re: Misery: Team Foundation Server Dual-Server Install

It's getting to the point where they may just have to ship VM images. Of course, this requires improvements to AD so it's easier to change the configuration after-the-fact.

By Tom on   7/31/2008 8:29 PM

Re: Misery: Team Foundation Server Dual-Server Install

Tom -

I agree about that. If they are going to sell totally integrated items, they need to integrate *cleanly*. As it is, the TFS/SQL Server integration is so tight, that a TFS license includes a SQL Server Standard edition license (for use with TFS only), because you can't even use SQL Server Express or Workgroup edition. Frankly, I really like TFS, and in the great scheme of things, even a multi-day install is not the worst thing out there, but it *does* make it impossible to demo stuff.

I also agree 100% that they need to make the post-deployment AD configuration much easier. It is nearly impossible to move SharePoint, TFS, Exchange, and a number of other Microsoft server products without severe problems. Heck, if you set up your domain "dumb", it might take you years to break free of it, because AD is so locked in stone. I like AD for its total integration, but the lack of flexibility is a killer.

J.Ja

By jmjames on   7/31/2008 8:32 PM

Your name:
Title:
Comment:
Add Comment    Cancel  

Links

Blog_Archive

New_Blog
You must be logged in and have permission to create or edit a blog.

Search_Blog
Print  

Copyright 2008 by George Ou or Justin James   Terms Of Use  Privacy Statement
DotNetNuke® is copyright 2002-2008 by DotNetNuke Corporation