Alexander Vanwynsberghe

"There is nothing impossible to him who will try"

TF400409: You do not have licensing rights

Today, I updated my TFS 11 machine to the recently released TFS 2012 RC version. More information about this release can be found on the the great blogpost by Brian Harry. Updating an existing TFS 11 setup is really easy, just uninstall the Application Tier and perform the installation of TFS 2012. When the setup is ready, you can follow the -upgrade- path to convert your existing databases and settings to TFS 2012. This went perfectly without any issues. Great job Microsoft!

So far so good. Although this is not the goal of this post. I want to share you something I was struggling with. When I looked at the homepage of my web access, I had this 2 red dialogs:

This behavior is really strange, because I did install the full version, nothing special, just a standard upgrade. I also found out that I didn’t have a ‘Backlog’ in the activities menu on the right, allthough I had this on the TFS 11 version (and on the TFS preview version). When I browsed to this page manually by going to http://tfsserver:8080/tfs/DefaultCollection/TeamProject/Team/_backlogs, I had this same permission error:

After some research, I figured out that you now have the possibility to define ‘Web Access Permissions‘ in this version of TFS. By default (meaning after the upgrade), this is set to ‘Limited‘ = no advanced features like the backlog etc. To activate this, just go to the Admin Control Panel, select ‘web access‘ and select ‘Full‘. Then click on ‘Set as default web access‘. You can also play with those settings by adding users to specific permissions. As you want…

That’s it, issue solved!


ALM Rangers Practical Kanban Guidance RC

Yesterday, together with the Visual Studio and Team Foundation Server 2012 RC release, the ALM Rangers have also SIMultaneously SHIPped their guidance as RC. As I’m really proud to have been involved in the ALM Rangers team, I can tell you that we also shipped the RC version of the Practical Kanban Guidance.

The Practical Kanban Guidance offers teams that are new to Kanban and teams that are using a manual, paper or whiteboard-based Kanban board, guidance and tool support for Kanban in Team Foundation Server 2010 and Team Foundation Server 2012. The guidance also describes how Team Foundation Server can capture metrics and other information that can be used to track and continuously improve a team’s software delivery process.

You can check it on the CodePlex project. If you have any suggestions for improvements, remarks, bugs,… just let us know! Your feedback is really valuable.

Enjoy the release!

Event 5586 after installing SP1 on SharePoint 2010

When I was at a customer recently, I found a strange error in the Event Viewer:

Event 5586:

Unknown SQL Exception 2812 occurred. Additional error information from SQL Server is included below.

Could not find stored procedure “proc_UpdateStatisticsNVP”.

This problem is caused by updating SharePoint 2010 to SP1. This update will try to execute this stored procedure, but it’s not there. If you go to location: “C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\SQL” you’ll see a file called “STOREUP.SQL”. This file will call this stored procedure. For one or another reason, the creation of the stored procedure fails when installing SP1. If you look at the file called “STORE.SQL”, you will see that there is a create statement for this stored procedure. Strange..

Ok, now that we know what the error is, we have to fix it. The first thing you have to do is to find out which databases do not have this stored procedure. You can do this by executing the following statement:

This will return you the databases without the “proc_UpdateStatisticsNVP” procedure. The next step is to create this stored procedure by using the following script:


That’s all you have to do! Be sure that you execute this script on the right database. Use the drop down in SQL Management Studio, or start the script with “USE [DBName]”.

Microsoft Feedback Client using TFS11


When your team is developing software, it is really important to capture feedback from the project stakeholders like end-users and the product owners. This way, you can ensure that the progress that the team is making is on track to meet the requirements that the stakeholders have in mind. In the next version of Team Foundation Server, there is a new tool called ‘Microsoft Feedback Manager’. I mentioned this in a previous post, but now I will handle this subject a little bit more in depth using the brand new TFS11 beta.

 You can start the Feedback tools in two ways. The first way is ‘voluntary‘, where you decide to gather some feedback without being asked. The second way is ‘on request‘, where you got a request to give your feedback about a particular part or feature of an application. To start a ‘voluntary‘ feedback session, go to Start -> All Programs  -> Microsoft Visual Studio 11 -> Microsoft Feedback Client. The first thing you have to do is connect to your Team Project. After you select the Team Project, the feedback client is running on the left side of the screen:

