We got home late last night and I went in to check on the status of the newly virtualized casadehambone.com. I quickly discovered why the machine I had chosen to host the virtual instance had been sitting on the shelf ... its hard drive was making a high-pitched clicking sound. Bad drive, and I had copied the actual virtual machine hard disk to this drive in order to free up my portable hard drive for normal backpacking uses. The portable hard drive is now connected to my Windows Vista RC2 tablet pc just to keep casadehambone.com up and running for the time being.
I happened to have one more 40GB hard drive that I put into the newly designated host and have installed 32-bit Windows Vista RC2 on it. (For those keeping score at home, that's four Windows Vista RC2 installations and one Windows Server 2003 installation in the span of three days.) Hoping that this installation will be a keeper for a bit, I'm venturing further into the rat hole and installing Virtual Server 2005 R2 SP1 Beta 2 (zomg that's a mouthful; note the link points to R2 and not R2 SP1 Beta 2. Head over to http://connect.microsoft.com and apply for the R2 SP1 Beta 2 program and download it there.) to host the virtual instance. What's the chances this will actually work on Windows Vista RC2 with IIS 7.0?
Knowing that IIS 7.0 has been componetized to high heaven and that Virtual Server uses things like CGI scripts, Windows authentication, etc., I started down the path of some web research to find out what I was going to need to enable in order to get Virtual Server 2005 R2 SP1 Beta 2 running. I came across this post by Dave Northey which also pulls through some of the stuff from Ben Armstrong, our Virtual PC Guy. Short version is that I took Dave's lead and installed everything except ftp for IIS 7.0. It makes me a little uncomfortable having everything turned on and I'll likely go back and turn some stuff of after some further research. Needless to say, Virtual Server 2005 R2 SP1 Beta 2 installed just fine on Windows Vista RC2.
The next challenge was in getting Internet Explorer connected to the Virtual Server administration site. Despite my attempts to enable Windows Authentication, run IE as Administrator, etc., I had nothing but heartache. Turns out IE was treating http://localhost as being in the Internet Zone rather than the Intranet Zone. Adding http://localhost to the Intranet Zone sites fixed that little issue and I've no issue accessing the Virtual Server administration web site. Furthermore, I'm browsing the site with UAC turned on and no explicit need to run IE as Administrator whatsoever. This is goodness. [Edit: Turns out I had not rebooted after re-enabling UAC. Doing so broke the ability to sign into the Virtual Server administration web console and I had to setup a shortcut to Internet Explorer and run it as Administrator as outlined in the articles above.]
So, as I write this, the virtualized casadehabmone.com is now running under Virtual Server 2005 R2 SP1 Beta 2 and (hopefully) will be stable for a while once again.