Hi all,

Here's a quick rundown of my setup. Got SCCM 2012 R2 installed. Configured DHCP scope options 66 and 67 as the target machine and SCCM server are on different VLANs. Can build Generation 1 VMs without issue. Generation 2 VMs, however, are not building. Here's the scenarios I've encountered so far:

with "067 Bootfile Name: Boot\x64\wdsmgfw.efi" set in dhcp I get the below result (sidenote: tried disabling "Secure Boot" just in case but this made no difference):

With "067 Bootfile Name: Boot\x64\wdsnbp.com" and "Secure Boot" enabled I get this:

With "067 Bootfile Name: Boot\x64\wdsnbp.com" and "Secure Boot" disabled I simply get: Boot Failed. EFI Network. No Operating System was Loaded. Press a key to retry the boot sequence...

As you may have guessed, nothing pops up in the smspxe.log for any of the above scenarios. The network folks say there's nothing blocking the communication between the target machine and the sccm server.

Has anyone got any suggestions as to what I might be doing wrong? Done a fair bit of hunting around online but haven't managed to get very far.

Gen 2 VMs clearly have some great potential but they're not much use if I can't get them built! Any help/info would be much appreciated

• Edited by Robot Archive Tuesday, March 03, 2015 3:47 PM

Is this a duplicate of https://social.technet.microsoft.com/Forums/en-US/326a7ba4-3d14-47c9-91cf-ba357a77c03e/sccm-2012-r2-building-gen1-gen2-hyperv-virtual-machines?

Hi Torsten,

Good spot! This post is similar, in that I still can't get Generation 2 VMs to PXE boot properly. However, I can now build Generation 1 VM servers without issue and the error message on the Generation 2 VM is PXE-E23 so the situation is different. Have you any suggestions on things to check? Information on how to troubleshoot PXE-E23 seems scarce and I'm slightly flummoxed by the fact the Gen 1 server builds fine but the Gen 2 doesn't!

Hi,

I think there is something wrong with your boot file. If you are using ConfigMgr for PXE, the boot file should be SMSBoot\x64\wdsmgfw.efi. As suggested in the other thread use IPhelper instead of DHCP option would be a better choice. And disable secure boot as

What OS version are you building? Gen 2 is only supported on Windows 8-> and Windows Server 2012 ->

Hi Daniel(s),

Thanks for taking the time to reply. I'm trying to build the Generation 2 VM with Windows Server 2012 R2 Standard.

As far as the boot file goes, I took your advice and put "SMSBoot\x64\wdsmgfw.efi" into the scope option. The boot sequence moved a little further down the line but timed out:

I then disabled the 'Secure Boot' and kicked off the build again. The machine started contacting the sccm server and messages started popping up in SMSPXE.log. However, it sort of got stuck in a loop (the same messages kept repeating ad nauseam in smspxe):

Eventually, the target machine returned an error of Windows Deployment Service Encountered an Error. Error Code: 0x102

As far as I can see, the machine is being picked up in smspxe, sccm finds there is an optional advertisement available and then it tries to find the boot image. However, rather than succeeding or failing to find the boot image the whole process simply starts again. Anyone got any comment on what is actually happening here or advice on how to fix this issue? Thanks

• Edited by Robot Archive Wednesday, March 04, 2015 12:24 PM

Have you checked this checkbox for the boot image P0100024?

http://www.danielclasson.com/dont-forget-this-step-when-you-want-clients-to-pxe-boot-using-configuration-manager-2012/

Yup, sure did. Have been tripped up by that before but made sure to tick it this time. Can't figure out whether the target machine is unable to access/locate the Boot Image or whether something else is happening. The messages in smspxe.log feel like i'm only getting half the picture. Besides smspxe.log is there anywhere else I could check?

Hello,

If client contact with server successfully, the next process should be downloading boot.sdi. So can you confirm if the file resides RemoteInstall\smsboot?

Just did a test, I deleted the file, and I can see the client is looking for my boot image in the log.

Is the file in RemoteInstall\SMSImages ?

Hi Daniel,

I can see the boot.sdi file in the RemoteInstall\SMSBoot folder so perhaps it can't download it for some reason? Is there any log I can check to view the progress of the deployment other than smspxe.log? Thanks for the help!

• Edited by Robot Archive 18 hours 15 minutes ago

Hi Daniel,

I can see the boot.sdi file in the RemoteInstall\SMSBoot folder so perhaps it can't download it for some reason? Is there any log I can check to view the progress of the deployment other than smspxe.log? Thanks for the help!

• Edited by Robot Archive 1 hour 30 minutes ago

Hi Daniel,

I can see the boot.sdi file in the RemoteInstall\SMSBoot folder so perhaps it can't download it for some reason? Is there any log I can check to view the progress of the deployment other than smspxe.log? Thanks for the help!

• Edited by Robot Archive 1 hour 27 minutes ago

Did you see the boot image in RemoteInstall\SMSImages?

Yup, the boot image the machine is looking for is in the RemoteInstall\SMSImages folder. Anything else you can think of that it'd be worth having a check on?

Hi Daniel,

I can see the boot.sdi file in the RemoteInstall\SMSBoot folder so perhaps it can't download it for some reason? Is there any log I can check to view the progress of the deployment other than smspxe.log? Thanks for the help!

• Edited by Robot Archive Thursday, March 05, 2015 2:22 PM