Category: TFS

Reporting on TFS

Today during the Deep dive in Visual Studio and MTM course we were covering the types of reports that can be produced in TFS. Either for tracking your tasks or your tests progress, these reports are produced from the same place and with the same mechanism. Let’s take a look to the next picture:

As we all know, the SQL Server database that is in TFS is in charge of storing and producing the right KPIs for our reports. Most of the information we query is directly extracted directly from the database where our project is hosted (our project collection DB). But most of the reports are produced directly not from the project DB but from the OLAP data cube that is managed by SQL Server Analysis Services.

So said that, we have two extra Data Bases, one is the OLAP Cube, TfsAnalysis data base, that is mainly use to generate reports in Excel or to export reports to SharePoint wherever you have an integration with it.

The other database, TfsWarehouse, is being used to generate reports through SQL Server Reporting Services, which give us the chance to generate also our own reports using the Report Designer tool. This reports are easily accessible through the Web Access of our team portal or from our Team Explorer in Visual Studio.

Either for TfsAnalysis or TfsWarehouse databases, you should have permissions to them both in order to create this reports.


SQL Server Reporting Services

When you finally get access to SSRS, you would be able to access to the folder above represented, and, depending on the project template that your team is using for the project, you will see less or more reports. But remember, the report builder is there!

Some of the reports are the next:

  • Test and bug reports

    • Test Case Readiness
    • Test Plan Progress
    • Bug Status
    • Bug Trends
    • Reactivations
  • Project Management Reports:

    • Backlog Overview
    • Release Burndown
    • Sprint Burndown
    • Velocity

All these reports and more are explained here

Probably the test case readiness is one of the most detailed and spectacular, showing us the next information:

This is an extended version of the simple chart that we usually take from the Microsoft Test Manager (Plan tab, Results menu), where we can analyse the Test Result Summary of our tests executions by tester, by suite, by configuration and answer to questions such as:

How much testing has the team completed?

How many tests are left to be run?

How many tests are passing?

How many tests are failing?

How many tests are blocked?

Why tests are failing?

Are new issues going into production?

Is there any regression on the failing tests?

Last but not least, another way to create reports in TFS is using Microsoft Excel.

These awesome pivot tables can be generated from either the Team tab in Microsoft Excel or from Visual Studio (straight from a query).

If you are creating the report from Visual Studio Team Explorer, you basically have to look for the query you want to use to generate the report, and then right click and create report in Excel.

If you decide to create the Report from the OLAP Cube, in Microsoft Excel there is a tab called “Data”. There you will find an action called “From other sources” where you can select “From Analysis services”

After you chose this option, a wizard will be introduce to you:

  1. Connect to the DataBase server
  2. Select DataBase and Table (Tfs_Analysis will be ours)
  3. Give it a name and point it to our file
  4. Report will be generated

I hope this blog post has thrown some light on what reports are available in TFS and do not forget… In terms of having these reports, you have to generate the data first! So make sure you create your work items such as tasks, user stories, test cases, and others properly or reports will be useless J


Eduardo Ortega

How to update to TFS 2013.4

​Step 1: Download the Visual Studio Team Foundation Server 2013 Update 4 from your MSDN subscription or Microsoft downloads

Step 2: Start the installer:

<Image not available>

Step 3: Let the installation be. It will copy the needed components for the update

<Image not available>

Step 4: Follow the Team Foundation Server Upgrade starting with clicking “Next”
<Image not available>

Step 5: Before doing any upgrade (as happens for example in the TFS2010 to TFS2013 migration), you should do a DataBase backup of the main databases. So click where you read “Click here to launch the Database Backup Tool”.
<Image not available>

Step 6: Once finished. Go back to the previous screen and check “By checking this box, I confirm that I have a current backup”.

Step 7: Provide the settings for the application Tier. This means, which system account you want to use for the Application Tier services. By default it will use the Network Service and NTLM authentication.

<Image not available>

Step 8: Here is your moment to set up the Reporting Services. Even if you don’t have reporting services set up previously, you can do it now. If they are already in place just populate properly the fields. Example below:
<Image not available>

In the next step, the database will show up automatically in the databases list. Just make sure you Test the connection to it.

Step 9: Proceed on the same way with the Analysis Services. In case the Analysis Services is stopped, make sure it’s running.

