The sconfig.
Although I love the computername the installer picked for me, I’ll change it to the following naming convention.
Change computername (2) to nodename, in my case N1BC, N2BC or N3BC. I’ll use my second node (N2BC) for this post.
This requires a reboot to take effect.
Next is to configure remote management (4)
- (1) Allow MMC Remote Management
- (2) Enable Windows Powershell. This we’ll need to allow for server manager remote management and of course other future nifty cmdline stuff . Reboot is required otherwise the sconfig does not allow enabling the next option. So reboot.
- (3) Allow Server Manager Remote Management
I’m skipping download and install patches for the moment and use WSUS 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 under option (8), as you can see the list only shows the NIC’s from the dual-nic card. The 12-network is filled in as Hyper-V gets this from the iSCSI Remote Boot LUN from which it started. The Hyper-V Server 2008R2 currently does not detect the LOM, an Intel 82579LM, so here we have some work to do:
Download the correct driver set from Intel. 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 win7/2008core) and will fail. The documentation of Intel only points out to use the /e switch which of course doesn’t work either. You need to add a /f <dir> to it:
PROWin7_64_v16.2.exe /e /f c:temp
Copy to a USB stick. On each node do:
appssetupsetupbdwinx64setupbd.exe
It stays a while on the installing drivers window, no worries.
This will install the correct drivers for the 82579LM LOM. After the successfull installation the LOM will finally show up in the sconfig under option 8.
Using option 8, I’ve added the correct networks on the correct NIC’s.
I’ll go and finish these steps for the other two nodes. Then we can test if we can RDP into the nodes, makes life a bit easier 🙂
It works! Keep in mind tho, that by “easier” I mean that I don’t have to unplug/replug monitor/keyboard/mouse from node to node to see what I’m doing. You still get the sconfig and cmd window only…
Network connectivity tests & Windows Advanced Firewall
As the Windows Advanced Firewall (advfirewall) is default on and does not respond to ICMP, I’ll turn it off on all nodes to be able to test connectivity:
netsh advfirewall set currentprofile state off
Now I can ping each node through each connected network to see if everything connects. Make sure this basic network stuff works before you continue!
To turn the advfirewall back on:
netsh advfirewall set currentprofile state on