While installing TFS 2013 in a Windows Server 2012, I was having issues getting the TFS Application Tier to connect to WMI on the Reporting Server. Being that I’ve installed Team Foundation Server 2010 and 2012 countless times, I was sure that all of my settings were correct. Therefore, I predicted that this must be a firewall issue…and I was correct.
I have a TFS 2012 infrastructure designed according to Microsoft’s proposed multi-machine architecture. I am currently running Team Foundation Server 2012 with Update 1. A few weeks ago, I noticed my reports in SharePoint not being updated. Upon examining the web service admin interface (http://<your url>:8080/tfs/TeamFoundation/Administration/v3.0/WarehouseControlService.asmx), I was able to confirm that the jobs were not running.
You’ll notice in the attachment, my request to the process service is: 2013-02-16T23:29:54, however, the last time the Incremental ran was 2013-02-16T20:35:28. Furthermore, there is no <NextRun /> element. I’ve checked the settings, and its set to run every 7200 seconds (the 2-hour default).Read more
I was asked to take over a TFS installation. Apparently, there was no one, previously, knowledgeable in administering Team Foundation Server because there were many installation and configuration issues – it was a mess.
One such issue was misassignment of user permissions. For instance, the business needed multiple users to have access to the TFS analysis cube in order to generate reports and pivot tables in Excel. The business’s solution to granting users “read” access to the cube was to grant them TFS Administrator privileges. In fact, there were over 20 users who were authorized as Team Foundation Administration Console Users.
By doing this, not only does the user have incredibly insane permissions around TFS, but they have administrative privileges (Read/Write) to the analysis cube – they would be added as a member of theTfsWarehouseAdministrator role group on the analysis server.