The entire process of installing and deploying vsts in the domain environment

TFS has been tested and installed on a single machine, but TFS has not been installed in the domain. This installation in the domain also encountered some minor problems. In general, the installation was still smooth, and there was no re-engineering.

Installation environment:

CPU: P4 2.8g
Memory: 1 GB

Windows Server 2003 Enterprise Edition + SP1
Windows SharePoint service 2.0 + SP2
SQL Server 2005 Developer Edition
Vs2005 team Foundation Server
VS 2005 team edition for software developers

Install on a machine with a new system installed as follows:

1. Install SQL Server 2005

Use the default instance during installation and select all services.
After the installation is complete, all services are running and the startmode is automatic. You can view and set it through the SQL Server Configuration Manager under configuration tools in the SQL Server 2005 menu.
Modify the settings so that SQL Server 2005 supports remote connections and TCP/IP connections.

Remote connections setting process:

There is an SQL Server surface area configuration under configuration tools in the SQL Server 2005 menu. After running, enter the surface area ConfigurationForServices and connections, locate remote connections in the tree on the left, and select local and remote connections and using both TCP/IP and named pipes, OK.

Note: We recommend that you Install SQL 2005 SP1. If SP1 is not installed, sqlserverkb must be installed from the installation disk of TFS before TFs is installed, and SQL server must be restarted once. Otherwise, widbloc will appear during TFs installation: cocould not list of fields to localize from the database error. solution.

2. Install Windows SharePoint Services 2.0 + SP2

During installation, select service farm. You do not need to make any settings after installation.

3. Install patchesProgram

. NET Framework 2.0, In the kb913393 directory of the TFS installation disk.
SQL Server 2005, In the sqlserverkb directory of the TFS installation disk (select one as needed ). This installation is not required if SQL Server 2005 SP1 is installed.

4. Prepare a domain account

Prepare two domain accounts. It is best to register two dedicated accounts. The password should be easy to remember and never expire. Then, add the two users to the local Administrators Group. These two domain accounts are used to run services, such as team Foundation server Windows Services and SQL Server reporting services.

Note: because the service is installed in the domain, you must use the domain user to run the service. Local users cannot be used.

5. Install TFs
Select single-server during installation, enter two domain accounts in sequence as prompted, and configure SMTP server and e-mail address according to the company's situation to receive prompt notifications from TFs. In this way, the installation is complete.

The widbloc: cocould not list of fields to localize from the database error occurs during TFs installation. solution.

TFS installation is complete.

6. Client installation

The system requirements of the client are the same as those of vs2005.

Installation environment:
CPU: P4 2.4
Memory: 768 m

Windows Server 2003 Enterprise Edition

First install Office 2003, and then install Project 2003.
Install VS 2005.
Install team explorer on the installation disk of TFS.

Installation is complete.

7. Install team Foundation build

In the build directory of the TFS installation disk. I installed the build on the machine where TFs is located. During the installation process, I entered the domain account and password for running team Foundation server Windows Services again. Build can also be installed on another machine.

In addition, the team Foundation server proxy is not installed because it is deployed on the LAN.

Note: you can install vs2005 + Team Explorer as a client on the host where TFs is installed. In this way, TFS can be configured and managed through team explorer in vs2005. If the client is not installed on the server. You can run

Tfssecurity/g + ADM: N: adatum \ dzilch/Server: http: // localhost: 8080
Adatum \ dzilch is a domain account

To add an administrator (domain account) for TFs. The command is located under <drive >:\ Program Files \ Microsoft Visual Studio 2005 team Foundation Server \ tools. In this way, the administrator can connect to TFs through team explorer on other machines in the domain for configuration management.

I used a command to add a domain account to the TFS Administrator group, and then used this domain account to log on to the domain on a machine in the domain, when using team explorer to establish a connection with TFS (machines not in the domain may not be connected, and machines that install TFs are in the domain ), the system prompts you to enter the user name and password (Windows authentication should be used and you do not need to enter the user name). If you enter the user name and password, you cannot log on to the system.

Error Message
Tf31003: Your user account does not have permission to connect to the team Foundation Server {0} . Contact your team Foundation server administrator and request that the appropriate permission be added to your account.

However, there is no problem with the TFS local connection. Somehow, after the TFS host is restarted, The Machine name cannot be connected to the TFS.

Error Message
Tf31002: Unable to connect This Team Foundation Server {0} . Team Foundation server URL: {1} .

However, the machine name and port number are correct. After the machine name is changed to an IP address, try to connect and successfully log on to TFs.

Although a TFs user uses a domain account, it also has its own role (group membership ). TFS users and project users are managed separately. First, all groups and users belong to the team Foundation Valid users group so that they have the permission to log on to TFs. It works in the same way as a Windows account.

 

The use of team system is still under exploration. If there is any deficiency in this article, it is normal. I hope you can give some advice and supplement.