I'm trying to bring Dell workstation driver packages into MECM/SCCM, but I'm running into some issues. Dell has switched to providing driver packages as EXE files instead of CAB files. I've managed to extract the drivers for specific models into a folder. However, when I attempt to create a new Driver Package, I often face a UNC path error. To work around this, I've created an empty folder to point to, which has helped at times.
When I try to import the drivers into the driver package after zipping the extracted files, I get an 'Invalid File' error. MECM specifically looks for ZIP files, while the Dell Command wizard still seeks CAB files.
Additionally, I've attempted using MakeCAB to address the situation, but it throws a duplicate file error because there are files with the same name scattered through the folder structure of the drivers.
Just to give you some context, I'm using MECM version V2211 on a Server 2019 OS.
2 Answers
Have you checked out the Dell Command Update? It's designed for commercial customers, but it might help in your situation. Just ensure you have the right .NET version installed, as it's required for installation and usage. This could simplify your driver extraction process a lot!
Even though you're downloading the driver package as an EXE, you should have the option to extract files during the first prompt. After extracting, you can use the 'Import Drivers' option in MECM and point it to that folder on a network path. Make sure you set a proper network path instead of using a local one; MECM typically needs that network location. It might also help to download individual driver packs for each model directly from Dell's site for better reliability.
I found the driver packages for the models I need, but running the EXE doesn't give an option to extract as CAB—only to place files in a source folder. Plus, MECM wants a ZIP for Import Drivers, while the Dell Integration Suite looks for CAB. It’s frustrating when the systems aren’t compatible.