More on the 2007 Install
I've been chided for inadequate planning. So, today, I plan to install 2007 again.
You guys that know me know that I don't see how that's inadequate.
Ok, maybe just a little more background.
In the past, I've gotten the software installed countless times. Then I was on hiatus for a few weeks and, then, many of my previous blog posts were lost to the ether. So right now, I'm just reminded how quickly I can get so stupid.
Here's what's happening, I get the software installed to where we get the central administration tasks. And I've always tried to follow them explicitly. But when I get to the Shared Service Provider part, it always wants to use my primary port 80 web site for the SSP. When I go into "Create new web application" the machine starts to act weird, taking forever and then leaving me on some strange page, I forget the details.
So, our new best friend Ethan, dropped me a note that suggest working all of the IIS website stuff first. His suggestion involves creating the IIS web sites for SSP and MySites, differentiating them by host headers, modifying the HOSTS file to support the host header names, and creating application pools and sibling folders to the wwwroot folder to virtualize their contents. Then, when you're staring at Central Admin and you go to create your SSP, there's already a perfectly functional web site there to use.
Now, I've always liked to leave Default Web Site alone so that you could always prove IIS was okay dokey just by pulling up the Under Construction page in wwwroot. However, bowing to the color of expertise, I'm going to try to follow his plan explicitly.
So, with that plan, off I go. Wish me luck and I'll get you an update.
-robot
Tags: