Lesson for today: read the install instructions.

Well, as soon I a stuck the Team System DVD into the drive, the install instructions came up. They are excellent - well written and helpful. I just wish I saw them earlier today.

So it turns out I missed several important steps.

* Both the application and database server needs to have the Application Server role configured. The application server needs ASP.NET while the database server does not. Neither server uses Frontpage Extensions.

* I had to download all the Windows Updates. There were a lot (22).

* I had to download and install SharePoint Services 2.0. Then had to download and install the Windows Update for that.

* I had to download and install ADAM (Active Directory Application Mode). I'm currently stuck, as the install instructions appear to require ADAM running on a specific port number, but my server says that port (SSL) is already in use.

Anyways, it's way past my bed time. I'll have to tackle the rest of this tomorrow.

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:

• SQL Server 2005 Beta 2
• Team System Foundation Server
• Visual Studio 2005 Client Beta 1

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.

Darren J has an excellent blog entry on how he was able to install Visual Studio 2005 Team System Beta 1 Refresh onto a single PC using Virtual PC. The most telling line was the last, however:

If you haven’t got 2GB ram on your laptop and your running this on VPCs, you best get an upgrade.

Uh oh. I'm going to do the install this afternoon. I might need to run out to Best Buy really quick!

Today has been one heck of a busy day. Right now, it is only 6:00pm, but it feels like 10:00pm. My brain is fried. I need some rest, and I can't seem to do any more work.

Problem is, this is crunch time on my project. I have a million meetings during the day, and a million things on my to-do list that have to get done pronto.

I love this job. Days like today make me glad I chose this career. But man oh man, I have to get this stuff done. Hopefully bitching about it on my blog will motivate my brain to hold on for a couple more hours.

Microsoft was kind enough to send to me the latest DVD of Visual Studio 2005 Team System. I am looking forward to installing this thing, starting tonight.

Here is an interesting article on the trials and tribulations of installing Team System using Virtual PC.

Klaus Aschenbrenner Blog:

Last week 've "tried" to install Visual Studio 2005 Beta 1 Refresh with the Team Foundation Services. First of all I want to say that it doesn't work, because the whole process is a little bit quite complex. To get the whole thing running you need 3 "separate" computers...

One important thing to mention: you must install all tiers on separate computers. Otherwise it doesn't work. Furthermore you need for the whole stuff a domain. So Microsoft also suggests to install on the database tier a domain controller...

Reading Klaus' site, I am a bit worried about the level of deep Windows technical knowledge required to perform the install. His site mentions the need to change the computer's SID. And I suppose these Virtual PC's need to talk to one another... (Hold me, I'm scared.)

Very informative. Thanks Klaus.

I read an interesting article today about Team System:

Above all, LaPlante promised BorCon attendees, VS Team System will be simple to use. "If you have to go and hire a consulting firm to figure out what you installed, we have failed," he says. "If, in order to collaborate, you have to do 20 more steps, then you are using Rational's tools."

I just saw a commercial from L'Oreal that promised to “decrinkle” your face. I looked it up on Google, and there is only one reference on the Internet to that word. Dictionary.com has never heard of it.

That's what is called a marketing gimmick. L'Oreal could not promise to dewrinkle your face, because that would invite lawsuits when it doesn't work. But you can't sue L'Oreal if feel they broke their promise to decrinkle your face, because there is no dictionary definition of that word.

So let me propose one for the benefit of L'Oreal customers everywhere.

crinkle: (n) A wrinkle, ripple or fold.
           (v) To cause to crinkle.

decrinkle: (v) To remove one or more crinkles.