Microsoft's Team Foundation Server Deployment Topology

Rob Caron — Tue, 22 Aug 2006 19:35:29 GMT

See Brian Harry's blog to understand the scope of our Team Foundation Server deployment. The image on...

Team Foundation Server Use at Microsoft

.net DEvHammer — Tue, 22 Aug 2006 19:59:34 GMT

bharry talks about how we use Team Foundation Server at Microsoft, and even provides a nice pictorial...

TFS Internal Dogfooding

Ken's Place — Tue, 22 Aug 2006 23:36:41 GMT

Brian Harry blogs about our current TFS Dogfood topology at Microsoft.&nbsp;
"Given how much I talk&nbsp;about...

MSGuayaquil — Wed, 23 Aug 2006 10:54:58 GMT

Microsoft's Team Foundation Server Deployment Topology

寝ても覚めても.NET（？） — Wed, 23 Aug 2006 11:01:32 GMT

bharry's WebLog　からMicrosoftがTFSのDogfoodを行ったときのサーバー構成などに関する覚え書き？に近いもののようです。Microsoft's Team Foundation...

re: Microsoft's Team Foundation Server Deployment Topology

bharry — Thu, 24 Aug 2006 15:31:25 GMT

A couple people have noticed that some of our instance configurations have 3 servers in the little box. They have both the AT and DT and another server - for example tkbgitvstfas01.

They further observe that none of our public documentation describes any scenario where by this can be done. Good observations :)

Those "extra" servers on the diagrams are SQL2005 Analysis Services Servers. Basically, they are the cube process portion of the TFS data warehouse. For a couple of our largest instances, we have off-loaded this work onto a third server to reduce the impact of reporting on the operational stores.

This configuration is NOT supported in V1. We made a couple of fixes in the coming TFS SP1 that enable this. Once TFS SP1 ships, we'll produce a Knowledge Base article that explains how to do this.

A word of warning though - it still won't be a configuration for the faint of heart. We don't have tools to automatically set it up and it requires openning up SQL Server Management Studio and modifying some data. I would only recommend this configuration for people who have servers with VERY high levels of data/load on them.

In a future version we will make this and other topology configurations more main stream.

Brian

Martin's got a confession

Jeff Beehler's Blog — Fri, 12 Jan 2007 16:22:34 GMT

I'm not sure if size matters, but if it does, Martin's laying claim to the World's Smallest TFS as compared

¿Cómo Estructuró Microsoft su Deployment Interno de Team Foundation Server?

Julio Casal — Sat, 05 May 2007 17:19:29 GMT

Ok, Ok, toda empresa de desarrollo seria debería ya estar al menos pensando en implementar Team Foundation

Hello

Grant Holliday's blog — Wed, 18 Jun 2008 12:18:21 GMT

You might remember me from such blogs as OzGrant.com , mailing lists such as OzTFS.com , the Team System

Team Foundation Server Proxy blog

Grant Holliday's blog — Fri, 27 Jun 2008 04:41:19 GMT

Before I joined MSFT I hadn’t had any exposure to Team Foundation Server Proxy. As you know from Brian’s

re: Microsoft's Team Foundation Server Deployment Topology

Edmund — Wed, 20 May 2009 09:39:48 GMT

Hi,

Can you explain a little about the domains you have to support these regions. For example is 001-DevDiv a child domain of REDMOND.CORP, what about Pre-Production environment, is this a domain?

That would be most helpful.

Edmund

re: Microsoft's Team Foundation Server Deployment Topology

grantholliday — Wed, 20 May 2009 17:55:02 GMT

@Edmund

The domain is corp.microsoft.com and redmond, fareast, europe, northamerica are all child domains.

The 001-DevDiv is just a label, all it's saying is that 'instance #1 is for DevDiv'

The Pre-production environment is also on the redmond domain, it is not a separate domain.

Grant

re: Microsoft's Team Foundation Server Deployment Topology

Edmund — Wed, 20 May 2009 20:32:08 GMT

Where are your production servers? Are they in a different domain. I am wondering how you would prevent a developer from affecting production (intentionally or by mistake).

Is this whole domain just for development purposes?

Thanks again.

Edmund