Step 10: Report Reader Account. In this step we should provide a user account as System or Network Services accounts cannot be used here.
<Image not available>

So that’s it! We have skipped the SharePoint configuration as for this instance we don’t have such services set up. Just go to review and click on Configure.

<Image not available>

<Image not available>

Now you are ready to enjoy the new features on TFS 2013 Update 4. I recommend you to see what’s new on TFS2013.4.

But just a sneak peak, check the new access levels from the configuration console in the Team Web Access:

<Image not available>

Happy upgrade!

Eduardo Ortega

Team Foundation Server 2013 Access Levels

*Info updated here:

The amazing world of licenses…when to use them, how to use them, how many computers, how many users, how many services available, on premises or online… These are few of the many questions that I receive every time a Dev or Test teams need to increase its number or its disciplines.

Let’s explain first how it works for those users that work with Team Foundation Server 2013 (the On-Premises server).

TFS 2013.3 Access Levels

First, a user, whatever kind of user is, needs to access to TFS2013 Update 3, so we need to specify which features need to get accessible. For that we have 3 levels (more info here):

  • Limited (Stakeholder access level)

    • View My Work Items
  • Standard (Basic access level)

    • View My Work Items
    • Standard Features
    • Agile Boards
    • Backlog and sprint planning tools
    • Chart Viewing
  • Full (Advance access level)

    • View My Work Items
    • Standard Features
    • Agile boards
    • Backlog and sprint planning tools
    • Request and Manage Feedback
    • Test case management (including running tests)
    • Team rooms
    • Agile Portfolio Management
    • Chart Viewing
    • Chart Authoring

Now that you know more about the licensing, let’s differentiate the licensing on TFS2013.3 from TFS2013.4 and Visual Studio Online.

In TFS2013.3 the access levels were Limited, Standard and Full.

In TFS2013.4 the access levels are Stakeholder, Basic and Advance.

In Visual Studio Online the levels are Stakeholder, Basic, Professional, Advance and MSDN Subscribers.

TFS2013.4 Access Levels

Let’s see now how the licensing changed from TFS2013.3 to TFS2013.4:

Access level

License required


TFS client-access license (CAL) or Visual Studio Professional with MSDN subscription


One of these MSDN subscriptions: Visual Studio Ultimate with MSDN, Visual Studio Premium with MSDN, MSDN Platforms, or Visual Studio Test Professional with MSDN.


No license required. Assign Stakeholder access to customers or stakeholders that you want to collaborate with but who aren’t on your team.

It means that the Stakeholder level (previously called Limited), will allow you to create Workitems (such as Bugs, Test Cases, Requirements, etc) but now, on the Update 4 for TFS2013, we have some extra features:

Stakeholder access level:

  • View and edit all work items (not only yours)
  • Standard features
  • Agile boards
  • Basic backlog and sprint planning tools
  • Agile Portfolio Management

If you go for the Basic access level (you would require a CAL or a license of VS Professional), you will get the next features access:

Basic access level (all stakeholder’s plus…):

  • Chart viewing
  • Build
  • Code
  • Administer account
  • Advanced home page
  • Advance backlog and sprint planning tools

Advanced access level (all basic’s plus…)

  • Chart Authoring
  • Request and manage feedback
  • Test case management
  • Team rooms
  • Advanced portfolio management

Visual Studio Online Access Levels

And last but not least VSO. If you don’t want to host the TFS server on your premises or just you want to avoid all the set-up of servers, SQL Server Databases, etc. Maybe the best option is to subscribe to an on demand service called Visual Studio Online (previously called Team Foundation Service). This service allows you to get licenses on demand and monthly, so you will save a considerable amount of money. Right now you can’t have divided your infrastructure half on premises, half on the cloud, so that means that your online users will work on team projects hosted on the cloud.

VSO features are slightly reduced in comparison to TFS (like reporting or SharePoint integration) but most of the features are available!

Let’s go through the features accessible through the different access levels

Stakeholder access level (free):

  • Work item tracking, queries, tagging
  • Alerts
  • Agile planning boards and backlogs
  • View Iteration and capacity planning
  • Portfolio management boards and backlogs
  • View query based charts 
  • Provide feedback
  • Track test progress and charts