There you see in the Instructions that you’re running the tool in ‘voluntary’ mode. In this mode, you don’t have any instructions available about the feedback session. The other way to start the feedback client is by making use of the ‘Request Feedback’ link on the TFS11 Web Access.

In the “Request Feedback” screen, you select the Stakeholder(s) you want to invite. You also provide some information about the product/application and what you expect as feedback. This can be anything related to a particular feature or about a general thing

When you click on ‘Send’, you should receive an email with the request for a Feedback session. In this email, there is link which will open the Feedback Client. The first time you do this, you’ll get a dialog asking you to open the Feedback client

When the Feedback client is started, you now see that the ‘Application‘ and ‘Instructions‘ have the same content as you provided in the previous dialog on the Web Interface

When you click ‘Next‘, you’re ready to gather some feedback. Do what you have to do (described in the instructions) and enter as much feedback as you can. The Feedback client has support for audio, video, screenshots and attachments. Using this functionality, you can create rich feedback to the developers. When you make a Feedback Request, you can also request multiple feedback items. In the Feedback Client tool, you will see multiple items to gather feedback for.

The last step is to Publish your feedback. Just click on ‘Next‘ and you will see a summary of the feedback you provided. You will also see the location where the feedback will be stored.

Now your feedback is submitted to TFS. The person who requested the Feedback can check your session. You can do this using the TFS Web interface. Go to the ‘Work Items‘ section of you Team Project, select ‘Shared Queries‘ and open the ‘Feedback Requests‘. There you will see you feedback request and the actual feedback session.

One of the nice things is that you automatically get the System Information which can be very useful for Web Application, because it will also show you the browser version and some additional information. Actually, this information is linked to your Feedback Response Work Item.

Now you have an idea what the possibilities of what the Feedback Client can do for your. It’s really a powerful tool to help you collection all information you want from your stakeholders. It’s nicely integrated in the Visual Studio 11 suite and it looks slick in the new metro-style. Thanks for reading!

Cloning Microsoft Test Manager 11 Test Suites


With the next version of Microsoft Test Manager, MTM11, there is a possibility to clone test suites across plans. This is something which can be very helpful if you’re working on multiple releases. This way, you can clone an existing Test Suite from a previous release, and just change the necessary things related to the new release. When you clone a test suite, the new suite will contain the copies of all test cases in the source suite. However it will not retain all historical data like the previous test runs, the related bugs, old results. It provides a clean starting point.

Getting started

This feature is available through the command line utility tcm.exe. You can start this utility using the ‘Developer Command Prompt‘ from Visual Studio 11 (beta). Start->All Programs->Microsoft Visual Studio 11->Visual Studio Tools. Enter ‘tcm‘ to see the list of available commands:

We will continue with the ‘tcm suites’ command. This command will provide us all operations related to Test Suites, like listing and cloning. The first thing you can do is get a list of all available Test Suites using the ‘tcm suites /list’ command. This will give you a list of Suites with an ID and a Name. This ID is useful to know when you want to clone from one Suite to another Suite. For each command you want to execute, you have to provide the URL of your Team Project Collection and the Team Project Name you want to work with. In my case (using the great HOL VM from Brian Keller), the command is:

tcm suites /list /collection:http://vsalm:8080/tfs/DefaultCollection /teamproject:FabrikamFiber

In this example above, I have “TestPlan1” containing the ‘A Demo Suite‘ test suite. What I want to do is clone this test suite into “TestPlan2“. So I want Id 3 to be cloned in Id 2. To do this, just use this command:

tcm suites /clone /suiteid:3 /destinationsuiteid:2 /collection:http://vsalm:8080/tfs/DefaultCollection /teamproject:FabrikamFiber

When this command is executed, the clone operation is ongoing. This command returns an operation Id back. This Id is an identifier of the actual clone process. In some cases, a test plan/test suite can contain a large number of test cases, resulting in an operation which can take a serious amount of time. In my case, it’s only a small one. What you can do to follow the process of the clone operation is executing the following command:

tcm suites /clone /status:2 /collection:http://vsalm:8080/tfs/DefaultCollection /teamproject:FabrikamFiber

As you can see, the operation ‘2‘ has succeeded. You also have some information about the clone operation like the number of test cases cloned and the cloned shared steps.

Each clone operation is stored in the TFS_DefaultCollection (or TFS_YourTPC) database. You can get an overview using table ‘tbl_CloneOperation’ where you have the same information as in the screenshot above.

