I've built a test lab running Windows Server 2016 and SCCM 2016 and I'm having an issue with PXE booting a VM to install an OS via SCCM. Here's the run down on the configuration. At this stage SCCM isn't being touched
Windows Server 2016 Technical Preview 4 with Hyper-V Role installed Private Network Virtual Switch, no VLAN set, named "Local only"
VM - DHCP - Gen2 VM - Windows Server 2016 Technical Preview 4 with DHCP Role installed, Network Adapter - On vSwitch "Local Only"
VM - Win10BC - Gen2 VM - No OS (PXE UEFI), Network Adapter - On vSwitch "Local Only"
For both VMs NIC Hardware Acceleration Tab has Enable Virtual Machine Queue ticked, Enable IPsec task offloading ticked with Maximum number: 1
For both VMs NIC Advanced Features Tab has Protected Network ticked
DHCP Server has a single domain authorised IPv4 Scope bound to Eth0 192.168.0.5, NICs from full OS VMs in the same configuration can get a DHCP Lease
Win10BC VM attempts to PXE Boot - "PXE Network Boot using IPv4 ( ESC to cancel), Performing DHCP Negotiation........"
Using Wireshark on DHCP Server I can see DHCP Discover from 0.0.0.0 to 255.255.255.255, DHCP Server Responds 192.168.0.5 to 255.255.255.255 with DHCP Offer.
After a short delay the DHCP Discover and Offer process occurs again and there is no DHCP Request or Acknowledge step returned to the DHCP Server.
It ends up timing out and Virtual Machine Boot Summary, 1. Network Adapter DHCP Failed
This is where I'm stuck, either the DHCP Offer Broadcast isn't reaching the PXE VM or it's receiving and not responding to the DHCP Server. I've tried adding a vLAN to each member, I've tried turning off VMQ and IPsec task offloading, I've turned off Protected network with no change.
On the DHCP Server I've ensured the DHCP firewall rules for IPv4 apply to Domain, Private and Public, Checked the NIC is correctly bound to respond and that other devices can get leases.
All of this is on a single Hyper-V host with the DHCP Server and PXE Guest on the same vSwitch. I realise this is Technical Preview software but I'm hoping there is a solution and this isn't a bug in the preview software.
Has anyone experienced this before? On 2016, 2012? I can provide screenshots of configuration as required.