An incorrect value is specified in the Source parameter or in the Destination parameter. about driverautomationtool

[bkehl1971]

Thanks funky-d! That works great!

…

On Fri, Jul 12, 2024 at 12:13 AM funky-d ***@***.***> wrote: To use DAT to create these driver packages after manually downloading the drivers: 1. Download the latest driver package from https://www.dell.com/support/kbdoc/en-us/000124139/dell-command-deploy-driver-packs-for-enterprise-client-os-deployment 2. Navigate to the share where DAT is saving your driver packages (this is found under the Common Settings tab in DAT). 3. Drill down to your list of models and create a folder for the model you are attempting to import, i.e. "Latitude 7350" (depending on how far DAT got before it failed, this folder along with some subfolders listed in the next steps may already exist). 4. Create a "Driver Cab" subfolder within the model folder you just created. 5. Copy the driver package you downloaded in Step 1 into this Driver Cab folder. 6. Go back to the model folder and create a "Windows11-" subfolder. Your folder structure will now look something like this: image.png (view on web) <https://github.com/user-attachments/assets/a8f968d6-4e30-4656-8aec-07dd0243b99f> 7. Either use the command line or a program like 7zip to extract the driver package you copied into the Driver Cab folder into the Windows11- folder. 8. Open DAT and start the Download/Extract/Import process for the drivers again. It will see the driver package exists, see the extracted files exist in the Windows11- folder, and will automatically create the package for you. 9. Optionally, you can edit the package info in SCCM and add the correct driver version. This should tide you over until these drivers can be processed natively via DAT. Hope this helps anyone who was confused, it took a bit of trial and error on my part before I got it working. — Reply to this email directly, view it on GitHub <#537 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AWVSYTMM2CX2YUTMJLKNDNTZL5XW5AVCNFSM6AAAAABFWDV3V2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMRUHAZTGNBXHE> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[bohnanza22]

@TokenRing is right this issue is Dell recycling the model name. Here is a breakdown of what I am seeing. When downloading the Latitude 5550 driver with the DAT the Latitude 5550 has the SKU/Identifiers as 0CB9 and 0CBC. The tool downloads, extracts, and creates the package for Windows 10 but fails for Windows 11 drivers. Here are the screenshots from these resources.
DAT Latitude 5550 item:

Package General Tab:

DAT downloaded cab and manifest xml:

Manually downloading the drivers from https://www.dell.com/support/kbdoc/en-us/000109893/dell-command-deploy-driver-packs-for-latitude-models

Notice the newer driver files are version A01.

As you can see the DAT is downloading the old Latitude E5550 model's driver package from 2020 version A08, then importing it as the newer Latitude 5550 and applying the newer sku's to the metadata of the old driver.

This is causing my OSD task sequences to fail and the computer blue screens after when booting to the full OS for the first time. This is also the reason Windows 11 drivers are failing to download where Windows 10 is downloading something. Since there are no Win 11 drivers available for that old device.

I am going to manually create my packages for this model. If anyone has a good tutorial for me I would appreciate it.

[funky-d]

To use DAT to create these driver packages after manually downloading the drivers:

1. Download the latest driver package from https://www.dell.com/support/kbdoc/en-us/000124139/dell-command-deploy-driver-packs-for-enterprise-client-os-deployment
2. Navigate to the share where DAT is saving your driver packages (this is found under the Common Settings tab in DAT).
3. Drill down to your list of models and create a folder for the model you are attempting to import, i.e. "Latitude 7350" (depending on how far DAT got before it failed, this folder along with some subfolders listed in the next steps may already exist).
4. Create a "Driver Cab" subfolder within the model folder you just created.
5. Copy the driver package you downloaded in Step 1 into this Driver Cab folder.
6. Go back to the model folder and create a "Windows11-" subfolder. Your folder structure will now look something like this:
   
7. Either use the command line or a program like 7zip to extract the driver package you copied into the Driver Cab folder into the Windows11- folder.
8. Open DAT and start the Download/Extract/Import process for the drivers again. It will see the driver package exists, see the extracted files exist in the Windows11- folder, and will automatically create the package for you.
9. Optionally, you can edit the package info in SCCM and add the correct driver version.

This should tide you over until these drivers can be processed natively via DAT. Hope this helps anyone who was confused, it took a bit of trial and error on my part before I got it working.

[Acabar]

I'm seeing the same with the Latitude 5450 and Latitude 5550. Did a Optiplex 7020 (Micro and SFF) with out an issue.
I'm using the forked version of the .ps1 provided by ajn142attamu (#524 (comment)) until the msi hotfix issues are fixed.

[Acabar]

