SCCM 2012 Windows 8.1 deployed but no NIC driver
I am extremely new to SCCM, please bear with me and be explicit in your answers :-)
I have a Dell E7450 that I'm deploying Windows 8.1 to via SCCM PXE boot.
The OS Deployment seems to be working OK through the WinPE stage, but when the machine reboots and starts to run Windows 8.1 it doesn't have the network driver installed and so can't join AD (or do any of the other stuff in the task sequence).
I've grabbed the Dell driver CAB for this model and extracted this and imported it as a driver package, plus made a new category for it.
I've got the task sequence after "apply windows settings" but before "apply network settings".
Any suggestions/help would be much appreciated. Thanks in advance.
I have a Dell E7450 that I'm deploying Windows 8.1 to via SCCM PXE boot.
The OS Deployment seems to be working OK through the WinPE stage, but when the machine reboots and starts to run Windows 8.1 it doesn't have the network driver installed and so can't join AD (or do any of the other stuff in the task sequence).
I've grabbed the Dell driver CAB for this model and extracted this and imported it as a driver package, plus made a new category for it.
I've got the task sequence after "apply windows settings" but before "apply network settings".
Any suggestions/help would be much appreciated. Thanks in advance.
then you are not selecting that package when the installation runs after it discovers the device bios.
it has been observed that a Microsoft kb has to also be applied
https://sccmfaq.wordpress.com/2014/02/01/osd-for-dell-e7440-e7240-nic-driver-problem-kmdf-update/
it has been observed that a Microsoft kb has to also be applied
https://sccmfaq.wordpress.com/2014/02/01/osd-for-dell-e7440-e7240-nic-driver-problem-kmdf-update/
Hi,
I have deployed that exact model recently but for W7 (yes, I know!). I used the latest CAB
Latitude E7450 Windows 8.1 6NDJW A05 01/12/2016 565 MB.
I use Johan's "driver control freak" method and add an Apply Driver package with a WMI filter "is like Latitude E7450". I did also experience the sudden KMDF paradigm but strangely it went away when I created a reference image.
Also I found that the E7450 was already supported in WinPE natively, but the E7250 (the baby brother) was not. Quite annoying at the time - I like to the boot WIM clean.
Clearly you have the opposite issue, so make sure your filter is OK and the driver is in the package. The driver is the L2. I can confirm the full name tomorrow.
Attach your smsts.log file if you are still stuck.
Mike
I have deployed that exact model recently but for W7 (yes, I know!). I used the latest CAB
Latitude E7450 Windows 8.1 6NDJW A05 01/12/2016 565 MB.
I use Johan's "driver control freak" method and add an Apply Driver package with a WMI filter "is like Latitude E7450". I did also experience the sudden KMDF paradigm but strangely it went away when I created a reference image.
Also I found that the E7450 was already supported in WinPE natively, but the E7250 (the baby brother) was not. Quite annoying at the time - I like to the boot WIM clean.
Clearly you have the opposite issue, so make sure your filter is OK and the driver is in the package. The driver is the L2. I can confirm the full name tomorrow.
Attach your smsts.log file if you are still stuck.
Mike
ASKER
Thanks for the replies - something cropped up so I've not been back to this yet.
This is the kind of thing I was thinking of though, why would I not just do this? https://technet.microsoft.com/en-gb/library/hh825070.aspx#AddDriverDISM
I like the idea of keeping the original install.wim as vanilla as possible (with the exception of slipstreamed Windows updates) as, and only adding the bare minimum of drivers to just get the image to do the bare minimum to get it to the next stage of the SCCM task sequence.
This is the kind of thing I was thinking of though, why would I not just do this? https://technet.microsoft.com/en-gb/library/hh825070.aspx#AddDriverDISM
I like the idea of keeping the original install.wim as vanilla as possible (with the exception of slipstreamed Windows updates) as, and only adding the bare minimum of drivers to just get the image to do the bare minimum to get it to the next stage of the SCCM task sequence.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Per the original question, on this hardware WinPE has networking, Windows 8.1 does not. If you have no network I don't see how anything can be installed, unless SCCM adds the drivers on the fly to the win 8.1 image as it pulls it down so that they're already present on the disk when Win 8.1 boots? But if that's how it's supposed to work, it isn't.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for the responses.
Mike, so the "apply driver package" task happens whilst the machine is running WinPE?
Mike, so the "apply driver package" task happens whilst the machine is running WinPE?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Glad to hear it's working. I've never used DISM for network drivers. I was tempted recently to put printer drivers in but I resisted :).
Please note that you will need to know the exact driver to install prior to re-installing Windows so use the manufacturer restore disk first, make a note of the driver and then get a fresh download from the manufacturers website. (for instance Intel 82579LM Gigabit Network Connection driver is e1c6232.sys)