Injecting new NIC driver in Boot (x64) file causes WDSServer service not to start

Hello ConfigMgr community,

This week, we have received a new model workstation, HP EliteDesk G1 800 SFF. So, as per usual, I do my job of testing out my current production image on it to see what drivers would need to be included in the driver package.

First thing I notice, I do not get an IP in Windows PE. Fine.

I download the NIC drivers off the support web page of HP, and after fiddling with a test Boot image I have, I finaly manage to isolate the SYS/CAT/INF/DLL files I need to import in my drivers.

The driver itself is: Intel (R) Eternet Connnction I217-LM.

I then add this specific driver in the Windows PE tab of my Boot Image (x64). Press a few next next finish, which then launches the process of recompiling my boot image, injecting the drivers and redistributing the image on my 50 or so Distribution Point.

Here's where my problem lies. As soon as the distribution starts, my individual DPs go from Install Pending to Installed. I then start receiving alerts from my SCOM agent stating that my Windows Deployment Service isn't running.

Sure enough, I manually log into a few of my servers, and the service is stopped.

If I try manually starting the service: Windows could not start the Windows Deployment Services Server service on Local Computer. Error 1067: The process terminated unexpectedly.

And here's the kicker: if I roll back the change, and remove the driver I just injected, WDSServer service is able to restart without any issue.

I also tried the whole process with the latest driver downloaded from Intel.com website, again, same issue.

Looking over Google/Bing for this specific problem doesn't yield anything very useful to me.

I was wondering if anyone ever had this issue, and if so, how did you resolve it?

Thanks,

Stephane

October 1st, 2013 8:34pm

Hello,

Download the drivers x86 or x64 with this link https://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=18713&lang=eng&OSVersion=Windows%207%20%20*&DownloadType=Drivers

I am try and this good.


Free Windows Admin Tool Kit Click here and download it now
October 2nd, 2013 3:55pm

Hello,

Download the drivers x86 or x64 with this link https://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=18713&lang=eng&OSVersion=Windows%207%20%20*&DownloadType=Drivers

I am try and this good.


October 2nd, 2013 3:55pm

Thanks for your reply.

I tried something else in the meantime before reading your reply.

My solution works, altough, I'd classify it more of a workaround than an actual fix.

1- Delete the Boot Image from all DPs

2- Import driver in Boot Image, recompile

3- Re-distribute image on all DPs

Luckily, in my case, the boot image remained slim enough at 140MB so it was only a minor nuisance, and since I don't modify my Boot image all that often, I chose to stick with this as a valid workaround.

  • Marked as answer by SteFau Thursday, October 03, 2013 6:56 PM
Free Windows Admin Tool Kit Click here and download it now
October 3rd, 2013 9:56pm

Thanks for your reply.

I tried something else in the meantime before reading your reply.

My solution works, altough, I'd classify it more of a workaround than an actual fix.

1- Delete the Boot Image from all DPs

2- Import driver in Boot Image, recompile

3- Re-distribute image on all DPs

Luckily, in my case, the boot image remained slim enough at 140MB so it was only a minor nuisance, and since I don't modify my Boot image all that often, I chose to stick with this as a valid workaround.

  • Marked as answer by SteFau Thursday, October 03, 2013 6:56 PM
October 3rd, 2013 9:56pm

Thank you! Your suggestion to download the driver from Intel worked. I have tried and forced HP drivers to no avail until I found this link and used the other backdoor (which is the intel link) and that worked!
Free Windows Admin Tool Kit Click here and download it now
January 29th, 2014 6:07pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics