search

MSEndpointMgr / ModernDriverManagement

Official repo of Modern Driver Management from MSEndpointMgr.com
https://www.msendpointmgr.com
MIT License
133 stars 80 forks source link

Issue Downloading Drivers for New OptiPlex 7010 (Micro, SFF, and Tower) #239

Open jchirino-uf opened 1 year ago

jchirino-uf commented 1 year ago

Hello,

We get the errors below when downloading the Win 11 drivers for the new OptiPlex 7010. We also notice that it tries to create the Win11 folder, but it is not named properly. Even if we rename the folder, it will recreate a new folder named incorrectly again, and nothing gets extracted. Is anyone else experiencing the same issue? I believe there is an issue with how Dell handles the new models now: it is by the model's form factor instead of the model itself. How the tool manages it might also be a problem because the folder it is extracting it to is listed as Optiplex 7010, but there are three form factors now of Optiplex 7010's... Will they all go to the same folder? Which one does it know to pick?

image

`[Start Up]

Start-Process : This command cannot be run due to the error: No application is associated with the specified file for this operation. At line:20727 char:6

Exception calling "Substring" with "2" argument(s): "Length cannot be less than zero. Parameter name: length" At line:20728 char:6

Exception calling "Substring" with "2" argument(s): "Length cannot be less than zero. Parameter name: length" At line:20068 char:8

Start-Process : This command cannot be run due to the error: No application is associated with the specified file for this operation. At line:20727 char:6

Exception calling "Substring" with "2" argument(s): "Length cannot be less than zero. Parameter name: length" At line:20728 char:6

Exception calling "Substring" with "2" argument(s): "Length cannot be less than zero. Parameter name: length" At line:20068 char:8

Start-Process : This command cannot be run due to the error: No application is associated with the specified file for this operation. At line:20727 char:6

Exception calling "Substring" with "2" argument(s): "Length cannot be less than zero. Parameter name: length" At line:20728 char:6

`

WorkplaceEngineerAtWork commented 1 year ago

Same issue here. It does not matter if it is for Windows 10 or Windows 11. Other new devices from Dell do work fine (i.e. Precision 7780) but not for the Optiplex 7010 series. The previous version Optiplex 7000 works.

blurayofdeath commented 1 year ago

Yes we have the exact same issue.

blurayofdeath commented 1 year ago

I think half the problem is the EOL Dell Optiplex 7010 and the new Dell Optiplex SFF 7010 Plus.

randhirsinggh commented 1 year ago

We experiencing same issue. Did anyone found solution?

blurayofdeath commented 1 year ago

We manually created the package in the same format as the others. This was the comment field for 7010 package is below, the SKU is 0BD0 and I suspect the other SKU's are for the old model 7010's, but it worked so moving on with life. (Models included:02C3;0577;0BE3;0BE4;0BE5;0BE6;0BD0;0BD1;0BD2;0BD3;0BCC;0BCD;0BCE;0BCF)

sveken commented 1 year ago

Same issue here but with a Latitude 3340. As @blurayofdeath mentioned i think it is something to do with the EOL model as the 3340 is both a new and old model (thanks Dell) Ended up downloading the cab file manually, extracting it manually, and then rerunning the tool so it detects the extracted files and auto makes the package.

Then in SCCM had to adjust the version number to A00. All works.

Next problem is this also affects BIOS versions too. We had an A16 revision still in sccm for the EOL 3340 which was marked as higher as the 1.3 version of the new 3340 so it never gets downloaded. We only have a single EOL 3340 in service so we just deleted the BIOS packages off for it, then it worked for the BIOS.

kjarant commented 3 months ago

@sveken we just got some of the new 3340's and running into the same issue. I downloaded the driver package from dell, added it to the folder and extracted it to the windows11- folder. I ran the tool again and it isn't loading the drivers in to the folder but it is creating a wim file in the standard folder. Any advice?

sveken commented 3 months ago

You might need to manually create the driver package unfortunately. As long as you name it correctly and add the Model ID in the description your existing task sequences will still pick it up.

kjarant commented 3 months ago

Yeah, thats what I was resigning myself too. Thanks Dell...