The cluster nodes have been renamed in a previous post.
There are some notable changes in the new version of sconfig. To configure remote management select option (4).
- It looks like Remote Management is enabled by default, if this is not the case press (1) Enable Remote Management
By default, the Hyper-V Server 2012 host does not respond to ICMP and in the old days you had toenable this by using the netsh command. Microsoft has put this as a selectable menu item now
- (3) Configure Server Response to Ping
I’m skipping download and install patches for the moment and use SCCM later.
Next I’ll enable (7) Remote Desktop. For now allow clients running any version of RDP, this will be locked down later using Group Policies.
The network settings are still under option (8), as you can see the list only shows the NIC’s from the dual-nic card. The YELLOW-network is filled in as Hyper-V gets this from the iSCSI Remote Boot LUN from which it started. The Hyper-V Server 2012 does detect the LOM, an Intel 82579LM, but strangely enough not the top-half of the dual-nic card.
Although Intel does not (yet) have Server 2012 core version of the drivers, I’m using the 64-bit version of the latest 2008R2 which you find here. As I do not have the same platform as the driverset, you can’t extract it by doubleclicking the file. It detects that the OS is different (e.g. 32 bits XP instead of the 64 bits 2008core) and will fail.
The /e switch does not work anymore, the new way is to use winzip to select and unzip its contents. Copy to a USB stick. On each node do:
2012PROWinx64appssetupsetupbdwinx64setupbd.exe
Click install and wait, this may take a couple of minutes to complete. Once its done verify under option (8) if you now see all three NICs. Select each NIC and give it a static IP address.
Make sure you already know the IP address of your new dc1 and fill this out as DNS server here.
One node down, two to go…