Basic access level (5 free and $20/month new ones). All stakeholder access plus:

  • Team chat
  • Git repositories and TFVC
  • Work with Xcode, Eclipse, IntelliJ and others
  • Code Reviews
  • Enterprise Scale
  • Full Build and Deployment features
  • Web-based test execution. Test runner
  • Administer accounts, users, teams and projects structure

Professional access level (includes stakeholder and basic access levels). $45 per user per month.

  • Includes Visual Studio Professional

Advanced access level (includes stakeholder and basic access levels). $60 per user per month.

  • Request and manage feedback
  • Test planning: create test plans
  • Test authoring
  • Test suite management
  • Test tracking

As you can see it’s slightly different the On-Premise Server than the On-Line Services but in practice, this would be transparent for your developers, testers or team leads.

For more information follow the links below.

Happy licensing!

Eduardo Ortega


VSO Matrix:

Visual Studio Versions:

Work as a stakeholder:

Visual Studio Online Pricing:

Pay for users accessing your account:

Visual Studio Online Basic:

Installing Team Foundation Server 2013 in Windows 8.1

Yes! It is possible, let me show you how:

  1. Download Team Foundation Server 2013 Update 3, you can do it from your MSDN Subscription, from the Microsoft Downloads site or even you can download the Express 2013 version here.
  2. Once you have it with you, just start the installation as usual and unless you have an error about your computer not following the minimum requirements, everything will be done in few minutes and 1 restart.
  3. Once the installation is done, it’s time to configure the server. Just a quick reminder, when you install TFS 2013 on a client machine, is only intended for a few concurrent users, you will use SQL Server Express and we are trying the have the most compact TFS installation possible. The main purpose of installing it in our Windows 8.1 is to have Source Control, Work Item tracking and Build Services, but you will see that you can do much more. So let’s select the Basic configuration

  4. So, welcome to the Basic Configuration Wizard! Let’s begin with the Installation of SQL Server Express:
  5. The information to review is giving us some hints about what’s going to happen after the configuration:

  • The authentication will be Windows Authentication.
  • IIS will be configured.*
  • A main site for TFS collections will be created.
  • The port 8080 will be opened for this purpose (check firewall after set up).
  • SMTP will be disabled by default as a client we usually don’t have a SMTP mail server set up on our machine.

    Note: IIS should be installed previously enabling also compatibility with IIS 6 and URL forwarding.

  1. Click on VERIFY before continue and if you have the 4 green checks, you can go for the next step.
  2. And the configuration it’s starting!

    And finishing after few minutes:

  3. Last step, check the connection to the Team Foundation Server Web Access:

Done! Now you can set up extra services like the Team Foundation Build Service but this is a different topic that we will cover in another blog post.

For now, just before we finish this post, check that the Team Foundation Server Administration Console has been installed on your computer and open it. From there you will be able to create new Team Project Collections, modify the Application Tier Set Up and access to the main administrative tools of TFS.



Interesting references:

TFS Overview:


The best Team Foundation Server 2013 MUST HAVE downloads

Here is my personal list of MUST HAVE downloads for Team Foundation Server 2013, sharing it with my beloved community.

Visual Studio Downloads:
including trials of:

  • Visual Studio Ultimate 2013 with Update 3
  • Visual Studio Premium 2013 with Update 3
  • Visual Studio Professional 2013 with Update 3
  • Visual Studio Test Professional 2013
  • Team Foundation Server 2013 with Update 3

Microsoft Visual Studio Team Foundation Server Express 2013 with Update 3

Microsoft Visual Studio Team Foundation Server 2013 with Update 3

Microsoft Visual Studio Team Foundation Server 2013 Power Tools

Microsoft Visual Studio Team Foundation Server 2013 MSSCCI Provider 32 bit

Team Explorer for Microsoft Visual Studio 2013

Microsoft Team Explorer Everywhere 2013

Feedback Client for Microsoft Visual Studio Team Foundation Sever 2013

Featured downloads:

From the Visual Studio Gallery:


TFS Install and Administration Guides


  • Happy downloading time! –


Enterprise agile – Integrating Project Management and Software Development Teams

Management vs Development, they look like 2 worlds apart right? J Yes they are indeed, but this doesn’t mean that they can’t exists together on the same world and be interconnected. If you want to know more about how to bridge the collaboration gap between their project management offices and their software development teams continue reading…

