I am having an issue with Hyper-V once I install NIC drivers.
Scenario:
I have 2 x Servers that are configured to boot via iSCSI from a NAS. The hyper-v install is grabbing the iSCSI boot information i assume via iBFT from the NIC as it is not a HBA iSCSI.
The installation goes off without a hitch, it see's the iSCSI disk and installs. When I boot the Hyper-V install there is only 1 NIC, the card that runs iSCSI (I thought that because it is using this for booting it may hide it like XenServer does), so I run the installation for the NIC drivers (All Intel adapters) which install the other NICs. Everything will work, i can setup VMs etc; but once I reboot the server, on the next boot up it stays on the splash screen for a while (little balls going in a circle) then get's a BSOD with something referring to the boot volume. I can press f8 and boot last known config and the server boots, but alas i assume this removes the driver because the other NICs aren't there.
The LAN and SAN are of course 2 different subnets.
Any advice on what i can try from here?