I can't seem to add a user to the licensed user group in TFS 2010. Everything online says to open up Visual Studio, connect to the server, then drop down team, click Team Foundation Server Settings, and then Groups.
I can get that far, but then it says to click on the Licensed Users Group, and I don't have that group in my list.
I don't think this should even work really though, because I believe those directions are for TFS 2008 not 2010.
We've got TFS 2010 installed, and on my development PC I'm using VS 2008, and we have another PC in the office using VS 2010 so I can connect to it either way. I also have full rights to the 2008 server that the TFS is actually installed on, but cannot seem to find the licensed user group anywhere.
Are your instructions from Microsoft or an internal document? I've never seen the Licensed Users Group in TFS. Instead, we add our users to [SERVER]\Team Foundation Valid Users when they are licensed.
In Visual Studio 2010, first ensure that you are connected to the Team Foundation Server. Then, under the Team menu, select Team Project Collection Settings then Group Membership. This will bring up a dialog box that shows all of the valid groups. Find the one that is called [SERVER]\Team Foundation Valid Users and click on Properties.
In the secondary window that pops up, select Windows User or Group and click Add.
Alternatively, create an Active Directory group that represents your authorized users, and add that group to the Team Foundation Valid Users TFS group. This way, when you add new users, you can have your network administration simply add the licensed user to that Active Directory group and they'll automatically be included in the Valid Users.
To add to what's been said here, that particular group isn't expected to exist in all editions:
After you install Team Foundation Server Workgroup Edition, you must add users to Team Foundation Licensed Users security group in order for them to connect to the server. This security group is a server-level group specific to the Workgroup Edition. This group is created during installation of the Workgroup Edition, but not the Trial Edition or the Standard Edition
https://devblogs.microsoft.com/devops/how-to-add-users-for-team-foundation-server-workgroup-edition/
Related
I'm working on a .NET project with a subcontractor.
The client has all source code in Visual Studio Team Services (VSTS).
The client has granted access to the subcontractor, but he cannot see any source code or builds.
When logging in to the VSTS website, he receives the following error messages:
"TF400409: You do not have licensing rights to access this feature: Code"
"We could not verify your Visual Studio subscription so we've downgraded you to Stakeholder."
The subcontractor meets the criteria for commercial development using the Community Edition of Visual Studio (fewer than 5 developers etc.), so it would be sad if they had to purchase a license, just to access one client's source code.
Is there a way out?
Could he maybe set up a free VSTS "Community" instance and thus be marked as "licensed" in the system?
Access level is assigned per Visual Studio Team Services (VSTS) subscription and not per company. So even though you contractor might be considered a single entity he will be part of the free license count for the particular subscription he is trying to access. Either there are already 5 free developers or he is not assigned the correct level.
Access level is assigned through the dashboard https://{youraccount}.visualstudio.com (select Users from the '...' menu). The 5 free licenses can be used by assigning the users to the Basic access level. You can read more here: Manage users and access in VSTS (if you turned off User Hub).
I have different accounts with different VSO subscriptions. I'm trying to connect to a different account (from the one I'm logged in VS-2015) so that I can check in code in the repository that I have in that account. But when trying this, Visual Studio brings me to the profile website, from which is basically a dead end - what am I supposed to do from there?
The "Connect to Team Foundation Server screen sometimes just freezes after authentication, and doesn't go anywhere from there.
So clearing the settings file, which is named CurrentSettings usually in the folder C:\Users\your user name \Documents\Visual Studio 2015\Settings (Windows) - helped get passed this issue.
Also, when you are brought to the VSO Profile page (the one I showed in my picture question) you have to select the project you are trying to open.
I'm using Visual Studio Team Services (was TFS Online) server {MyProject}.visualstudio.com. I'm able to connect to the server, map the project, even receive a review request, but I can't see my team projects under DefaultCollection.
Currently when I'm opening the Source Control Explorer I'm only seeing
{MyProject}.visualstudio.com\DefaultCollection
underlying projects are missing, but my user is in project team members list.
What I missed, what I should do else to be able to browse my projects, get and work with them?
Note: My account was not a microsoft account. I received an email to join the visual studio after tfs administrator added my email as the project team member. I follow to the link and I create a new account during VS sign up using that email and then successfully signed in.
Thanks a lot
This is usually caused by the "Access Level" that the Admin assigned to your account.
When your account is assigned as "Stakeholder", you can only access to "Work" section, cannot access to "Code". If you want the access to "Code", you need to ask your Admin to change the access level of your account.
Have the TFS Admin review your user's rights to the code in the team project. Generally we add users to the Contributor role for the project.
You should also try hitting the Refresh button (third from the right) on the Source Control Explorer window.
I had similar problem and as usual Microsoft has not useful error. Here is step by step tutorial to fix it.
The problem
Solution
This is related to user permissions. Note two things
If you are using 5 user free version, make sure to select user as "Basic user". Free version allows only basic membership.
Then go to Security setting, expand to see "Team Foundation Administrators" and add the new user this. This should resolve the browe project issue.
I can't seem to figure out this permission issue. I setup permissions on a TFS collection to allow access to certain folders in that collection. That is working fine. The users are part of a windows group. The users have VS2010 and VS2012, looking under "Team"->"Connect to Team Foundation Server" the users don't see the collection. If I go to Source Control Explorer they can see the collection and are able to use it as they need.
The question is: why can't they see the collection in "Connect to Team Foundation Server"? Is there some special permission that I need to enable to see the collection in "Connect to Team Foundation Server"?
For folks to be able to connect to a Team Project they needs to be in the Reader group of that team project as a minimum. If you just add them to the source control folder without adding then to the team project you will get the symptoms that you report.
If you connect to Team Web Access and navigate to the project you can add the user to the Team on the team dashboard.
If you are using pre-TFS 2012 you can connect in Team Explorer and right-click on the Team Explorer node of the Team Project in question and select "Group Membership". Add the users to at lease Reader, but most likely Contributor.
I am trying getting ready to move my TFS 2010 database for the third time to its final perminent server, however, I am running into a very annoying user issue. When I restored the new system as a test I connected my Visual Studio IDE to the new server (same name as the old one) and tested and got that system working properly. Now when I go to the old server now I can connect and see everything - but I no longer have permissions to create work items or edit items.
I can use Visual Studio 2012 just fine as well as the Microsoft Test Center 2010 to edit items. I've experienced this before with my local system tfs at home and got around it by changing the user name I log into on my computer and then adding permissions for that new username.
Since these the user id's are workstation accounts - not domain accounts each system has its own user guid even though they might have the same account name. I noticed in VS 2010 the workitem in history show modified by unknown user - however it has the username in VS2012. It seems that connecting to both systems might somehow made the user matching between my domain user account and workgroup user account break.
I am about to roll to the new server and am concerned that my userbase will not be able to modify items in VS2010. I cannot use the workaround I did before since I can't have everyone create a new username.
Any help would be appreciated - as I am sure I am not the only one with a workgroup not domain tfs system that has run into this issue before.