Planning and Upgrade teams would appreciate your candid feedback!

The TFS Planning and DR Avoidance Guide and TFS Upgrade Guide teams are busy updating the relevant guides for the latest version of TFS 2012 and the upcoming TFS 2013. They would appreciate your candid feedback, either by adding a comment to this blog or by email, so that they can fine-tune the guides to be balanced between expectation and reality.

Question 1 – Which is your typical TFS deployment and why?


Question 2 – What Services are considered value-add and crucial in your TFS environments?


Thanks for your candid feedback!

Comments (9)
  1. Brian Baker says:

    1: Primary deployment scenario would be an all-in-one on premise server. Under consideration is using Team Foundation Service with some on-premise build servers (would love to have lab management in conjunction with TF Service as well!).

    2. Critical services are VC and WIT (including agile planning) with build followed closely behind. Reporting, deployment and collaboration aren't as critical.

  2. Rob Karatzas says:

    1. Primary deployment scenario would be an all-in-one on premise server.

    2. All are critical, with Reporting being less critical (could live without it for a week).

    Finally, the biggest expectation is that the upgrade work as planned or have the ability to roll-back on failure (which has not happened with us in the past).

  3. Dylan Smith says:

    (#2) Multi-Server "Scale Up"

    All of those features are crucial with the exception of Collaboration/SharePoint and Deployment (I'm assuming you mean the InRelease stuff which is too new to have a lot of traction yet).  Also you're missing TFS Lab which is also crucial to most of my teams.

  4. Matt Ring says:

    1: Multi-Server "Scale up & out" (App Tier farm, clustered Data Tier, Build Servers)

    2. Critical services are VC, WIT and Build.

    Additional Notes:

    – Curious about Collaboration w/ SharePoint – not enough useful information on this, IMO.

  5. Alfred D says:

    We use Project Server and Lab Management very heavily. Our automated tests with our test controllers an scvmm servers (multiple labs on multiple TPCs) are critical and we can only afford 8-10 hours of upgrade time. We have dozens of VMs and hundreds of UI tests with network isolated environments.

  6. binit says:

    individually nothing is crucial. but what make TFS crucial is collaborating or integrating all this under one platform/ product; i.e under TFS.

  7. Assaf L says:

    1.Option 2 – Scale Up

    2. Options 1, 2 and 4

  8. Roger says:

    Reporting is critical for us. We've written 20+ custom reports on TFS 2012, and having guidance on what's changed will be critical for us to understand what we need to do to make our reports work against TFS 2013.

  9. @Roger, I will pass your feedback to the Upgrade and the Reporting Guide teams.

Comments are closed.

Skip to main content