Let's discover what means and what we have to do to install, configure and customize the Microsoft Team Foundation Server 2013

1. Davide Benvegnù
InternationalDevelopmentManager – Aruba.it
DotNetToscana StaffMember
davide.benvegnu@gmail.com- blog.dbtek.it
www.davidebenvegnu.com- @davidebenvegnu
Install, Configure and
Customize TFS 2013
ALM Deep dive with TFS 2013
#vsalmdeep

2. Session Lineup
Installation / Update
Configuration
Customization
#vsalmdeep

3. Event Sponsor
#vsalmdeep

4. TFS 2013 Installation
#vsalmdeep

5. TFS Installation requirements
#vsalmdeep
 Server OS requirements:
 64 bit versions of Windows Server >= 2008 R2 SP1
 Does not support the Server Core installation
 Client OS requirements:
 64-bit or 32-bit versions of Windows >= 7 SP1
 Doesn’t support SharePoint Products integration,
reporting and TFS proxy
 It supports virtualized environments

6. TFS Installation requirements
#vsalmdeep
 Database requirements:
 SQL Server 2012 SP1 CU2 and SQL Server 2014
 Express, Standard and Enterprise
 For TFS: Database Engine Services, Full-Text and
Semantic Extractions for Search
 For reporting: Reporting Services, Analysis Services
 Microsoft does not support any direct operations
against the TFS databases

7. TFS Installation requirements
#vsalmdeep
 SharePoint requirements:
 SharePoint 2010 (Foundation, Standard, Enterprise)
 Not supported on Windows Server 2012 or
Windows Server 2012 R2
 SharePoint 2013 (Foundation, Standard, Enterprise)
 SP1 adds support for Windows Server 2012 R2
 With Enterprise: 5 Dashboards Excel-based
 With others: 2 Dashboard based on SQL Server
Reporting Services

8. TFS Upgrade requirements
#vsalmdeep
 You can upgrade every version of TFS 2010 and TFS
2012 to TFS 2013
 Direct upgrade from TFS 2008 is not supported
 You may have to upgrade other components to meet
the “normal” installation requirements
 3 Upgrade types:
 Basic: if you have no Sharepoint and no Reporting
 Standard: Application tier use the same hardware
 Advanced: Application tier will use new hardware

9. TFS Environment
#vsalmdeep
Number of users Configuration CPU Memory Hard disk
Fewer than 250 users
Single-server (Team
Foundation Server and
the Database Engine on
the same server).
1 single core processor
at 2.13 GHz
2 GB
1 disk at 7.2k rpm (125
GB)
250 to 500 users Single-server.
1 dual core processor at
2.13 GHz
4 GB
1 disk at 10k rpm (300
GB)
500 to 2,200 users
Dual-server (Team
Foundation Server and
the Database Engine on
different servers).
This row is for Team
Foundation Server.
1 dual core Intel Xeon
processor at 2.13 GHz
4 GB
1 disk at 7.2k rpm (500
GB)
This row is for the
Database Engine with
500 to 2,200 users.
1 quad core Intel Xeon
processor at 2.33 GHz
8 GB
SAS disk array at 10k
rpm (2 TB)
2,200 to 3,600 users
Dual-server.
This row is for Team
Foundation Server.
1 quad core Intel Xeon
processor at 2.13 GHz
8 GB
1 disk at 7.2k rpm (500
GB)
This row is for the
Database Engine with
2,200 to 3,600 users.
2 quad core Intel Xeon
processors at 2.33 GHz
16 GB
SAS disk array at 10k
rpm (3 TB)

10. DEMO
TFS Installation Wizard
#vsalmdeep

11. TFS Install / Upgrade guide
#vsalmdeep
You can find all the info you need about TFS installation
and upgrade in the official guide (web & chm formats):
http://msdn.microsoft.com/library/dd631902.aspx
(http://bit.ly/1n3GyhL)
http://www.microsoft.com/en-
us/download/details.aspx?id=29035
(http://bit.ly/1o9rYHv)

12. TFS 2013 Configuration
#vsalmdeep

13. TFS Configuration
Two “layers” of configuration:
 Via Web Portal
 To configure all the web portal related stuff
 To manage the web portal Access levels
 To load “Web Access Extensions” (JS)
 To manage collections and collections’ security
#vsalmdeep

14. TFS Configuration
 Via TFS Administration Console
 To configure the Application Layer
 Collections, Team projects
 Security
 […]
 To configure the Service Extensions and Integrations
 SharePoint integration, Build, Backup, …
Some configs are shared between the two tools
#vsalmdeep

15. DEMO
TFS Web Administration
TFS Administration Console
#vsalmdeep

16. TFS Configuration
You can also use the “TFSConfig” command-line tool.
But, to operate correctly, TFSConfig must be able to
connect to all the servers and services used by your TFS
deployment.
For more information:
http://msdn.microsoft.com/en-us/library/ms253116.aspx
#vsalmdeep

17. TFS 2013 Customization
#vsalmdeep

18. What can be customized?
 TFS
 Process templates (PT)
 Work item types (WIT)
 Test Plans and Test Suites (coming soon in Update 3)
 Build templates
 Project portals
 VSO
 Process templates customization coming (very)
soon – Announced as work in progress on May 20th
#vsalmdeep

19. What can be customized?
#vsalmdeep

20. Process Template customization
#vsalmdeep
Plug-ins define the tasks to perform when you create a team project, most of
which configure defaults, set permissions, and upload object files.

21. Tools used for PT Customizations
 Visual Studio Professional (or upper)
 It has the “Process template Manager”
 TFS Power Tools
 Available on Visual Studio Gallery under MSDN
 Enables the “Process Editor” under “Tools” menu
 TFS Team Project Manager
 Community project available on Codeplex
#vsalmdeep

22. PT customization normal flow
To customize a process template, you first download an
existing or blank process template, modify or add files,
upload the process template files, and then verify your
changes.
#vsalmdeep

23. Tools used for WIT Customizations
 witadmin
 CLI tool
 TFS Power Tools
 Available on Visual Studio Gallery under MSDN
 Enables the “Process Editor” under “Tools” menu
 TFS Team Project Manager
 Commuity project available on Codeplex
#vsalmdeep

24. WIT customization normal flow
To add rules or add a custom field, export, edit, and then
import the WIT definition file.
#vsalmdeep
Only if you
don’t use
the TFS
Power Tools

25. WIT Customizations best practices
 If possible, use an already defined field. Use of an
existing field supports cross-project reporting
 No more than 1,024 fields in each project collection
and no more than 1,024 unique reportable fields in all
project collections
 Merged fields count as one reportable field
 Use systematic naming conventions when you label
fields for reporting
 Remember: editing or adding fields impacts existing WI
#vsalmdeep

26. DEMO
TFS Customizations
#vsalmdeep

27. Recap
 Team Foundation Server 2013 installation is quite
simple and fits almost every kind of need or
organizational structure
 You can configure TFS to integrate itself with other
existing company tools
 You can customize a lot of TFS items and aspects, to
adapt it to your own processes and work models
#vsalmdeep