Information
The topic you requested is included in another documentation set. For convenience, it's displayed below. Choose Switch to see the topic in its original location.

Organize your server with team project collections

You can manage your team projects more efficiently by grouping them together and assigning the same resources to them. For example, you can group projects that have similar requirements or objectives, such as all projects that relate to a particular code base. You can then manage that grouping as an autonomous resource with its own user groups, server resources, and maintenance schedule. In Team Foundation Server (TFS), you group team projects together in one or more organizational units called team project collections. A team project collection is an organizing structure that you can use to define and control a group of team projects within TFS. When you create a collection, you specify the logical and physical resources that team projects within that collection can use. All the artifacts and data that those projects use are stored in the single database of the collection.

Team project collections provide server administrators with the following advantages:

  • A single database that stores all the data for every project in each collection. Administrators can back up and restore this database independently of other collections. An administrator can also detach a team project collection, back it up, and then restore it to a different deployment of TFS.

  • A scalable method that administrators can use to manage the resources that development efforts require. Administrators can reassign resources to better meet the demands of the projects within a collection.

Team project collections provide project administrators with the following advantages:

  • A grouping of related projects that can share reports, work items, and process guidance, as well as a code base.

  • An autonomous code base that can be built, branched, merged, and iterated according to the needs of the projects within the collection. Code dependencies outside the collection can be formally managed.

If you create multiple collections, you can store all databases for them on a single instance of SQL Server, or you can distribute the databases across one or more instances.

The following illustration shows how databases for team project collections are integrated with the logical architecture of TFS:

Example: possible location of collection databases

When you install TFS, a default collection is created to contain all team projects. You can create others as needed. All team projects must be created within a collection.

A: If you create more than one collection, you can better separate the operational needs for one code base or other grouping of projects from the operational needs for another grouping. Because the data for each collection is stored in its own database, you can independently manage many aspects of each collection separately from other collections in your deployment. For example, you can stop and start each collection individually. Therefore, you can schedule maintenance operations for each collection at different times.

Because each collection has its own set of users and permissions, you can help increase your operational security by isolating different code bases in different collections. You can then add users only to the collection that contains the project or projects that pertain to that particular code base.

A: There can be. If you create more than one collection, you increase the complexity of your deployment of TFS. You must back up and restore the database for each collection, and other management and maintenance tasks also increase in proportion to the number of collections that you have. For example, you must manage the set of users and permissions for each team project collection individually.

In addition, you should consider the following facts when you decide whether to create multiple collections:

  • You cannot link work items across collections.

  • You cannot branch or merge code across collections.

  • You cannot create queries across collections.

You can perform all of these functions across team projects within the same collection. You should consider consolidating team efforts to projects within a single collection if your development efforts will benefit from the ability to branch and merge code or you must query the status of work items that relate to the same code.

A: You can create team project collections from the administration console.

  1. Open the administration console for Team Foundation.

  2. Expand the name of the server, expand Application Tier, and choose Team Project Collections.

  3. In Team Project Collections, choose Create Collection.

    The Create Team Project Collection wizard opens.

  4. In Name, specify a name for your collection. Under Description, you can optionally specify a brief description of your collection and its purpose. Choose Next.

Note Note

