Steps to Upgrade to TFS 2010 onto new hardware
Important: Install the hotfix mentioned here before running the upgrade wizard:
The steps below outline how to upgrade your TFS server to TFS 2010 when using new hardware. This will let you keep your production server up an running while you poke around with TFS 2010.
Note that if you do not plan to have both your production server and test server up at the same time, you can skip a lot of these steps. You don't need duplicate Reporting Services and SharePoint, for example. You also will not want to restamp re-stamp the TFS instance, so you can skip step 15 below.
1. Backup TFS databases
a. For TFS 2005 and TFS2008: TfsActivityLogging, TfsBuild, TfsIntegration, TfsVersionControl, TfsWorkItemTracking, TfsWorkItemTrackingAttachments
b. For TFS 1010: All DBs that start with TFS_ : Tfs_Configuration, Tfs_<CollectionNames>, Tfs_Warehouse, Tfs_AnalysisServices
2. Backup RS databases
a. ReportServer, ReportServerTempDB
3. Backup SharePoint content Database (Only need the one with TFS content)
a. STS_Content_TFS ( or WSS_Content_TFS, or WSS_Content or STS_Content)
4. Install SQL RS 2008 (optional: you can opt-out of Reporting in TFS 2010)
5. Install SharePoint WSS 3.0 SP1 (optional: you can opt-out of SharePoint in TFS 2010)
6. Configure SharePoint for Server Farm (optional)
a. Either Use the SharePoint wizard
b. Or the cmdline: (as Administrator, Change directory to (%commonprogramfiles%\MicrosoftShared\Web Server Extensions\12\bin”)
i. stsadm -o setconfigdb -databaseserver <datatier\instance> -farmuser <wssAccount> -farmpassword <wssAccountPassword>
ii. psconfig -cmd adminvs -provision -port 17012 -windowsauthprovider onlyusentlm
iii. stsadm -o extendvs -exclusivelyusentlm -url https://<machineName>:80 -ownerlogin <wssAccount> -owneremail "admin@localhost" -sitetemplate sts -description "Default Web Site"
iv. stsadm -o siteowner -url https://localhost:80 -secondarylogin <currentUser>
v. iisreset
7. Restore TFS databases to new data tier
8. Restore RS databases to new data tier (optional)
9. Configure Reporting Services to use restored RS databases (optional)
a. Open Reporting Services Configuration Manager
b. Connect to RS instance
c. Database page -> Change Database -> Choose an existing report server database -> Next -> Next -> [Select restored RS databases] -> Next -> Next -> Next -> Finish
d. Web Service URL page -> Change and then unchange the Virtual Directory textbox ‘ReportServer’ so the Apply button gets enabled. Click Apply.
e. Report Manager URL page -> Change and then unchange the Virtual Directory textbox ‘Reports’ so the Apply button gets enabled. Click Apply.
f. Encryption Keys page -> Click ‘Delete’ button to delete encrypted content. Click Yes to the popup.
10. Restore WSS Content database (optional)
11. Attach WSS Content database to SharePoint server (optional)
a. Open cmd window (as Administrator, Change directory to (%commonprogramfiles%\MicrosoftShared\Web Server Extensions\12\bin”)
i. stsadm -o addcontentdb -url https://<machineName>/sites -databasename <WssContentDatabaseName> -databaseserver <datatier\instance>
ii. stsadm -o addpermissionpolicy -url https://<machineName> -userlogin <currentUser> -permissionlevel "full control"
iii. iisreset
12. Install TFS.
13. Select Upgrade Wizard.
a. On Reporting Services page, Point to new RS instance
b. On Sharepoint Settings page, Point to new SharePoint server
14. Open Admin Console, click ‘Configure URLs’ on Application Tier page to fix the public URL to reference the local machine. The safe default option is to use 'localhost'.
15. If this is only a test server, you will want to re-stamp TFSso clients do not confuse this server with the live production server. Ignore this step if this is your production server.
a. Tfsservicecontrol quiesce
b. tfsconfig changeserverid /sqlinstance: <dataTierName> /databasename:Tfs_Configuration
c. tfsconfig registerdb /sqlinstance: <dataTierName> /databaseName:Tfs_Configuration
d. tfsservicecontrol unquiesce
e. Open TFS Administration Console, navigate to SharePoint Web Applications node. Select the Web application in the list. Click the 'Repair Connection' link on the right.
16. Fix SharePoint access grants which were broken after restamping TFS in previous step.
a. Open Admin Console, Navigate to SharePoint Web Applications page. Click on local SharePoint Web Applications entry. Click hyperlink ‘Repair Connection’.
17. Update Process Templates to Dev10
Comments
Anonymous
February 23, 2010
Hi, I tried installing TFS 2010 RC and importing from our production TFS 2008. Everything worked fine except the TFS Portals... So I decided to remove TFS and WSS and do an Upgrade instead. I followed your steps in the above blog, and everything went fine. The only thing I changed was SharePoint DB, which was set to 0012srvwtfs002Microsoft ##SSEE which I changed to 0012srvwtfs002, since our database is the default in this server. Problem: I can see all Sites in WSS Admin Console -> List Sites, but I cannot open them in IE. We just get error HTTP 404.... Any clue? Could it be a permission issue? TIA CLaes Wedin, Solid Park, Stockholm, SwedenAnonymous
August 17, 2010
You may need to run Internet Explorer with elevated (As Administrator) privileges. I would encourage you to post your issues on the TFS Setup forums so others can help and benefit from answers. social.msdn.microsoft.com/.../threadsAnonymous
February 15, 2011
I migrat upgrade TFS 2005 to TFS2010 by above guide, all things go well, when config it in TFS admin console, Sharepoint Production has warnings as bollows:
[Warning] TF252012: A SharePoint site could not be verified for the following team project: Test. No SharePoint site could be verified with the following address: http://server/sites/Test. After the operation is complete, verify that the SharePoint site is displaying data for the corresponding team project, or manually modify the project portal settings as needed. [2011-02-15 08:54:07Z][Warning] TF252014: A SharePoint site could not be created at the following location: http://liuho04-newtfs/sites/DefaultCollection. The server returned the following error message: TF249064: The following Web service returned an response that is not valid: http://server/_vti_bin/TeamFoundationIntegrationService.asmx. This Web service is used for the Team Foundation Server Extensions for SharePoint Products. Either the extensions are not installed, the request resulted in HTML being returned, or there is a problem with the URL. Verify that the following URL points to a valid SharePoint Web application and that the application is available: http://server. If the URL is correct and the Web application is operating normally, verify that a firewall is not blocking access to the Web application.. To address this error, open the Team Foundation Administration Console and make sure that the settings for the SharePoint Web applications that supports this team project collection are correct.
what should i do to fix the problem?