We’ve been running an instance of Team Foundation Server (BETA 3) up on a virtual machine at Readify for about five months and a few people – especially Darren, have taken full advantage of it. This evening I spent about four hours remotely installing Team Foundation Server Workgroup Edition (RTM) into its production home on a non-virtual server.

The installation went smoothly as expected (I can almost do it in my sleep now) and it seems to be performing quite well. Now that we have the infrastructure setup there are a few housekeeping items that need to be dealt with and then we’ll open the gates.

Here is my TODO list over the next couple of days:

  1. Work with our fabulous infrastructure guys that aren’t at all the nasty draconian kinda guys that you find in most IT organisations to sort out our disaster recovery strategy (already having fun discussions around this).
  2. Figure out if we have a self-service story. I’m not going to give everyone the keys to the kingdom on this box, some of the assets that we are putting into it are going to be too valuable to risk this box being played around with. But – I still want people to be able to create their own team projects and this involves having some fairly heavy rights on the server. I’ll probably look at what is required to get the PCW kicked off via a web-based front-end which runs with elevated rights.
  3. Find out what we need to do as a partner, down here in Australia, to get a license for the full blown standard server edition. While the workgroup edition is a good start, we need to be able to support more than five users on this thing.
  4. Migrate existing projects across to the new box. I opted to do a fresh install onto a physical box rather than try and upgrade from BETA 3 to BETA 3 Refresh then to RTM, and then try to migrate the databases across. I know some people have been looking at what is required to migrate projects, and when we setup the BETA 3 environment we said that we wouldn’t necessarily be able to take the projects, I did say I would give it a good go. At the very least I should be able to dump out the source code and take the work item data across.

Of course, my first order of business tomorrow will be to take the above list of tasks and insert them into a TFS Team Project to manage adoption, issues and feature requests for TFS.