VMM 2012 SP1 Bare-Metal Deployment PXE Issue

I have been having some issues getting bare-metal deployment up and running. Our environment has a VMM 2012 SP1 Cluster, a dedicated Windows Deployment Server (Server 2012) and a dedicated DHCP server (Server 2012).

VMM reaches out to the HP DL380 G8 over IPMI and reboots the server but when it attempts to PXE boot it gets the following error:

Your PC needs to be repaired / The Widnows Boot Configuration Data (BCD) file from the PXE server does not contain a valid operating system entry. Ensure that the server has boot images installed for this architecture / Error code: 0x0000098

I have verified the following:

• The SMBIOS GUID which VMM is discovering and what the PXE server is answering is the same. 

If I discover the computer via PowerShell I get the following GUID:

$BMCAddress = “10.168.25.182”
$BMCRunAsAccount = Get-SCRunAsAccount "HP iLO"
$MyComputer01 = Find-SCComputer -BMCAddress $BMCAddress –BMCRunAsAccount $BMCRunAsAccount -BMCProtocol "IPMI"
##View the discovered BMC
$MyComputer01
PS C:\Users\nhawkins> $MyComputer01

BMCType            : IPMI
BMCProtocolVersion : 2.0 (DCMI 1.0)
BMCAddress         : 10.168.25.182
BMCPort            :
SMBiosGUID         : 38303736-3635-4d32-3233-313630333431
SerialNumber       :
AssetTag           :
FirmwareVersion    : 1.13
Model              :
Manufacturer       :
ComputerPowerState : On
Error              :
PhysicalMachine    :

When I view event 4096 on the WDS server I can verify the same SMBIOS GUID:

• The VMM OSD Provider is installed. Below is the output of wdsutil /get-server /show:config I have also checked the path (E:\RemoteInstall\DCMgr\bin\OSDPxeProvider.dll) for the .dll

WDS PXE Providers:
     Name: VMMOSDProvider
     Path: E:\RemoteInstall\DCMgr\bin\OSDPxeProvider.dll
     Order: 1
     Critical: Yes

     Name: SMSPXE
     Path: E:\SMS_DP$\sms\bin\smspxe.dll
     Order: 2
     Critical: No

     Name: WDSDCPXE
     Path: C:\Windows\system32\wdsdcpxe.dll
     Order: 3
     Critical: No

• I have also checked the registry location(HKLM\SYSTEM\CurrentControlSet\services\WDSServer\Providers\WDSPXE\Providers\VMMOSDProvider) for the relevant VMMOSDProvider entries. vmm01.gwpcdemo.com is the name of my VMM cluster. 

When I try to browse to the Server in the above key using HTTP as Greg Cusanza recommended trying in another post I get a "page cannot be displayed" error.

One thing I find interesting that I need clarification on is what exactly the PXE settings need to be on the WDS server. The official Microsoft documentation says:

"You do not have to configure the settings on the PXE Response tab in Windows Deployment Services. VMM ignores these settings because VMM uses its own PXE provider"

I have found that I cannot get the servers to PXE boot unless I configure WDS to "Respond to all client computers (known and unknown)". 

The official documentation also states:

"When you configure Windows Deployment Services, you do not have to add images to Windows Deployment Services. During host deployment, VMM uses a virtual hard disk that you have created and stored in the VMM library"

I find that if I add the VMM WIM (E:\RemoteInstall\DCMgr\Boot\Windows\Images\Boot.wim) to the boot images in WDS that my server will PXE boot and load the VMM image. Of course with this configuration the problem with this is because all of my hypervisors will have this "Hypervisor Deployment" VLAN native to the switch trunk and the boot order with PXE first, they will always PXE boot the VMM image. 

I understand this is a false configuration as per the documentation but something in my configuration is not working. Any help from the community would be greatly appreciated :-)