1. Granting only the Administer Shelveset permission does not add a user or group to the Team Foundation Valid User group.
Details: If you add a Windows user or group and only set to Allow any Version Control permissions at the server or project level, such as the "Administer Shelved Changes" permission, they will not be added to the Team Foundation Valid Users group. If they are not a member of the Team Foundation Valid Users group, they cannot connect to Team Foundation Server.
Workaround: Because the Team Foundation Valid Users group cannot be manually changed, you must either add the user or group to an existing group (to inherit permissions of the existing group) or explicitly grant the user or group another server-level or project-level permission (for example, View Server-level Information) in addition to the Administer Shelveset permission. This extra permission will add them to the Team Foundation Valid Users group.
2. You receive the following message when you run TfsAdminUtil ChangeAccount for the TFSReports service account: "Remember to add new account: domain\TFSReports to Team Foundation Service Accounts group by using TFSSecurity - Team Foundation Server Security Tool."
Details: When You Use TfsAdminUtil to change the TFSReports service account, the final message generated by TFSAdminUtil ChangeAccount is incorrect. However, this message is relevant when you change the TFSService account.
Workaround: None. Ignore the message. Do not add the TFSReports service account to the Team Foundation Service Accounts group.
3. You can no longer build projects in Visual Studio after uninstalling Team Foundation Server.
Details: If the Visual Studio IDE and Team Foundation Server are installed on the same computer, and you uninstall Team Foundation Server, the Visual Studio IDE may be broken. You may see various errors when you try to build a project in the Visual Studio IDE.
Workaround: Repair or reinstall Visual Studio from Control Panel.
4. Workgroup Edition: Users cannot connect to Team Foundation Server.
Details: Users attempting to connect to Team Foundation Server Workgroup Edition receive the following error: TF31001: Team Foundation cannot retrieve the list of team projects from Team Foundation Server. The Team Foundation Server returned the following error: The request failed with HTTP status 403: Domain\User is not a licensed user...
Workaround: Workgroup Edition limits access to Team Foundation Server by checking that the user is a member of the "Team Foundation Licensed Users" application group. This is a special server-level application group with no permissions, and is used only by the Workgroup Edition. A Team Foundation Server administrator must add the user to this group in order for them to have access to Team Foundation Server. Note that the user still needs to be added to another Team Foundation Server application group to be granted permission to access the server and have various levels of functionality.
5. Workgroup Edition: Upgrade to Full Edition does not remove the "Team Foundation Licensed Users" group.
Details: After upgrading from Workgroup Edition to the Full Edition, when opening the server-level groups dialog (Server->Team Foundation Server Settings->Group Membership), the "Team Foundation Licensed Users" group is still present on the server.
Workaround: The full edition of the server ignores the "Team Foundation Licensed Users" group. Note that this group cannot be removed because it is a special application group.
6. Re-installing Team Foundation Server must be done with the same service account as the original installation.
Details: Re-install fails if you are user a different service account than when you installed Team Foundation Server.
Workaround: If you need to change the service account, re-install with the original service account and then run TfsAdminUtil ChangeAccount to change the service account.
7. After renaming a single server machine, the TFS Web services no longer appear to work.
Details: After renaming a single server machine Team Foundation Server no longer works, even after running TfsAdminUtil ActivateAT and TfsAdminUtil RenameDT. The NT event log will contain numerous errors that suggest that the remote server name could not be resolved. The issue is that the Web service to Web service calls will still be using the old single server name.
Workaround: When renaming the single server machine that contains the application tier and data tier, you need to update the values for TfsNameUrl and TfsName on the top level web.config under (%ProgramFiles%\Microsoft Visual Studio 2005 Team Foundation Server\Web Services\). You also need to update the BisDomainUrl and change its name to TfsNameUrl in TfsServerScheduler.exe.config file.