I still remember those days, years back, where the Projects Manager used to spend an uncountable number of hours with the Team Lead catching up on the status of the projects, delivery dates, impediments and other matters related. It was such a show to see the TL trying to explain the Management what an iteration and user stories were. My manager used to leave these meetings with a terrible headache and long face, so the next action were to come to desks and ask us all the details about when, how and why of the releases we had on the pipeline.

This rings a bell for you right? This continuous reporting is good and bad at the same time, this makes the transparency to increase but the amount of time lost in reporting is huge. What if Project Managers and Software Development Teams can use the tools that they prefer, work at the level of precision that supports their needs and share information organized, transparently and immediately?

To enable this flow of data you can have two options:

Option A – TFS and Project Server Integration: On the management side (usually the PMO) install the Team Foundation Server Extensions for Project Server on the application-tier or web-tier servers that run Project Server that will participate in data synchronization.

With this, Project Managers would be able to use Microsoft Project Server to access up-to-date project status and resource availability across software teams using Team Foundation.

This integration enables data to flow from work items in Team Foundation Server (TFS) to tasks in enterprise project plans in Project Server.

Option B – Team foundation plug-in to Microsoft Project: This scenario doesn’t require a Project Server, just Microsoft Project but it is a very limited scenario. For example:

  • Supports mapping a task field in Project to a field in Team Foundation but Tasks are not bound to work items
  • Project plans are bound to Team Foundation server
  • For resource tracking, hours are rolled up in Project but not in Team Foundation, so resources are not rolled up either
  • View across multiple enterprise project plans and reporting, portfolio optimization and demand management are excluded in this operational model


Oh yes! Now we are talking J

Let’s take a look at the internals and how this works.


As you can see you can use MS Project to open a project plan, manage and track the work across all your backlogs and teams and even control the timesheets and the resources usage. This will be fully connected through a series of mappings to TFS so the development team will see the changes reflected on their dashboards when they will access through the team web portal or Visual Studio Team Explorer.

As well every time the development team make a change on the user stories or the work items, this will be reporting directly to the project server (if changes applies).

The process flow for Top-Down Planning on a regular project is represented on the next figure:

  1. The Project Manager define the deliverables, features and requirements in the project plan (Project or Project Web App – PWA)
  2. Save and publish the project plan to Project Server
  3. Each time something is published from Project Server, the sync engine performs the right mappings between the item types of Project Server and the work items in Team Foundation Server, binding them both.
  4. The team lead opens the Team Explorer or the Web Portal to review the deliverables with the Team
  5. The team lead break down into tasks the user stories and features that the Project Manager established in the Project Plan
  6. And assigns a resource to each task
  7. Saving it on the Team Foundation server and publishing it back to the Project Server for the Project manager review
  8. The Project Manager reviews the progress of each deliverable and adjust the schedule based on the updated information and
  9. A baseline is established, so it will be able to track progress against the baseline.



Usually you will find scenarios where to integrate TFS with Project Server 2010 or Project Server 2013.

There is no a big difference between using 2010 or 2013 but small differences on the authentication and security:

For example:

  • On Project Server 2010, during the set up you must install all the cumulative updates on all Web Tiers and on all App Tiers in the server farm.
  • On PS2010, the Classic Mode Authentication is the only allowed authentication mode.
  • Security: On PS2010 you manage your PS security through customizable security groups where in PS2013 you can use SharePoint Permission Modes to control user access to sites and projects.

So this will be the typical architecture:

/benefits of integrating TFS with Project Server/

  • Go deep into portfolio execution, alignment with strategic objectives, and resource usage of software development projects.
  • Automate the sharing of project information across teams whatever methodologies are using (waterfall, agile, cmmi,…)
  • Enable development and project-management teams to collaborate through project timelines and progress using tools such as Visual Studio, Microsoft Project, SharePoint and Excel.


/How the Project Manager will see this in MS Project/

Basically like this:

To mark a new deliverable as an item to synchronize with Team Foundation Server, we will have to set the Publish to Team Project property to Yes and set the Work Item Type to the right value (p.e. Requirement, task,etc).

All we need now is to save and publish the project plan to the Project Server and the synchronization will be triggered.

/How the Team Lead will see this in the Team Explorer/

