Able to PXE boot a Hyper-V VM, but not actual machines.

[RealRider 0]

Hi All,

I installed SCCM 1706, SQL 2016, ADK for Windows 10 (version 1703), and MDT 8443 on a Server 2016 VM, and I followed this guide https://www.windows-noob.com/forums/topic/12873-how-can-i-deploy-windows-10-enterprise-x64-with-mdt-2013-update-1-integrated-with-system-center-2012-r2-sp1-configuration-manager/ because I wanted to deploy Windows 10 with SCCM.  I was able to deploy Windows 10 to a Hyper-V VM using PXE, but I couldn't make it work on an actual laptop or desktop (both HP).  I got the following blue screen after pressing F12.  I've disabled and re-enabled my distribution point's PXE support for clients, added network and storage drivers to the MDT boot image and updated distribution points, but nothing worked.  Does anyone have any idea why it works for VMs but not actual machines?  

[RealRider 0]

I did more troubleshooting but I am not sure if I am on the right path.  Here is what I did.

I checked SMSPXE.log and it said "Warning: Matching Processor Architecture Boot Image (0) not found".  Many people said both x64 and x86 boot images need to have the option "Deploy this boot mage from the PXE-enabled distribution point" checked.  Since I only had a x64 boot image for Windows 10 created using MDT, I created a x86 boot image using MDT and checked that option and also distributed it to my distribution point.  Now when I deployed the task sequence and tried to PXE boot my HP laptop (which already has Windows 10 and Configuration Manager Client installed),  it rebooted by itself after I pressed F12.  SMSPXE.log now shows "no advertisements found, No boot action. Aborted.  Not serviced."  

Not sure what I did wrong or where I should go from here.  Please help.

Edited September 6, 2017 by RealRider

[Jorgen Nilsson 44]

Hi,
Is the machine unknown or did you import it into SCCM before? Installed before? Both boot images are needed so that is a good start. The machine must have a deployment targeted to it as well, wither through Unknown computer support or by beeing a member where the TS is deployed to.

Regards,

Jörgen

[RealRider 0]

Hi Jörgen,

The laptop has Configuration Manager Client installed and is listed under Devices in SCCM.  It originally had Windows 7 Professional (x64) installed on it, I upgraded it to Windows 10 Pro using a SCCM task sequence.  Now I wanted to re-image it using a task sequence described here

.  When I deployed the TS, I chose "All Unknown Computers" as the collection.  I was able to deploy this TS to a 2016 Hyper-V Gen 2 VM without problem but not to actual machines.