1- tfsconfig prepSql /sqlInstance:<ServerName>
where ServerName is the name of the new sql instance. Repeat this command for all new sql instances in your deployment

2- tfsconfig remapdbs /sqlinstances:<ServerName,ServerName2,..> /databasename:<ServerName;Tfs_Configuration> /analysisInstance:<ASServerName>
where:
ServerName is the name of the sql instance hosting configuration db
ServerName2,ServerName3, ..,ServerNameN are the name of any other sqlinstances in your deployment, you must specify all the instances in /sqlInstances option separated by commas
AnalysisInstance is the name of the sql instance hosting Analysis database

3- tfsconfig accounts /add /accountType:ApplicationTier /account:<domain name>\<user name> /password:<domain password> /sqlInstance:<ServerName> /databasename:Tfs_Configuration
where ServerName is the name of the sql instance hosting configuration db

4- tfsconfig accounts /add /accountType:ReportingDataSource /account:<domain name>\<user name> /password:<domain password> /sqlInstance:<ServerName> /databasename:Tfs_Configuration
where ServerName is the name of the sql instance hosting configuration db

5- tfsconfig RegisterDB /sqlInstance:<ServerName> /databasename:Tfs_Configuration

6 – In addition, if the Application Pools for Team Foundation Server were originally configured as Network Service, the Identity of each of the Team Foundation Server application pools also need to be changed to the appropriate domain account (as specified in the tfsconfig accounts command above), otherwise, Team Foundation Server will still fail to connect to the Tfs_Configuration database and TFs clients will not be able to connect to the Tfs Web Services.

Advertisements