1 Installing Team Foundation Server 2010 Beta 1
2 =============================================
3 :author: Aaron Ball
4 :email: nullspoon@iohq.net
5
6 The installation of Microsoft's latest beta release of Team Foundation Server
7 2010 has apparently been quite a hot topic in IT lately. My Twitter page isn't
8 that popular and when I first started tweeting my progress, shortly after I was
9 receiving messages regarding my documentation and progress. Here is the shortly
10 awaited documentation on what I've done to install TFS.
11
12 Here's what my environment looks/will look like:
13
14 * Windows Server 2008 Enterprise (with hyper-v but that's irrelevant)
15 * SQL Server 2008 Standard
16 * WSS 3.0
17 * Sharepoint 2007 Enterprise
18 * Team Foundation Server 2010 Beta 1 (of course)
19
20 There are a few ways this environment can be changed around (which versions
21 such as Enterprise or Standard can be used). Check out Microsoft's TFS
22 installation documentation for this information (a convenient .chm file...check
23 my blog post on this if you have issues opening this file).
24
25 Additionally, _this post documents a single-server installation on a
26 64-bit machine_.
27
28 Here's a summary of the order of software installation that will be taking
29 place.
30
31 * Windows Server 2008 (we have to have an operating system)
32 * IIS 7
33 * SQL Server 2008
34 * Team Foundation Server 2010 Beta 1 (with WSS 3.0)
35
36 If it isn't obvious yet, this is going to be a long post. I've taken
37 screenshots of many of the steps which won't help the length. Is everyone
38 buckled in? Good. Let's get started.
39
40
41 [[installing-windows-server-2008]]
42 Installing Windows Server 2008
43 ------------------------------
44
45 The install of Windows Server really isn't that complicated. There are not
46 special requirements for this. However, post-install, my server was added to a
47 domain so I could use domain service accounts. It isn't necessary to have the
48 server added to a domain though.
49
50 [[installing-iis-7.0]]
51 Installing IIS 7.0
52 ------------------
53
54 This part really isn't too bad (thankfully). In the server management, on the
55 left click **Roles**. On the right, click **Add Role Services**.
56
57 image:IIS_01_Add_Role.jpg[height=300]
58
59 image:IIS_02_Role_Services.jpg[height=300]
60
61 Here some default values are selected. You need to add **HTTP Redirection**,
62 **ASP.Net**, **Windows Authentication**, and *IIS 6 Management Compatibility*
63 and all subordinate check boxes. Click **Next**.
64
65 Here your selections are reviewed. If everything is correct, click **Install**.
66 Once the install has completed, you'll see another review window. If everything
67 was successful, click **Close**.
68
69
70 [[installing-sql-server-2008]]
71 Installing SQL Server 2008
72 --------------------------
73
74 Here's where the real fun begins. This install isn't too bad. The real ticket
75 is to know if you have any service accounts you want to use for the SQL
76 services. Since I did a single-server install on a server dedicated to my team,
77 I used NT Authority/Network Service for mostly everything, but I'll get to that
78 a little later.
79
80 First off, insert the SQL installation media (I used an ISO file mounted
81 through Hyper-V for mine).
82
83 From here, run the setup executable on the disk. Mine did an autorun. From
84 that window, I selected **installation**on the left navigation pane. On the
85 screen that loads on the right, select **New SQL Server stand-alone
86 installation or add features to an existing installation**.
87
88 The screen that comes up will run five tests. If your installation is clean
89 than most likely all five will pass with a green check mark. Mine threw a
90 warning to me on Windows Firewall because mine was turned on with default
91 settings. Since the server is behind two firewalls, I elected to disable the
92 Windows firewall completely. Re-running the test after that resolved the
93 warning. Click **Okay**.
94
95 Here we are at the obligatory Product Key screen. Enter your product key and
96 hit **Next**.
97
98 If you accept the license terms (License Terms page), check the box and click
99 **Next**.
100
101 The next screen wants to install setup support files. Go ahead and click
102 *Install* to continue. The following screen will yet again, run some more tests
103 (eleven to be precise). Again, if this is a clean install, every test should
104 pass.
105
106 Here's one of the crucial screens: *. On this screen, you should select to
107 install *Database Engine Services* (for TFS), *Full Text search* (for
108 reporting), *Reporting Services* (for reporting), **Analysis Services**,
109 **Client Tools Connectivity**, and **Management Tools Basic**. Once those are
110 checked, click **Next**.
111
112 image:SQL_03_Instance_Configuration.jpg[height=300]
113
114 Hit *Next* to continue to the * screen. If you want to, you can rename this SQL
115 instance to whatever you want it to be. I chose the default MSSQLSERVER since
116 it will be used for TFS only and nothing else will be connecting to it. Click
117 **Next**.
118
119 Click *Next* on the *screen.
120
121 Here we are at the Server Configuration section. Unless you have any specific
122 domain accounts set up for running SQL, NT AUTHORITYNetwork Service will
123 suffice for all of the accounts listed. No password is required to use this
124 username. Also be sure to change *SQL Server Agent* to start up automatically
125 (by default it is manual). Click **Next**.
126
127 The Microsoft documentation suggests on the Database Engine Configuration page
128 that Windows authentication mode be checked. I have had some pretty nasty
129 experiences with this in the past and selected **Mixed mode authentication**.
130 Following this, you need to type in a password for the SQLSA user. Also, don't
131 forget to add all of the users you want to have access to the DB engine. Once
132 you're done with that, click next.
133
134 The next page is the Analysis Services Configuration page. Add any users you
135 want to have access to the analysis services that your SQL instance will
136 supply. Click **Next**.
137
138 On the Reporting Services Configuration page, select **Install the native mode
139 default configuration**. Click **Next**.
140
141 Here's the obligatory Error and Usage Reporting screen. Check whether or not
142 you want Microsoft to receive anonymous usage statistics regarding your SQL
143 instance and click **Next**.
144
145 Nearing the end, click *Next* on the Installation Rules screen.
146
147 *Finally*
148
149 Once the installation is complete, click *Next* and **Close**.
150
151
152 [[installing-team-foundation-server-2010-beta-1]]
153 Installing Team Foundation Server 2010 Beta 1
154 ---------------------------------------------
155
156 Here we are at the final software install. This part really isn't too bad
157 (surprisingly enough).
158
159 To begin, insert the installation media (once again, I mounted an ISO through
160 Hyper-V). If autorun is enabled, a standard window should come up giving you
161 the option to explore the newly inserted media. If this does not happen, just
162 open up Computer and navigate to the disk.
163
164 Inside the disk there are three folders. Depending on your processor
165 architecture, choose either the TFS-x64 or TFS-x86 folders. From within that
166 folder, run the Setup.exe file.
167
168 Here we're at the first screen. Click *Next* to proceed.
169
170 Once again, the ever-present Licensing Terms page. If you accept, check the box
171 and hit **Next**.
172
173 image:TFS_02_Features_to_Install.jpg[height=300]
174
175 The Microsoft documentation suggests that only Team Foundation Server be
176 checked. I actually need the build server to be on the Team Foundation Server
177 as well so I checked all three. Either will work though. **Click Install**.
178
179 image:TFS_04_MidInstall_Restart.jpg[height=300]
180
181 During your installation, the server will need to be restarted. Click restart
182 now. Upon restart, the configuration option will become available to you.
183
184 Pat yourself on the back. You just installed TFS. This is a long enough blog
185 post for now. I'll post here very shortly the configuration steps I took for
186 TFS (still haven't taken all of the screenshots I need for it).
187
188 Thanks for reading.
189
190 Dirk
191
192
193 Category:Microsoft
194
195 Category:Team_Foundation_Server
196
197 Category:MsSQL Category:IIS
198
199
200 // vim: set syntax=asciidoc:
|
