Let’s move on to the Team Foundation Server configuration. When you launch the administrative console for the first time after installing the product, you will be offered to configure the installed components (Figure 1). Several options are available for the most common cases when you start the configuration wizard (Figure 2). The Basic option installs the strict minimum for TFS with all the options configured by default, so you will have nothing to choose from. The second option, available only if you are on a Windows Server, configures your tool on a single server. Again, you will have almost nothing to choose from. The Advanced option allows you to configure everything from A to Z. It is this last configuration that I will describe in this article. The last two options allow you to configure only an application tier when you are performing a multiserver installation or to migrate an existing TFS to your new server.
Let’s go back to the advanced configuration. I describe here a complete configuration on a Windows Server 2012 R2 computer with an instance of Sql Server 2012, Reporting Services and Sharepoint Products 2010 already installed. It is quite possible to install some components later, but the configuration of these then becomes more complex. This is why I recommend that you install all your products before Team Foundation Server.
Once the wizard is started, you will be taken to a first home screen briefly describing what you can do (Figure 3). Be aware that you do not have to follow the order of the steps. You can simply click in the left menu on the step you want to configure directly. Points you must absolutely configure are marked with a warning icon.
The configuration really starts from here with the database part (Figure 4). Specify the name of the Sql Server instance on which you want to create your databases. You can specify a label to prefix these databases, which allows you, for example, to have several third-party data on a server. Note that this prefixes only the name of the database type and not the full name. For example, if I choose to add a MyLabel label, the name of the configuration database will be Tfs_MyLabelConfiguration instead of Tfs_Configuration.
The next step asks you to choose the account that will be used to manage Team Foundation Server. You must specify an account for the primary service and an authentication method (Figure 5).
Nothing special for the next step. It is suggested that you change the site name for the web access as well as the port number and virtual directory (Figure 6).
We then proceed to configuring Reporting Services. You are asked first if you want to configure them now (Figure 7). If you do not check this box, you can always return to it later. The next three steps are only accessible if the box is checked.
The first part asks you to specify the instance of Sql Server on which the Reporting Services are installed as well as the web addresses to the server and the report manager (Figure 8).
Here, nothing complicated, just mention the instance of Sql Server on which the Analysis Services are located (Figure 9).
An account is required to generate Team Foundation Server reports. This is where you need to specify it (Figure 10). Please note that this account requires only minimal rights. You do not need to use an administrator account.
Like the reporting part, the SharePoint configuration is optional (Figure 11). Again, the next step will only be available if you check the box.
If you want to link your TFS server to an existing SharePoint server, select the second option so that you can specify its addresses on the next screen (Figure 13). If you choose the latter option, you must first install the Team Foundation Server 2012 Extensions for SharePoint Products on your SharePoint server.
You can create a collection from the start to place your first projects (Figure 14). If you prefer to start in an empty environment, uncheck the box.
Your intervention is now complete, except to click the Next button. You will first get a summary of the different steps you have just covered (Figure 15).
Before starting the configuration, the wizard must verify that everything is compliant and available. A global check is therefore launched (Figure 16).
If all checks are passed, you can click the Configure button. The different points are then configured one after the other (Figure 17).
If all goes well, a message appears at the bottom of the page confirming the successful configuration (Figure 18).
Clicking the Next button brings you to the last screen that confirms your successful configuration and the details of your server (Figure 19). If you have the default Windows firewall, the exceptions are automatically added by Team Foundation Server. The list of these exceptions is listed in this last screen. If you use another firewall, do not forget to add the exceptions manually.
You are now ready to take full advantage of all the power of the product. Your Administration Console takes over all configuration points and allows you to modify some of them.