Using 64-bit Windows Server 2008 as a Workstation OS, Part 3

This article lists the steps I used to setup Windows Server 2008 (WS2008) Standard Edition as a workstation operating system on two different laptops.

First, if you plan to use WS2008 and Hyper-V to run virtual machines on a laptop, you’ll get best results if your laptop meets these criteria:

  • Processor that supports hardware virtualization (required for Hyper-V)
  • At least 4GB memory (8GB if you want to run multiple virtual machines simultaneously)
  • Fast internal hard disk (I’m using a 320GB 7200 RPM SATA drive)

I should also mention that I’m using WS2008 for running virtual machines in Hyper-V, and also for email, web-browsing, word-processing, spreadsheets and presentations. That’s it. Since Hyper-V performance is of primary importance to me, I don’t install the Vista-like Desktop Experience feature or tweak processor scheduling to improve media playback.

Now, here are the specific step to install WS2008.

1. If you’re replacing an existing operating system that you’ve already been using, then backup anything you want to save to an external drive. The folders I backed-up include:

a. C:Users{your username}

b. Project folders

2. Gather drivers for your laptop. Vista x64 drivers should work just fine.

 

3. Run the Windows installation

a. Create 2 partitions

i. A 40GB partition called RECOVERY, for backups
ii. All the rest goes to another partition SYSTEM

b. Install WS2008 on the SYSTEM partition

4. After the WS2008 installation completes, log on as Administrator and run Windows Update multiple times until there are no more Important updates to install.

 

5. Using the Server Manager app, add the following Role: Hyper-V.

 

6. Using the Server Manager app, add the Features you want. Here are the features I found useful:

a. Telnet Client (useful for testing ports and what have you)

b. Windows Server Backup

c. Windows Powershell

d. Wireless LAN Service

7. If you want to remove Internet Explorer Enhanced Security:

a. Using Server Manager, go to the Security Information section of the summary page and click on “Configure IE ESC”. Adjust settings to personal preference.

8. If you are not installed WS2008 SP1 (Build 6001), you may need to install the RTM version of Hyper-V. Download it from here.

9. Install your office productivity software.

 

10. Run Windows Update, install everything not marked Optional.

 

11. Using Windows Backup, backup the C: drive to the RECOVERY partition.

 

12. Using the Hyper-V Manager, available through the Server Manager, setup your virtual machines on Hyper-V.

 

13. Use this nifty converter tool to further configure the OS. Options I installed are:

a. General

i. Set owner information

ii. Disable IE Enhanced Security Configuration

b. Visual Tweaks

i. Disable ctrl+alt+del at Windows Startup

ii. Disable Shutdown Event Tracker

c. Network

i. Enable Wireless Networking

d. Other

i. Enable Windows Search Service

Gotchas

  • Since Hyper-V is a service that’s always running, it’s more difficult to use VHDs on an external drive. I’ve been told that it is possible to unmount an external drive containing a VHD used by a Hyper-V virtual machine, but I’ve not yet figured out how.
  • The Hyper-V role disables sleep mode and hibernate. I’ve seen some blog posts that describe a registry hack to enable sleep mode. But from what I’ve gathered it introduces system instability, so I’m willing to go without these handy features. More info here.
  • It used to be that you could not install Windows Live Messenger or Windows Live Writer directly. But I’m pleased to report that the Windows Live installer now fully supports Windows Server 2008!
  • If you install the Desktop Experience feature (I didn’t – don’t want to waste CPU cycles on it), Windows Vista desktop is not enabled by default, and it’s not at all clear how to get it setup. Here’s a great blog post that walks you through the process.
  • Here is another excellent blog post on tweaks to make Windows Server 2008 a better desktop OS.
  • Virtual machines configured to run on Virtual PC will need to be reconfigured to run on Hyper-V. This blog post walks through the process.