[SOLVED] WADS | WINPE filter problem on Dell Pro 14 PC14250

[PA DEQUIDT]

WADS | WINPE filter problem on Dell Pro 14 PC14250

Good morning,

We use the WADS solution to deploy our Windows 11 workstations, relying on our existing MDTs.

We have a number of drivers, such as those for Dell Latitude models (about ten), as well as several HP workstations. These do not appear to pose any problems during hardware deployment.

Regarding the Dell Pro 14 PC14250 workstations, the drivers are not deploying correctly during the master image process. See the attached image for details

Dell_Pro_14_PC14250_01.png (14.82 KB) Viewed 21193 times

We see the line corresponding to the driver in question: at the Filters level I indicated the return of the command: "Get-CimInstance -ClassName Win32_ComputerSystem | Select-Object Manufacturer, Model" from a Pro 14 PC14250 workstation.

I used the manufacturer's drivers: https://www.dell.com/support/kbdoc/fr-f ...windows-11

Do you have any suggestions for solving this problem?

Thank you in advance.

Pierre-Alexis DEQUIDT

[sfonteneau]

Hello,

on the deployed machine, do you have the folder:

c:\installdir\drivers

present?

Simon

[PA DEQUIDT]

Hello,

thank you for the quick reply.

The folder is there but it contains no content.

[sfonteneau]

I think I understand; there's some confusion.

The filter you mentioned is meant to be used as shown in the image.

Is that what you're doing before deployment?

After clicking the button, the "driver configuration" column should be populated.

[PA DEQUIDT]

This is indeed how we select drivers across all our workstations during a WADS imaging process.

Could you confirm that for Dell Pro 14 PC14250 workstations, the filters are correctly set to: Dell Inc.\Dell Pro 14 PC14250?

[sfonteneau]

Technically, when you click on "Automatic Driver Bundle Selection," the console takes the "Manufacturer" and "Product" columns from the grid.

Then, the console retrieves all existing driver bundles and checks their filters. If it matches MANUFACTURER\PRODUCT, then the driver bundle is assigned.

Therefore, for this to work, the PC's "Manufacturer" and "Product" columns must be populated, and the filter must match.

You can verify if the filter matches by checking that, after clicking "Automatic Driver Bundle Selection," the "Driver Configuration" column is populated with the correct bundle.

[PA DEQUIDT]

Hello,

I was able to find the solution. The filters were correct; the problem was with the driver import method. I was using the .exe file directly, instead of the unzipped folder containing the .exe. Once imported by pointing to the folder instead of the .exe file directly, WADS correctly sees and installs the drivers.

Thank you for all your feedback.

Have a good day