Binsfeldius Cluster, Getting the DC1 online

Before we can start the cluster process, we first need the DC1. As Hyper-V Server does not have a full GUI, you’ll need a windows client machine for the next steps. I’m using MMC snap-ins and Remote Server Administration Tools (RSAT) to connect to the first node and move my existing DC VM (from my existing single Hyper-V host I have) to the ttgdc1 LUN.

To be able to do this, I need to enable remote management on the node, install RSAT on a Windows 7 client, use HVremote, enable RSAT features and specifically the Hyper-V tickmark. Almost starting to regret using Hyper-V Server 2008R2 instead of Windows Server 2008R2 with the Hyper-V role .. but hey, makes this process a bit more interesting.

Remote management: prepare node

As you’ve read in this previous post, I’ve enabled MMC Remote Management, Powershell, Server Remote Management. This, of course, is not enough to make it work…

Two-stage approach

First, as I don’t have a domain (yet) and I do need remote management, I’ll run through the steps of getting non-domain remote management to work for node N1BC and my Windows 7 client. So with the local (administrator) accounts on both systems.

Second, when the DC1 is up & running I’ll run through the same steps of getting remote management fixed, but now in the domain context. The way it should be, with administrative domain accounts (because now I can add domain accounts for remote management to the nodes)

So, for first stage. I’ll be using John Howard’s excellent HVremote tool, which uses the Windows Scripting Host.

1. on N1BC, create a local administrator account using sconfig option (3), lsarayf
2. on N1BC, in cmd: cscript hvremote.wsf /add:lsarayf
3. on Win7, create a new local administrator account, exactly as in step 1, : lsarayf
4. on Win7, start a cmd with runas lsarayf
5. on Win7, in cmd: cscript hvremote.wsf /anondcom:grant
6. on Win7, in cmd: cmdkey /add:n1bc /user:n1bclsarayf /pass: <then type the password>
7. on both, in cmd: cscript hvremote.wsf /show /target:<either n1bc or win7>

Remote management: prepare client

Get the latest RSAT from here, make sure you get the correct version! I’m using a 32-bit Windows 7 client, so I’ll grab the Windows6.1-KB958830-x86-RefreshPkg.msu file.

• Run the installer
• Go to Control Panel – Programs – Turn Windows features on/off
• Under Remote Server Administration Tools – ’ Role Administration Tools
• Put a tickmark in the Hyper-V Tools box

Now I can start the Hyper-V Manager on the Win7 client. Make sure you start it as the user: lsarayf. I could logon as lsarayf to avoid the runas however I have all my stuff on under the administrator account AND appearently the local administrator account on the Hyper-V Server doesn’t seem to connect for RSAT. Following the exact steps the administrator account fails whereas lsarayf works immediately, that’s another week off my life expectancy for keeping on trying.

In the Administrative Tools you’ll now find the Hyper-V Manager program. Start it and go to the Actions. Connect to Server… and connect to the node…

Next is to do some disk management stuff:

1. Use iscsicpl on N1BC to connect the TTGDC1 LUN
2. run the following command on N1BC and on Win7 client (yes on BOTH!): netsh advfirewall firewall set rule group=”Remote Volume Management” new enable=yes
3. Start an MMC runas lsarayf and connect to N1BC, whoohoo success!

The Disk Management window detects the new ttgdc1 storage and now we can initialize and format it for use 🙂

I assigned the driveletter R:

As this VM needs to communicate with the clusternodes, it must be placed in the same network and therefore I’ll create the first virtual switch. An External Network, called DMZ, attached to the DMZ NIC (blue network). Also allowing management operating system to share this network adapter.

I’ve stored this existing DC1 on a LUN, which I’ll now attach to be able to copy the .vhd and put it on the newly created TTGDC1 location.

Allright, so I’ve created a new VM based on the existing DC1 virtual harddisk. However, it fails to initialize and start. Got it! The VM was created on a Core-i5 and the cluster runs on Core-i3 CPU’s. So you have to tick the box Migrate to a physical computer with a different processor version under the VM settings -> Processor. Now my good ol’ DC starts 🙂

And with a working DC1, I can join the nodes to the domain, get my domain admin on the nodes and prepare for creating the cluster.

Use the sconfig menu option (1) to join each node to the domain. No rocket science here

Remote management: prepare node – Second Stage (permanent)

Instead of creating and using a local (administrative) account, I’ll use the priviliged account srayf from my domain tartarus.intranet. At this point I am going to switch from the Win7 client to the DC1 for management services which means that I also have to run the Remote management:prepare client instructions again. The steps are:

1. on N1BC, in cmd: cscript hvremote.wsf /add:tartarussrayf
2. on both N1Bc and DC1, in cmd: cscript hvremote.wsf /show /target:<either n1bc or dc1>
3. To be able to use remote disk management run the following command on all the nodes and on the DC1: netsh advfirewall firewall set rule group=”Remote Volume Management” new enable=yes
4. As this is a Server 2008R2, everything is already there and only needs enabling.
5. Go to Control Panel -> Programs -> Turn Windows features on/off
6. Under Remote Server Administration Tools -> Role Administration Tools
7. Put a tickmark in the Hyper-V Tools box

Test it by starting a MMC, add the Disk Management snapin and connect to N1BC.
Success!

Test it by starting the Hyper-V Manager and connect to N1BC.
Success!

Now repeat for the other two nodes.