For those of you who are deploying Hyper-V on Server Core, there is one very important thing to configure before setup Hyper-V Cluster. This step is changing NIC order. In Full installation, it is easy to change the NIC order since the GUI is present.
However in Server Core, since there is no GUI, you need to change the NIC order in registry.
Before we modify the registry, use nvspbind utilities to capture the MAC address for each NIC.
| nvspbind.exe > C:\nicmac.txt |
The end result will transfer to a text file. Use it as a reference to identify the MAC address.
Once you’ve complete this step, proceed to modify on registry
Go to
- HKLM\System\CurrentControlSet\services\TCPIP\Linkage
- Bind: Contains NIC GUIDs
- Export: Contains NIC GUIDs
- Route: Contains NIC GUIDs
Sample result on my server:-
Bind
| \Device\{F95F9F29-2440-45AF-ADD9-60EA6479FDFD} \Device\{29D39985-50FC-4B3E-A39D-8C79CDDF9205} \Device\{1D683A18-B32A-4436-8C61-728F2E57ACD0} \Device\{D42AB6E5-3C77-430C-95F8-7226B353B6EF} \Device\{2E04C18D-622C-4217-A1E9-F2B81EFE657A} \Device\{6BE58993-C250-4BCF-A96F-A43C0A5EBDE7} \Device\{C10CDD27-6802-43E1-8AC9-3F45FC93FE71} \Device\{35F54C5A-36D1-46B4-A493-BAAE914D10B9} \Device\{79BE86E5-1A1E-4136-9A5C-54705045289D} \Device\{1F01EA62-2D73-4AE0-833A-058781F95140} \Device\{96790720-8BE9-4465-8309-74EF2142632B} \Device\{E80BD870-B6C0-415A-BEBB-108FA83B3019} |
Export
| \Device\Tcpip_{F95F9F29-2440-45AF-ADD9-60EA6479FDFD} \Device\Tcpip_{29D39985-50FC-4B3E-A39D-8C79CDDF9205} \Device\Tcpip_{1D683A18-B32A-4436-8C61-728F2E57ACD0} \Device\Tcpip_{D42AB6E5-3C77-430C-95F8-7226B353B6EF} \Device\Tcpip_{2E04C18D-622C-4217-A1E9-F2B81EFE657A} \Device\Tcpip_{6BE58993-C250-4BCF-A96F-A43C0A5EBDE7} \Device\Tcpip_{C10CDD27-6802-43E1-8AC9-3F45FC93FE71} \Device\Tcpip_{35F54C5A-36D1-46B4-A493-BAAE914D10B9} \Device\Tcpip_{79BE86E5-1A1E-4136-9A5C-54705045289D} \Device\Tcpip_{1F01EA62-2D73-4AE0-833A-058781F95140} \Device\Tcpip_{96790720-8BE9-4465-8309-74EF2142632B} \Device\Tcpip_{E80BD870-B6C0-415A-BEBB-108FA83B3019} |
Route
| "{F95F9F29-2440-45AF-ADD9-60EA6479FDFD}" "{29D39985-50FC-4B3E-A39D-8C79CDDF9205}" "{1D683A18-B32A-4436-8C61-728F2E57ACD0}" "{D42AB6E5-3C77-430C-95F8-7226B353B6EF}" "{2E04C18D-622C-4217-A1E9-F2B81EFE657A}" "{6BE58993-C250-4BCF-A96F-A43C0A5EBDE7}" "{C10CDD27-6802-43E1-8AC9-3F45FC93FE71}" "{35F54C5A-36D1-46B4-A493-BAAE914D10B9}" "{79BE86E5-1A1E-4136-9A5C-54705045289D}" "{1F01EA62-2D73-4AE0-833A-058781F95140}" "{96790720-8BE9-4465-8309-74EF2142632B}" "{E80BD870-B6C0-415A-BEBB-108FA83B3019}" |
Modify the NIC GUID order according to
1. Management
2, Cluster Heartbeat / CSV
3. Live Migration
4. iSCSI
5. MS Virtual Network Adapter
6. Microsoft Failover Cluster Virtual Adapter
and so on…
Once complete, reboot the server for the NIC order to take place.