This is a nice (hidden) feature in the new improved version of Microsoft Test Manager 11. I hope they will include this command in the interface so you don’t have to use the commandline version of the tool. Thanks for reading!

TFS 11 Beta Build Service on Windows Azure


With the new upcoming version of TFS, you will have to possibility to have your own TFS instance running on Windows Azure, called “TFS Preview”. One of the cool things about this is the fact that you’re not responsible anymore for the TFS infrastructure. You don’t have to invest in some decent hardware, everything you want is there for your, on Windows Azure.

The one thing you need to have ‘on premise’ is a build server, as TFS Preview does not give you any options to use a cloud-based build server. Which is in fact understandable, because a build server can generate lots of load and needs to be monitored precisely. But, shouldn’t it be cool to have ‘everything’ in the cloud? Well, actually you can: TFS Build Service on Windows Azure using the VM Role

In this post, I’ll take you trough the steps to setup your own build service and host it on Windows Azure.

1. Azure account

Because you will be hosting your build service on Azure, I suppose you already have your an Azure account. If not, you might already have access using your MSDN subscription (there is some good information on this blog post). The next thing you have to do is signup for the VM role beta program. You can do this on and then select “Beta Programs”.

2. Base VM Role Image setup

The next thing you have to do is create your VM Role Image, which you will use to upload on Windows Azure. In fact, this virtual image will be configured like an on-premise build service. This image contain an operation system (off course) and a TFS 11 build controller with one (or more) build agents.

  • To get started, open Hyper-V manager on a Windows 2008 (R2) machine, and select the option to create a new Virtual Machine.
  • Follow the wizard, and set the amount of memory to 2048 MB. Also be sure to select the ‘Virtual Network’ connection.
  • Create a new virtual disk called “baseimage.vhd” and set the size to 30GB (when you select this size, you can deploy the VM in a “small” role, take a look at the pricing for more info)
  • Finish the wizard, boot your new virtual machine and install your operation system (windows 2008R2 for example).
  • There is a special requirement for a valid VM Role image. You have to allocate the entire virtual hard disk file to a single partition where you install the operating system. To avoid creating a recovery partition during the installation, follow these steps:
    1. Choose the Custom (advanced) installation type to select the partition where you will install Windows.
    2. Press Shift + F10 to open a command prompt during GUI-mode setup.
    3. At the command prompt, enter the following commands:
      1. diskpart
      2. select disk 0
      3. create partition primary
      4. exit
    4. Close the command prompt window.
    5. Install Windows in the newly created partition.

3. TFS 11 Build Controller

  • Next step is to install the TFS build controller on the VM, but do NOT configure it yet. We will configure it when the VM role is online on Windows Azure.
  • To do this, run the TFS 11 beta installation (you can download the beta using MSDN or this link.)

  • When the installation is finished, close the Configuration screen.
Tip: When you are planning to build more than some ‘basic’ applications, be sure to also install Visual Studio!


4. Windows Azure VM Role Integration Components

The next part is the installation of the VM Role Integration Components. The integration components must be installed on the machine before base image is uploaded to the Azure. The integration components start each time the OS starts. It handles the integration between the role instance and Azure environment. Follow these steps:

  1. In the Virtual Machine Connection window, in the Media menu, point to DVD Drive and then select Insert Disk. In the Open dialog, browse to the location of the ISO file for the VM Role Integration Components, wavmroleic.iso, and then click Open. The wavmroleic.iso is located at ‘C:\Program Files\Windows Azure SDK\v1.6\iso\’
  2. In the Operating System Configuration step, enter an Administrator Password, confirm it, and then click Next.
  3. Follow the wizard and once the installation of the components has finished, you will be prompted to restart the system. Click Yes to continue.
  4. Wait for the system to restart and log in to the guest machine once again. Now, inside the VM, open the Start menu, type %windir%\system32\sysprep\sysprep.exe and then press Enter to launch the System Preparation Tool. Set the System Cleanup Action to“Enter System Out-of-Box Experience (OOBE)”, check the option labeled Generalize, set the Shutdown Options to Shutdown, and then press OK. This tool will prepare the image by cleaning up various user and machine settings and log files, as well as removing any hardware-dependent information.
  5. Wait for the system to completely shutdown. Your image is now ready for deployment.


5. Uploading the VM to Windows Azure