If the team lead opens the Team Explorer and goes down to the Work Breakdown to check the work items.
There the new requirements and tasks will be visible and we will be able to edit them and add extra information like for example the effort estimation, the priority, change the assignation, etc.

Also, any change made from here will be synchronized with the Project Server as well, as for example, imagine that we are working on an specific work item and once we finish it we want to report that the Remaining work time for this Work Item now is 0. Just saving the Work Item from Visual Studio the Project Manager will see the submission request on the PWA portal as this:

Where the task update to get approved will have the next details:

And therefore will be updated also in the Project Plan.

/Wrapping up/


It can be a bit messy if you don’t look at the picture from a general view, as you have to know a bit how the project management usually work and how the development team operates. What this integration is offering is a way to communicate both teams, save time, be transparent and improve the internal process of control.

I recommend you to follow these Hands On Labs to know more about the integration of PS with TFS and if you want to go deeper on it, you know where to find me J


– May the plan be with you –

Eduardo Ortega Bermejo



Team Foundation Server and Project Server Integration Virtual Machine:

Demonstration videos:

Accessing TFS. Why Team Explorer and troubleshooting

Here is the big question, how to enable the “Team tab” in Excel without installing the Visual Studio in manager’s computer J, the answer is obvious, installing Team Explorer on his/her computer, but not always is so straightforward, sometimes we have restrictions from IT and we have to look for workarounds.

The list of options is not so big but we have a bunch of clients that can give us access to Team Foundation Server, with more or less capabilities depending what we want to do and the client.

Primary Clients:

Task-specific clients:

Office-Integration clients:

Let’s stop at Office-integration clients for a minute. These add-ins (COM Objects that have to be installed and registered in our OS prior use in Office) supports Office 2007, Office 2010 or Office 2013.
The way to install them is through the Team Explorer standalone installation or with any edition of Visual Studio.

Non-straightforward and dangerous workaround

You can try to do a workaround that is extract the TFSOfficeAdd-in.dll from the Team Explorer ISO and register it manually in the target OS as follows:
regsvr32 TFSOfficeAdd-in.dll

Uninstalling any previous clients (if exists) using the next script:

regsvr32 /u TFSOfficeAdd-in.dll

Also you would need to install the right .NET Framework version required, 2.0, 3.5 or 4.0, depending on the version that you are using.

Note: Make sure that the DLL is available in C:\Windows\System32\

Note: You have to run it as an Administrator, and in some cases depending on the OS, shut down Windows Defender and Windows Firewall.

After this process is finished go to excel and enable the plug-in:

  1. Open Excel
  2. Click File à Options àAdd-ins
  3. Select COM Add-ins

  1. Check the Team Foundation Add-In

This implies to register it as an Excel COM Add-In in the OS, it will require administrative rights and also the installation of .NET Framework as well. Also if they want to uninstall this from the computer further it will be a dirty job. Extra configuration on MS Project and MS Excel will be required as well.

Note: Verify or configure the .NET Programability Support option in the Install or remove individual Office programs and components:

Last step should be to check the registry of Windows we have to make sure that the Entries for Microsoft Office Add-ins are created properly.
For example, for Excel you would find them here:


You can find extra information about the needed keys here:

Note: This steps can be used as well for troubleshooting in case the Team Explorer repair option doesn’t work.

My recommended choice for a non-invasive installation is to install Team Explorer as a standalone installation.

Why Team Explorer?

Team Explorer is the client software that you use to access the Team Foundation Server functionality. And we can think that it is only to extend Visual Studio in order to connect to Team Foundation Server but it is not the case.

Team Explorer has side-by-side compatibility of Team Foundation clients. You can run Team Explorer with:

  • Microsoft Test Manager
  • Microsoft Project
  • Microsoft Excel
  • PowerPoint Storyboarding.

Even exists a MS Word non official Add-in provided by the Visual Studio ALM Rangers and published in Codeplex here.

How it works?

In MS Project the process is the same:

What can you do with this Team options?

For example, using Excel you can add or modify work items with Excel as well update reports. More info here.

Using MS Project, you can create your backlog and tasks, publishing and refreshing your work items, timelines, resources usage, etc. More info here.

Using PowerPoint, you can turn your ideas and goals for your PBIs in something more visual. Storyboarding is part of the PBI in TFS2012 and TFS2013. More info here.

