VSTS Rangers Projects – Virtualizing the Deployment of VSTS 2010: Query => Which image flavours are “crucial” and which are “would be nice”?

This post invites you for input on a number of possible image scenarios we are considering as part of the guidance for the VSTS Rangers Virtualizing the Deployment of VSTS 2010 project, which is listed as one of the VSTS Rangers initiatives mentioned in the index post here.31568_SMJPG_174721981657484_thumb[3] We would appreciate your candid input, either by adding a comment to this blog post, or by contacting me directly.


The diagram shows 7 hypothetical flavours of virtualised environments for Team Foundation Server (TFS) and Visual Studio Team System (VSTS) 2010, which can be summarised as follows:

  1. Base image, with the latest version of TFS) pre-requisites, including SQL Server, Windows SharePoint Services (WSS) and operating system configuration.
  2. Based on flavour 1, this image additionally contains TFS.
  3. Based on flavour 2, this image additionally contains VSTS.
  4. Based on flavour 3, this image additionally contains the TFS Load Agent.
  5. Flavours 5-7 are in essence the same as 2-4, but using MOSS.

When we ask the questions, forget about practicality and licensing, instead focus on what would be most beneficial and a value-add to “you”, in “your” environment.

So what are the questions?

  1. Which flavours do your regards as crucial?
  2. Which flavours do you regard as useful?
  3. Which flavours, if any, are we missing?

Thanking you for your candid feedback!

Comments (2)

  1. EH: I would go for the MOSS installation, because of the Excel services. When installing an AT I do not want a VS or Load on the machine to keep things isolated

  2. Fredo says:

    Hi Willy,

    I’d prefer Flavour 2 as we can continue from there on our own as necessary.

    Appreciate all your effeorts 🙂

Skip to main content