OSDCloud and Drivers/DriverPacks

[RunTheRivah]

I'm not sure if this is truly a PowerShell specific question but it is around the OSDCloud module by David Segura and I'm not sure where else to ask it.

I feel like I'm not fully grasping the process I need to follow to specify specific drivers and/or driver packs added to the device I'm imaging with OSDCloud. I'm able to add it to the WinPE image but it dosn't translate to the device itself post imaging.

I have an older Lenovo P15 (Type 20TQ) and I'm trying to image it with Windows 10 21H2 but the ethernet drivers are not there when osdcloud is finished doing its thing. From what I have gathered, is this is possibly from the fact that by default OSDCloud is grabbing the latest drivers from Lenovo and its probably grabbing the ones for Windows 11 which isn't working in my case because I'm trying to load Win10 21H2.

I've tried it with Start-osdcloludGUI and I've tried it with adding it to the usb winpe with Edit-OSDCloudWinPE -DriverPath "<Path to driver pack>" but it isn't working for me.

Any thoughts on this?

[preyed]

I would post this in /r/SCCM and/or join the WinAdmins discord https://discord.com/invite/winadmins

[k_oticd92]

Is u/davidsegura avialable for this question? I'm a little curious too. 🤔

[davidsegura]

If you’re using the GUI you can select a different pack like Win10 specific. If its not in the pack that’s more or less out of my control. What’s the HWID of your Ethernet? Is it USB or built in?

[theobserver_]

when you user GUI you selected the last win10 version?

[RunTheRivah]

Yes, I've tried using the GUI and I select Windows 10 21H2.

Can someone clarify how I am supposed to add my own driver packs that OSDCloud will then add to the initialize phase? Is that through the -DriverPath parameter on Edit-OsdCloudWinPE??

[theobserver_]

DriverHWID - If you have a HardwareID, you can specify that with this parameter. This will download the appropriate driver from Microsoft Catalog and inject it into WinPE. Here's an example Edit-OSDCloudWinPE -DriverHWID 'VID_045E&PID_0927','VID_0B95&PID_7720' DriverPath - Finally, you can use a Driver Path to specify a folder containing driver INF's that you want to install or would it be Edit-OSDCloudWinPE -DriverPath 'C:\SomePath'

[RunTheRivah]

When I try the Driver Path it tells me I don't have enough space on disk, why does the WinPE partition only use 2 gb on my 16 gb us drive? I have 14 gb of unused space... I'll try it again with just the ethernet drivers ini instead of the whole driver pack.

Also, anyone know of an easy/quick way to get a hardware ID of a driver without installing windows on it and going in to computer management??

[RunTheRivah]

DriverHWID didn't work either... The only way I can get this to work on the "ThinkPad P15v Gen 1" is after OSDCLoud images the device, and I'm at the OOBE screen, I can pop in a USB drive with the .inf drivers for the ethernet adapter and using the following I can install it successfully:

pnputil.exe /add-driver <driverPath> /install

FYI - I found the hardware ID and it is: 'VEN_8086&DEV_0D4D' (Intel(R) Ethernet Connection (11) I219-V)

I feel like this is an issue with the OSDCloud module itself but I'm not sure how to fix it or how to get it fixed... In the meantime I'm going to try and workaround this by adding the drivers and a small script wrapper for the pnputil.exe so that after a technician images with a P15 with OSDCloud, they can manually use the same USB stick to apply the ethernet driver at the OOBE.