Yesterday I had an interesting problem I had to fix. As you may or may not know, using Hyper-V within Failover Clustering sometimes requires the use of volume GUIDs for storage if you have more LUNs than drive letters available (like we do). What you may not know is that these GUIDs can, under some circumstances, change – completely screwing up Failover Clustering’s ability to move virtual machines between nodes.
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.
I’ve found myself using Windows Server 2008 Core quite a lot recently, and apart from using the GUI CoreConfigurator I’ve realised that I’m often completely forgetting a whole bunch of commands related to Server Core setup. Now nine times out of ten I’m working from a prepared Sysprep image with Group Policies setting everything I need; but every so often I forget or am setting up a test lab and need these commands. Anyways, here’s a list of codes that I use very often.
Well, with Windows Server 2008 actually being released today I thought I’d put down in writing how I configured a server for one of our branch offices here. I decided that for a small office we’d need DHCP, DNS and a domain controller. However, this being a branch office with no IT function within it, this gave me the perfect opportunity to play with the Windows Server 2008 Read-Only Domain Controller (RODC) role within a Windows Server 2008 Core installation.