So here is the main ask for you, how far do you want to go?

As depending on the client that you are using the possibilities will be extended or reduced. It’s not part of this blog post to cover one by one all the features accessible through the TWA, Team Explorer and Office, for that just access to this link and check the Tasks and client support tables, but summarizing what you can do with these clients here a short list:

  • Manage source code and builds
  • Plan a project, track progress
  • Bulk add and modify work items
  • Add and modify work item links
  • Collaborate with team members and stakeholders
  • Happy planning! –

Eduardo Ortega

Links of interest:

Compatibility between Team Foundation clients and Team Foundation Server:
Choose the Team Foundation client to support your tasks:
Connect Microsoft Excel or Microsoft Project to a team project:
Microsoft Project and Microsoft Excel Integration Architecture:
Working with Team Foundation Clients:
Managing Work Using Team Web Access:
Bulk add or modify work items with Excel:
Work in Limited access view or Work Item Only View:
Work in Team Explorer:


Microsoft Visual Studio Team Explorer Everywhere 2010 with SP1:

Microsoft Team Explorer Everywhere 2013:
Visual Studio Team System 2005 Team Explorer:

Microsoft Visual Studio Team Explorer 2010 – ISO:

Team Explorer for Microsoft Visual Studio 2012:
Team Explorer for Microsoft Visual Studio 2013:

Installing and Configuring TFS 2010 with PS2010, SP2010 and SQL 2008

Today I was configuring a Virtual Machine with TFS 2010, as some of my clients want to integrate it with the PMO and using it together with Project Server 2010, SharePoint 2010 and Visual Studio 2010.

This is a very common combo as in many companies they have a PMO (Project Management Office) where they are tracking all the projects committed in the company using MS Project and Project Server as EPM. SharePoint in these scenarios is a critical tool as it will show all the reports related not only with the project management but also with the development progress, thanks to the integration with TFS 2010.

The trick is how to combine PS and TFS together to link the management with the development and how to leverage SharePoint to gather all the reports we need about both. But not only that, from the Project Server Web Access, you also will be able to approve changes on the product backglog, control the timesheets and how these changes that come from Visual Studio can affect to your project planning and reflect them automatically on MS Project.

But step by step, let’s start by the TFS 2010 installation and for now let’s take a look to the different topologies that we can find when we are facing these scenarios:

Simplest Topology