Now we have a VM image ready for deployment.  Next step is to upload this image. To do this, we will use the ‘csupload‘ command from the Windows Azure Command Prompt. Follow this steps:

  1. Open the Windows Azure SDK Command Prompt as administrator
  2. Type the following command to link the context to your current subscription:
    • csupload Add-VMImage -Connection “SubscriptionId=[SubscriptionId]; CertificateThumbprint=[ThumbPrint]” -Description “TFS Build Service” -LiteralPath “C:\baseimage.vhd” -Name baseimage.vhd -Location “West-Europe”
      • The subscription id can be found on the management portal in the property grid, when you select your subscription.
      • The certificate thumbprint is a private certificate that is installed on the local machine and that is linked to the management certificates on the Azure portal.  Uou can easily copy the thumbprint from the property grid in the Azure Portal
      • Be sure to change the LiteralPath to the location of where your VHD is located.
      • The location (data center) needs to be defined where the storage will be created. You can use friendly names like “West-Europe”
  3. Now the upload will start. The first step in the process is the preparation
  4. After preparation, it will start uploading. When the upload starts, you can see your new vhd on the Windows Azure portal as ‘Pending’
  5. Wait for the upload to complete. This can take several hours, depending on the upload speed of your Internet Connection. When finished, you should see:

6. Creating the Service Model

After completing the previous step, you now have a VM image deployed to your Windows Azure account. In this task, we will create a service model and configure it to reference this image.

  1. In Visual Studio, create a new Windows Azure Project. In the New Windows Azure Project dialog, click OK without adding any roles. You will create a Virtual Machine role in the following steps.
  2. When the solution is created, right-click the Solution folder and select New Virtual Machine Role. This option is ONLY available when you are in the VM Role beta program. When your request was accepted, you should have received an email with a link to enable the VM Role option in Visual Studio. If you lost this mail, you can use this link (32bit or 64bit), it’s a small change to the Windows Register.
  3. You should see a the properties of the new VM Role. In the ‘Virtual Hard Disk‘ section, select your Azure subscription and select the the image we have just uploaded
  4. In the ‘Endpoints’ section of the wizard, add a port for the build-controller. A TFS Build Controller uses 9191
  5. Save your settings and close the window. Next step is to publish your VMRole and meanwhile enable Remote Desktop. You can do this by right-click on the solution, and select ‘Publish’.  In this window, follow the Wizard and enable ‘Remote Desktop’.
  6. Now you can Publish this solution. You can follow the status of your deployment using the Windows Azure Activity Log screen.

  7.  The roles take the following statuses
    • Initializing
    • Waiting for host
    • Setting up Windows for first use
    • Starting Windows
    • Starting Traffic
    • Ready
  8. When finished you can see your Hosted Service using the Azure Portal. Now you can also connect to the VM using Remote Desktop. Click on the Remote Desktop icon and log in using your account (defined in the Remote Desktop Setup process).

7. Configure your Build Service

Last step is to configure your brand new Build Service. When you are logged-in on the VM using Remote Desktop, launch the TFS Build Controller configuration.

  1. Click on “Configure Team Foundation Build Service” and then click the Start Wizard button at the bottom.
  2. On the Project Collection screen, identify your team project collection/account on the hosted service.  You can’t type here so just click the Browse button and add your TFS preview/Hosted TFS account. In my case, I already have a build controller running, but I’ll add another one
  3.  Next step is to configure the Build Service. In my case, I already have a build controller, but I will replace it with a new one (the original one is offline). You can also decide to use this machine as a ‘Scale out’ system for an existing Build Service. This existing one will use this new machine as extra agent capacity.
  4. In the next step, you can configure which account will run the Build Service. This can be network service, or a specific account within your Active Directory (if you use Azure Connect with AD integration). This depends on the installation type. In my case, I’ll just use the network service.
  5. In the ‘Advanced‘ section, you can define your hosted TFS  Service Service Account. Leave this by default. You can also change/manage this using the Administration section of your Hosted TFS account, in my case:
  6. Verify and confirm the Configuration Settings
  7. Configuration completed
  8. That’s it, now your Build Service is up and running, on Windows Azure. Now you can tweak this by adding some agents,… You can manage the Build Controller using Visual Studio 11 (or 2010) by going to the ‘Builds‘ section of your Team Explorer, and click on ‘Actions‘.

8. Conclusion

Now we have our TFS11 Build Service up and running on Windows Azure. Now you can create Build Definitions and queue builds (a failing build in my case)

