Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 5 years ago.
Improve this question
Since TFS 2018 does not support SharePoint integration, which databases should be migrated and what should be done with the SharePoint databases.
Update:
If you are upgrading to TFS 2018 from a previous version configured to integrate with SharePoint 2010 or 2013, you will need to disable the SharePoint integration after upgrade, or your TFS SharePoint sites will fail to load.
During installation, if SharePoint and TFS are on the same server, the installer will display the following warning message:
TFS 2018 and later versions no longer support integration with
SharePoint. If you have configured TFS integration with SharePoint,
then you will need to disconnect to the TFS Integration on each
SharePoint server, or your TFS SharePoint sites will not work.
After upgrading the TFS server, you must uninstall the prior version of the TFS from the SharePoint server. After uninstalling the TFS, the TFS SharePoint sites will fail to load. This is because they reference TFS artifacts that no longer exist.
The solution is to install the TFS Disconnector for SharePoint on the SharePoint 2013 server. The TFS Disconnector for SharePoint installs all the required references for TFS sites to display properly, while disabling TFS-SharePoint integration.
After the upgrade, your TFS SharePoint sites will display, but all integration functionality is disabled. The following image shows what the site will look like after you upgrade and disable SharePoint integration.
For more information, read Disable SharePoint integration after TFS 2018 upgrade.
Also take a look at Future plans for TFS and VSTS SharePoint integration
There are a number of changes coming to Team Foundation Server requirements in TFS 2018. Details on requirements across versions of TFS can be found in requirements and compatibility. Before you upgrade to TFS 2018, take a look at below note:
Operating systems
TFS 2018 will not support Windows Server 2008 R2, Windows 7, Windows
8.1, or Windows 10 Home edition. We have never recommended installing TFS on client OSes except for evaluation purposes or personal use. We
will continue to support Windows 10 Professional and Enterprise
editions.
SQL Server
TFS 2018 will no longer support SQL 2014, but will continue to support SQL 2016 and will add support for SQL 2017. We typically
strive to support at least one "overlapping" version of SQL between
major releases of TFS in order to make it easier to upgrade TFS
deployments incrementally.
SharePoint
TFS 2018 discontinues support for the TFS Extension for SharePoint.
For more information, go here:
https://go.microsoft.com/fwlink/?linkid=852977.
Build compatibility
TFS 2018 will no longer support the XAML build system. For more
information, go here:
https://blogs.msdn.microsoft.com/bharry/2017/05/30/evolving-tfsteam-services-build-automation-capabilities/.
If your TFS2015 installed on a not support system, you may have to first set up a new operating system.
Even though there is not a complete tutorial for TFS 2015 to TFS 2018 upgrade procedure by now. You could refer this article aims to expand on the Upgrade overview and give a step by step walk-through of the upgrade to TFS 2017. You just need to take care of some notes mentioned above.
The general process for upgrading an existing deployment of Team Foundation Server is to:
Prepare your environment. Such as upgrade your SQL sever
(required), operating system...
Expect the best, prepare for the worst. The single most important step you can take here is to ensure you have a complete and consistent set of database backups.
Do the upgrade!
Configure new features.
I don't think that you will find one complete guide in doing this, but a source of information is the Requirements and compatibility page.
There are different considerations depending on your configuration, e.g. do you use SharePoint, Reporting Services etc. One thing that you need to deal with, is that TFS 2015 and TFS 2018 does not support the same versions of SQL server, so you will need to upgrade SQL during the upgrade or move your collection(s) to a new server with the appropriate version of SQL (see here).
I would suggest to do a test migration of one or more collections and sort out the process before attempting it on your production server.
Related
At work, I've been put into the role of TFS administrator, as the real TFS admin is leaving our organization in two weeks. We're currently using TFS 2015. I'm trying to upgrade us to TFS 2018, hopefully before the current admin leaves.
To that end, I've been reading various resources on TFS migration from TFS 2015 to TFS 2018. One resource I came across is this one Migration from TFS 2015 to 2018. This document spoke about integration between TFS 2018 and SharePoint. I had thought that integration died, after TFS 2015. Specifically, up to TFS 2015, TFS had what they called "TFS Project rooms". Sort of like a simple bulletin board type system. But Microsoft decided to break that connection, so I was lead to believe, after TFS 2015.
So, I'm wondering, since the linked to PDF speaks of integration between TFS 2018 and SharePoint, what is that about? Especially if TFS team rooms have gone away?
According to this doc about TFS 2018 and SharePoint integration:
TFS 2018 and later versions no longer support integration with SharePoint.
The SharePoint integration supports the TFS 2017 and earlier versions. In TFS 2017 and earlier versions, in addition to the team room function, this integration also has other functions.
For more detailed information about sharepoint integration , you could refer this Blog.
Since you are upgrading the TFS 2015 to TFS 2018, if you have configured the SharePoint integration in TFS 2015, you need to disable the SharePoint integration after upgrade.
In addition, in TFS 2018, we start to use Microsoft teams or slack for monitoring and communication.
Hope this helps.
Think this MS-Post might give you the answers: The future of TFS/Sharpoint Integration
As part of a server move, we'll be transferring our TFS and its SQL back-end. Can someone tell me if this is possible, and if so, what order we should be doing the migration vs upgrade? Would it be best to do the upgrade in-place before moving hardware/domain? Are there any particular pitfalls I should be wary of?
Details:
Moving TFS2010 to TFS2018 (potentially via 2013.5)
Moving SQL Server 2008 R2 to 2017
All moves will be done to new hardware on a new domain
Build and work item compatibility is not a concern, as we use TFS only for version control
Direct upgrade to Team Foundation Server 2018 Update 2 is supported from TFS 2012 and newer. If your TFS deployment is on TFS 2010 or earlier, you will need to perform some interim steps before upgrading to TFS 2018 Update 2. Please see the chart below for more information.
Can someone tell me if this is possible, and if so, what order we should be doing the migration vs upgrade?
Yes. You can upgrade from TFS 2010 to TFS 2018. But you have to upgrade to TFS 2012 and newer, then upgrade to TFS 2018. You could refer to the link below:
https://learn.microsoft.com/en-us/vsts/tfs-server/upgrade/tfs-2005-to-2015?view=tfs-2015&viewFallbackFrom=tfs-2018
And, changing the hardware is a restoration-based move, and you should never combine the two move types. First complete the hardware move, and then change the environment: https://learn.microsoft.com/en-us/vsts/tfs-server/admin/move-across-domains?view=tfs-2015v
Would it be best to do the upgrade in-place before moving hardware/domain?
You could do in place upgrade, or move to new hardware. If you're upgrading in place, consider doing a dry run of your upgrade in a pre-production environment, and make sure the system environment is meet.
Are there any particular pitfalls I should be wary of?
Before upgrade, you can read this article first, and be sure you have full backup of your database.
We currently have a TFS 2012 Server which is being replaced by a 2015 server, the aim is to gradually migrate our code from one to the other.
When we do this we would like to maintain the checkin history, labels etc, Looking at similar questions the answer seemed to be to use the integration toolkit, however it looks like it (and its successor the integration platform) do not support TFS 2015.
We are using TFVC rather than git, if that makes a difference.
I don't have much knowledge about the integration toolkit, but I would actually suggest to do the upgrade one Team Project Collection at a time, but moving them separately to a new server with TFS 2015 installed. This way you will keep all history, label etc.
We have done this way back when upgrading from TFS 2010 to TFS 2013. Only obstacle that we had was a collection around 500 GB in size so it took around 16 hours for the upgrade to finish.
The following answer specifies the steps needed to move a collection to another server:
Copy TFS 2012 collection to another server with TFS 2015 Installed
We have used this Migration tool for our Client.
It’s possible to migrate TFS 2012 data to TFS 2015 with all information intact without any system downtime. The premium version of OpsHub Visual Studio Migration Utility (OVSMU) supports migration of projects with TFVC repository from one instance to another. It supports the 2010, 2012, 2013, and 2015 versions of TFS and all versions of Visual Studio Online, including the 2017 version. Along with basic data, you can migrate all workitems with history, comments, attachments, relationships, and source control with changesets, history, labels, comments, etc. You can checkout the details here: https://www.opshub.com/products/opshub-visual-studio-migration-utility/
I wish we could use multiple build controllers on the same machine because we have many team project collections but they're not used at the same time so there's no real performance issue here and most of our build servers are not used for extended period of time. I know it's possible to do this with TFS 2010 and TFS 2012 (see following post) but it's an unsupported feature.
Anyone can tell me if it's now officially supported with TFS 2013, I've not been able to find any useful information about this.
This is still an unsupported feature. This feature would be loudly trompetted should it arrive.
On the chances of this arriving in the TFS 2013 updates, I don't expect it. Maybe with TFS v14 (they're skipping v13) or maybe the version after that?
Make your voice heard on UserVoice:
http://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/2037679-remove-one-one-binding-between-collection-and-buil
http://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/4417771-use-a-build-controller-over-more-than-one-team-pro
http://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/3872254-tfs-2012-possibility-to-have-more-than-one-build
Update
A new build system was introduced in TFS 2015 and Visual Studio Team Services. It's agent based. doesn't have Controllers and you can install multiple agents on a single machine.
Agents are grouped in Pools and live at the Server level, allowing you to use them across collections.
I'm currently planning to upgrade our TFS 2008 server to TFS 2010 with the condition below:
1. upgrade everything except for the sharepoint
2. upgrade everything including sharepoint but sharepoint will be enabled only at later stage. will this stop us from using TFS for our development?
Thanks,
Chen
Sharepoint shouldn't be a requirement unless you have a strong need to have project portals. Everything else (workitems, source repository, etc. should work fine).