Can anyone explain me what I am dealing with here, I am doing a simple migration procedure, I have tfs2013 update4 and I am trying to migrate it to vsts, I am using microsoft's migration utility to do it, but when I pass the validation command i.e TfsMigrator.exe Validate /collection:http://localhost:8080/tfs/java test it gives me error TF255003, it says it can't fetch the installation path please elaborate me whats going wrong here.
That means the TfsMigrator is not available for your current version of TFS.
The official TfsMigrator tool is only supported for TFS 2017, you can download the corresponding tool based on your TFS version (RTW_15.105.3924742 or Upate1_15.112.3923436)
So, you need to upgrade to the latest version of TFS (2017 update1) first if you want to use TfsMigrator tool. Please see Validating a Collection for details.
Related
I have been responsible for administrate our TFS projects and have started to investigate the current configurations. I found the following link for determining which process our team projects are connected to: How to determine what Process template an existing TFS 2012 project is configured with?
When using the rest API described in the article above, it seems like the projects depend on a process template called "Microsoft Visual Studio Scrum 2013". When reading this article: Scrum process it seems to me that the process is outdated and should be upgraded to use the "Scrum" template.
I have searched the internet for knowledge on how to upgrade the project to use the new Scrum process but had no luck of finding an answer. Does anyone have an idea of how to update the projects to depend on a newer process? Maybe the whole question is wrongly put as I may lack some obvious knowledge about how these things are meant to work. All I want is to ensure our projects are updated to use the latest TFS technology.
We use Visual Studio 2017 and did recently upgrade our TFS server to TFS 2018.
In general, some new features will be introduced when upgrade from old to new version of TFS.
Generally if you haven't made any changes to the original process template, upgrading is quite easy. Just enable new features by running the Configure Features Wizard in your team projects configuration page.
If it can’t upgrade automatically, you need to apply updates manually. See Add updates to team projects manually.
If you customized the process template, then you can follow the steps mentioned in this link to Update a customized process template to access new features.
To update the existing projects, a not so nice but easy way is to remove all work items and process data from your project and then add the newest items. Martin Hinshelwood has some great guidance on how to do this.
I'm planning to upgrade TFS from 2013 to 2015. In case something goes wrong during the upgrade installation, I'll rollback and revert every thing to its original state (TFS 2013). I'm performing the upgrade on the same server, which means that if the upgrade is successful, TFS 2015 will override 2013.
Is there an article to follow in case of rollback? Preferably an official article from Microsoft.
Just as jessehouwing's answer above, you can follow the restore procedure, but if your setup includes Sharepoint, Report Server and one or more build servers you may need to revert those too, that would be a very tedious and complex job.
Another way is that you can make a system image to back up you environment first,then restore it in case something goes wrong during the upgrade installation. Please see Back up and restore your PC for details,or use any other backup tools.
You're basically looking at the Restore procedure outlined here:
https://www.visualstudio.com/en-us/docs/setup-admin/tfs/admin/backup/restore-data-same-location
But before you restore you need to uninstall TFS 2015 and reinstall TFS 2013 and its latest update packs.
If your setup includes SharePoint, Report Server and one or more build servers you may need to revert those too. As far as I know there is no definitive rollback documentation. The recommendation is to do a trial upgrade on a second environment, resolve any issues you may find and then perform the final upgrade.
wondering if anyone else has experienced anything similar and has overcome it. I am using OpsHub to migrate from an on premise 2012 TFS to VSOnline. I've set up my project with perms according to the instructions provided by Opshub. I ran a dry run of the migration to a personal instance of VSOnline in early December. Now I am trying to follow the same migration steps to our company's vsonline instance. I've set up everything the same. I am receiving an error that sure seems like a false positive. The utility is reporting that the WIT for Code Review Response has been customized. Specifically the field Reviewed By has been customized. I've opened up both WIT's and compared them. The only thing that is different is that on the 2012 WIT it didn't contain the rules ALLOWEXISTINGUSER and VALIDUSER and the Reportable field was blank. I tried adding them to the 2012 WIT but that didn't alleviate that problem and I set to the Reportable field to Dimension to match the 2015 WIT. I've checked the spelling on the 2012 WIT, it is the same. This has not alleviated the issue. Has anyone experienced and better yet, solved this? If so, would you mind sharing?
You need to restore the WIT definition to the original 2012 template rather than update it to match 2015 template. To do this, download the original process template used to create your team project and import the WIT XML definition files for Code Review Response using witadmin importwitd.
Refer to this link for details: https://www.visualstudio.com/en-us/get-started/setup/migrate-team-projects-vs
I installed the Basic TFS trial version and now it got expired.
It is mandatory for me to get the history of TFS.
Where does it store the history? Does it store it in the SQL Express?
Is there any way to get the saved history?
Digging through the database is not trivial. You'd have to piece the history back together and de-deltify all the blogs.
It would be much easier just to get your TFS instance working again so that you can get the files out of it. TFS Express 2012 is now available, and has no such time restriction. It's free for up to 5 users. You may be able to upgrade your existing installation.
If you are still able to do a get, you could hook up git-tfs. Once you execute the git-tfs clone, you will be able to view the history using git. You can look at this tutorial for more information.
Did you consider trying querying the TFSWarehouse and use and automatic script to recreate history ?
Reference: Export TFS 2010 History to Excel or Text Document
Our team is migrating from VSS 6.0 to TFS 2008 to be used for source control purposes. I am wondering if anyone has any experience with this migration. In particular, we are interested in preserving the history of files in source control, as well as any other potential gotchas.
Do you have VSS 2005 installed? You need it rather than the previous version (6.0d).
Also, do you really need the history in TFS? Or can you draw a line in the sand and say that all history before such and such a date is in VSS and all history after that date is in TFS? If so, you can simply do a get latest from VSS and add the files into TFS. Migrating is non-trivial because you need to deal with VSS users that don't map to domain users, VSS users that don't exist anymore, and although the order of source-control operations is maintained the actual date/time of the operation isn't migrated, it is however stored in the comment as part of the migration.
This is fairly easy once setup. You will first need to create a usermap.xml. This will map your VSS users to your TFS2008 users. Then you create a project configuration file. I would post examples of mine but I can't get the XML to post.
The project configuration file will point to the usermap XML file. Then all you have to do is type the command "VSSConverter migrate settings.xml" to migrate or "VSSConverter analyze settings.xml" to analyze the project. I suggest you to analze before migrating the project.
Here is a link for more information.
http://msdn.microsoft.com/en-us/library/ms253090(VS.80).aspx
Unfortunately, when I tried this...
TF60032: The VSS Converter requires Visual SourceSafe 2005 or later to run.
Please install Visual SourceSafe 2005 or later and try again.