Good luck with your Build Service and enjoy it!
Thanks for reading.

Installing SharePoint 2010 prerequisites offline

When you want to install SharePoint (Foundation) 2010, the first thing you have to do is install the prerequisites required to successfully complete your installation and run SharePoint. One of the annoying things about the prerequisite installation procedure is the fact that your machine does need internet access. In many cases, that’s no problem. But there are some cases where it’s impossible (due company/network restrictions) to have internet access on the machine where you want to install SharePoint.

There is a solution where you can install the prerequisites in an offline mode. In this post, I’ll explain each step how you can install SharePoint (Foundation) 2010 without an internet connection

1. Download and extract your SharePoint Installer

  • The first step is to download SharePoint 2010 using an internet connected machine. You can download this using your MSDN subscription or using this link (for SharePoint Foundation 2010).
  • Once your download is finished, go to the ‘C:\’ drive of your SharePoint machine, and create a new folder. Let’s call this folder ‘SharePointFiles‘.
  • Copy/Paste your downloaded exe in this folder.
  • Open a command line prompt and navigate to this folder ‘cd c:\SharePointFiles
  • In the cmd, enter SharePointFoundation /extract:c:\SharePointFiles (the first term is the name of the downloaded exe, in my case the SP Foundation 2010 one)
  • The command in the previous step will extract everything to your folder ‘c:\SharePointFiles
  • Now you should also see the executable: PrerequisiteInstaller.exe which will allow us to install the prerequisites.

2. Download your prerequisites

3. Create a PrerequisiteInstaller.Arguments file

  • The next step is to create a PrerequisiteInstaller.Arguments.txt file in the SharePointFiles folder. This file will contain arguments, which will be used by the PrerequisiteInstaller executable.
  • Each component required by the PrerequisiteInstaller will have its own argument. This argument has a name, and a location where the installer can be found. In our case, we will create a list of arguments for all required components combined with the location of that particular installer.
  • To get a list of all prerequisite arguments, you can type ‘PrerequisiteInstaller /?‘. This will give you a popup with a list of the prequisites
  • In the PrerequisiteInstaller.Arguments.txt file, add the following commands: (All in one line, with only a space between each separate argument)
    • /Unattended /IDFXR2:C:\SharePointFiles\PrerequisiteInstallerFiles\Windows6.1-KB974405-x64.msu /SQLnCli:C:\SharePointFiles\PrerequisiteInstallerFiles\sqlncli.msi /ChartControl:C:\SharePointFiles\PrerequisiteInstallerFiles\MSChart.exe /Sync:C:\SharePointFiles\PrerequisiteInstallerFiles\Synchronization.msi /adomd:C:\SharePointFiles\PrerequisiteInstallerFiles\SQLSERVER2008_ASADOMD10.msi /Speech:C:\SharePointFiles\PrerequisiteInstallerFiles\SpeechPlatformRuntime.msi /SpeechLPK:C:\SharePointFiles\PrerequisiteInstallerFiles\MSSpeech_SR_en-US_TELE.msi /ReportingServices:C:\SharePointFiles\PrerequisiteInstallerFiles\rsSharePoint.msi
  • Note: Because I’m on a 2008R2 machine, I use the arugment ‘IDFXR2’ instead of ‘IDFX’. Be sure to change this if you’re on a 2008 machine!

4. Run the prerequisites installer

  • The only step left is to install the prerequisites.
  • You can run ‘PrerequisiteInstaller.exe’ manually by double-clicking on it, or using the command line
  • Because the file PrerequisiteInstaller.Arguments.txt is in the same directory, the installer will use this file for its own arguments and thus install the prerequisites in an offline mode.
  • You’re done!

5. Troubleshooting

  • It can be possible (like it was in my case) that the installation using PrerequisiteInstaller.exe did not complete. In my case, it was because there were some arguments missing in my arguments file.
  • There are log-files available who can tell you what went wrong. You can find this log-files in folder: ‘C:\Users\{user}\AppData\Local\Temp
  • The file is called something like  ‘PrerequisiteInstaller.2012.02.15.log

My Prerequisites in a zip file: here
My PrerequisiteInstaller.Arguments.txt: here

Thanks for reading!

TFS Extensions for SharePoint, manual installation