I also tested it with the latest official .ps1 and received the same error.

[mchippy]

I'm getting the same for 5550. Tried updating to 7.2.3 to see if it was something with the application and now my AV is eating the newer executable.. so we're dead in the water for this tool until I can get it whitelisted. Manually crafting driver packages is a pain when you're used to having this tool doing the work for you!

[bkehl1971]

My guess is that it has something to do with these models being so new but I don't know what.

…

On Thu, Apr 18, 2024 at 3:15 PM mchippy ***@***.***> wrote: I'm getting the same for 5550. Tried updating to 7.2.3 to see if it was something with the application and now my AV is eating the newer executable.. so we're dead in the water for this tool until I can get it whitelisted. Manually crafting driver packages is a pain when you're used to having this tool doing the work for you! — Reply to this email directly, view it on GitHub <#537 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AWVSYTJLEDDADS6TYO2NRTTY6AZYTAVCNFSM6AAAAABFWDV3V2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANRVGMZTOMBYGE> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[mchippy]

Yeah, I'm not sure either. I downloaded the EXE manually and placed it, but it can't run the extraction now.

[bkehl1971]

I couldn't make manual package creation work either. I downloaded the CAB, expanded it using the EXE, and then used DISM to create my package.

…

On Thu, Apr 18, 2024 at 3:43 PM mchippy ***@***.***> wrote: Yeah, I'm not sure either. I downloaded the EXE manually and placed it, but it can't run the extraction now. image.png (view on web) <https://github.com/maurice-daly/DriverAutomationTool/assets/97312277/5e3ce191-4322-4fd4-8748-eb0cb5dbdebd> — Reply to this email directly, view it on GitHub <#537 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AWVSYTLAUYKNJHUZB4PUPJDY6A5AVAVCNFSM6AAAAABFWDV3V2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANRVGM3TKMJRGQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[mchippy]

Ouch. Thanks, mate. Looks like these will have to be manual.

[bkehl1971]

Yeah, it was ugly.

…

On Thu, Apr 18, 2024 at 3:47 PM mchippy ***@***.***> wrote: Ouch. Thanks, mate. Looks like these will have to be manual. — Reply to this email directly, view it on GitHub <#537 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AWVSYTO6KAE2O3VPS2AVDJ3Y6A5PTAVCNFSM6AAAAABFWDV3V2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANRVGM3TSNBVGI> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[mchippy]

Looks like it might be working after I manually extracted the drivers to the "Windows11-" directory it creates. If I try and give the Windows11- it's version (A00), it doesn't see it, so it might have something to do with the way Dell is naming of the files? Might have to rename some of the directories to append "A00" and do a little cleanup. fingerscrossed

[bkehl1971]

I'll try that, I have a couple more that aren't working.

…

On Thu, Apr 18, 2024 at 3:58 PM mchippy ***@***.***> wrote: Looks like it might be working after I manually extracted the drivers to the "Windows11-" directory it creates. If I try and give the Windows11- it's version (A00), it doesn't see it, so it might have something to do with the way Dell is naming of the files? Might have to rename some of the directories to append "A00" and do a little cleanup. *fingerscrossed* image.png (view on web) <https://github.com/maurice-daly/DriverAutomationTool/assets/97312277/106f19bd-89de-4bf5-a58d-8339d2b2e79a> — Reply to this email directly, view it on GitHub <#537 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AWVSYTLVZQCW5YTWWPQEFHDY6A6YTAVCNFSM6AAAAABFWDV3V2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANRVGM4TINZZGA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[browndervilleb]

Looks like it might be working after I manually extracted the drivers to the "Windows11-" directory it creates. If I try and give the Windows11- it's version (A00), it doesn't see it, so it might have something to do with the way Dell is naming of the files? Might have to rename some of the directories to append "A00" and do a little cleanup. fingerscrossed

Can you provide a bit more detail on how you accomplished this?

[TokenRing]

We have the issue with the Latitude 5550 as well. I'm suspecting this might have something to do with Dell's (idiotic) decision to re-use model names. Notice that both the 5550 and 5450 both have E-named equivalents, but the version of the name without the E was used in Dell's documentation - case in point: https://www.dell.com/support/manuals/en-us/latitude-e5450-laptop/dell_latitude_e5450_om-v1/technical-specifications?guid=guid-ff58d80e-59c8-4c89-bcf1-57aedc89cc0d&lang=en-us - the "Dell Latitude E5450 / 5450 Owner's Manual"

The E-named laptops were released almost a decade ago now. And here Dell is, reusing model names without the E.

I speculate that DAT needs some improved logic to handle Dell's stupid naming decisions.