TFS 2012 Installation - TFS Sharepoint Extension (Part-3)

This is a continuation of the following posts:

• TFS 2012 Installation - Build out initial farm (Part-1).  
• TFS 2012 Installation - Adding Additional App Tier (Part-2)

The steps here illustrates the installation and configuration of TFS Extension for SharePoint (2010).  This assume you have an existing SharePoint farm you want to integrate TFS with.

1. For DOMAIN\_TFSService account, grant the following rights:
   - Add this account to the Farm Administrators group in Sharepoint- Add this to the  "Policy for Web Application" for that web app
2. Launch the tfs_sharePointExtensions.exe file from the SharePoint Extensions folder to install only the Team Foundation Server Extensions for Sharepoint Products.  NOTE:  If your SharePoint consist of multiple servers, you will need to perform the first SharePoint extension install on the server that hosts the Central Admin.

Provide the TFS server url and the SharePoint Web App URL

When you are done with the initial server, continue to install TFS SharePoint Extension on the remain SharePoint WFE server(s).

 Once you are done with the above, you will need to configure the TFS server to talk to SharePoint:

1. Launch the TFS Admin Console from the TFS Server

2. Under Application Tier, select  SharePoint Web Applications

3. Click Add under the SharePoint Web Applications category and provide the info as shown below:

TFS 2012 Installation - Adding additional App Tier (Part-2)

This is a continuation of TFS 2012 Installation - Build out initial farm (Part-1).  The steps here illustrates how you would add an additional app tier to your TFS farm.

1. Please refer to the previous post for service account requirements.
2. If your SQL, SSRS, and SSAS are located on a different server, you need to Install SQL Client Tools first by:
• Runnning the SQL setup on the TFS machine
• Select Client Tool Concectivity & Client Tool SDK
• Install
3. Run "tfs_server.exe" as Administrator
4. Select Application-Tier Only and click Start Wizard and follow the wizard:

Enter the database server name and click List Available Databases.  Select the TFS_Configuration database and click Next.

TFS 2012 Installation - Build out initial farm (Part-1)

I just finished implementing a new TFS 2010 farm.  This farm consist of two App Tier servers.  The data tier consist of a SQL 2008 R2 cluster.  The below instruction is for creating your initial farm or the very first server:

1. Service Accounts:
• Domain\_TFSSetup
  - Add to server's local Admin Group
  - Grant SQL "severadmin" role
• Domain\_TFSService
  - Add to local security policy "Log on as a service" on the app tier server.
  - Grant db-owner and db-crate for any databases that Team Foundation Server uses
• Domain\_TFSReports
  - Add to local security policy "Log on as a service" on the app tier server.
  - Grant TFSWareHouseDataReader on the report server
  
2. If your SQL, SSRS, and SSAS are located on a different server, you need to Install SQL Client Tools first by:
• Runnning the SQL setup on the TFS machine
• Select Client Tool Concectivity & Client Tool SDK
• Install
  
3. Run "tfs_server.exe" as Administrator
   
4. Select Advanced and click Start Wizard and follow the wizard:

Enter the SQL server name or the cluster alias

It is a good idea to have a service account.  For me, I have an AD account called _TFSService

If you have SSRS setup, enter the requested info.  Otherwise, you can skip it for now.

If you have SSAS setup, enter the requested info.  Otherwise, you can skip it for now.

You can create your first Project Collection if you want or do it later

Userful Powershell / STSAdm Commands

During my SP2010 upgrade process, on of the challenges I have is constently running PowerShell scripts and piping the results to a file so that I can parse and create new scripts against the results.  I have been doing it using the old way... like using "> test.txt".  Than I found ou that you can use the CovertTo and Export options with better and consistent results.  Below are a few examples:


TEST-SPContentDatabase -name MyContentDB -webapplication http://intranet -serverinstance MyDBServer  | ConvertTo-Html | Out-file intranet.html


TEST-SPContentDatabase -name MyContentDB -webapplication http://intranet -serverinstance MyDBServer  | ConvertTo-CSV -Delimiter "~" | Out-file intranet.csv


TEST-SPContentDatabase -name MyContentDB -webapplication http://intranet -serverinstance MyDBServer  | Export-CLIXML intranet.xml

Other PowerShell Commands useful around Upgrade

Get-Command -noun SP* - similar to stsadm -help

Test-SpContentDatabase – discussed in this post
Upgrade-SPContentDatabase – to resume failed upgrades
Upgrade-SPEnterpriseSearchServiceApplication – Upgrade Search
Upgrade-SPSingleSignOnDatabase – Upgrade SSO
Mount-SPContentDatabase – Used to attach a database or multiple parallel databases to the farm. Essentially is nearly the same as the STSADM –o addcontentdatabase.   If you‘re doing parallel content database attach for example, this PowerShell method is recommended. You‘d simply run each ofthese in different command/management windows.
Upgrade-SPProjectWebInstance – Upgrade Project Server databases. Obviously this only applies with Project Server deployments, but I know there are definitely many out there.
Upgrade-SPEnterpriseSearchServiceApplication – Upgrade the Search Service Application Instance. This commandlet it designed to upgrade the content sources and configuration of search and to upgrade it into the new service application.
Set-SPSite  -- Can use this command to setup site collection admins

STSADM Commands useful around preparing for Upgrade

stsadm -o ExportIPFSAdminObjects

stsadm -o MergeContentDB

stsadm -o EnumAllWebs

stsadm -o DatabaseRepair [-deletecorruption]

stsadm -o DeleteSite [-force] [-gradualdelete]

stsadm -o DeleteWeb [-force]

stsadm -o ForceDeleteList

stsadm -o VariationsFixupTool

stsadm –o Upgrade (Used for build to build upgrades, including service packs.)