You cannot use certain characters, such as slashes, in names of collections. For more information, see Naming restrictions in Team Foundation.

  1. In SQL Server Instance, specify the name of the server that is running SQL Server. If you want to use a named instance to host the database for this team project collection, you must also specify the name of the instance as in the following example:

    ServerName \ InstanceName

  2. In Database, perform one of the following steps:

    • If you want to create a database for this team project collection, choose Create a new database for this collection.

      Important note Important

      The service account that the Visual Studio Team Foundation Background Job Agent uses must have permissions to create a database on the instance of SQL Server where you want to create the database.

    • If you want to use a database that already exists on the instance of SQL Server, choose Use this existing database, and specify the name of the database in the text box.

      Note Note

         To use this option, you must specify an empty database that exists on the instance of SQL Server and to which you have been granted write permissions.

  3. Choose Next.

  4. If you have configured one or more SharePoint web applications to support your deployment, in the Web application list, choose a SharePoint web application, and perform one of the following steps:

    • If you want to use the default option of creating a site collection, choose Next.

    A SharePoint site collection will be created, and the name of the collection is used as the name of the sub-site of the root site that is configured in the SharePoint web application.

    • If the service account for Team Foundation Server is not a member of the Farm Administrators group, you cannot create a site collection as part of this wizard. You must use an existing site collection that a member of the Farm Administrators group created for you. In that case, expand Advanced configuration, choose Specify a path to an existing SharePoint site, and specify the relative path of the site collection that was created for you. Choose Verify Path, and if the path is correct, choose Next.

      Important note Important

      Unless your business infrastructure requires that you use an existing site collection, you should use the default option to create a site collection.

  5. If you have configured a server that is running SQL Server Reporting Services to support your deployment, perform one of the following steps:

    • In Reports, review the information for the server and the folder that will host reports for this collection, and choose Next.

    • If your user account does not have permissions to create a folder on the server that is running Reporting Services, you must use a folder that an administrator created for you on that server. In that case, expand Advanced configuration, choose Specify a path to an existing folder, and specify the relative path of the folder that has been created for you. Choose Verify Path, and if the path is correct, choose Next.

    Important note Important

    Unless security restrictions in your business infrastructure prevent the automatic creation of a folder as part of the wizard, you should use the default option to create a folder.

  6. In Lab Management, choose Configure Lab Management, and choose Next.

    Important note Important

    If Lab Management is disabled in the list of wizard pages, you must first configure Lab Management in the administration console for Team Foundation. For more information, see Configuring Lab Management for SCVMM Environments

    If you do not use Lab Management in your deployment, skip to step 12.

  7. In Library Shares, choose Add and Verify, choose one or more virtual machine manager (VMM) library shares that should be used to store virtual machine images for team projects in this collection, and then choose Add.

    You can also change the name of the library share to a friendly name by double-clicking it. For more information, see How to: Change the Library Share for Your Team Project Collections.

  8. Select or clear the Auto Provision check box for each library share, and choose Next.

    If you select this check box, Team Foundation Server automatically adds the library share to the team projects you create in this collection. For team projects that have not yet been created, the share is added when the New Team Project wizard creates the project.

    Important note Important

    You must add at least one Library Share to team project collection to enable Lab Management.

  9. Choose Next.

  10. In Host Groups, choose Add and Verify, choose one or more VMM host groups that should be used to deploy virtual machines for team projects in this collection, and then choose Add.

    You can also change the name of the host group to a friendly name by editing it. For more information, see How to: Change the Host Groups for Your Team Project Collections.

    Important note Important

    To enable Lab Management, you must add at least one host group to a team project collection.

    The verification process now confirms the following changes:

    • The service account for Team Foundation Server has been added to each host in the host groups that you have specified so that Team Foundation Server can communicate directly with the hosts on the host group.

    • The network adapter that will be used to connect to the virtual machines is specified.

    1. If the service account for Team Foundation Server (TFSService) has not been added to the administrators group on one or more hosts in these host groups, you must provide a domain account that has administrative permissions on all hosts in the host groups that you have added. This step allows the service account for Team Foundation Server (TFSService) to communicate directly with the hosts on the host group.

    2. If you have one or more Hyper-V hosts that have multiple network adapters and if Team Foundation Server cannot determine which adapter should be used to connect the virtual machines, the Multiple Network Adapters dialog box appears for each of these hosts. In the list, specify the network adapter that corresponds to your network location that you want to use.

    3. Select or clear the Auto Provision check box for each host group.

      If you select this check box, Team Foundation Server automatically adds the host group to the team projects in this team project collection. For team projects that have not yet been created, the host group is added when the New Team Project wizard creates the project.

  11. To specify the user account to use for communication between the test agents and build agents and between the test controllers and Team Foundation Server, choose Service Account.

    Caution note Caution

    For this service account, you must specify a domain account that has limited permissions. You must specify an account that does not have any administrative permissions and that is not used by any trusted service, including the build controller and the test controller. You should consider creating two accounts to use for this service account. For more information about these two accounts, see How to: Configure the Lab Service Account.

    1. On the Service Account tab, specify the name of your account in Account Name and the password in Password.

    2. To check whether the user account is valid, choose Test.

    3. Choose Next.

  12. In Review Configuration, review your data. If you want to make any changes, choose Previous until you reach the page that you want to change. If all the information is correct, choose Verify.

  13. In Readiness Checks, review the status of the checks.

    A blue underlined Error indicator appears next to any configuration that contains an error. You can choose the indicator for a detailed message about the problem. You must address all errors before you can continue.

  14. After all readiness checks have passed, choose Create.

    The process of creating a team project collection starts.

  15. After the wizard finishes, choose Close.

