TFS Installation and Management

The whole days of TFS, some of the relevant configuration and installation of the key points to write down, hope to be useful to everyone. This article is mainly the installation and configuration of the content, the next article will describe how to use and use of relevant experience.

This article is brief:

1. Install deployment 1.1. Process

1.2. Install the operating system

Server recommended more than 2G memory, 500G hard disk space.

Must be Windows 2003, windows2008.

1.3. Configure the operating system

Change the computer name.

Install IIS.

Create TFS to run Reporting Services with auto-built users, recommendations belong to the Administrators group and are recommended to be named:

Tfsbuilder is used to build services automatically.

TFSReports: for Reporting Services.

1.4. Install prerequisite Software

Install Visual Studio 2010.

SQL Server 2008, you must install Reporting Services.

Install SharePoint 3.0 (the installation is automatically configured during the TFS installation).

1.5. Install TFS

The installation of TFS2010 is done with a very simple automatic wizard, which is basically the default configuration that you can install, and note the associated configuration of SharePoint with Reporting Services.

1.6. Precautions

For the server's machine name, you must complete the modifications before you install TFS, or if you modify the computer name after you complete the installation, some services in TFS will not function correctly.

If Reporting Services does not install correctly with SharePoint before you install TFS, TFS does not automatically configure the associations for those services, and subsequent use of manual configuration will be complex and have a low success rate.

The VS2010 is installed on the server side so that it can be configured with its clients after completing the TFS installation and has the highest permissions.

The server is estimated to take 3-5 hours from bare metal to the installation of TFS.

2. TFS Management 2.1. Project structure

TFS has a concept called a project set for project management, so that you can create a collection under which the related projects are created.

The application scenarios are:

1, the enterprise can create a project set according to each project group, the project of each project group under own project set.

2, a large project contains a number of small projects in the management mode.

2.2. Create and delete items

Open VS2010 team Manager, click on the project Set right button, action.

Then, depending on the wizard, fill in the project name, whether to create a portal site, whether to use the new source control, and so on, and finally TFS will automatically help you create the project you set.

To remove project management, open VS2010 Team Explorer, right-click the project, and then select the action:

Note: The deletion of the project information here does not automatically delete the portal site, the need to manually delete, delete the way see the following chapters.

2.3. Permissions configuration 2.3.1. Permission Description 2.3.1.1. Permission Association

TFS's permissions are associated with the operating system's user or domain, and TFS is a rights management support for database accounts, operating system accounts, and domain accounts. TFS, which is commonly used under 20 people, is recommended to use the operating system directly for easy and simple accounts. When a team of more than 20 people or more, it is recommended to use the method associated with the domain account.

2.3.1.2. TFS Permissions Structure

The permissions structure of TFS is hierarchically managed based on the project set, project, and content. The lower layer overrides the upper-level permissions configuration.

2.3.1.3. Permission Groups

TFS has a default group at each permission level, and you can modify existing groups or create your own groups.

The following groups are defaulted under the project set:

Under each item, the following groups are defaulted:

Each permission group can include different members, with different permissions for operations.

2.3.2. Project Permissions Configuration

The project's permissions configuration includes project-level, source code, region, team query, and generated permission control.

Project-level permissions control, just to control whether users have access to the project, as well as the project set. Project-level access does not represent permissions with source code, zones, and so on, and requires one by one configuration, but TFS generates 4 permission groups by default, and there are default configurations for different content, typically only members of those groups need to be configured.

To accommodate the default permission group, add members as an example:

Click VS2010 Team project Manager, right-clicking the team project, action:

The following dialog box appears, selecting the Participant click Properties:

In the following dialog box, select Add from Windows user or group, before the new pop-up box is entered in the system-created user name.

Note: For simple configuration, create an account for everyone participating in TFS Management on the operating system, and each subsequent user will log on to TFS based on the user name/password of the current operating system.

Once the operation is complete, the configured user can access TFS and work on it. The default four groups have different permissions, for example, the visitor has the fewest permissions, the user in the current group has the fewest permissions, and the Administrators group has the highest permissions.

When a user belongs to both the Administrators group and the Access group, the current user has all the permissions of the Administrator plus the visitor.

If you need granular permission assignments, you can create your own user groups for management. However, the newly created user group needs to assign permissions to the source code, region, team query, Generation, and so on, and then join its members.

The permissions of the source code can be divided according to the directory.

The permissions for a zone are primarily control over the work item content, such as whether a work item can be created, whether the task can be closed, and so on.

Team queries, mainly control the permissions of some of the customized query information.

Generated, primarily for permission control of the build operation.

2.3.3. Reporting Services Permissions Configuration

The permissions for Reporting Services are independent of project management permissions for TFS, and are set up in the following ways:

Open the report Configuration Manager, select the Report Manager URL tab, and click its URL to enter the following Web site:

Click TFSReports to enter the subdirectory, select the set of items you want to configure permissions for, and then select the items to go to subdirectories.

Then click on the properties for a few clicks:

Once you click Security, click New Role Assignment,

The following page appears:

Group or user name must enter the current operating system under the group name or user name, the contents of the permissions are checked according to the actual situation, and finally click the OK button to submit the completed operation.

2.3.4. portal Site Permissions Configuration

The permissions of the portal site for TFS are also independent of the permissions of the TFS project and need to be set separately. The Setup method is as follows:

In the server's VS2010 team resource management, select the project under Project set, right-click the display project portal and the following site appears:

Click on the link in the Red Circle-site action, select Site Settings in the dropdown box, and the page appears.

Select people and groups, and the page appears.

Click the New button and the new user page appears.

User/user group, you must fill in the user or group in this operating system, you can click Check Name to confirm after entering. The grant of permission is checked according to the actual situation, and finally click OK to complete the operation.

2.4. Work Item Management

Once a work item in TFS is created, it cannot be deleted. The main consideration should be that Microsoft feels that since there is a plan to add work items there must be a need to provide modifications, but no longer the UI page provides a way to delete. If you do need to delete a work item, you can delete it by using the command line. The operation is as follows:

Enter command-line mode,

Enter the command:

CollectionName: The name of the project set, which requires HTTP and port.

Idnum: The ID number to delete.

3. Template Customization 3.1. Method

TFS supports customization of work items, process templates. A secondary tool, Microsoft Team Foundation Server, is recommended for Power tools. After installation, you can export the template definition file directly from the server and import it directly to the TFS server after saving. If you do not use a tool, you can do it from the command line (not recommended).

After you install Microsoft Team Foundation Server Power Tools, this feature is added to the VS tool:

3.2. Work Item

Customize the work items, you can customize bugs, tasks, and so on, or create a new work item. This article explains how to modify the default task work item as an example.

Using Microsoft Team Foundation Server Power Tools, do the following:

Pop-up Select Type dialog box, select Project set, Project, type after Popup interface:

Fields is the field that defines the occurrence of a task work item.

Layout is the field layout that defines the dialog box that creates a work item popup.

Workflow is a workflow that defines the changes and actions of work item state.

3.2.1. Field definitions

The template can add a new field definition, and the information for the field can be referenced using the tool:

Select the custom definition you want to add from the work Item Field Explorer, depending on your actual needs.

3.2.2. Layout modifications

A template can define the location of fields in a window, and can also be checked using the preview feature.

Create a new control at the specified location, and then select Filedname and type in the Properties window.

Here you can choose the new type or the existing type that you just imported in the previous step, type specifies the control, which can be a drop-down box, a date selection or text, and so on.

3.2.3. Workflow Modifications

Templates also allow custom workflows to be modified with the VS designer and the toolbox controls.

3.3. Field mappings

In TFS Export to project file, you can customize the fields of TFS to be mapped with peoject fields, as follows:

To download the mapping file:

Project set name, project name enter according to the actual situation, the map file name can be customized.

When the download is complete, use the editor to open the XML,

You can add a record that corresponds to the field properties in the Work Item field Explorer, and to the fields in project.

Upload to TFS using instructions after you complete the modification:

TFS Installation and Management