Windows Deployment Services

[Jrgt_5132]

Hello everyone,

 

WDS Problems unfortunately.

 

Info:

Machine 1: Dell Precision T1650

PXE Boot: Works fine

Loads boot image: Works Fine

Lets me install image: Works fine.

 

Machine 2: Dell A.I.O OptiPlex 7440

PXE Boot: Works fine, I get all my options

Loads Boot Image: works fine. I can choose any of my boot options and it loads them

Lets me install image: nope.

 

the machines were tested using the same port. same boot image.

Once the boot image loads and I get the purple/pink screen it does not let me choose what install image to install. instead I get the error message, "An error occurred while obtaining an IP address from the DHCP server. Please check to ensure there is an operational DHCP server on this network segment."

 

As mentioned above, Machine1 works fine. it passes everything.

 

I can only think of drivers. and Bios settings since it shouldn't be the routers, switches, DHCP, or WDS servers. I did check BIOS and I did import the drivers for the AIO. is there something I am missing? maybe a specific setting in BIOS?

 

Thanks,

 

JR

 

[Naeaes]

Uhh. I've use WDS plenty and had my share of issues with it too. But it's been a few years since I touched any of it and my memory is really failing me. Can't remember this specific error and hence forth. What I can tell you is that aside from checking that the time and date are correct (a security thing) and that booting from Network is enabled and set primary, there's nothing you need to worry about in the BIOS. I worked for a boutique PC builder and WDS was how we installed Windows on all the machines. Those two things were usually the only ones we set in BIOS prior to installing the OS.

 

The only variable I can see here is the drivers. It does look like the Otiplex comes with a brand spanking new Intel I219-LM NIC whereas the precision has the Intel 82579 from the days of yore. It would make sense that the older drivers were included in the image but not the newer. I wouldn't be surprised if including the drivers for the I219-LM fixed this.