It’s Monday morning and things are relatively slow on the IT front, so I’ll get you up to speed on the technologies I’ve been working on/at.

Team Foundation Server:

This little gem is an MS server application that acts as a companion to Visual Studio desktop applications. The TFS allows developers to store and share code on the server with a TFS plugin in Visual Studio. Our developers are spread out between England and the US, so this was a logical upgrade from Visual Source Safe, where outside developers had to VPN in order to share code. TFS has a SQL back-end and Sharepoint Services reports and document storing area, which means you have install about 4 programs and 5 upgrades before actually installing TFS.

The problems:

1) The application had to be set up before a consultant got, but the dedicated hardware for the application hadn’t arrived yet. So, I had to set up the TFS on a server with another SQL back-end application already running. This other application was not production yet, thank goodness, so I could back it up and run TFS.

2) Day one of transfer: Once the consultant left and the new hardware arrived, it was time to back up the TFS and move it to the new server. Let me tell you, it’s not as easy as you would think. The MSDN forums were fairly helpful, in that other people had the same problems as me, but were unable to solve them.

3) Day two of transfer: MS documentation has faltered and I end up calling MS TFS support. They responded fairly quickly and were very helpful. Three days, two remote assistance sessions and nine hours on the phone later, it was fixed and ready to roll. Oddly enough, the application that ‘had to be ready’ a week before, could be down for three day without any complaint.

4) Now that everything was working we still had the problem of VPNing for outside users. The main reason that TFS is pretty good is the HTTP(s) access works and there are instructions, but it still had to be setup. Having never set up an SSL certificate website for IIS, I had our friendly ISP walk me through it. The MS instructions for HTTPS/SSL setup were pretty darn good, so once I had the certificate, it went smoothly. Now all I had to do was open up ports in the firewall for the new SSL ports.

5) Now that TFS is working, I have to get the old application, an Incident Management application, working. While it’s not nearly as complex as TFS, I still had to call support. This was solved within a day.

Tomorrow: The on-going backup exec server saga…