When I was at a customer last week, I had a situation that SharePoint Foundation 2010 was installed as a local instance on the TFS application tier. The TFS extensions for SharePoint were already installed using the TFS installation. Now the SharePoint Foundation 2010 instance had to be changed to a farm installation. So the SharePoint Content and Configuration databases had to be located on a data tier (SQL Server 2008 R2). After the re-install of SharePoint Foundation 2010 in a farm mode, the TFS extensions for SharePoint had to be installed again.

When I went to the Team Foundation Administration Console, the ‘Extensions for SharePoint Products’ were still there (as it was previously connected to our local SharePoint Foundation 2010 instance). The problem was that the TFS extensions were not available anymore on our new SharePoint instance. When I click on the ‘Extensions for SharePoint products’, I got the error:

“TF249063: The following Web service is not available: http://abc:17012/_vti_bin/TeamFoundationIntegrationService.asmx. This Web service is used for the Team Foundation Server Extensions for SharePoint Products”

That’s correct, that TFS integration service asmx was not available anymore. The first thing I did was an un-install from the extensions (using the TFS installation media). Then I did a re-install of the extensions, but without any result. I hoped those steps could solve my problem, but they didn’t.. Time for the next step.

stsadm to the rescue

To resolve the issue, you have to install the TFS extensions manually to the SharePoint solutions store, and then deploy them. To do this, you need the stsadm tool from SharePoint. That’s the command-line administration tool from SharePoint. You have to add 3 .wsp files to your SharePoint farm.

  1. Go to the directory: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\bin\
  2. Open a command window (Shift + right-click -> Open Command Window here)
  3. Be sure that you run the command window with a user who has the right credentials (SharePoint Farm Administrator and have rights to the Central Admin Content Database on SQL server)
  4. Run the following commands:
    1. stsadm -o addsolution -filename “C:\Program Files\Microsoft Team Foundation Server 2010\Tools\Templates\Microsoft.TeamFoundation.SharePoint.wsp”
    2. stsadm -o addsolution -filename “C:\Program Files\Microsoft Team Foundation Server 2010\Tools\Templates\ TswaWebPartCollection.wsp”
    3. stsadm -o addsolution -filename “C:\Program Files\Microsoft Team Foundation Server 2010\Tools\Templates\Microsoft.TeamFoundation.SharePoint.Dashboards.wsp”
  5. Open your SharePoint Central Administration (http://server:17012 or something equal)
  6. Go to system settings and click ‘Manage farm solutions’
  7. You should see the 3 TFS wsp files
  8. Click on the first one, and click ‘Deploy Solution’
  9. Deploy the solution by clicking ‘Ok’
  10. When you deployed the 3 solutions, you should see
  11. All you have to do now is grant access for your TFS instance to SharePoint using the TFS Administration console.

That did the trick for me. Thanks for reading!

Add reporting to a Team Project using Powertools

Last week, I had the following situation at a customer: There was a dual-tier TFS 2010 installation without reporting and analysis services. The customer did already create some Team Projects, and now they wanted to activate the reporting and analysis functionality. Ok, no problem at all. First installing the SQL Server 2008 R2 reporting and analysis functionality on the application tier and then link the reporting and analysis services to the data tier (where all database are stored, so the services do run on the application tier, and the data is stored on the data tier).

After the installation of the services, we wanted to upgrade our existing team projects to make use of the reporting functionality. There is a way to do this manually, like described in this post, but this is really hard. You have to download your process template, create the correct mapping on your reporting server, upload ‘all’ reports (for each team project), divide them in correct folders,..

There is a better way, use the TFS Power Tools. Just install the Power Tools on your application tier, and open a command prompt. If you enter ‘tfpt’, you should see a list of all the commands you can use with the Power Tools.

One of the cool features you have is ‘addprojectreports’. This will add or overwrite all reports of a team project with the reports from your selected process template. In our case, the team project does not have any reports (yet), so we want to add the ‘ MSF for Agile Software Development v5.0’ reports. We can simply do this using the command:

All you have to do is supply your TFS instance, the team project name and the process template name you want the reports from. After executing this command, you have your reporting linked to your team project. Note: Be sure that your team project collection has a folder on the report server (http://your_reportserver/Reports) like ‘TfsReports/DefaultCollection”, and that you link this folder to your reports section of your team project collection in the TFS administration Console.

To make use of your reporting, all you have to do is rebuild your analysis cube using the administration console ‘Start Rebuild’ button in the reporting section. Have fun!

(You can also use the Power Tools to create a SharePoint  project portal using the command: tfpt addprojectportal)