I’m at what I hope to be the tail end of a long, and I mean loooong, drawn out Sharepoint Services Upgrade. I’ve been using 2.0 forever, and want to upgrade to 3.0 to support Office 2007, as well as to get on the newer version.

Well, I finally had a successful migration in my test environment! Yay! Now, I’ll just wipe it all out, try it again, just to make sure it wasn’t a fluke.

Here’s where I run into the problem. After uninstalling everything, and then re-installing Sharepoint Team Services 2, I received the error below:

Well, after a quick review of my tax papers before I send them out tomorrow, I discovered a serious error. I did it again, and wound up paying a lot more than I had thought I originally would. My wife wasn't satisfied with this, so I did it all again with the same result.

So I went online and did it at H&R Block's web site. Same.

I just wanted to apologize in advance for the upcoming show, and for anyone who dropped in on our first ever ustream.

First of all, we weren't able to set aside a block of time to figure out the ustream stuff before we went live, so we were figuring it out right there, in front of all of you. Sorry if we bored you to death while we fumbled around with it. There were a few people with us at the beginning but they dropped out after a while. One stayed with us till the end, so thank you, whoever you are.

Do you ever get nervous about using images on your blog or web site?

I’m sure that I’m not the only one who has become accustomed to opening up Computer Management on a server, and looking in the shared folders in order to find out who has a file open. Well, that was Windows Server 2003. Now that we have Windows Server 2008, it’s just a little bit different.

<!--extended-->

Here’s how you do it.

In Server Manager, expand Roles, then expand File Services, and click on “Share and Storage Management”.