Hello Guys,

After endless serarching I have to post the question. I have a standalone environment, I'm tesing the OSD, but my Hyper-V clieant does not want to boot into PXE, it starts hanging after it receives the IP from DHCP. The interesting thing, that this happens with Gen 1 VM only... on Gen 2 works like charm. DHCP options been correctly set. PXECONTROL.log says nothing... I have no more idea.

Can someone please help? 



How about the SMSPXE.log? Have you tried using a legacy network card?

Also clear... :\ loads the two boot images correctly. Yes sure, it uses legacy.

That's really odd, I typically use Gen 1 with the legacy NIC and have no issues.

How did you configure DHCP option? Have you tried to use IP helper instead?

I set on my DHCP OPTION 66 (IP of WDS) 67 and \smsboot\x64\wdsnbp.com ... How I should use IP helper, i have no network device... its on virtual private network, so no gateway.

No DHCP options are required if the client and server are on the same subnet.

Yes, thats why I was wondering why not working, because without the settings... does not work also :(

Can you please share the SMSPXE.log file?

Sure, please find here.

http://www.filedropper.com/smspxe

Hi,

I found several post on the errors, some are caused by firewall, and another just reboot primary site, restarted WDS services. Since Gen 2 works, firewall may not be the culprit here.

ConfigMgr migration, PXE Provider shutdown (SMSPXE)

Can you please enable verbose logging, then retry the PXE boot, and then post the new SMSPXE.log file?

Also, please re-start the WDS service after enabling verbose logging, just to be sure that the new log setting takes effect on the PXE provider.