Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Thursday, June 15, 2017 6:03 PM
I believe some context may be important here.
I've been having troubles with deploying images from my SCCM 2012 server for a bit now. First, clients were not able to download the boot image. I found that there were some issues with permissions when the person who I took over for had his account disabled and the boot images I had were corrupted. Before they left everything was working well.
I sorted out the permissions and removed the old and added new boot images. After I resolved that and clients were able to download the boot image, they were running into an issue where the computer would hang at "Preparing Network Connections" and restart. I deleted and re-added drivers and everything seemed to be working again... except for our Dell Latitude E7470s and Precision 7510s. It looks to me like the drivers are not correct. Ipconfig does not acknowledge any Ethernet adapters, so of course it does not have an IP address. smsts.log isn't showing any errors that I can see. I've downloaded the latest cab files for the machines, imported and added net drivers to the boot image but nothing has changed.
I am using SCCM 2012 on 2008 R2 server
DC also has 2008 R2
Legacy Boot
All clients are x64 architecture.
What would make these models fail when others do not? The settings in the BIOS are the same across the board.
All replies (4)
Thursday, June 15, 2017 9:56 PM âś…Answered
If ipconfig shows no information, then it's 100% a missing driver for the NIC.
The drivers you add to the boot image must match the version and architecture of the boot image and the not the version or architecture of the OS deployed.
Also, just because you have a CAB from Dell doesn't mean it has the correct driver for your NIC in it.
You can manually test drivers from within WinPE using the drvload command/executable. You simply supply the .inf file from the driver which you can copy to a USB key and reference from there.
Jason | http://blog.configmgrftw.com | @jasonsandys
Tuesday, June 20, 2017 6:56 PM
Thanks for the reply!
I narrowed it down to a specific driver and was able to receive an IP address after using drvload. So I downloaded directly from Intel, and added to the boot image. Unfortunately the error is still happening. So it must be an issue with the boot image, or perhaps it isn't actually being updated to the distribution point?
Tuesday, June 20, 2017 7:25 PM
It's certainly possible that your boot image with the driver is not making it to DP -- only you can check and validate that.
When you run ipconfig, are you getting an IP address at all?
Jason | http://blog.configmgrftw.com | @jasonsandys
Wednesday, June 21, 2017 11:23 PM
So no, it wasn't being updated to the DP, but it also looks like there was some sort of issue with the boot image. I created new .wim files using ADK, added them and updated everything to point at it and now it's working.
Finding the right drivers and recreating the boot images fixed it.
Thanks for your help!