Geeks With Blogs

Disclaimer: The views expressed on this blog are my own and do not necessarily reflect the views of my employer.

Creative Commons License

Check out my profile!

INETA Community Speakers Program

Follow enriquelima on Twitter
Locations of visitors to this page

Intentional Thinking Enrique Lima

The good on the story is that migrations just keep on getting better, and actually never have been bad.  This time around there was a curveball, and it came from the SharePoint side of things.

SharePoint, it is no secret, can be temperamental when it comes to patches and cumulative updates.  Add to that temperamental side a version migration/upgrade, now this just elevated concern and risk.

Now, for the time being, I had to do what was best for the situation, and that warranted an uninstallation, and rebuild with WSS 3.0 and not SharePoint Foundation.  After all, the most important part of this was access to the information that was stored in the Content DB. There is a lot of shoulda, coulda, woulda.  But success was achieved.

Now, another roadblock, this time, since SharePoint extensions had been configured to SharePoint Foundation 2010, and that was taken away … well, what to do?  I have seen this asked on the MSDN Forums quite a bit.

Here is the lesson learned. TFS deploys web services and additional components to SharePoint.  And how would this be done you ask?  How about using WSP files (SharePoint solutions)?  That would be the path and the way to go.

Where are the WSP files?  I used the C:\ drive for deployment, therefore the path is C:\Program Files\Microsoft Team Foundation Server 2010\Tools\Templates.

Combine that location with the WSP files, and use stsadm to deploy.




If you do not have the “12 hive” in your path, then

  1. Open a command prompt as Administrator
  2. Change directory to %programfiles%\Common Files\MIcrosoft Shared\web server extensions\12\bin
  3. execute stsadm –o addsolution –filename <path to one of the files above>, example C:\Program Files\Microsoft Team Foundation Server 2010\Tools\Templates\Microsoft.TeamFoundation.SharePoint.wsp.
  4. Repeat step 3 for all WSP files.
  5. Next comes the process of deploying the solutions to take effect and “unleash their goodness”, yeah or being technical, get the web services for integration in place.
  • Option 1: use stsadm –o deploysolution –name <name of solution>, there are several parameters to work with.
  • Option 2: use Central Admin to deploy. This means, once you access Central Admin, go to Operations, then from Global Configuration, click on Solution Management.  At this point, you will need to click each of the deployed solutions in the previous steps, make sure they deploy successfully.
Next, we will look into the Configuration from Team Foundation Administration Console.
Posted on Thursday, August 19, 2010 9:31 PM | Back to top

Comments on this post: Another TFS 2008 to TFS 2010 migration, more lessons learned. Part 1 of 2.

# re: Another TFS 2008 to TFS 2010 migration, more lessons learned. Part 1 of 2.
Requesting Gravatar...
Thanks a lot!
Extremely helpful post, I was stuck on that issue for hours!
Left by Alfonso Garcia on May 19, 2011 9:33 PM

# re: Another TFS 2008 to TFS 2010 migration, more lessons learned. Part 1 of 2.
Requesting Gravatar...
I'm haveing big trouble trying to connect. For some reason under central administration the option for Operations is nowhere to be seen. Why would this be?
Left by Byron Phillips on Aug 08, 2012 11:20 AM

comments powered by Disqus

Copyright © Enrique Lima | Powered by: