We have TFS installed in a US server. We need to login into VPN to access the TFS server. TFS is configured to use with company's domain user account. However my system is part of the domain. Hence I couldn't access the TFS. I have Visual Studio Team System Developer edition. Can someone here help how to access TFS server installed with different domain?
Regards,
Krish
TFS uses the domain information of the current logged in Windows account, it's part of the TFS API.
If you're logging into the machine with an account which is on a different domain (Note: Local users are also on a different domain) you will not get single-sign-on.
As far as I'm aware there isn't a way around the authentication model which VSTS uses. You could write your own VSTS-style extensions using the existing VS API which say, uses a config file for the authentication credentials as the TFS API does support authentication through a manually-created user (we have an external application at work which authenticates against our TFS server and is used by employees of our many offices on different domains).
For codeplex you have to connect to TFS using 'SND\username_cp', maybe you can use 'DOMAINNAME\username' as well.
Related
I want to make use of the TFS API to retrieve information about builds/commits etc. As I follow this article, I see that I first need to create a security token for my user.
However, nowhere in my TFS web interface I can find where to configure the security of my user.
Any tips? What do I miss?
P.s. I use TFS on-premise, not Team Services (should not make difference though)
There should be . From your home page, open your profile. Go to your security details. Add the screenshot of my TFS2017 for your reference:
Note: Personal access tokens are only available with TFS 2017 and above or VS Team service. It's not support in TFS2015.
When pointing to TFS2015 or TFS2013, you may have to pass a username and password (could masked as a secret variable) in your script instead of using personal access tokens. For a sample you can refer below links:
VSTS/TFS REST API: The basics and working with builds and releases
TFS 2013.4 On-Premise. Enable Basic Authentication to access Tfs
REST Api
I am very new in Team Foundation Server.
I want to create a server at home and i want to use this server from another computer with my developer partner.
The main problem is that, i don't want to create domain users to access team foundation server. I am running an svn server and i want to migrate its data to TFS. Can non domain user (only a dedicated user like in svn server) access TFS from outside of the network?
I installed a Windows Server 2012, SQL Server 2012 and Team Foundation Server 2012. I have created a team project, then i want to connect to server from visual studio from another computer and got a standard "server unable to access" error message.
Can anybody write down the solution by step by step?
There are a few choices for collaborating in tfs:
Domain: This is the easiest to setup, user-wise. All you have to do is be a member of the domain and a member in a team project.
You have already said that you do not want this option.
Workgroup This requires you setting up the TFS server as a work group and then creating users in that workgroup that represent your team members. You then add them to your tfs team project(s). The pain part comes from you having to make sure that the username and password your team members log in with matches the work group username and password.
This is probably going to be your best bet unless you want to subscribe to visual studio online.
Visual Studio Online
This is almost as easy as the domain setup but isn't free. But connecting remotely is a good option. Plus if you are doing any cloud work it integrates nicely.
This link (http://msdn.microsoft.com/en-us/library/ms252507(v=vs.100).aspx) from Microsoft describes various domain \ work group combos. The one I describe above refers to the one where everything is in a workgroup.
Local user accounts must be created on the Team Foundation server for
all users requiring access to the server. Local user accounts must be
added to Team Foundation Server server-level and project-level groups
so that the users are authorized on the Team Foundation server. When
connecting from a Team Foundation client, such as Team Explorer, in
the workgroup, the client user account credentials must match those of
the server, or the user will be prompted for a user name and password
for an account on the Team Foundation Server.
I just installed TFS Server 2010 on Windows 7 Ultimate.
I even managed to connect to the TFS server using Visual Studio 2010 - I didn't have to enter any login and password, as Windows Authentication was automatically used.
Now I need to add a new user to TFS, with a specific login and password, so that a member of the project could access the TFS server from the Internet.
However, I did not find a way to add a new user to TFS!
I used to work with Visual SourceSafe, and there the management of users was quite straightforward.
Any help would be appreciated!
It's a little weird in non-domain situations.
Create a new local user on your computer.
In Visual Studio, look on the Team menu for Team Project Collection settings
Add that new user to the Authorized Users group (I think-- I'm not able to access mine right now, so I'm not sure what it's called. It's something like that, though).
On the Team menu, find Team Project Settings
Add the same user to the Contributors group.
When the other user logs on, they will have to specify the TFS Application Tier computer as the domain name. For example, if you installed TFS on a computer named MyWin7Box, they would sign on as MyWin7Box\Username
There seems to be a fault with my access to directories on Team Foundation Server.
See the image below.
I'm the only one with this problem. All of the other clients can connect to the server fine, so it must be my local copy of Team Foundation Server thats gone haywire.
Any ideas?
This is usually a permissions problem. Use the TFSAdmin Tool to check permissions on the SSRS and Sharepoint systems (which are separate from TFS itself, unfortunately). Check that the settings are working the way you intend by browsing directly to the Reporting website & the Team Project Portal from inside IE.
There are other possibilities, however.
Check the Application event log on the server to see if your attempts to connect generate any exceptions.
If you're using SQL Server 2008, make sure you have Team Explorer fully patched up to 2008 SP1. (you'll need to re-run SP1 if you installed Team Explorer afterward)
Make sure you're connecting to TFS using the same URI as other people. If you're using a fully-qualified domain and they aren't (or vice versa) you could be exposing a server configuration problem in TFS's Registration database. Details here: http://blogs.msdn.com/buckh/archive/2007/03/31/configuring-team-foundation-server-to-use-fully-qualified-domain-names.aspx Also, there is a known bug in the admin util: http://support.microsoft.com/default.aspx/kb/959126
Check, recheck, and re-recheck your proxy settings. Both software configuration (TFS inherits them from IE / Control Panel) and at the network level (whether you're on some LAN segment that gets proxied differently). Use an HTTP protocol analyzer on a good & bad machine to be certain.
I had the same issue after trying to connect to alternative address of our TFS server.
In my case it seemed that it just cached the previous TFS address although I changed it back to the original address.
What fixed it for me was to delete this folder:
C:\Users\<user>\AppData\Local\Microsoft\Team Foundation
I installed TFS 2008 Workgroup Edition a while back, and everything was running fine.
Recently I tried opening TFS to a couple of friends so that we can collaborate on a project. The Source Control portion is working correctly, but the Documents and Reports folders are not available (they have red crosses on them).
When I looked at the properties, I noticed that the URLs were using my internal machine name, not the external address (e.g. http://INTERNALNAME/Sites/MyProject instead of http://www.EXTERNAL-NAME.com/Sites/MyProject).
My preference would be to somehow use relative paths, so that if I ever decide to stop exposing TFS to the outside, I don't have to do anything.
I realize this may not be possible because TFS cannot make the assumption that Reporting Services and Share Point are on the same machine.... so is there at least an easy way to assign a new server name?
Yeah, relative paths cannot be used due to the way that TFS works - it sends back the full URL's to the Sharepoint and Reporting Services servers to the client machine.
To update the URL's that are used for sharepoint and reporting services to match your fully qualified domain name you want to use TFSAdminUtil. Remote desktop to the TFS server, open a Command Prompt window, and change directories to %ProgramFiles%\Microsoft Visual Studio 2008 Team Foundation Server\Tools.
At the command prompt, type the following command (all on one line):
TfsAdminUtil ConfigureConnections /SharepointUri:BaseSiteURL
/SharepointSitesUri:SharePointSite
/SharepointAdminUri:SharePointAdministration
/ReportsUri:ReportsUri
/ReportServerUri:ReportServer
Replacing the following strings
SharePointSite is the new URI for the SharePoint Products and Technologies site collection.
SharePointAdministration is the new URI for the SharePoint Central Administration Web site (used for new team project creation)
ReportsUri is the new URI for SQL Server Reporting Services.
ReportServer is the new URI for the ReportsService.asmx Web service.
BTW - If you have installed SP1 for Visual Studio Team System 2008 Team Foundation Server, the ReportServer parameter will not function correctly and you have to stick /ReportService.asmx on the end. For more information about this problem and its resolution, see this KB: Team Foundation Server 2008 SP1 TfsAdminUtil.exe 'ConfigureConnections' fails to properly set ReportServerUri.
For example, the following command would work with TFS 2008 SP1:
TfsAdminUtil ConfigureConnections /SharepointUri:http://tfs.external-name.com /SharepointSitesUri:http://tfs.external-name.com/Sites /SharepointAdminUri:http://tfs.external-name.com:17483 /ReportsUri:http://tfs.external-name.com/Reports /ReportServerUri:http://tfs.external-name.com/ReportServer/ReportService.asmx
One last thing to note is that if you are accessing your TFS server externally, then it is recommended that you do this using HTTPS to encrypt the TFS traffic. For more information on this configuration see the post on the MSDN site: Walkthrough: Setting up Team Foundation Server with Secure Sockets Layer (SSL) and an ISAPI Filter