blob: a3daf611bb3a7cf4de94da226efe43bf7677657e (
plain)
1 Team Foundation Server 2010 Beta 1 Configuration
2 ================================================
3 :author: Aaron Ball
4 :email: nullspoon@iohq.net
5
6
7 == {doctitle}
8
9 After finishing my last post on the installation of Team Foundation Server 2010
10 Beta 1, I closed down for the day and went home (now now, no judging...that was
11 a long post). Today I'm back to go over the configuration of TFS 2010 Beta.
12
13 If you're coming to this blog post from my last one on the installation of TFS
14 2010 Beta, you will have just restarted your server and the Team Foundation
15 Server configuration screen should be up. That's where we'll be starting here.
16
17 image:files/01_Welcome.jpg[height=300]
18
19 At the first configuration page, you must decide which confiruation path you
20 want to take. The descriptions that the page gives are quite helpful in
21 deciding which path to take since they give "You want to use this if..." and
22 "You don't want to use this if..." sections for each option. For my purposes
23 (Single-server installation with Sharepoint not installed yet and using the
24 default instance of SQL Server), the *Default Configuration* will suffice.
25 Click **Next**.
26
27 The next page of the configuration wizard (if Default Configuration was
28 selected) simply indicates that some tests will be performed on the server to
29 determine if certain pre-requisites are met for a proper configuration. Click
30 **Next**.
31
32 image:files/03_Enter_Service_Account.jpg[height=300]
33
34 Here you are prompted for a service account. This account will be used as the
35 service account to run Windows Sharepoint Services (WSS) and SQL Reporting
36 Services. For my instance, I created a domain user account called TFSWSSService
37 (creative, yeah?). If you want, you can click *Test* to confirm that the
38 username and password work. After typing in the requested username and
39 password, click **Next**.
40
41 image:files/04_Rediness_Checks_Successful.jpg[height=300]
42
43 Here the configuration wizard runs tests on your server to confirm everything
44 is installed properly. The first time through, I received a warning on the
45 first test because my firewall was disabled (I talked about that in the last
46 post regarding installing TFS). Since we're all learning here, I elected to
47 re-enable my firewall so I could have the problems that accompany closed
48 firewall ports (the more problems you have, the better you get at
49 troubleshooting the given system, right?). Click **Next**.
50
51 image:files/05_Applying_Configuration_Settings.jpg[height=300]
52
53 Here's where the real fun begins...if you can classify sitting around for about
54 20 minutes watching a looping progress bar as fun.
55
56 image:files/06_Success.jpg[height=300]
57
58 Once the configuration is complete and assuming you had no errors or warnings
59 on previous screens, you should seen a screen that says what we all love to
60 exclaim at the end of a long project...SUCCESS. The great thing is that if you
61 click **Next**, it continues to say Success as well as telling you where you
62 can find the configuration log. How considerate. Click **Close**.
63
64 That's it for now. If you followed my last post on the installation of TFS, you
65 probably noticed that I installed Team Build as well as TFS. My next post will
66 be on the configuration of Team Build.
67
68 Thanks for reading.
69
70 Dirk
71
72
73 Category:Microsoft
74
75 Category:Team_Foundation_Server
76
77 // vim: set syntax=asciidoc:
|