A: You can support physical and organizational changes in your business infrastructure by modifying the settings for your team project collections.

To stop or start a team project collection

  1. Open the administration console for Team Foundation.

  2. Expand the name of the server, expand Application Tier, and choose Team Project Collections.

  3. In Team Project Collections, highlight the collection that you want to stop or start.

  4. In General, choose Stop Collection or Start Collection.

    If the project collection is started, only Stop Collection appears. If the project collection is stopped, only Start Collection appears.

    Note Note

    If you stop or start a collection, the operation can take several minutes to complete. You might need to choose Refresh to display the change in state.

To edit the description of a team project collection

  1. Open the administration console for Team Foundation.

  2. Expand the name of the server, expand Application Tier, and choose Team Project Collections.

  3. In Team Project Collections, highlight the collection whose description you want to edit.

  4. In General, choose Edit Settings.

  5. In Edit Team Project Collection Settings, update the text, and then choose OK.

To manage membership in groups for team project collections

  1. Open the administration console for Team Foundation.

  2. Expand the name of the server, expand Application Tier, and choose Team Project Collections.

  3. In Team Project Collections, highlight the collection for which you want to administer membership.

  4. In General, choose Group Membership.

  5. In Global Groups, perform one of the following steps:

    • To add a group, choose New, and provide the required information.

    • To add users to or remove users from a group, highlight that group, choose Properties, and either choose Add, or highlight the user or group you want to remove and choose Remove.

    • To remove a group, choose Remove. This option is only available for groups that you added.

    • To rename a collection-level group, highlight it, choose Properties, and specify a different name.

To manage permissions for users and groups in the collection

  1. Open the administration console for Team Foundation.

  2. Expand the name of the server, expand Application Tier, and choose Team Project Collections.

  3. In Team Project Collections, highlight the collection for which you want to administer permissions.

  4. In General, choose Administer Security.

  5. In Global Security, highlight the user or group for whom you want to administer permissions, and then select the appropriate Allow or Deny check boxes.

    For more information, see Permission reference for Team Foundation Server.

To display the status and the log file for a team project collection

  1. Open the administration console for Team Foundation.

  2. Expand the name of the server, expand Application Tier, and choose Team Project Collections.

  3. In Team Project Collections, highlight the collection for which you want to view the status, and then choose the Status tab.

  4. In Status, review the information in Most Recent Servicing Activity.

  5. To view the log, either double-click it in the list, or highlight it and then choose Enter.

To display a list of team projects in a collection

  1. Open the administration console for Team Foundation.

  2. Expand the name of the server, expand Application Tier, and choose Team Project Collections.

  3. In Team Project Collections, highlight the collection for which you want to display a list of team projects.

  4. In Team Projects, review the list of projects and their descriptions, if any.

If you don't have SharePoint Products integrated with TFS, there will be no settings for you to manage. If you want to add SharePoint resources, see Add SharePoint products to your deployment.

To display the default root location for team project portals

  1. Open the administration console for Team Foundation.

  2. Expand the name of the server, expand Application Tier, and choose Team Project Collections.

  3. In Team Project Collections, highlight the collection for which you want to display the default location where team project portals will be created.

  4. In SharePoint Site, review the information in Current Default Site Location.

