VSTS Setup and an Old Habit
A few months a go I had the pleasure of setting up Visual Studio Team
Systems for a small team of people to evaluate. Along the way I picked
up my old habit of writing down each step that was taken so I could
reproduce exactly what I did. I thought it might be kind of fun to
share my notes for setting up the Team Foundation(TF) server. I
installed the TF server in a virtual server that was a guest on a
Windows Server 2003 machine running Virtual Server. The TF server
needed to be the TF server, the data tier, an Active Directory server
for the test domain, and a VPN end point so the remote team members
could connect. This is what my notes look like:
- *1 Install Server 2003 + Windows Update
- Assign Static IP 192.168.***.***
- *2 Install SP1
- Windows Update
- Install Active Directory (Typical first server install)
- TFDomain.local
- Note: Installs DNS
- Note: Installs DHCP
- Remove DHCP server
- Install IIS
- *3 WIndows Update
- Install SQL 2005
- *4 Create & Assign SQL Server Reporting Services Application Pool
- Install Sharepoint Services
- Windows Update
- Exclude SQL Server Reporting Services from Windows Sharepoint Services Management
- Setup Domain Users
- TFSSetup *password*
- TFSService *password*
- TFSMike *password*
- Rest of team users
- *5 Create Domain User Group TFSAdmin
- Install Team Foundation Server
- Add TFSService to Namespace Admin
- Add TFSAdmin to Namespace Admin
- Reset SQL Analysis to 1 hour
- *6 Add TFSAdmin to Sharepoint Administrators
- Add VPN Role to server
- IP range 192.168.***.*** - 192.168.***.***
Enable Undo Disks
- Install ctl00... fix from http://www.amaxo.com/blog/archives/2005/05/eliminate_ctl00.html
- *7 Delete registry key HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VSS\VSSAccessControl
Enable Undo Disks
- *8 Add clients to TFDomain.local domain
- Add registry key back to eliminate errors (see 3 steps up)
- Enable Undo Disks
The *[number] steps indicate where I took a copy of the virtual
hard disk and saved it to a different location in case I needed to back
up a step or 2.
The clients were all Virtual PC images running Windows XP Pro that I
added to the domain and installed Visual Studio 2005 Team Suite
Edition. The team members are able to log on to the Virtual PC image
using the domain users I setup and then VPN to the TF server and use
all of the Team functionality. Overall, it works pretty well. Of course
since then Microsoft has released a Virtual PC image that has all of
the comonents pre installed. It makes it a lot easier to play with VSTS
but you don't get the feeling of accomplishment from getting this beast
all setup and running for the team.
Now, doesn't that look fun?