Addition to TFS 2010 Installation Guide: Migrating SharePoint content in preparation for TFS2010 upgrade

As with any major server based upgrade, it is recommended that you test the upgrade prior to doing the production upgrade.  For TFS 2010, to do this you will need to setup a separate environment that you can upgrade.  We have made this easier to accomplish than in previous releases.  You only need to copy the necessary databases (TFS and WSS content) to a separate set of hardware and run the TFS Upgrade Wizard.   You no longer need to “clone” the existing system. 


However, there is an important set of steps to add to our TFS 2010 Installation Guide.  The guide provides a checklist for performing the upgrade (see "Checklist: Upgrade from Visual Studio Team System 2008 Team Foundation Server").  Here are some additional instructions that you need to follow if you want to first copy your WSS content to another server to use in the upgrade test.   I recommend you migrate/copy the WSS content to the new server prior to running the TFS 2010 upgrade test by following these additional instructions.  You can insert these steps right after the step "Prepare Portal Server" in the Upgrade checklist.

Install Windows SharePoint Services 3.0.  If you setup a copy of your existing WSS content for as part of a migration based upgrade you need to install Windows SharePoint Services 3.0 by following the instructions found in the Prerequisites section under "How to: Install SharePoint Products and Technologies on Windows Server"

For more information see: How to: Install SharePoint Products and Technologies on Windows Server" topic in the TFS Install guide

Restore the SharePoint content database.  Backup the WSS Content database from your previous TFS instance and restore it onto the Data Tier server you will be using for TFS 2010.


Attach the restored WSS Content database to WSS.


To perform this step on Windows Server 2008, you must open an elevated command prompt. This step is required even if you log on with administrative permissions. To open an elevated command prompt, click Start, right-click Command Prompt, and then click Run as Administrator.

1.      Open a Command Prompt window on the server that is running SharePoint Products and Technologies.

2.      Change directories to the following location:

Drive:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\bin\

3.      At the command prompt, type the following command, replacing the placeholders as specified:

stsadm.exe -o addcontentdb -url http://WSSServerName/sites -databasename contentdatabase  -databaseserver SQLServerName


WSSServerName is the name of the server that is running SharePoint Products and Technologies

Contentdatabase is the name of the WSS content database

SQLServerName  is the name of the data tier server that is running SQL

4.      At the command prompt, type the following command, replacing the placeholders as specified:

stsadm.exe -o addpermissionpolicy -url http://WSSServerName  -userlogin Domain\UserName -permissionlevel "full control"

WSSServerName is the name of the server that is running SharePoint Products and Technologies

Domain\UserName  is the domain and user name of the account used during setup SharePoint Products and Technologies.

If you are installing SharePoint on the Application Tier server you can skip the section in the checklist called “Install and Configure Extensions” as this will be done for you during the Application Tier installation.  If you are using a separate server to host the SharePoint site, then you will need to follow the instructions in that section.



Comments (7)
  1. Martin Hinshelwood on Unable to connect to TFS using HTTPS over the Internet from behind ISA Ed Glas

  2. Dev10 Beta 1 has shipped! We are really excited to have you trying our Beta and giving us feedback. The

  3. says:


    Trying to move the Team Portals from TFS2008 to TFS 2010RC.

    We have successfully imported the tfs-stuff.

    We have backed up the old WSS_Content and restored it over the TFS2010 WSS_Content. Had tvo stop the Timer Service to succed…

    Now when vi run the stsadm.exe it does som work and then ends with a message saying that there already exists a WSS_Content databse.

    We arte stuck here.

    What shall we do?


    Claes Wedin

    Solid Park AB, Stockholm, Sweden

  4. sanwuch says:

    Trying to migrating sharepoint content from TFS2005 to TFS2010 onto a new machine.  Got to the point to follow Step #3 on "Attach the restored WSS Content Database to WSS.", and got message..

    The pre-upgrade scan tool has not yet been run on this database SPContentDatabaseName=sts_content_tfs Parent=SPDatabaseServiceInstance.  You must run the pre-upgrade scan tool before you can continue with the upgrade process.  Run the tool from the following path c:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12binprescan.exe.

    ..Then tried to run prescan on the new machine, and got "This program requires Windows SharePoint Services v2.”

    So, am I supposed to run prescan on the old machine first?

  5. Jarno says:

    Hi Martin,

    Could you please explain what URL I should use with addcontentdb, e.g. http://computername/ or http://computername/sites.

    I've seen some examples of addcontentdb using both, and I don't want to end up with /Sites/Sites/…

    Tomorrow I'm finishing the migration to TFS 2010 – bit nervous about it still. 😉



  6. Hello Brian,

    This article is a godsend!!! I read several articles and tried several methods and was unable to perform the upgrade. Turns out I was missing the "/Sites" from the URL parameter for the STSADM to attach content database. Thanks for this wonderful article!!


Comments are closed.

Skip to main content