Share via

Deploy to HyperV Client can't PXE boot

ComputerHabit 1,031 Reputation points
2022-04-15T21:20:55.137+00:00

I'm trying to setup HyperV on my WIndows 10 PC so I can create VM's for Task Sequence testing with OSD. I have OSD and PXE working and can connect.

I am testing from my PC and I'm using a TFTP command to verify I can get to the PXE server.

tftp -i 10.0.124.12 GET \smsboot\x86\wdsnbp.com

This works from my PC but not from the VMs on my PC. I have separate static MAC addresses assigned to a new Version 1 template. I can get an IP address but then I get a PXE error. PXE-E32 TFTP Open Timeout

Is this SCCM not liking my VM's? Am I missing something about HyperV?

Windows for business | Windows Client for IT Pros | Storage high availability | Virtualization and Hyper-V
Microsoft Security | Intune | Configuration Manager | Deployment
0 comments

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Rahul Jindal [MVP] 10,911 Reputation points MVP
    2022-04-16T07:03:28.193+00:00

    Hi. Did you check the wds\pxe side logs? Is the pxe client in the same subnet as pxe server or different? Do you have dhscp scopes or IP helpers configured for pxe support across subnets?

    0 comments
  2. ComputerHabit 1,031 Reputation points
    2022-04-18T12:59:26.357+00:00

    I thought that since TFP was working that would be evidence of IPHelper. Or at least I'd think I'd get the same results as my PC.

    0 comments
  3. ComputerHabit 1,031 Reputation points
    2022-04-18T15:06:39.087+00:00

    Turn out it was the use of Antivirus software. The message wasn't helpful since the AV software was on the HyperV server.

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.