New:

Quiescing is shutting down the services needed. Here is a link to it: http://support.microsoft.com/kb/950893
"When you are performing Team Foundation Server system servicing, such as installing a service pack or hotfix, the installer disables access to the Team Foundation Server for the duration of the servicing. This is called "quiescing" the server. After completion of the servicing, the server is reenabled, or "unquiesced". "

Radio TFS has a podcast from 3 people who are very pro-TFS.

Check-in policies:
In episode 10, they talk about check-in policies. Comment and work items check in policy are two they feel are critical. First use the work items. It makes a check-in need to have a work item. My comment is everyone should have a personal work item if work items are required.

In TFS08 SP1 the ability to limit the set of work items based on other meta data. Such as user, bug level or feature selection will reduce the possible set of work items. This will reduce the ability to assign a check-in to ANY work item.

The in-ability to require the check-in policies is a big flaw. Since they are client-based, the server has to accept what the client sends? What can be done is the server can send an email based on the override. Also, one can isolate based on branching.

Teamprise:
It appears that the Teamprise's client will be a superior client. Based on it being Java-based cross platform tools.

Microsoft Team Foundation Server (TFS) is a collection of application servers. These servers interact with developers, testers and product managers. The key servers are team server itself, sharepoint and SQL Server. It is a very complicated and expensive product. Why bother when you can get the same set of tools in the open source community? Click to see one possible set of tools.

Team Foundation Server 2008 is the second version of the tool. The best post I have found relates to installing TFS. Is the TFS 2008 install a big joke on us?. If it can't be installed easily in a usable state, Microsoft's marketing department must be doing a wonderful job!

Power Tools:
One important optional piece is called the "power tools". Where to get the power tools: Same tool, different contents.

Visual Studio Team System 2008 Team Foundation Server Power Tools

or

Visual Studio Team System 2008 Team Foundation Server Power Tools - March 2008 Release

Team Foundation Installation Guide for Visual Studio Team System 2008

Team Foundation Administrator's Guide

The cost:

From: http://reddevnews.com/features/article.aspx?editorialsid=674

"The costs of some of the versions are going to hurt the smaller shops. They still have a need for source control, testing, etc., but the cost of these tools is too prohibitive for them. Bottom line, if you're a large Microsoft shop, then the tools are great. If you're a mixed tool and platform environment, then you'll need to look elsewhere for your tools. If you're a small shop, think carefully about nthe cost-benefit ratio of VS."
TFSC:
A paper about branching that looks a lot like ones I have seen before:
http://msdn.microsoft.com/en-us/library/aa730834(VS.80).aspx

Problems:
http://teaandbiscuits.org.uk/drupal/node/68
Discusses losing changes to source code.

http://codebetter.com/blogs/eric.wise/archive/2007/05/31/bye-bye-team-fo...
talks about losing code after 6 months. I also posted on there.