加速软件开发：Team Foundation Server 2015管理指南

需积分: 0 51 浏览量更新于2024-07-17 收藏 11.09MB PDF 举报

《Essentials of Administering Team Foundation Server 2015》是一本由Gary Gauvin编写的专著，针对Microsoft Team Foundation Server (TFS) 2015的管理和操作提供了深入指南。该书的核心内容围绕在开发和测试环境中高效地使用TFS展开，旨在帮助读者加速软件开发流程。书中首先讲解了TFS的基础安装和配置，确保读者能够理解和设置这个系统以适应其特定的开发环境。作者着重强调了TFS如何通过集成源代码管理，将版本控制和项目管理无缝融入到整个软件开发生命周期中，使团队协作更为流畅。对于初学者和经验丰富的管理员来说，本书都包含了实用的建议，如如何设置TFS以支持敏捷开发方法，以及如何有效地利用其特性，如Team Build来管理构建过程。读者会了解到如何配置和部署构建服务器和代理，以便实现自动化构建和测试，以及如何使用模板简化生成过程，跨平台解决方案构建和测试的策略。在团队管理方面，书中详细讨论了角色账户设置、用户和组的管理，以及TFS的安全性与运行安全的最佳实践。确保数据安全和灾难恢复是管理员的重要职责，因此，作者也详述了备份和恢复TFS集中式系统的必要性，包括备份规划、还原步骤以及应对潜在灾难情况的措施。此外，本书还深入探讨了在创建和管理集合（项目）时的关键TFS功能，以及如何利用这些功能进行高效的项目管理。作者强调了对TFS中各种功能的深入理解和实际操作能力，这对于提升团队的整体生产力至关重要。《Essentials of Administering Team Foundation Server 2015》是一本实用的参考书籍，不仅适合TFS管理员，也适合开发人员和项目经理，帮助他们在使用TFS的过程中优化工作流程，提升开发效率，同时确保系统的稳定性和安全性。通过阅读这本书，读者将获得全面的TFS 2015管理知识，以应对不断变化的软件开发挑战。

Chapter 1 ■ planning for team foundation Server

Installation Considerations

There are a few pieces of information that you need to collect, and a few configuration tasks that you’ll

need to make sure have been completed properly. Here I’ll cover the system requirements and provide a

handy checklist that you can use so you aren’t hunting around for critical information when you are anxious

to begin.

Basic Requirements

One “new” requirement for this release is a 64-bit server operating system (OS). I know this is really not

“new” news for everyone, but if you haven’t had to install or upgrade an operating system in a while, this

may come as a surprise. Also, you may require different hardware to support a 64-bit operating system

(check with your hardware manufacturer on this). If this applies to you, now you may have that justification

you were looking for on ordering that new server.

You may have had no reason to upgrade your operating system before now, but to run TFS you need to

have a 64-bit server. Running TFS brings the perfect justification for upgrading your OS! )