To add or change a default root location for creation of team project portals

  1. Open the administration console for Team Foundation.

  2. Expand the name of the server, expand Application Tier, and choose Team Project Collections.

  3. In Team Project Collections, highlight the collection for which you want to change the default location where team project portals will be created.

  4. In SharePoint Site, choose Edit Default Site Location.

  5. In Edit Default Site Location, perform one of the following steps:

    • If you want to specify a different SharePoint web application, choose an application in the SharePoint Web Application list, and then specify the relative path for an existing root site or site collection.

      Note Note

      If the SharePoint Web Application list is empty, no applications have been configured for use by Team Foundation Server. For more information, see Add SharePoint products to your deployment.

    • If you do not want to change the web application, specify the relative path for an existing root site or site collection.

  6. In Full Path, review the information, and choose OK if it is correct.

To remove the default location for team project portals

  1. Open the administration console for Team Foundation.

  2. Expand the name of the server, expand Application Tier, and choose Team Project Collections.

  3. In Team Project Collections, highlight the collection for which you want to remove the default location.

  4. In SharePoint Site, choose Clear Configuration.

    Important note Important

    By removing the configuration, you are removing the default location in which the Create New Team Project Wizard will create team project portals. However, you are not removing the site itself or any team project portals that already exist under it. Project administrators can still create a team project portal, but they must specify a location for it.

If you haven't added reporting for TFS, there will be no settings to manage. If you want to add reporting, see Add reports to a team project.

To view the root folder for report subfolders

  1. Open the administration console for Team Foundation.

  2. Expand the name of the server, expand Application Tier, and choose Team Project Collections.

  3. In Team Project Collections, highlight the collection for which you want to display information.

  4. In Reports Folder, review the information in Current Default Folder Location.

To add or change the root folder for report subfolders

  1. Open the administration console for Team Foundation.

  2. Expand the name of the server, expand Application Tier, and choose Team Project Collections.

  3. In Team Project Collections, highlight the collection for which you want to add or change the default root folder.

    Important note Important

    In this release, you cannot add a report server after the installation and initial configuration of Team Foundation Server. If you did not add a report server at that time, you cannot add a folder for storing reports.

  4. In Reports Folder, choose Edit Default Folder Location.

  5. In Edit Default Folder Location, specify a path or folder name in Folder path on the Reporting Services Server, and then choose OK.

    Note Note

    This operation will fail if you type the path of a folder that does not exist on the server and you do not have permission to create a folder on that server. You must specify an existing folder if you do not have permissions to create folders on that server.

To remove the default location for report subfolders

  1. Open the administration console for Team Foundation.

  2. Expand the name of the server, expand Application Tier, and choose Team Project Collections.

  3. In Team Project Collections, highlight the collection for which you want to remove the default location.

  4. In Reports Folder, choose Clear Configuration, and then choose OK.

    Important note Important

    By removing the configuration, you are removing the reporting functionality for all existing and future team projects in this collection. This change can significantly impact the functionality of all team projects in this collection. If you are not sure whether you want to make this change, choose Cancel.

A: Just like creating team project collections, you delete them using the administration console.

  1. Open the administration console for Team Foundation.

  2. Expand the name of the server, expand Application Tier, and then choose Team Project Collections.

  3. In the list of collections, highlight the name of the collection that you want to delete.

  4. On the General tab, choose Detach Team Project Collection.

    The Detach Team Project Collection Wizard opens.

  5. (Optional) On the Provide a servicing message for the team project collection page, in Servicing Message, specify a message for users who might try to connect to projects in this collection.

  6. Choose Next.

  7. On the Review settings that will be used to detach team project collection page, review the details.

  8. If you want to change any settings, choose Previous. If they appear to be correct, choose Verify.

  9. When all the readiness checks have completed successfully, choose Detach.

  10. On the Monitor the team project collection detach progress page, when all processes have completed, choose Next.

  11. (Optional) On the Review supplemental information for this team project collection page, note the location of the log file.

  12. Choose Close.

    The team project collection no longer appears in the list of collections in the administration console.

  13. Open SQL Server Management Studio, connect to the instance of the SQL Server Database Engine that hosts the collection database, and expand the instance.

  14. Highlight the name of the collection database (by default, TFS_CollectionName), and then delete the database.

    For more information, see the following page on the Microsoft Web site: How to: Delete a Database.

  15. Open SharePoint Central Administration, and delete the site collection that supported the deleted collection.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft