I had problems accessing http://localhost on the Data/App tier of my Team Foundation Server after a clean install of VSTS Beta3 - Refresh
on Windows Server 2003 with Active Directory enabled. I followed exactly the instructions in the Single-Server Deployment Checklist.
The problem was resolved by making TFSSERVICE a member of Enterprise Admins and then rebooting the server. Clearly, there are some permission issues here.
Is this a known bug Can TFSSERVICE be made a member of groups with less power than Enterprise Admins
Will

TFSSERVICE needs to be a member of Enterprise Admins - problems accessing http://localhost
Janneman
Thanks,
Fdeveloper
TaegerD
1 x Primary domain controller (1.5 GHz + 512M RAM + Windows Server 2003 ) for doing not much more than managing 5 user's logon + permissions.
1 x Team Foundation Server (2.2 GHz + 1M RAM + Windows Server 2003 ) for data and application tier
1 x Build machine (1.5 GHz + 512M RAM + Windows XP - SP2) for continuous integration
5 x Developer machines (2.0 GHz + 256M [1G pref] RAM + Windows XP - SP2) - Windows XP for client tier + Visual Studio
Question 1: Would you agree with the above spec What adjustments would you make
Question 2: Would it make more sense to consider using a workgroup Are there similar gotchas to avoid
Question 3: Can you give me a link to a forum / blog where these sorts of issues are discussed
It would be a shame if VSTS was considered unsuitable for small agile teams. What are your thoughts on this I hope you're not going to say that teams of five and less are just playing at software development!
Thanks for your help; no more questions, I promise.
Will
sparkymark75
Please see the following http://blogs.msdn.com/robcaron/archive/2005/10/05/477565.aspx
Thanks,