Another question I’m getting these days on just about everything is if this (Team Foundation Server 2015

in this case) will support a Server Core installation. It will not. (More information on the Core Installation

Option is at http://technet.microsoft.com/en-us/library/cc771345(v=ws.10).aspx.) Just not enough

of what TFS needs with these options.

Installation Checklist

Here is a checklist to make sure that you have the basic information to begin. Please refer back to Table1-1 in

future chapters, because you’ll be reusing the information here in most chapters.

Table 1-1. Team Foundation Server 2015 Installation and Configuration Checklist

Details Parameters for Installation

Server names for each server involved:

• TeamFoundation2015(ortheoldTeamFoundation

Server if you are upgrading, and the new server)

• ActiveDirectoryDomain/DomainController

• SQLServer(ifyoursisseparate)

• SQLReportingServicesServer(ifyoursisseparate)

• SharePointServer(ifyoursisseparate)

See the “Active Directory” and “Supported Operating System

Requirements” sections in this chapter for additional

requirements for this environment. If your planned systems

don’t meet the specifications, go no further until you correct it.

☑ TFS Server

☑ Active Directory Domain

☑ Domain Controller

☑ SQL Server

☑ SQL Reporting Services Server

☑ SharePoint Server

(continued)

Chapter 1 ■ planning for team foundation Server

Accounts and Permissions

You will need a number of accounts for installing and running Team Foundation Server. Since the largest

number of issues I get questions on end up being permissions related as a root cause, I’m going to suggest

that you read this section carefully, without opting for shortcuts. Also, unless you are working on an upgrade

where the accounts have been established and working for a while, I’m going to recommend that you

establish new accounts and not reuse old ones, especially if this is an enterprise install.

Why you ask? Well, for one thing, people tend to adjust the security settings and permissions of

accounts over time either by accident (i.e., having trouble with getting a service to run and giving it Domain

Administrator privileges, and then forgetting to set it back), or if you have an IT security group that scans for

privileged accounts and scales them back based on the last login date (I worked for a large defense contractor

where that was the norm; caused me days of aggravation). You’ll avoid that by starting with new accounts.

Also, no section like this would be complete without a disclaimer: these recommendations should fit

most situations. If you are building a large scaled-out environment in a really security-strict environment,

you will likely need to make some additional adjustments to comply with these rules. Also, the user accounts

could be domain (recommended) or local accounts. If you are installing a component in a workgroup, you

must use local accounts for user accounts, however. The following names are only suggested. There is no

real requirement to use a specific name, but if you do not, be sure to list the one you use since I’ll be referring

to the suggested name from here on out.

Table1-2 provides the lists of user and service accounts, including descriptions of what they are.

Details Parameters for Installation

Service account names and login information. You’ll want this

information handy throughout the tasks in this book. If you are

creating these, see the “Accounts and Permissions” section in this

chapter as well to make sure that you have the permissions set

correctly. In a simple single server environment you may choose

to use a single account for this, TFSSERVICE for instance.

You will need these basic accounts for installation and operation

(see the “Accounts and Permissions” section). A common question

I get is, “Do I need to actually name my accounts this?” You don’t.

But if you do, it will make your life easier since this is how they are

referred to in most Microsoft documentation and this book.

But if you don’t, here is a handy place to list the equivalents:

TFSREPORTS – reporting reader account

TFSSEVICE – the server service

TFSBUILD – for the build service

TFSPROXY – for the proxy service

And you’ll need these for the other supporting software

(see the “Accounts and Permissions” section, but these are

generally user accounts):

WSSSERVICE – for SharePoint

SQLSERVICE – for SQL Server

☑ TFSREPORTS

☑ TFSSEVICE

☑ TFSBUILD

☑ TFSPROXY

☑ WSSSERVICE

☑ SQLSERVICE

Visual Studio Team Foundation Server 2015. You’ll need this

later on during the installation. For now, just locate the Team

Foundation Server 2015 DVD or ISO file from MSDN.

☑ InstallationMedia/ISO

Table 1-1. (continued)

Chapter 1 ■ planning for team foundation Server

Table 1-2. TFS Account Permissions

Where Used Recommended

Name (you will find

Microsoft referring

to that name)

Permission Requirements Notes

Installation/

maintenance

user account

TFSADMIN Full System Administrator

permissions on the server(s) for

the install.

You will likely get some grief if you

are in a big IT shop and request

this. However, it is definitely

recommended to make the install

go smoothly.

Reporting TFSREPORTS A user account that has the Allow

logon locally permission. You

will also see this referred to as the

Report Reader account since that

is what it does. This should not be

an administrator account.

You will be prompted for this

account during the install. You

will not be able to specify a built-

in account for the report reader

account.

Team

Foundation

Server

TFSSERVICE Can use a built-in account or a

user account. If you use a user

account, it must have the logon

as a service permission.

If a SharePoint site wasn’t

installed with Team

Foundation Server, you need

to add TFSSERVICE to the

Farm Administrators group

for the SharePoint Central

Administration site.

Do not use the account that you used

to install Team Foundation Server as

the account for TFSSERVICE.

If this installation will use reports,

you need to add TFSSERVICE

to the Content Manager role on

the server that is running SQL

Server Reporting Services. This

will default in the installation to

the Network Service account. This

usually works fine.

Team

Foundation

Build

TFSBUILD This can be a built-in or a user

account. If it’s a user account,

make sure it has the logon as a

service permission.

Team

Foundation

Server Proxy

TFSPROXY This can be a built-in or a user

account. If it’s a user account,

make sure it has the logon as a

service permission.

Only used in a Proxy install, but

better to have it ready if you decide

to deploy this component.

SharePoint

products

WSSSERVICE Needs to be a user account. If you install Team Foundation

Server with the default options,

this will be the same as the report

reader account. Note: It is also

the identity of the application

pool for the SharePoint Central

Administration site.

SQL Server SQLSERVICE This can be a built-in or a user

account. If it’s a user account,

make sure it has the logon as a

service permission.

No particular TFS requirements for

this account; just make sure SQL

Server is functioning normally for

the install.

(continued)

Chapter 1 ■ planning for team foundation Server

Supported Operating System Requirements

If anything, the supported operating systems got tighter this release with the elimination of some platforms.

You can use:

Server operating systems (Server Core installations not supported):

• 64-bit versions of Windows Server 2012 R2 (Essentials, Standard, Datacenter)

• 64-bit versions of Windows Server 2012

• 64-bit versions of Windows Server 2008 R2 (Standard, Enterprise, Datacenter)

• Windows Small Business Server 2011 (Standard, Essentials, Premium Add-On)

For the love of sanity, if you choose to go the SBS route, make sure that you calculate your fully

configured SBS server with all its components (Exchange, etc.), and then add the Team Foundation Server

requirements to those. Better yet, use it in your deployment, but not as a single-server TFS solution.

For installations of TFS or SQL Server with Windows Server 2008 R2, you need .NET Framework 3.5

installed. On Windows Server 2008 R2, you can install .NET Framework 3.5 by using the Add Features Wizard

from Server Manager.

Supported client operating system requirements:

• Windows 8.1 (Basic, Professional, Enterprise)

• Windows 8

• Windows 7 (Home Premium, Professional, Enterprise, Ultimate, SP1 minimum)

Where Used Recommended

Name (you will find

Microsoft referring

to that name)

Permission Requirements Notes

Release

Management

Server

RMSERVER Identity used in Internet

Information Service (IIS) for the

application pool and the Release

Management Monitor Windows

service.

This will default in the installation

to the Network Service account.

This usually works fine.

Release

Management

Server

DEPLOY This account is used to configure

machines in your environment,

so it will need whatever

permissions are required to do

this. Most of the time it will need

to be in the Administrators group.

If this account needs to access

builds on the network, make sure

it has access to the network drop

location that you specified in

the build.

Release

Management

Server

(connected

to TFS)

RMTFS This is a TFS user that is a

member of the Project Collection

Administrators group. Set “Make

Requests on Behalf of Others”

to Allow.

Not sure what this piece is all about

yet? Don’t worry, we’ll hit it again

later, and you might not even

need it.

Table 1-2. (continued)

Chapter 1 ■ planning for team foundation Server

It’s best to use a client OS only as a test install for a proof of concept. You will not be able to install

SharePoint, Reporting, or TFSProxy. What does this mean for you? No web site to collaborate, no HTML

project reports, and you won’t be able to proxy source files. Move to a server OS above for any production

use. I always find it amazing when I see questions on “performance issues,” and then find someone using a

client operating system. Also, the “Standard” install isn’t supported on a client OS since it installs SharePoint.

Have I talked you out of trying to do this on the cheap with a client OS yet? Very good.

Performance and Planning

Nothing gets more hotly contested in systems engineering circles than performance recommendations.

The recommendations in Table1-3 come directly from Microsoft. They are the minimum. Take special note

of the new hard disk requirements. Also, the numbers do not include recommendations for SharePoint

installed on the same server; those recommendations are in the next section. My notes from my personal

experience are in a following note.

Table 1-3. Scaling and Performance Recommendations

Number of Users Role Configuration CPU Memory Hard Disk

Less than 250 users TFS Server Single-server (Team

Foundation Server and

the Database Engine on

the same server).

1 single-core

processor at

2.13 GHz

2 GB 1 disk at 7.2k

rpm (125 GB)

250 to 500 users TFS Server Single-server (Team

Foundation Server and

the Database Engine on

the same server).

1 dual-core

processor at

2.13 GHz

4 GB 1 disk at 10k rpm

(300 GB)

500 to 2,200 users TFS Server Dual-server (Team

Foundation Server and

the Database Engine on

different servers).

1 dual-core

Intel Xeon

processor at

2.13 GHz

4 GB 1 disk at 7.2k

rpm (500 GB)

Database

Server

This is for the Database

Engine portion with 500 to

2,200 users (for preceding

configuration).

1 quad-core

Intel Xeon

processor at

2.33 GHz

8 GB SAS disk array at

10k rpm (2 TB)

2,200 to 3,600 users TFS Server Dual-server (Team

Foundation Server and

the Database Engine on

different servers).

1 quad-core

Intel Xeon

processor at

2.13 GHz

8 GB 1 disk at 7.2k

rpm (500 GB)

Database

Server

This row is for the

Database Engine with

2,200 to 3,600 users (for

preceding configuration).

Performance

2 quad-core

Intel Xeon

processors at

2.33 GHz

16 GB SAS disk array at

10k rpm (3 TB)

剩余197页未读，继续阅读

iebukes

粉丝: 9
资源: 132

加速软件开发：Team Foundation Server 2015管理指南

The Essentials of Risk Management, 2nd Edition.pdf

Windows Server 2016 Essentials和Windows Server 2016的区别

xamarin.form 打开pdf

1 2023-04-13 11:18:39 沙坪坝 客户提出计划 将商品进行打包 1 1根据以上进行生成20条数据

周克敏 essentials of robust control 课后解答

Windowsserver2012

推荐几个blog关于mqtt开发

添加Xamarin.Essentials库到Xamarin.Forms项目中

essentials of stochastic答案

https://zh-cn.tenable.com/products/nessus/nessus-essentials

最新资源

1 2023-04-13 11:18:39 沙坪坝客户提出计划将商品进行打包 1 1根据以上进行生成20条数据