We’re running TFS 2013 Update 1 and I’m planning an upgrade to TFS 2015 Update 1.
We have both SharePoint and Reporting Services installed and configured for TFS that I like to remove, because nobody ever uses them.
So, do I simply uncheck both Reporting and SharePoint during the TFS 2015 upgrade wizard. Is this the best way to do it?
Or, do I un-configure Sharepoint and Reporting Services first from our TFS 2013 installation? If so, what are the steps to do so?
Environment:
Server computer A:
Application tier for TFS 2013 Update 1
Data tier: SQL Server 2012 SP 1 for the TFS databases, and Reporting Services databases
Sharepoint services (only for TFS)
Server computer B:
SQL Server 2008 R2 hosting the SharePoint databases.
You can do either.
I'd probably uninstall/disable first if you're really sure you don't want them in the future (check with all the teams that they're not storing docs in SharePoint as they will lose them). That way the backup will be smaller/faster when you backup before you upgrade (Make sure you take a backup!!).
It's simple enough to do, just fire up the TFS Administration Console.
Select Reporting, Edit (this will stop the jobs) and uncheck "Use Reporting". Click OK.
For SharePoint, click SharePoint Web Applications and under the top section, click Modify against your server connection and choose Remove.
Make sure you take a new backup at this stage and then you can start the upgrade.
Some things to consider:
Are you sure you want to do this in-place? You could clone the server to new hardware and test the upgrade first or perform a migration upgrade. It means less downtime in the event of something going pear shaped.
If your collection(s) are large, this is likely going to take a long time. The 2015 upgrade seems to be slower than previous upgrades due to all the schema changes.
Are you sticking with a single server? That's fine, but you won't need server B for SharePoint so you could move to a dual server TFS install if capacity is a problem (You'd need to upgrade the SQL version on server B to act as a data tier though)
I'm a couple years late, but this still popped up in a search result so worth mentioning - use cmd prompt to do this:
Navigate to %programfiles%\Microsoft Team Foundation Server %#%\Tools\, and type TfsConfig.exe setup /uninstall:SharePointExtensions . This will "unconfigure" the feature in your App Tier.
Related
I'm trying to migrate our existing TFS 2008/SharePoint installation to TFS 2012/SharePoint 2010. If I do it without SharePoint it all works OK, but if I try and include SharePoint it fails.
At the moment I'm starting from scratch and including SharePoint.
I've run the Configure Extensions for SharePoint Products Wizard, restored the TFS 2008 databases, run STSADM from the command line, and now I'm attempting to run the TFS 2012 Upgrade Wizard: it fails at the, Configure the Server Running SharePoint step with the error "TF250004: The SharePoint Products installation is either corrupt or is not valid. Verify that SharePoint Products is a supported version and is functioning properly, and then try again."
Can someone please advise me what I've done wrong?
It seems that your TFS server can't detect you SharePoint .
Where is your Sharepoint server, is it running on the same computer with TFS server or on another machine?
With your upgrade ,did you change your hardware or use the same hardware as before.
Accroding to your description, you didn't mention whether you need to upgrade your SharePoint. You should finish SharePoint upgrade before your TFS server upgrade.And match TFS upgrade requirements https://msdn.microsoft.com/en-us/library/vstudio/dd631912(v=vs.120).aspx
You should also pay attention to your sharepoint permission.I suggest you use a "Full Permission" Account in sharepoint which interact with TFS .For your reference:http://social.msdn.microsoft.com/Forums/sr/tfsadmin/thread/ea2ef379-dd14-4e23-86e6-fbc156e430d8
I eventually unchecked the "Configure SharePoint Products for Use with Team Foundation Server" option to exclude SharePoint during the upgrade and then manually configured SharePoint after the upgrade, overcoming a host of problems along the way.
I am using Team foundation server 2021. I do take backup of all TFS databases regularly. So now in case of disaster recovery (in case full machine gets crash) how can i use this backup to recover TFS and all collection etc. I want easy and the best approach .
I have seen so many articles in microsoft website but nothing is really so helpful and difficult to understand. So please suggest a better tutorial or procedure to do it
I guess that you have TFS2012 Update 1 (there is no 2011 version). You should upgrade to TFS2012.2 which has the Scheduled Backups feature included.
When taking a backup of a running TFS instance always backup all databases. In cases of a disaster situation the only way to recover, is to restore all databases and re-run the TFS Application Tier install.
There is ample guidance available, plus the Backup tool that was introduced in the product with TFS 2012.2 is also available for older versions (2012 rtm and update 1) as part of the Team Foundation Power tools.
The guidance you should follow is that for either:
restore TFS to the same location (in case the server name for TFS and SQL remain teh same)
restore TFS to a new server (in case the server name for TFS or SQL has changed)
I wanted to know,
if, I can setup sharepoint 2010 server along with visual studio 2010. And sql-server on another machine in some domain
and
create multiple accounts on the sharepoint 2010 machine
and allow developers to develop sharepoint projects on the same machine with those accounts.
Also I wanted to know about version controls system like svn availability for sharepoint 2010.
in our company each developer has own development server, but some time we work simultaneously on the same server. I don't know why you need separate slq server, for development purposes SharePoint works fine with SQL express installed on the same machine. But if you wish you can use separate SQL server of course. If you would like to use specific accounts for SharePoint it is a good practice. Look at this post, there is some information about typical SharePoint accounts pool.
About simultaneous development. If you work with Visual Studio, not configuration, when you are deploying solutions server will restart IIS each time, is is not so useful for normal development of few employees. Also if you will decide to work like this, my advice to work in different web applications for each developer it will allow you more useful debug capabilities. You will not interrupt each other because of attaching to the same process w3wp. But notice, SharePoint is flexible and extendable environment, you can do I lot of things just with configuration and JavaScript development by SharePoint Designer. So if you will work most of time by configuring it will be possible successfully work on the same server for whole team.
About source control. If you are developing with Visual Studio, TFS is for you, or any other source control system, like svn or git. If you are develping by configuring with SharePoint Designer, I advice you to store some reusable functionality also withing TFS, by just copying. For other content you can turn on versioning on SharePoint libraries, so each your modification will be stored with comments if you wish.
I've just tried out TFS 2010 today, along with Project 2010 and VS 2010. Only Later realized that without Sharepoint, TFS is only configured as Basic. This reduces it's functionality as oppose to what I've seen during VS2010 product launch. Sadly I can't find any alternative but to get a trial copy of Sharepoint to see if it serve my purpose. Well, apparently Sharepoint only comes with x64 edition. I'm not formatting any machine to x64 just to give this a try. So, after some reading up, I found that Project Server is actually based on Sharepoint. Now I wonder is whether TFS can be configure to connect to Project Server?
If it's possible, would the setting be much different that Sharepoint's?
And what am I missing from this setup as oppose to Sharepoint's?
Based on Sharepoint != Sharepoint. I think that Project Server is just a subset of Sharepoint functionality. Also, basing Project on Sharepoint allows for some really tight integration into your portal. To answer your question, I don't think you still will get your fully featured TFS without Sharepoint Proper.
FYI - Sharepoint 2007 (or 3.0 or whatever it is) is not x64 only, but will run on x86. TFS 2010 will go full feature on 2007
Sharepoint 2007 Trial
To answer what you are missing:
Reports
Project Portal
TFS Web Access
That's about it. You still get 90% of the features with your current deployment without SharePoint. Tommy is right about MOSS 2007, it comes in 32-bit and will give you all features. Project Server runs on top of SharePoint as a shared service provider. Traditionally MS releases a power toy to integrate TFS with Project Server. They said they would go over this at TechEd, which just happened about a week ago.
Also, I suspect the integration with Project Server 2010 will be better, but then you will have to run SharePoint 2010 :(
In my opinion, TFS has enough to run most projects by itself and you can use the client version of MS Project for critical path anaylsis, etc.
Use Windows Sharepoint Services for Windows 2003 & Windows 2008:
http://technet.microsoft.com/en-us/windowsserver/sharepoint/bb400747.aspx
For Windows Server 2008 sp2 and Windows Server R2, use SharePoint Foundation 2010:
http://www.microsoft.com/downloads/details.aspx?FamilyID=49c79a8a-4612-4e7d-a0b4-3bb429b46595&displaylang=en
Both are free.
I'm not formatting any machine to x64
just to give this a try.
Why not use VMWare Server, Hyper-V, Virtual Box or some other virtualization software to run the pre-made demo/trial/lab VHD's - no formatting, no installation, no setup, more hair.
Link
I am in a situation where the corporation has just recently upgraded to TFS 2008. They have no intention of upgrading to TFS 2010 at this time. As a development group, we've moved to Visual Studio 2010 this week. As with any large corporation, we cannot get our own environment created to install TFS 2010. Steps on too many toes, and isn't corporate standard. Etc.
I want to take full advantage of the new testing features in relation to the new UI Testing and other features. This appears to require TFS 2010. So my "dream" is to do my daily work at the office and write tests, but at night, have my code synchronized with my TFS 2010 server at home and run automated builds with the full testing capabilities enabled.
So is there is best practice for this? I've read up on the Workspace theory and the binding issues that are involved and that sounds the biggest hurdle to overcome.
Possible Solution - Create two workspaces $/WorkProject and $/WorkProject-Mirror and use a custom application using FileSystemWatcher to kick off a job that synchronizes code changes and a custom rewrite of the bindings. Use job on work laptop and home machine to allow bi-directional binding.
Research to see if TFS Integration Platform will help with this
You are correct the new testing UI (Test Manager 2010) requires TFS 2010, you are also correct that you can use the TFS Integration Platform between a TFS2008 & TFS2010 server. Then use test manager on the 2010 server.
All the above should be easy, the tough part will be the bindings in the solution file. I would suggest you have a second one created that points to your TFS2010 server so that you can open the correct solution file for the correct environment without stepping on your co-workers toes.
I think the two workspace route is overkill, it's just a solution file you need.
I wonder if you could use a read-only account to perform a get from TFS2008 and then do a check-in to your TFS2010 with a more-privileged account. I'm sure those two things and a little clever PowerShell scripting could get you what you're looking for.
I would encourage you to write a second utility to monitor that this script continues to work and to notify you if it detects a failure or something.