TFS 2008 Licensing - clearing some of the misty valleys

A colleague asked me whether is true, that TFS 2008 Workgroup edition now supports 20, instead of the 5 users. The answer to this one, and I checked with the TFS guys, is that the 5-user limit still applies ... no change in this area.

Let me summarise some of the common licensing questions we get/got and the answers as I understand them to be at this stage:

  1. Do we need a client access license to submit work items to TFS?
    • With TFS 2005, yes.
    • With TFS 2008, no. Licensing changes with 2008 allow an unlimited number of users to (1) create any work item, (2) query for work items they have created and (3) update work item they have created.
    • NOTE: The new "bug filing" clause only applies to Standard Edition and not to the Workgroup Edition.
  2. Do we need one or two TFS Server licenses when installing a dual server implementation?
    • Single Server deployment = 1 TFS Server license, one for the TFSATDT.
    • Dual Server deployment = 2 TFS Server licenses, one for the TFSAT and one for the TFSDT.
  3. Do we need any license when installing the TFS Proxy server?
    • Yes, you need a TFS Server license per TFS Proxy Server.
  4. When do I actually "not" need a client access license (CAL)?
    • Looking at the EULA ... in other words from the horses mouth ... and we quote:
      • You do not need CALs for any of your servers licensed to run instances of the server software.
      • You do not need CALs for up to two devices or users to access your instances of the server software only to administer those instances.
      • You do not need a CAL to access work item tracking functionality to create new work items, or view and update work items you opened.
      • Your CALs permit access to your instances of earlier versions, but not later versions, of the server software. 
      • ... end quote.
  5. What is an external connector license and when should I consider one?
    • Again extracting from license agreements:
      • "Each external connector license assigned to a server permits any number of external users to access instances of the server software on that server.  You do not need CALs for those users".
      • "External users" means users that are not either (i) your or your affiliates' employees, or (ii) your or your affiliates' onsite contractors or agents."
  6. What licensing implications do we have on a standalone TFS Build server?

These are, however, my views and I urge you to digest the TFS licensing whitepaper and to contact your local Microsoft licensing representative to double-check.

Share this post: email it! | bookmark it! | digg it! | reddit! | kick it! | live it!
Published Wednesday, March 05, 2008 9:17 AM by willy
Filed under:

Comments

# re: TFS 2008 Licensing - clearing some of the misty valleys

Wednesday, March 05, 2008 10:02 AM by cjlotz

I wish MS would create some sample team setups to illustrate the above licensing model better. What about illustrating the cost for a typical small company/medium/large company where for every company you include x amount of the typical users in a SDLC, i.e. project managers, business analysts, system analysts, developers, testers.  Illustrate the examples for both Single/Dual Server deployments and show the other extras like the TFS Proxy server as well.  That would go a long way in clearing out all the confusion around TFS license costs.

Carel

# Affiliates » Blog Archive » TFS 2008 Licensing - clearing some of the misty valleys

Wednesday, March 05, 2008 6:05 PM by Affiliates » Blog Archive » TFS 2008 Licensing - clearing some of the misty valleys

Pingback from  Affiliates  » Blog Archive   » TFS 2008 Licensing - clearing some of the misty valleys

# re: TFS 2008 Licensing - clearing some of the misty valleys

Thursday, March 06, 2008 11:42 PM by yah

Guess it would be nice to have a quick cheat sheet so that anybody/noobs could follow the trail as to what the required licenses are for development teams... Even better still... Do you have this information available in flowchart form? I know you have given a checklist above, but I would like to see it as it applies to real world dev teams / projects...

Has MS done any analysis as to why not simplify the licensing schemes into just one, surely this plethora of options might be affecting the adoption of the suite/product?

# VSTS Links - The Willy-Peter Schaub post

Wednesday, March 12, 2008 3:56 PM by Team System News

See what happens when I get behind in my VSTS Links reading: Willy goes on a post frenzy: TFS 2008...

# re: TFS 2008 Licensing - clearing some of the misty valleys

Tuesday, March 18, 2008 4:51 PM by Andy Mackie

You say you need a VSTS licence for the edition installed on the build server. However, according to this Microsoft MVP/Regional director, quoting the Microsoft Whitepaper on licensing, that licence can be an existing licence that a developer has, no need for an additional separate licence for the build machine:

blogs.msdn.com/.../licensing-team-system-editions-for-your-build-machine.aspx

# How to get up to speed with Team Foundation Server

Friday, June 20, 2008 11:26 AM by CodeClimber

How to get up to speed with Team Foundation Server

# re: TFS 2008 Licensing - clearing some of the misty valleys

Monday, July 28, 2008 12:58 PM by starter

I have a startup company and for the IT I have 5 programmers who need VSTF. How many licenses do I need?

Do i need 1 copy of team foundation on the server and 5 copies of VS2008? Or do I need 5 copies of VS2008 and 5 copies of TF? Or how does this work?

# re: TFS 2008 Licensing - clearing some of the misty valleys

Monday, July 28, 2008 2:22 PM by willy

You would need one copy of TFS Workgroup Edition, which supports 1-5 users, or one TFS Server license, which supports 1-many users, on the server side.

You would also need one copy of VSTS for each programmer, or alternatively another IDE and 5 copies of the TFS Server CAL.

Leave a Comment

(required) 
(required) 
(optional)
(required) 

Enter the numbers above: