I have read several posts that don't truly fit my issue but I may be wrong but I need help. Let me provide as much details as I can in hopes of resolving my issue.

Network was recently segmented

SCCM 2012 R2 is a VM on x.x.0.0 VLAN 100
Desktops/Laptops are on x.x.20.0 VLAN 20

I did not have this issue prior to segmenting the network and I enabled DHCP Scope options 66 and 67, Option 60 N/A as the DNS and SCCM are not on the same server.

Option 66: FQDN of SCCM server
Option 67: smsboot\x86\wdsnbp.com

When I PXE boot the client sees the deployment server, hit F12 option and it gives error: PXE-M0F: Exiting Intel Boot Agent.
I added a second NIC to the VM and put it on the x.x.20.0 subnet and VLAN tagged 20 on there.

Still the same result. I see that the client gets an IP address from DHCP which is on the x.x.0.0 subnet, I check the Address Leases and what I see may be the issue but not 100% sure on my theory.

Instead of the normal 12 Hex MAC address it is coming up with the GUID address that I see in PXE, think this is also called the SMSBIOS GUID from what I have read.

The Client Machine is a Lenovo T540p if that makes a difference. I thought about removing the WDS feature and reading but I am hesitant on that as it applied to other issues that is not quite like mine.

Any Suggestions would be greatful, thank you!

maybe someone else can chime in, but it really seems like the PXE broadcast isn't getting to the PXE server.

That is my thoughts exactly, hence the reason I added a 2nd Virtual NIC for the 20.0 segment but I do not know exactly how to confirm this. This is my 2nd year working with SCCM.

IpHelpers not configured?

Steve,

No IPHelpers configured, our network admin wants to stay away from that as it may cause issues with other broadcasts.

I'm by no means a Network expert, but I've had a similar issue before and solved it by configuring the IPhelpers...

Hi,

please try to enter the ip address instead of the fqdn for option 66. 

your bootimages are properly distributed?

greets

I had the same thought as you and I am not a network guru even a novice at that so when I asked they explained to me how IPHelpers can have issues. That is why I added a 2nd NIC and set a static IP on that subnet in hopes of bypassing the need for IPHelpers.

• Marked as answer by Blacksuit1 Friday, February 21, 2014 3:35 PM

Yes my bootimages are properly distributed as they worked prior to the network segementation. I can even PXE Boot VMs on VLAN 100 with no issues, it is only an issue on my Physical End-User machines.

I will try the IP Address instead of the FQDN and report back in 24hrs as I am working off site today.

For your suggestion on the IP Address for Option 66 should I just use the IP or tftp://IP Address?

Well it looks like it is a LENOVO Issue. I got an HP Desktop in and it booted from PXE just fine.

Thanks everyone for the suggestions and feedback. Now I got to figure out why Lenovo T540p is not PXE Booting.

The issue has to be with the Lenovo Laptop because I was able to PXE boot to VMs on both subnets/vlans with no issues.

This issue is not related to Lenovo at all.  Did you do anything with BitLocker or any other Encryption solution that uses the TPM chip in the machine?  Go into setup (from a cold boot - setup is locked out after failed pxe) - go to security chip settings, make the chip into "Active" status, and clear it using the option that appears.  You will then be able to PXE boot just fine.

Yes - VMs won't have TPM.

What's the point of segmenting if you are just going to do this?  IP Help-address works just fine.  MS recommends a dhcp server on every subnet.  Does anyone else?  No.

• Proposed as answer by NimbleNerd 16 hours 6 minutes ago
• Unproposed as answer by NimbleNerd 16 hours 6 minutes ago

What's the point of segmenting if you are just going to do this?  IP Help-address works just fine.  MS recommends a dhcp server on every subnet.  Does anyone else?  No.

• Proposed as answer by NimbleNerd Monday, June 22, 2015 3:42 PM
• Unproposed as answer by NimbleNerd Monday, June 22, 2015 3:42 PM

The Problem/Difference is with the Lenovo's. Try hitting the Function Key while Pressing F12.

BTW...@Huggins.Sean et-all with your TPM and IPhelper solutions and theories. Please SHUT-UP if you don't know the answer. Your spamming up the network.

• Proposed as answer by NimbleNerd 15 hours 59 minutes ago

The Problem/Difference is with the Lenovo's. Try hitting the Function Key while Pressing F12.

BTW...@Huggins.Sean et-all with your TPM and IPhelper solutions and theories. Please SHUT-UP if you don't know the answer. Your spamming up the network.

• Proposed as answer by NimbleNerd Monday, June 22, 2015 3:49 PM

Yes, pressing Fn button with F12 resolved the issue. thank you guys:)