If you work with Exchange 2007 or Terminal Services/Remote Desktop Services in any anger, you’ve probably had to use Network Load Balancing (NLB) to balance services. For example I use it for the Client Access and Hub Transport roles in Exchange 2007, and to balance requests across my Terminal Services (Remote Desktop) Gateway servers. However, when virtualising these services, I found that Hyper-V doesn’t always play nice with NLB.
A quick disclaimer: this should work for the entire IBM DS3xxx series, but I’ve only tested with the DS3300. Your Mileage May Vary!
So I’ve decided to have a go with some pre-release software and use Hyper-V R2 server. I work with several clients who rely on Windows Server 2008 Enterprise using Hyper-V in a clustered manner and either Enterprise R2 or Hyper-V R2 sound perfect for them. Cluster Shared Volumes are a brilliant idea and bring Hyper-V much closer to VMware for management ease. Specifically on my SAN I’m using IBM’s DS3300 iSCSI platform so to try this out I went about trying to get the RDAC MPIO drivers installed on the Hyper-V R2 beta.
In my last post I wrote about how to install Windows Server 2008 R2 into a VHD for dual-booting purposes. Well, recently I broke my laptop and had to rebuild my boot loader. Anyways, adding an existing VHD to the Windows 7 boot loader is a doddle.
First, copy your current boot loader:
bcdedit /copy {current} /d "Boot Description"
This will generate a new boot entry and print out the GUID. You’ll need this! Next, you’ll set the VHD path for the OS to use.
bcdedit /set {GUID from last step} osdevice vhd=[DriveLetter:]\PathToVHD\VHD_File
bcdedit /set {GUID from last step} device vhd=[DriveLetter:]\PathToVHD\VHD_File
That’s it! Reboot your PC and your VHDs should be bootable. Remember though, you can only boot Windows 7 or Windows Server 2008 R2 VHDs like this.
I’ve been using Windows 7 as my primary OS on my laptop (a nice shiny new Dell Studio 17) for a little while now. I’ve found it almost as stable as Vista, definitely faster and some of the new features are very useful – the wireless connection stuff is much better for example. However, the lack of any hypervisor-based virtualization product with it means I have to use Windows Server 2008 for many work-based things.
Now, with both Windows 7 and Windows Server 2008 R2, you can boot from a VHD file. Why is this great? Well, my laptop only has one disk partition and I can’t be bothered to resize it (and no, using DISKPART doesn’t work – I have 0B available to shrink). It also means that I can stick in my USB stick with the Windows Server 2008 R2 install files on, open a command prompt (using SHIFT+F10 when the first dialog box pops up) and type:
diskpart
create vdisk file=D:\VHDs\Win2k8R2.vhd type=expandable maximum=32768
select vdisk file=D:\VHDs\Win2k8R2.vhd
attach vdisk
exit
I can then continue the install – it does complain about not being able to boot from this volume, but don’t believe it. Just press next and the whole thing works like a dream.
Well it’s been a long time since I posted here and I really don’t have anything to say, apart from that I’ve moved from a shared server to one of my own dedicated servers now. It’s really boring, but I’ve moved from a Linux-based host across to a Windows 2008, IIS 7 server. Anyways, it was really ridiculously easy; the only problem I had was with pretty URLs. Big thanks to the learn.iis.net team for this link: http://learn.iis.net/page.aspx/466/enabling-pretty-permalinks-in-wordpress/
One really annoying thing about the VMware Tools installation is that it reverts the video mode back to 640×480 for Windows Server Core installations; barely enough space for the command prompt. This can be fixed very quickly. Run regedit (one of the few GUI tools in Server Core) and find the keys DefaultSettings.XResolution and DefaultSettings.YResolution. Hint: they’ll be in a subkey of HKLM\System\CurrentControlSet\Control\Video\. Change these values from 640 and 480 respectively (another hint: change the value from hex to decimal!), reboot and you’re good to go.