I have already TFS and I want to upgrade to TFS 2017. Installed SQL SP 1 and TFS 2017. get backup from previous TFS configuration.and restore in new TFS.
But all user workgroup is blong to previous TFS. how can I fix all users automatically?
If you are moving your Team Foundation Server from one workgroup to another, you must re-create service accounts and user accounts in the new Team Foundation Server environment. Additionally, you must re-create any local accounts from the old Team Foundation Server on the new Team Foundation Server.
The account names created on the new Team Foundation Server deployment
must match the names of the accounts from the original Team Foundation
Server deployment. This includes both user and service accounts. These
account names are used to identify and update the Team Foundation
Server database records as part of the move process.
Please see this article for more information.
Related
how to migrate a single project alone (where project collection contains 30+ projects) from TFS to VSTS with all history, build-definitions, changesets
Microsoft has documentation on this exact scenario which can be found here: Migrate to Visual Studio Team Services : Move from Team Foundation Server (TFS) to Visual Studio Team Services (VSTS) and bring your data along.
This link also contains the download link for the migration tooling which you will want to use
Currently the following versions of TFS are supported for import:
TFS 2017 Update 3
TFS 2018
TFS 2018 Update 1
As described in About VSTS and TFS, Scope and scale data, the
long term direction for VSTS is to support grouping of accounts within
organizations. This would lead to:
VSTS accounts that serve as the equivalent of TFS project collections and VSTS organizations that serve as the equivalent of
TFS deployments.
This is why the TFS Database Import Service only supports importing single TFS collections as single VSTS accounts.
If you need to migrate individual team projects you will need to use
one of the other options—manual copy or public API based
migrations.
Source Link
It's very clear why you could not use TFS Database Import Service to migrate at team project-level directly.
You can also have a try for VSTS Sync Migration Tools,it allows you to bulk edit and migrate data between Team Projects on both Microsoft Team Foundation Server (TFS) and Visual Studio Team Services (VSTS). Note this without history. How to please refer: TFS 2017 Migration To VSTS with VSTS Sync Migrator
If you insist on keeping all history, the only way is using TFS Database Import Service, you may take the workaround as Daniel suggested.
I need to create a new team project collection in TFS 2015 Update 3 and I'm following this guideline.
Visual Studio Team Foundation Background Job Agent service account does not have the privilege to create databases on the DB server, and I intend to keep like this.
For this I consider:
DBA create empty database named appropriately but assign no permissions for the Team Foundation Background service account
Run “Use this existing database” in the Create Team Project Collection wizard.
I assume this will create necessary schemas/metadata in DB and allow TFSExecRole to the Team Foundation Background Job Agent service account on this new database.
Question: Is this correct?
Based on your description, you mentioned the Team Foundation Background service account should be the account which you specified to connect to the SQL Server during the TFS configuration.
You will find that the owner of the collection DB should be the user who created the collection (Right click the collection DB -> Properties -> General).
Actually, all the TFS Administrators (Add administrators to TFS) are the owner of the collection DBs (Security -> Logins -> Right click on any admin users -> properties -> User Mapping ).
So, whatever you need to use the TFS administrators account to create the NEW Collection. Just exactly following the guides: Create a team project collection
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 have a group of students connecting to Team Foundation Server. When they connect from school, when their computers are physically on the network, they can successfully access TFS and perform get operations, checkout, checkin, etc.
The same users go home, install VS 2010, connect to TFS, get the code, but the solution will be opened offline from TFS.
Why is this?
When the students are at home, do they access the server from a different name than they do at school? Often, users will use a short (not fully qualified) name to access a server internally. For example:
http://tfsserver:8080/
However, this will not work from outside of the network, the name will need to be fully-qualified. For example:
http://tfsserver.mycompany.com:8080/
The Visual Studio solution contains version control bindings that point to your Team Foundation Server. If the users cannot access the server by name in the bindings, the solution will be opened offline. The users should connect to Team Foundation Server and then select "Change Source Control" in the file menu. This will cause the solution file to point to the fully-qualified domain name of the Team Foundation Server which should allow access from within your internal network or from the outside world.
Suppose I have a team foundation server http://tfs:8080 and a collection named Collection1 and a project named Project1. How would I go about giving user User1 all privileges on the project? (Either by adding him to the Team Project Administrators group OR by granting individual privileges as you would in the GUI)
This is what i would recommend, download the TFS ADMIN tool http://tfsadmin.codeplex.com/, this is a community tool that for TFS Administrators, The TFS Administration Tool allows Team Foundation Server administrators to manage user permissions on all three platforms utilized by Team Foundation Server: Team Foundation Server, SharePoint, and SQL Server Reporting Services. The tool also allows administrators to easily copy user permissions among team projects and to easily identify any missing permissions on any of the three platforms.
However, you don't need the admin tool to assign permissions. You can right click on the team project and click on group membership, double click on the group that you would like to add the user to and add their windows login to the group. You can read more about this here, http://msdn.microsoft.com/en-us/library/ms252477.aspx
HTH
Cheers, Tarun