Here all server components are deployed on a single physical server (this is the case of the smallest VM I have set up for testing.
This is usually designed for small product development team with less than 50 users.

Team Foundation Build and the team’s test components can be installed in the same server as well.For reporting services, you can install SQL Server 2008 with SSRS and SSAS on the same machine and either use Sharepoint Services v3 that comes with the Windows Server or Install Sharepoint 2010 on the TFS Machine.

If you just use the SQL Server Express you have to realize that the integration with Sharepoint will not exist.If you install WSS 3.0 instead Sharepoint some dashboards won’t be available either (

So the final configuration would be something like this:

Using SQL Server 2008 and WSS 3.0 in the same single server.

If we want to have all the reports available on SharePoint we have to install SharePoint 2010 and not WSS 3.0.

The installation process for TFS is so straight forward. Just let me share two guides with you before I go through the process:

Team Foundation Installation Guide for Visual Studio 2010

Administration Guide for Microsoft Visual Studio 2010 Team Foundation Server

  1. Supported Operating Systems: Windows Server 2003, Windows Server 2008, Windows Server 2008 R2 (important to install Service Pack 2 for WS2003 or WS2008). So choose any of these 3 for your server. (you can install it on a Windows Vista/7 but SharePoint and any reporting tools won’t work on them)

  2. Enroll the machine in your AD in case you are working on an Active Directory environment. Just create a user called TFSAdmin with admin rights on the local machine. Verify that the account you will use to install Team Foundation Server is a member of the Administrators security group on the server where you will install Team Foundation Server.Note: Other service accounts should be set up depending on the TFS components that are going to be active. For more information:

  3. Install IIS Web Server with the ASP.NET Extensions with the Required Role Services and also the HTTP Redirection Role Service. As TFS makes heavy use of Windows Authentication, the Windows Authentication role service is also required. And finally the role service for IIS6 Management Compatibility too.

  4. Install SQL Server 2008 with Reporting Services in Native Mode (not SharePoint Integrated mode) and don’t configure the RS yet. Just set up Database Engine Services, Full Text Search, Reporting Services and Analysis Services. Add Client Tools and Management tools and we a ready for the next step.

  5. Install WSS 3.0 in the server or either install SharePoint Server 2010. Make sure that SharePoint user can access to the SQL Server. Just open SQL Server, and add a new Login. Type the fully qualified name for your SharePoint service user in the Login name box. The format of the username is domain_name\username. So, if your domain is MyDomain and the user is WSSSERVICE, you’ll enter MyDomain\WSSSERVICE.

  6. Check that SharePoint is working properly just checking the http://localhost website.

  7. Open the SQL Server Reporting Services Configuration Management Tool and configure the Reporting Services. Don’t forget to use the same user TFSAdmin during the set up process.

  8. Now it is time to Run the TFS Set-up installation.
  • Select Team Foundation Server. At this point we don’t want to install the Team Foundation Build Service (also is recommended to install it in a separate server).
  • After the installation finish, select the checkbox “Launch Team Foundation Server Configuration Tool” and click on Configure.
  • Now is when we have to decide the topology of our TFS. As we mentioned before, Basic or Advance configuration can work as we are installing our TFS in a single server that can have/not have SQL Server and SharePoint installed on it. If we check both configurations we can see de difference:

  • In my case I will go for the Advanced
    topology as I already have installed SharePoint Server 2010 and SQL Server 2008. Just make sure you are filling up correctly the wizard blanks like the SQL Server Instance (use the Instance name that you have created and click on Test)Account name for running the TFS Services:
    The IIS Web Site Default Name, port and Virtual Directory:
    And finally the default Project Collection
  • It’s very important that we kkep attention to the Readiness Checks to validate all the data input before and to check if something is wrong with our services or accounts.
  • Finally once is done, you will be ready to go, just install the Team Explorer 2010 or Visual Studio 2010 to Start Creating and Managing Team Projects!
    If you are using Eclipse or other development tools you can also download Microsoft Visual Studio Team Explorer Everywhere 2010 with SP1.

 I highly recommend to install the respective Service Packs:

  • SharePoint 2010 SP1
  • SQL Server 2008 SP1
  • Windows Server 2008 SP2
  • Team Foundation Server 2010 SP1

Wrapping up,

There are a lot of tools and software to install, of course my first recommendation would be to acquire Team Foundation Server 2013 for several reasons (main one are integration, capabilities, templates, reports,…), but still there are many customers out there with TFS2010 and a lot of CALs, and it is a very good product, despite is 4 years old. The greatness of TFS is the integration, doesn’t work alone, it integrates completely with Project Server, with SharePoint, with SQL Server, with Visual Studio, MS Project, MS Excel and not only with Microsoft Technologies but also with Eclipse, XCode, GIT…

I recommend to take a look to this video from Channel 9 where you can see all the power of TFS 2010 in action, called Microsoft Project Server 2010 and Microsoft TFS 2010, better together: (video).

That’s all for now, just let me drop you below some recommended installs for the scenario.

See you next time!

– May the plan be with you –

Eduardo Ortega Bermejo


In the Application tier we would need:

Team Foundation Server 2010 RTM with the following updates installed in the correct order:

In the Database tier, SQL Server 2008 Service Pack 1 (or TFS installation will block you).

Clients (Visual Studio & Microsoft Test Manager):

The MSSCCI Provider allows non-Microsoft tools to connect to TFS:

Team Explorer Everywhere (TEE) is an Eclipse IDE/Java implementation of the TFS client:

If you work in a cross-platform environment, you may also want to install the build extensions that allow you to execute Ant or Maven 2 builds and publish any JUnit test results back to TFS.

If the scenario also includes Project Server, is highly recommended to install the Feature Pack for Visual Studio Team Foundation Server and Project Server Integration, only available through MSDN Suscriptions..


Team Foundation Installation Guide for Visual Studio 2010:

Microsoft Visual Studio Team Explorer 2010 – ISO:

Microsoft Visual Studio Team Foundation server 2010 SP1:

Dashboards (Agile):

TFS 2010 Power Tools – December 2011:

Reporting Services Configuration Tool: