In my last post I talked about building my new primary workstation for running Windows Server 2008. This post continues with the installation of Windows Server 2008.
First off, the screen (please wait) after selecting your keyboard layout took about 3-4 minutes before proceeding to the screen allowing you to select the version of Windows Server 2008 you want to install. I selected the 64bit edition and proceeded to the screen to select where I wanted to install windows, and hit my first issue.
No matter what I did, I could not install to my Raptor hard drive. I kept getting an error message indicating that "Windows is unable to find a system volume that meets its criteria for installation". The error also indicated that I could install to volume 0, which was my Raid-1 drive which I want to use as my data drive. I thought about unplugging the drives but figured it couldn't be something that easy, but after some searching I found this KB article which basically told me to unplug the extra drives.
After that small issue, the rest of the installation went without incident and quite fast, and soon I found myself sitting in front of a fresh Server 2008 install. Now I forgot to check how much ram was being used at this point, and proceeded to install the Nvidia drivers (Vista 64 bit), but after that I was using between 650 and 675 MB of ram at start up. Now compare this to <200MB of ram on a fresh server 2k3 and I have to wonder, what is using 400MB of ram and what am I getting out of it. Maybe I am just to nostalgic and remember back to the Windows 2000 days when a fresh install used less then 100MB of ram. Perhaps I should just spend the extra $100 and max out to 8GB of ram, but I am getting off topic.
I need to go a on slight tangent and talk about the Windows 2008 server core active directory stuff I'm working on in parallel. Using the command line tools outlined in my previous post, as well as the dcpromo GUI wizard on my new full Server 2008 install (to create the unattended.txt file), I got AD installed on server core for my new domain. One thing that happened during the install, was that the firewall rules for remote desktop were modified. I found that the following command will re-open port 3389: netsh firewall set service type=remotedesktop mode=enable. You should also check and make sure that you have a firewall rule in place for DNS.
- netsh firewall set portopening ALL 53 DNS ENABLE SUBNET - This will open up TCP and UDP port 53 for your local subnet.
- netsh firewall show portopening - Display the current ports that have rules
Back on my main workstation, I setup about installing some roles and features. For features, I added the administration tools for things like AD, DNS and Hyper V. For the role, all I added was Hyper-V (and according to an article I read, hyper-v should be the only role installed). To install Hyper-V, first I installed the RC0 hotfixes, then added the role. It was pretty straight forward, although it required a reboot. Once Hyper-V was installed, I started setting up my first VM, a Server Core 2008 VM as my second domain controller for my new domain.
Poking around in the GUI manager for Hyper-V, I see some interesting things, such as resource allocation, integration services (heartbeats, backup/volume snapshot), and the ability in the networking setup to use VLANs. I should also note that after Hyper-V was installed, it created a new virtual network interface, and the interface that is for the actual physical adapter no longer has an IP address. I am assuming this has to do with the VLAN support in Hyper-V, but I don't know for certain.
I started out with two VM's a Server Core instance as my 2nd domain controller, and an XP SP2 instance that will serve as my primary office environment (i.e. developer tools, MS office, MS Money, etc). The network adapters were a little tricky with both instances. For the Server 2008 instance, you have to run the same hotfix in the VM as you did on the host OS. I created an ISO with the hotfix and then mounted it in Hyper-V. On the XP instance, I had to change to a legacy network adapter, as the smBus network adapter is only supported if you install the integration tools, and those are only supported in SP3 for XP.
Changing gears, I set about installing some games on my host, mainly World of Warcraft, Call of Duty 4 and UT3. I installed all of the games into C:\Games\ and set permissions for my normal user account to full control on that parent directory. I then installed all of the games using an Administrator account. WoW installed with no problems, COD4 does in fact require DirectX 9.0c, and I had to modify the .msi file in UT3 before installing (by following these instructions).
So far things are going OK. I still need to play test COD4 and UT3, but WoW works without issue. I've noticed some performance issues between my Folding@Home instances and my VM's running under Hyper-V, such that I am only running three instances instead of 4 so I always have at least one core free for the VM's.
I have a couple of things left to do:
- Finish setting up my XP instance for day to day tasks. This should be pretty straight forward
- Finish setting up AD and DNS on my domain controllers (basically make sure that the firewalls are configured correctly and that DNS and AD replication is occurring)
- Determine storage location of programming projects and documents (Do I store them on a VHD, or just share them out from a location on the host).
- Get the old hardware running up as a HTPC (it won't power on, even though it's the same hardware except for the case. I may have damaged something during the case transfer).
I will follow-up with a part III in the next couple of days.