I have TFS server, and I have a remote team that will work off it, the problem is that they don't have VS license they user VWD 2010, how do i share source with them? I don't want to abandon the TFS but I cannot ask them to buy licenses for a small project.
Anyone who connects to a TFS server has to have a license.
If they are checking in / out code, then you need to have enough licenses to cover all of them. It's not their responsibility to have a client license, it's yours as the owner of the TFS Server.
Related
I need to setup TFS 2017 for 20 developers/analysts. Usage will be mostly for code repository, therefore 1 server only with TFS 2017/8 and SQL 2017. I need to know the licensing requirements for TFS application only, I know for SQL. We plan on using SSRS, but not SharePoint. Will a Visual Studio subscription cover for the TFS license for server and does it have to be Enterprise or Professional subscription is OK? What license will be the most economical for the rest of 19 users?
Thank you,
Will a Visual Studio subscription cover for the TFS license for server
and does it have to be Enterprise or Professional subscription is OK?
Yes, Visual Studio subscriptions include a server license for TFS, plus a TFS CAL for the subscriber
What license will be the most economical for the rest of 19 users?
It's based on your real requirements. Client access licenses (CALs) aren’t required for people who just access work items – assign them “Stakeholder” access, which is free.
If the users want to work on codes, then they need client access licenses...
Extensions to TFS such as Test Manager, Package Management, and Private Pipelines require an additional purchase. Some TFS Extensions are included with Visual Studio Enterprise subscriptions and many others are free. Paid extensions can also be purchased monthly, no Visual Studio subscription is required.
Please see Team Foundation Server 2018 Licensing for details, it also applies to TFS 2017.
I have a TFS Administrator who does not develop or use Visual Studio. They only use TFS through the Web UI. Do they need to have an MSDN, all they are really doing is setting access levels.
TFS is licensed on a Server/CAL model. Thus, you need 1 Server license for the TFS server and 1 TFS CAL (client access license) for each user that will use TFS features.
That TFS CAL covers the usage no matter how the user accesses TFS (i.e. Visual Studio, Eclipse, Web Access client, Excel, MSProject, 3rd party tool, ect, etc).
Client access licenses (CALs) aren’t required for people who just access work items – assign them “Stakeholder” access, which is free.
So in your scenario, to manage the TFS they need CALs (client access license), Visual Studio/MSDN subscription is needed.
The two ways to acquire TFS CALs are:
Purchase a TFS User CAL
1 TFS CAL (and 1 TFS Server license) is included in each Visual
Studio/MSDN subscription. Thus, anyone who has an active MSDN
subscription assigned to them is covered with a TFS CAL.
Client access licenses (CALs) aren’t required for people who just
access work items – assign them “Stakeholder” access, which is
free.
Extensions to TFS such as Test Manager, Package Management,
and Private Pipelines require an additional purchase. Some TFS
Extensions are included with Visual Studio Enterprise subscriptions
and many others are free. Paid extensions can also be purchased
monthly, no Visual Studio subscription is required.
More details please refer below two blogs:
Understand TFS Licensing
Team Foundation Server 2018 Licensing
We are using Microsoft SQL Server Data Tools - Business Intelligence for Visual Studio 2012 for our SSIS Packages development. We would like to integrate this with Team Foundation Server Express edition since it is free.
Please let me know whether this integration possible at all? What will be other limitations?
Thanks!
SQL Server Data Tools is a feature in VS, while TFS is a server that provides features like source code management, reporting, ect. If Visual Studio 2012 is not installed, you need to install Team Explorer to work with TFS.
Regarding TFS Express limitation, you may check this case: Limitations & Features of TFS Express 2013
By the way, instead of TFS Express, you may consider using Visual Studio Team Service.
Is there any way to export TFS/VS Online?
We need to import the data to our onpremise environment.
We are running Windows Server 2012 R2 with TFS
AFAIK there is no free tool that can help you with migration from VSO (Visual Studio Online) to TFS (Team Foundation Server)
OpsHub has a paid product that should allow you to do this though.
http://www.opshub.com/main/index.php/products/oim
They have a free version of their tool to migrate from TFS on prem into VSO. Which seems to have been sponsored by Microsoft. http://blogs.msdn.com/b/bharry/archive/2014/05/14/migrating-on-premises-tfs-to-vs-online.aspx
Microsoft enabled this for a short while, but it is no longer available. There is a chance they will enable this again in the future. See this blog by Brian Harry for more details on the Export feature (about halfway down the post): http://blogs.msdn.com/b/bharry/archive/2014/02/21/vs-online-early-adopter-program-extended-to-may-7-2014.aspx
You can use the TFS Integration Tools to move your data from VSO to TFS. I have only done this once but it is possible. The TFS Integration Tools are however not hugely friendly and I would recommend contacting an expert 😊
http://nakedalm.com/migration-from-tf-service-to-tf-server-with-the-tfs-integration-platform/
I am installing VSTS. What components do i need to install for both .net & sql server. ?
How do we configure our projects?
There are two parts to a successful Team System environment: Team Foundation Server and Visual Studio Team System.
For best results, install the former on a dedicated server. There are great resources to help you through installation right from Microsoft. There's even a video series of TFS-related content!
Once your Team Foundation Server (TFS) is installed, Visual Studio Team System (VSTS) is installed on your development workstation. VSTS looks just like any other VS install at startup. To configure it to work with your TFS instance, go into Tools > Options and Select Source Control: here you will see a pull down which should contain an entry entitled Visual Studio Team Foundation Server. I forget how to select your TFS server instance for VSTS to work with but I don't recall having trouble with it when I did it a few months ago.
Once you've configured all that, you interact with your TFS work items and source code from the Team Explorer and Source Control Explorer panes in VSTS: it should begin to feel rather like using VS without integrated source control from there forward.
The bigger issue is configuring your process in TFS to reflect your project's strategy, etc. That is an exercise in thought/reading more-so than how to configure it.
All this documentation is readily available via Microsoft's website. It does require some reading but devote some time to it: it'll pay off in the long run.
Team Foundation Server Requirements