One of Windows Server 2016’s features is a version called NanoServer – it’s a stripped down version of a Core Windows Server installation (no GUI), and might just be perfect for a Minecraft server. Java will run in it, and since the server can be launched without a GUI, this could be very useful for a lightweight VM or laptop. Plus, it’s good excuse to get used to this new feature of Server 2016, even if it’s just a Technical Preview.
I ran into an issue – even when adding OEMDrivers and manually adding the drivers from a Windows 10 load, I get no networks for the virtualized Intel 1000T nic in my VM. Might just be a TP5 bug, as I see that it looked ok in others’ posts from TP4.
So, I installed the full Server 2016 Standard with Desktop (TP5) into VirtualBox to see what NIC drivers it used.
Look at the driver from the nic after the install.
That didn’t line up with anything, so I tried the 1000 MT Server driver… Bingo!
Now, I built a Nanoserver image – with the guest deployment type, using the 1000MT Server setting:
Crickets!!! OK, let’s try a “host” install with the -OEMDrivers flag:
Bingo!  The oiption to deploy as guest locks out OEMDrivers, and is for Hyper-V VMs. The host flag allows the OEMDriver pack, and of that pack with the Server 2016 release, only the Intel 1000/MT Server adapter is included.