Jump to content

Recommended Posts

Posted

So, I've set up WDS/MDT and everything is perfect, all machines image without a problem APART from these new Lenovo's we have purchased...

 

I'm getting this error when booting them into PXE;

IMG_2955.jpg

 

(Missing MTFTP Server IP Address)

 

Anyone any ideas why this is???

Posted
PXE-E7B: Missing MTFTP server IP address.

This message is displayed when the ROM did not receive any PXE discovery tags or proxyDHCP offers and the DHCP SIADDR field is set to 0.0.0.0.

 

Is there a fix for this?

Obviously I'm imaging them using a CAT5 cable to boot from PXE

Posted
Have you tried bios update which may update the PXE version?

 

No - but should this really need doing?

All other machines arrive and we OOTB image them!

Posted
No - but should this really need doing?

All other machines arrive and we OOTB image them!

 

Worth a shot. I had an Asus system that has an Atheros network card on board that flat out refused to network boot, and there was no further BIOS updates on Asus' site for that model.

 

It's gotten a lot better, but a few years ago there used to be lots of machines with funny BIOS and PXE issues. Really want UEFI to kill off the BIOS now.

Posted

Okay, so I've just now had a proxyDHCP error with some Ergos. There is no bios update for these and I need to upgrade these ASAP!

Any ideas about this?!

Posted
It's a horrible workaround at best but with SCCM you can create a boot disk to boot a build environment from instead of using PXE boot. Can you do the same with MDT? It'd get you out of a hole at least.
Posted (edited)
Okay, so I've just now had a proxyDHCP error with some Ergos. There is no bios update for these and I need to upgrade these ASAP!

Any ideas about this?!

 

If they can boot from USB, try this: Creating an MDT USB Boot key | Laurie Rhodes' Info

 

Edit: or you could use the ISO method that @Norphy mentions (MDT does have this, but it may be disabled in the deployment share properties)

Edited by computer_expert
Posted
Sometimes you see this when WDS has died.. Often after a power failure it tries to come up before the DCs and we don't notice for a couple of weeks...

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...