Adventures in Team Foundation Server RC

Team Foundation Server Install Guide

 (Single Server VPC version)

First, do not install a domain controller on the single VPC image. What the install guide does not say is as important as what it does say. In previous incarnations of TFS, you had to have domain accounts, which meant you either had to install on a DC image or join a domain. The current install will install on a workgroup, so you do not have to have a domain. NOTE: Installing without a domain is only useful for a small number of users, so it is not the proper way to go, but this is also a test machine with Visual Studio installed, so it is fine here.

Second, make sure to turn off SQL Browser before installing the patches (RC install). If not, it will disable the service. If you disable the service, you will have to go into the Services administrative console and turn it back to automatic. BTW, the first patch disables Service Broker regardless, but leaving it on will cause additional problems.


Step by Step

  1. RTFM. Then read it again. Then, you may still have problems, especially if you have done this before and try to work from memory. NOTE that the old rules do not apply anymore as Microsoft has made the install "easier"; follow the new rules.
  2. If you are making a VPC, create a VPC image with at least one large disk. By large, I mean larger than the 16 GB default. You will likely end up with a TFS install error if you only have one 16 GB virtual disk. For my install, I used a 16 GB root partition and a 127 GB expandable second drive. Please note that the install guide says 8 GB free is enough for a small team, but I have still had installs fail with this much room available. Just make more room. Nuff said!
  3. Install Windows Server 2003 R2 and then patch up the install with all of the latest patches. DO NOT install a domain controller on this machine; this was supported (and perhaps even necessary) in earlier betas, but TFS is not supported on a DC any more and WILL NOT install, period.
    1. For sanity, you should turn off the shutdown tracker if this is a VPC. To do this, see this site. This does not apply for production machines where the tracker is actually used.
  4. You might as well start the firewall now. It does nothing for you, but TFS expects to add exceptions, so you should start it before then.
  5. Create local accounts for install, TFS and reports. Do this now, as adding them just before they are supposedly needed can cause some issues. If you are on a domain, make them domain accounts; if not, you can make local accounts. The suggested accounts are.
    1. TFSSetup
    2. TFSService
    3. TFSReports
  6. Assign proper rights for the above accounts.
    1. All need to be local admin – this can be done right after adding the account by either opening each and adding it to the Administrator group or (better) opening the Administrator group and adding all three at one time.
    2. The service and reports account need “log on local” privileges. This is done with Local Security settings. Open Local Policies >> User Rights Assignment and find “Allow log on locally”.
  7. Install IIS
    1. Go to Control Panel >> Add/Remove Programs to launch the add/remove dialog
    2. Click Add/Remove Windows Components (left side)
    3. Click on Applications Server
    4. Enable ASP.NET (you will change this to ASP.NET 2.0 later)
    5. Click on details under IIS
      1. DO NOT (under any circumstances) add FrontPage extensions. They will hose up SharePoint. I repeat, DO NOT install FrontPage extensions.
      2. Add SMTP service, if you are going to set it up to send email alerts.
      3. You will also need BITS for TF Client install, but the TFS install will install for you, so you can leave it unchecked for now.
    6. Let it install. NOTE: You will need the Windows 2003 R2 disk 1 for this install. If you have two virtual drives and did not format drive 2 prior to original install, you will have to redirect the install to the proper drive letter for the CD. In my case, I have to change D: to E: every time it searches for files. I am sure I can fix this in the registry, if I cared enough to take the time.
    7. Check windows update again for patches, just to be safe.
  8. Install .NET 2.0. If you already installed this, you will have to run aspnet_regiis under the 2.0 directory with the -i (not the -ir) switch. This will register ASP.NET 2.0 as the default in IIS. The command is %WINDIR%Microsoft.NETFrameworkv2.0.50727aspnet_regiis.exe –i
    1. To double check this:
      1. open IIS Manager under admin tools
      2. right click the default web site and go to properties
      3. Go to the home directory tab
      4. Click on Configuration
      5. Make sure mappings for ASP.NET files points to v2.0.50727. The files are .ad, .adprototype, .asax, .ascx, .ashx, .asmx, .asx, .axd, .browser, .cd, .compiled, .config, .cs, .csproj, .dd, .exclude, .java, .jsl, .ldb, .ldd, .lddprototype, .ldf, .licx, .master, .mdb, .mdf, .msgx, , .refresh, .rem, .resources, .resx, .sd, .sdm, .sdmDocument, .sitemap, .skin, .soap, .svc, .vb, .vbproj, .vjsproj, .vsdiso and .webinfo. You do not have to check every file, unless you are really anal about these things.
  9. Install SQL Server 2005. The proper versions are Standard or Enterprise, although Developer seems to work fine.
    1. If you are following proper protocol, use the Setup account now. Any admin account will work; the Setup account is largely created so you can have a person setup the server who is not a domain admin.Find the SQL Server CD of choice and run it.
    2. Click on the install link (first link under the middle group)
    3. Accept the agreement and click next
    4. Click Install to install the Native Client and Setup Support Files and then click next when it is done (about 1 minute)
    5. It now says it is going through a system configuration check (not sure it does anything here for real, but it takes about 30 seconds). When finished, click next.
    6. You now do a visual system configuration check. Make sure everything is a success before going on. In other words, fix any problems if you have them. If fixed or no problems (the norm), click next.
    7. Complete the registration information. If this is an MSDN install, everything will be filled out for you. Click next.
    8. You need everything but Notification Services if you want to install TFS, so go ahead and check everything. If you also want the samples (for example, this is going to be a test dev machine rather than just a server), click advanced, click on Documentation, Samples, and Sample Databases and click “Entire feature will be install on local disk drive”. Do not click next … yet.
    9. If you are not already on advanced, go to advanced. Under Database Services, click on Replication and choose “Entire Feature will be unavailable”. Also wise to move data files if you have a second VPC hard drive.
      1. Click on Database Services >> Data Files and change the Installation path (browse to folder in question). I set my files on the D drive, as this allows you to move the VHD to another spindle, for performance (if you are not using VPC, it still makes sense to put data files on different drives).
      2. You will want to do the same for the Analysis Services >> Data Files.
    10. Before moving on, you can also make it so all of the client tools except management tools are not installed. This is not necessary on a test install to play with TFS, of course; on a real server, however, you do not want additional tools installed that increase the footprint of the attack surface.
    11. Click next after all is done
    12. Install as a DEFAULT INSTANCE. DO NOT (under any circumstances) install as a named instance. It will not work with TFS (install WILL fail … period!)
    13. If this is a test machine, use the built in system account for ease. If it is not, the install suggests using local system regardless, despite it being a bad practice. You can always change this to a more sane option.
    14. In addition, you will want to set all services to start, even though you will have to turn off SQL Browser in a bit for the .NET 2.0 patch (RC install only?). If you want to leave SQL Browser off, it is okay, you have to enable it later, as one of the patches disables it, but you will not have all steps verified (part of the last install step (below)). Click next.
    15. The safer option is Windows Authentication mode only. If this is a development machine, it is often easier to work with mixed mode. Make a choice, fill in options as appropriate, and click next when finished. NOTE: Install guide says Windows Auth only, but this does not mess things up if you are a rebel.

      As an additional note. If you use mixed mode, make sure you think up a strong password. SQL 2005 will not install with sa or password as a password, which is a major godsend.

    16. Click next on the next screen (collation) unless you are in a foreign country and do not want the English defaults.
    17. Under Reporting Services, it will complain if you did not install an SSL cert. Click next.
    18. Decide if you want to send Microsoft install reports and click next
    19. Click install on the next page and wait a long time (esp. if on VPC). SQL takes 45+ minutes to install. Then click next and then finish.
    20. Verify the SQL Server install
      1. Open the configuration tool and make sure everything is running
      2. Check protocols and ensure TCP/IP is enabled. If it is not, turn in on and stop and start the services. The developer edition only has shared memory by default. Depending on your app, you may also want named pipes, but this is not necessary for most installs and certainly not necessary for TFS.
      3. Open the Reporting Services site (http://localhost/reports if you are on the machine) and make sure it is running properly. It takes awhile to spin up the site the first time, esp. on a VPC image

        DO NOT try to configure RS at this time (it breaks things). NOTE that TFS install MAY do this for you later, but only if you follow directions correctly.

  10. Now it is time to run KB912838 (located on the TFS RC disk).
    1. Turn off SQL Browser. I have installed this patch with Browser running and ended up with the same results as when it is not stopped. As the manual suggests turning it off, I feel this is the safer route, however.
    2. Run the install exe
      1. AS2005-KB912838-x86-ENU.exe – 32 bit
      2. AS2005-KB912838-x64-ENU.exe – Intel 64 bit
      3. AS2005-KB912838-ia64-ENU.exe – AMD 64 bit
    3. Click through all of the screens
      1. Next on first screen. Nothing you can do here anyway.
      2. Agree and then next
      3. Click Next (have to install the patch, even though you have the choice to turn it off).
      4. Click Install. Yeah!
    4. Turn back on SQL Browser. As this patch disables the service for you, you will have to go to services and turn it back on.
    5. Verify your install of SQL Server per previous instructions. Reporting Services should fire up rather quickly this time.
  11. Now you install hotfix KB913393.
    1. Turn off SQL Browser again. This is a paranoid safety thing for me. 🙂
    2. Run NDP20-KB913393-X86.exe
    3. Click through fewer screens than last time.
      1. Click OK on “do you want to install”
      2. Click “I Accept”
    4. Turn back on SQL Browser. No, this time it is not disabled.
  12. Install Windows SharePoint Services from the R2 disk.
    1. You will need R2 disk 2 for this install. You can also install from Microsoft download 
    2. Install as Server Farm (TFS configures this later) This is one area the manual is weak, as this tidbit should be in the checklist. As it is not, you have to read the separate install page. Installing as Default installs SQL Express. SQL Express blows up the TFS install. You cannot uninstall and get TFS install working (perhaps a registry spelunking trip?). If you install default you might as well decommission this install and start over.
    3. Click Install.
    4. When the SharePoint site comes up at the end, wave hello and shut it down. Do not configure. Have not tried configuring this site, but TFS install is supposed to do this for me and I do not want to tempt fate.
  13. Verify SQL Server again. This is largely due to my extreme paranoia at this particular point in time. Whew! It is still working! So far, so good!
  14. Verify ports. If you are going to continue to use Windows firewall, add these ports.
    1. Port 80 TCP – Web Server (Reporting Services/SharePoint Services)
    2. Port 443 TCP – Web SSL (Reporting Services/Share Point Services)
    3. Port 1433 TCP – SQL Server Service
    4. Port 1434 TCP – SQL Browser Service
    5. Port 1444 TCP – SQL Server Monitoring
    6. Port 2382 TCP – SQL Analysis Service Redirector
    7. Port 2383 TCP – SQL Server Analysis Service
    8. Port 17102 TCP – SharePoint Central Administration
    9. Port 8080 TCP – Team Foundation Server
    10. Port 8143 TCP – Team Foundation Server (SSL)
    11. Port 8081 TCP – Team Foundation Server Proxy
    12. Port 8144 TCP – Team Foundation Server Proxy (SSL)
    13. Port 9191 TCP – Team Foundation Build Remoting
  15. Install Team Foundation Server. Here are a couple of observations:
    1. Click on Team Foundation Server install.
    2. Choose single server install.
    3. Decide whether to send info to Microsoft and click next.
    4. Accept agreement and press next
    5. It now runs a check to make sure you have everything installed. NOTE: Passing the check does not mean you will be able to install TFS. There are numerous things that can munge it up. Press next when done.
    6. Choose install location and press next.
    7. Choose TFS Service account and click next.
    8. Choose TFS Report Service account and click next.
    9. Decide whether to send alerts (email notifications) and click next.
    10. Click install.
    11. Wait … wait … wait … click finish.
  16. Install the Team Foundation Explorer on this machine.
  17. Install Team Build on this machine
  18. Follow suggestions in the help file to ensure Team Proxy is set up correctly.
  19. Run the Microsoft update site to be safe.
  20. If this is also a client machine (hopefully test only)
    1. Install Visual Studio 2005 Team Suite (or one of the other SKUs). Will install on C regardless of what you do, as you already installed SQL Server 2005 with its client tools (if you did not install client tools, you are golden).
    2. Install Office 2003 – put on D drive
    3. Install Project 2003 – put on D drive
    4. Go to and hit the updater or update to SP2 and then go to update site and get the latest patches.
    5. Install the Team Foundation Client. This hooks into both Office and Visual Studio 2005, which is why you have to install them first.

You are now done and have a new play toy. Have fun!

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: