TFS 2013 has some hacks

on Friday, November 1, 2013

I’m attempting to install TFS 2013 and as part of the process I’m trying to install Sharepoint 2013 that comes with the installer.

The installer asked me to create a domain account for TFS’s SharePoint to run under (Server farm account). And, after looking at, http://technet.microsoft.com/en-us/library/cc263445.aspx, I decided that it would be a good idea to add the account to my SQL Server instance. So, I created one and gave the username/password to the TFS installer.

The TFS installer comes with a “version” of Sharepoint that it will install on the server to host TFS sites. I gave the installer the username/password of the domain account, and gave it the SQL server name. The Sharepoint installer used that information to promote the Login to have these roles on SQL Server

  • dbcreator
  • securityadmin

It also created these databases, with these rights to each database

  • WSS_AdminContent
    • db_owner
    • SharePoint_Shell_Access
    • SFDataAccess
    • WSS_Content_Application_Pools
  • WSS_Config
    • db_accessadmin
    • SharePoint_Shell_Access
    • WSS_Content_Application_Pools
  • WSS_Content
    • SPDataAccess

With the usage of underscores some places and no underscores other places you can see that Sharepoint was developed under a single vision.

But, the amazing part is that this account wasn’t setup with any special permissions; it was added to the database as a Login with no permissions to anything. After the SharePoint installer ran, it had a ton of permissions.

I like that it makes the installation easier, but I feel like I was left out of the loop. Did I miss an installation screen that explained all this? My apologizes if I did.


Creative Commons License
This site uses Alex Gorbatchev's SyntaxHighlighter, and hosted by herdingcode.com's Jon Galloway.