Dell - Internal Use - Confidential Hi Hunter, We try not to break the driver signing when creating the CABs, but when extracting out the INF drivers for inclusion in the CABs it is possible to break the signing with that extraction process.
Thanks, Warren Byle Dell | Business Client Systems Management Product Manager office +1 512 724 2626 [email protected]<mailto:[email protected]> Client Command Suite<http://dell.com/command> Join the conversation Twitter: WarrenByle<http://twitter.com/WarrenByle> From: [email protected] [mailto:[email protected]] On Behalf Of Bazaco, Hunter Sent: Tuesday, April 5, 2016 8:16 AM To: [email protected] Subject: [MDT-OSD] Unsigned drivers in Dell Latitude E5470x86 CAB files Hello, I am working on adding the Latitude E5470 model to all of our task sequences in SCCM. X64 worked like a charm. However, I am running into an issue where 8 drivers are not signed; and, I'm getting these drivers directly from the Dell site via a CAB file. The drivers all come from the 'security' folder of the extracted CAB file. They all seem to be Broadcom drivers (although, other Broadcom drivers in the CAB file are signed/verified. We typically have a hard rule to not add any unsigned drivers to a task sequence but these are coming directly from DELL. Does anyone know if these are safe or if there are signed versions anywhere that I can grab? I am unable to find an alternative on my own. Thanks, Hunter Bazaco OCIO-IS Managed Desktop Systems Engineer (843)792-7820 -Office (843)670-3680 -Mobile [email protected]<mailto:[email protected]>
