/build/static/layout/Breadcrumb_cap_w.png

Systems Deployment Question


K2000 Issue with Dell latitude 3480 audio driver Build 1903

02/12/2020 68 views

We are just starting to use the K2000, and we ran into an issue with the Dell latitude 3480 audio drivers. Build 1903. Once imaged we could not fix the audio driver no matter what we did.We tried every driver Dell provided and removed and reinstalled but still had issues in the device manager

We used Dism and put the 1809 image onto the same laptop and the Audio works fine. Issue we have over 300 of this model laptop.  We are upgrading the 1809 build to the 1903 to see if it still works,  but i was wondering if anyone else has ran into this issue? if yes what have you done to fix it?


1 Comment   [ + ] Show comment

Comments

  • Have you activated the "Dell Driver Feed" for the Latitude 3480 in the KAE SDA Library?

    In addition, the KACE SDA normally sets up all drivers automatically for Dell systems.

All Answers

0

The latest enterprise driver pack for that model, is version A11:
https://www.dell.com/support/article/us/en/04/how13603/latitude-3480-windows-10-driver-pack?lang=en

That is the same version available in the KACE SDA, and it includes Audio Driver version  6.0.1.8555.

Is that the same driver version reported by Device Manager after the Imaging process?

Could be an issue with the driver itself,  Was that Imaged Sysprepped and Captured from a VM? (Virtual machines provide the best Images for mass deployment, as they won't carry any drivers from any previous device).

Also if you download the Audio Driver from Support.Dell.com (the non enterprise page, that usually have the newest but not tested drivers), and manually install it, does that work? (if so, you could setup a Post Install Task Script, to install that audio driver as part of the Imaging process).
If this Image was Sysprepped and Captured from a VM, with a KBE built with ADK 1903, then we can consider this a good image and look somewhere else.

I would suggest checking at the DISM log in Windows, get the dism.log from c:\windows\dism.log, (Not the one from c\windows\logs\dism\dism.log)

That log generated by Windows will tell you what drivers where injected and from where, and if Windows or DISM did not like them.

Also when you say issues with audio....., could your elaborate?

  

Answered 02/13/2020 by: Channeler
Red Belt

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