VMware Cloud Community
gcarson73
Contributor
Contributor

PXE not working with Server 2012

Setting up a MDT2013 and use WDS for PXE booting on Windows Server 2012 R2 Datacenter.

*Server 2012 is up to date with Microsoft updates

It sees my "Contacting Server" but PXE boot aborts.

FYI, I have set this up on a physical server with Server 2012 and its working..so the problem looks to be with ESXi and the VM.

*ESXi, 6.0.0, 3073146

I have tried the E1000 and vmxnet3 network adapters on the VM.

*VM Version 11

*VMtools tools Version 9.10.5, build 2981885

Any ideas??

2 Replies
lyleshaff201110
Contributor
Contributor

I am experiencing the same issue...

I get the initial WDSNBP(.com) file, then ends up at the same "Contacting Server: x.x.x.x............................" and never completes. Finally get:

Failed to restart TFTP.

TFTP download failed

PXE-M0F: Exiting Intel PXE ROM.

Our setup:

1x Windows Server 2012 R2 (Standard Edition) server, latest patches, WDS role installed. (DHCP Is on a DC, separate server). Latest and greatest updates. (HW = v11)

5 host cluster, running vCenter 6.0U1b (3339083), hosts are on 6.0U1b (3380124).

We have another MDT/WDS Server, running on Windows Server 2012 (NOT R2) on an ESXi 5.5.0 Host (1746974) on another network, and this server is still working just fine. We are hesitant to upgrade that host, since the other WDS Server is still running on it, and we cannot get WDS stable on ESXi 6.0.x... (This host is managed by the same vCenter server as the larger cluster)

I am hoping someone has a clue here...

0 Kudos
lyleshaff201110
Contributor
Contributor

Upon further review, I found 2 more functional servers in my environment:

Summary:

MDT/WDS on Server 2012 R2 on ESXi 6.0U1b (build 3380124) = NON-Functional (This is the west-coast cluster, with vCenter 6.0U1b - Call this location #1)

MDT/WDS on Server 2012 on ESXi 5.5.0 (build 1746974) = Functional (Same vCenter as west-coast, different datacenter, same location #1)

MDT/WDS on Server 2012 on ESXi 5.5.0 (build 1746974) = Functional (Completely separate cluster, east-coast, vCenter 5.5.0, build 1750787, call this location #2)

MDT/WDS on Server 2008 R2 on ESXi 6.0.0 (build 2494585) = Functional (same vCenter as west-coast, different datacenter, call this location #3)

The fun part here is that now even hardware in the location #1 can no longer PXE boot as well as VM's. All other MDT/WDS systems work with either VM's or Hardware, they just work...

Almost starting to sound like an ESXi 6.0U1* issue???


Thoughts?

0 Kudos