There are 2 things you should have in mind about TFS 2015 Upgrading.
1 The database upgrading process will cost much more time than upgrading among Update package of TFS 2013.
2 The dedicated SharePoint integration package is removed and M$ did a shit test again. If you, like me, installed TFS on a server other than SharePoint cluster, now you have to install the whole TFS on all SharePoint servers. After the installation, the upgrading wizard will be popped up but it will failed due to no database can be found. You have to choose to install SharePoint integration role yourself. And after that, you will know that TFS SharePoint integration package 2013 will NOT and NOT ABLE to be removed, lol, just another piece of crap.
Problem: If you remove one SharePoint server from Central Administration site, some information will be left in farm database. While adding a server with the same name back to farm, the Distributed Cache service may not able to start.
Fix: On the new installed server
Open C:\Program Files\AppFabric 1.1 for Windows Server\DistributedCacheService.exe.config with a notepad or other text editor with administrator permission.
Nav to configuration – dataCacheConfig – clusterConfig, remember the provider and connectionString.
Run Add-CacheHost -ProviderType xxx -ConnectionString yyy xxx is the provider gotten from step 2 and yyy is connectionString.
You are ready to re-run the Add-SPDistributedCacheServiceInstance now.
There is a big farm of SharePoint Server 2013 in my company. Most of these servers are prepared with SharePoint 2013 and upgraded to Service Pack 1. Some new servers are prepared with SharePoint 2013 with Service Pack 1 directly. Project Server are installed in all servers.
From WSUS, Microsoft pushed July 2014 update for SharePoint 2013 this month, which includes KB2881077, KB 2863837, KB2863826 and KB2881003.
The problem is these can be applied on all servers come with SharePoint 2013 with Service Pack 1 but failed to be done on all servers which were upgraded to Service Pack 1. Patch files are trying to uninstall Service Pack 1 on those servers but Service Pack 1 is marked not able to be removed.
The way to fix is:
Remove all servers which were upgraded to Service Pack 1 separately from Central Administration site. You cannot do that by wizard — it won’t let you do that due to patch incomplete.
Reinstall the whole operation system to that servers removed from step 1.
Install SharePoint 2013 with Service Pack 1 and all other related tools to those servers.
Upgrade all servers to July 2014 update.
Run wizard on all servers.
Add those servers back to farm.
You may need to fix the distributed cache problem by following this guide from Microsoft. If you get the error “Host Already Presented”, you may want to have a look at this post.
If you wanna deploy Sharepoint 2010 with a SqlServer 2008 R2 ON ANOTHER SERVER, make sure that the domain account which will be used as Sharepoint Service has the dbcreator and securityadmin permission in the target SqlServer.
If securityadmin is not selected, you may have trouble to setup a search service application. All you need is delete the deployed search service application, add permission to SqlServer and re-create a new search service application.