Jump to content

Recommended Posts

Posted

Certain models of computer will not UEFI PXE boot unless in the server VLAN (Viglens and 1 model of HP laptop.)

These computers have PXE'd in the past, but cores have changed and so have the DHCP servers (although options kept the same.)

 

We have:

HP Core Switches with IP Helper configured. Dell Edge Switches have tried with and without ip helpers on.

SCCM Server with latest patches

1 server VLAN and then individual building VLANS

 

Have tried:

No DHCP options 60/66/67

Tried DHCP with various options of 60/66/67

Options 66 and 67 all the rest of the model computers will PXE.

If I turn on legacy by altering option 67 the Viglens will PXE (but I don't really want to change the BIOSs of 300+ viglens...)

 

I am running out of ideas... Help?

Posted

I have had this issue,

It was specifically with the HP Stream 11 G4 EE a BIOS update solved with, but what I have ended up doing is using a secondary network port on the WDS Server VM and point that one directly at the client VLAN.

 

I know that is slightly messy, but would could do this for your VLANs to boot them up and image them.

Posted

Thanks, Probably would work but we have several VLANs due to the campus size so would need several client VLANs and so network adaptors. Its a hyper v host so possible but slightly fiddly due to the server switch.

 

As this used to work, I think there must be another answer....

Posted
As i recall, portfast brings the interface up on the switch instantly, otherwise there a time of negotiation and monitoring. is it possible the switch isnt making the port live quick enough for these units to pxe boot?

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...