I am just about to start installing Team System. I must admit I am a bit intimidated by it. It's a three-tier install:
The SQL Server bits do not coexist peacefully with the Team System Foundation bits, and even if they did I would be afraid of the CPU/memory overload of running all three on one box. And since I want to use Virtual PC, the lack of speed will likely kill me.
So I decided to install SQL Server 2005 on my laptop. Now I run XP Home on my laptop, and that is not one of the supported operating systems. So I will have to install Windows Server 2003 as a dual boot to get the database installed.
Foundation Server should run fine in a Virtual PC instance on my main PC. I will install Windows Server 2003 as the Operating System for that.
And of course the client can run natively in Windows XP Professional on my main PC.
So here goes:
Sun Oct 3
3:30 pm: Repartitioned laptop, to free up 10GB for dual boot OS.4:00 pm: Started Windows Server 2003 install in new partition.5:30 pm: Windows Server 2003 install finished without problem. Started SQL Server 2005 install.5:45 pm: Created new Virtual PC image on my main PC, and began Windows Server 2003 install on it.(Took a break for dinner and a movie.)8:00 pm: SQL Server 2005 installed without problem. It looks quite different from SQL Server 2000 - so this is one more thing I will have to play around with and learn.11:00 pm: Windows Server 2003 installed without problem.
Still To Do
I am going to set the Win2K3 on my main PC as the domain controller. I have read that the server components must run under a domain. I need to install the Team System Foundation Server bits into that VPC instance. Finally, I need to install the client components under Windows XP Professional.
Disclaimer The opinions expressed herein are my own personal opinions and do not represent my employer's view in any way.