Current Driver CAB Summary | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Delta Report for Previous Driver CAB v/s Current Driver CAB | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
(065VH-A07-05/09/2017) v/s (J4FJW-A08-08/08/2017) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
----Comparison Report---- | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
↧
Venue 8 Pro (5855) Windows 10 Driver Pack
↧
XPS 12 (9250) Windows 10 Driver Pack
Current Driver CAB Summary | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Delta Report for Previous Driver CAB v/s Current Driver CAB | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
(M08ND-A08-05/09/2017) v/s (FXM1W-A09-08/08/2017) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
----Comparison Report---- | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
↧
↧
XPS 15 (9550) Windows 10 Driver Pack
Current Driver CAB Summary | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Delta Report for Previous Driver CAB v/s Current Driver CAB | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
(NY46Y-A09-05/09/2017) v/s (5W9NN-A10-08/08/2017) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
----Comparison Report---- | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
↧
Dell Command | Deploy - Driver Packs for Enterprise Client OS Deployment
Below you will find Driver CABs for Dell Enterprise class systems (Latitude, Optiplex, Precision) to be used to simplify OS deployments on those systems with deployment tools like Microsoft System Center Configuration Manager (ConfigMgr/SCCM) or Microsoft Deployment Toolkit (MDT).
System CABs for Venue, XPS, Latitude, Optiplex, and Precision Workstations - are designed for deployment to a single model and are developed and supported by Dell
WinPE CABs are designed to provide required drivers for WinPE to boot a Dell Latitude, Optiplex, or Precision Workstation for the purpose of OS Deployment.
Family Driver Packs are designed for deployment to multiple models and are developed and supported by the Dell Configuration Services.
The links below will provide additional details on the CABs and a link to download.
If you are new to Dell Driver CABs, please check out the .CAB File Documentation and Walk-Throughs or the Win 7 Deployment video
You can also access the System CABs from http://support.dell.com -- Select Drivers & Downloads, and enter the system model. You will find the supported driver .cab file in the "Systems Management" section under "Driver Pack".
Automate your driver management by leveraging the Driver Pack Catalog.
Driver CAB's are grouped by product family and are listed with the most recent products at the top.
The Driver CABs are updated based on a release schedule which updates newer systems more frequently. New CAB download pages will include Delta Reports on what has changed in the CAB.
If you still have questions, check out the Deployment FAQ page or our discussion forums.
NOTE: Windows 8 CABs for older systems will be reviewed periodically to see if there are new drivers required. It is currently expected that Windows 8 will contain the drivers required for those systems.
WinPE - CAB Availability (follow the links for CAB details and to download)
| WinPE version | Current CAB |
| WinPE 10 | A04 (01/10/2017) |
| WinPE 5.x | A09 (02/14/2017) |
| WinPE 4.x | A06 (06/02/2015) |
| WinPE 3.x | A21 (02/14/2017) |
| WinPE 2.x | A00 (05/26/2009) |
XPS Systems - CAB Availability (follow the links for CAB details and to download)
| System | Windows 10 System CAB | Windows 8.1 System CAB | Windows 8 System CAB | Windows 7 System CAB |
| XPS 11 (9P33) | A00 (08/19/2015) | A00 (11/14/2013) | ||
| XPS 12 (9250) | A09 (08/08/2017) | |||
| XPS 12 (9Q33) | A00 (10/23/2013) | A00 (07/19/2013) | ||
| XPS 12 (L221x and 9Q23) | A01 (03/38/2016) | A01 (12/10/2012) | ||
| XPS 13 (9365) | A03 (07/11/2017) | |||
| XPS 13 (9360) | A04 (07/11/2017) | |||
| XPS 13 (9350) | A08 (07/11/2017) | A04 (07/26/2016) | A07 (07/11/2017) | |
| XPS 13 (9343) | A04 (05/09/2017) | A04 (02/09/2016) | A05 (11/08/2016) | |
| XPS 13 (9333) | A01 (03/08/2016) | A00 (11/22/2013) | A00 (11/22/2013) | |
| XPS 13 (L321x and L322x) | A01 (03/08/2016) | A02 (07/31/2013) | A04 (08/29/2013) | |
| XPS 14 (L421x) | A01 (03/08/2016) | A01 (02/25/2013) | A01 (02/25/2013) | |
| XPS 15 (9560) | A03 (07/11/2017) | |||
| XPS 15 (9550) | A10 (08/08/2017) | A06 (09/13/2016) | ||
| XPS 15 (9530) | A01 (01/12/2016) | A00 (10/23/2013) | ||
| XPS 15 (L521x) | A01 (03/08/2016) | A01 (02/25/2013) | A03 (02/25/2013) |
Internet Of Things - CAB Availability (follow the links for CAB details and to download)
| System | Windows 10 System CAB | Windows 7 System CAB |
| Embedded Box PC 3000 | A00 (02/14/2017) | A04 (07/11/2017) |
| Embedded Box PC 5000 | A01 (07/11/2017) | A04 (07/11/2017) |
Venue Systems - CAB Availability (follow the links for CAB details and to download)
NOTE: Detail on deploying Venue tablets can be found HERE
| System | Windows 10 System CAB | Windows 8.1 System CAB |
| Venue 11 Pro (7140) | A05 (04/11/2017) | A03 (01/12/2016) |
| Venue 11 Pro (7130 MS/ 7130 vPro/7139 vPro) | A03 (11/08/2016) | A07 (02/09/2016) |
| Venue 11 Pro (5130) | A02 (06/14/2016) | A08 (02/09/2016) |
| Venue 10 Pro (5056) | A08 (08/08/2017) | A03 (06/14/2016) |
| Venue 8 Pro (5855) | A08 (08/08/2017) | A03 (06/14/2016) |
| Venue 8 Pro (5830) | A02 (06/14/2016) | A07 (02/09/2016) |
Latitude Systems - CAB Availability (follow the links for CAB details and to download)
Optiplex Systems - CAB Availability (follow the links for CAB details and to download)
Precision Systems - CAB Availability (follow the links for CAB details and to download)
Family Driver Pack Availability.
Notice: The Dell Family Packs have moved here.
↧
Dell Client Command Suite Webcast
Join our weekly webcast to discuss the Dell Client Command Suite and other systems management topics of interest to Dell customers.
When: Thursdays at 10am US Central Time (see schedule below for details) Download a calendar invite (.ics) here
Where: http://delltechcenter.adobeconnect.com/command/
Upcoming Webcast Topics
| Date | Topic |
| August 24th, 2017 | Sorry, No Webcast today! Please watch a recording below. |
Previously Recorded Webcasts
↧
↧
Dell Command | Configure
NOTE: if you have issues importing an .EXE into SCCM with our plug-in, you need to upgrade to version 3.3 below.
Overview
Dell Command | Configure is a packaged software application that provides configuration capability to business client platforms.
This product consists of a Command Line Interface (CLI) and Graphical User Interface (GUI) to configure various BIOS features. Dell Command | Configure supports following Windows and Linux operating systems: Windows 7, Windows 8, Windows 8.1, and Windows 10, Windows Pre-installation Environment (Windows PE), Red Hat Enterprise Linux 6, Red Hat Enterprise Linux 7, and Ubuntu Desktop 16.04.
This is the 3.3 version of Dell Command | Configure.
Downloads
- Windows download (Released - 08/03/2017) Error Codes
- Linux downloads (Released - 02/02/2017)
- Documentation
Fixes in the Release
Fixes in version 3.3:
Added support for 64-bit SCE packages for WinPE 64 environments
-ASM (advsm) option does not display the current status for probes issue has been resolved
Enhancements:
- Support for new platforms
- Support for following new BIOS features/attributes -
Enable MPM Configuration (--mpmcfg)
Limit system memory to less than 1 TB (--onetbsystemmemorylimitenable)
Tablet Button Illumination (--tabletbuttonillumination)
Enable AMD Turbo Core Technology (--amdturbocore)
Enable AMD Simultaneous Multithreading Technology (--amdthreadcontrol)
Enable AMD-V Technology (--amdvtenable)
Enable AMD-Vi Technology (--amdvienable)
Enable Rear USB 3.0 Ports (--rearusb3ports)
Enable Bluetooth, Front USB ports, and Rear USB 2.0 ports (--frontusbportcollection)
TPM Clear (--tpmclear)
Computrace (--computrace)
MAC Address Pass-Through (--macaddrpassthru)
Usb Ports Internal2 (--usbportsinternal2)
Pcie LinkSpeed (--pcielinkspeed)
Sign Of Life By Audio (--signoflifebyaudio)
Sign Of Life By Display (--signoflifebydisplay)
Sign Of Life By KbdBacklight (--signoflifebykbdbacklight)
MINISAS-HD_0 (--minisas0)
MINISAS-HD_1 (--minisas1)
MINISAS-HD_2 (--minisas2)
MINISAS-HD_3 (--minisas3)
Intel VMD Technology (--intelvmdtechnology)
Rugged Desk Dock NIC PXE (--ruggeddeskdocknicpxe)
The following fixes are made for 3.2.0 A00 only.
- Removed dependency on MSVCR110.dll and MSVCP110.dll in 32-bit application.
- Missing HAPI driver libraries issue for CLI alone installation has been resolved.
- Error codes are retained same as 3.1 release.
New in the Release
- Support for new platforms.
- Support for SMBIOS 3.0
- Updated the default installation path for Linux (RHEL and Ubuntu) as /opt/dell/dcc.
- Support for following new BIOS features/attributes:
- Determining if BIOS should attempt to boot from the legacy boot list when the UEFI boot list fails (--attemptlegacyboot).
- Configuring the Active State Power Management (ASPM) level (--aspm).
- Configuring the automatic BIOS recovery without any user interaction if BIOS corruption is detected (--biosautorecovery).
- Configuring the BIOS connect feature (--biosconnect).
- Configuring the state of the available BiosConnect boot paths (--biosconnectactivation).
- Allowing or restricting downgrading of the system BIOS (--biosdowngrade).
- Configuring the BIOS integrity check during the booting process (--biosintegritycheck).
- Allowing or restricting the BIOS event log to be cleared on the next boot (--bioslogclear).
- Configuring the visibility of BIOS settings (--biossetupadvmode).
- Configuring the time-out value for the keyboard backlight when an AC adapter is plugged into the system (--brightnessac).
- Configuring the panel brightness to be used when the system is using battery power only (--brightnessbattery).
- Configuring the Reliability Availability Serviceability (RSA) support on CPUs (--cpursa).
- Configures the CPU snoop mode (--cpusnoop).
- Configuring the platform external displays (--dgpuexterndisplay).
- Configuring Configures the dock battery charge mode (--dockbattchrgcfg).
- Allowing or restricting to use the docking station in the absence of AC power while the battery is charged for more than specified percentage (--docksupportonbattery).
- Configuring the fan speed control if the fan speed is set to Auto using fanspeed attribute (--fanspeedctrllevel).
- Configuring whether to clear the fault tolerant memory log during the next boot (--faulttolerantmemlogclear).
- Configuring the full screen logo that appears during BIOS POST (--fullscreenlogo)
- Configuring GPS WWAN Radio (--gpsonwwanradio).
- Configuring System Isochronous mode (--isochronous).
- Configuring the time-out value for the keyboard backlight when an AC adapter is plugged into the system (--kbdbacklighttimeoutac).
- Configuring the time-out value for the keyboard backlight when the system is running only on battery power (--kbdbacklighttimeoutbatt).
- Configuring lid switch functions (--lidswitch).
- Configuring the liquid cooler 1, and the liquid cooler 2 (--liquidcooler1, and --liquidcooler2).
- Configuring M2 PCIE SSD 0 and M2 PCIE SSD 1 (--m2pciessd0, and --m2pciessd1).
- Configuring the master password settings (--masterpwdlockout).
- Configuring the time limit value of the memory fault tolerance (--memfaulttoltimelmt).
- Configuring Reliability Availability Serviceability (RSA) support on memory modules (--memoryrsa).
- Configuring the memory performance monitor feature (--memperformancemonitor).
- Configuring the Reliability Availability Serviceability (RSA) support on PCIe devices (--pciersa).
- Allows or restricts the power event log to be cleared on the next boot (--powerlogclear).
- Configuring the Stealth Mode control of the Intel 8260 card (--poweroffintel8260stealthmode).
- Configuring the Dell recovery tool (--recoverytool).
- Allowing or restricting the system to boot from SD card (--sdcardboot).
- Configuring the read-only mode for SD card (--sdcardreadonly).
- Configures Secure Guard Extensions (SGX) feature (--secureguardext).
- Indicating that the power button has been pressed during POST (--signoflifeindication).
- Determining which sleep mode to be used by the operating system (--sleepmode).
- Configuring the boot flow for SupportAssist OS recovery tool in the event of certain system errors (--supportassistosrcvry).
- Deleting the service OS non-volatile region (--svcosclear).
- Allows or restricts the thermal event log to be cleared on the next boot (--thermallogclear).
- Configuring the thunderbolt controller in the system (--thunderbolt).
- Configuring the thunderbolt security level (--thunderboltsecuritylevel).
- Configuring the maximum power for type-C connector (--typecbtryovrldprotection).
- Determining whether the system should prompt the user to enter the Admin password, if set, while booting from a UEFI boot path from the F12 Boot Menu (--uefibootpathsecurity).
- Configuring the provisioning of Intel AMT from a USB storage device (--usbprovision).
- Configuring the USB wake from s4 power state of the system (--usbwakefroms4)
- Support for additional possible values for the following BIOS features/attributes:
- --cpucore
- --speaker
- --primaryvideodeviceslot
- --processorcorecount
- Withdrawal of support for the following BIOS features/attributes:
- --clearsel
- --speakervol
Known Issues
Issue: The exported SCE (.sh) file does not run on Linux, and displays the error message that "Improper version of OS used".
Description: The SCE (.sh) file exported using Dell Command | Configure GUI does not run on the systems running the following operating systems: RHEL 6.8, RHEL 7.3 & Ubuntu Desktop 14.04.
Resolution: Add the OS version of the target system by manually editing the exported .sh file.
Examples:
For the systems running Ubuntu Desktop 14.04, edit the .sh file as highlighted below.
if [ -f /etc/lsb-release ]; then export OS=`lsb_release -r | sed s/[^0-9]//g`; if [(( $OS == 1504 )) || (( $OS == 1604 )) || (( $OS == 1404 ))]; then CCTKPATH=/opt/dell/dcc; |
For the systems runningRHEL 7.3, edit the .sh file by as highlighted below.
elif [ -f /etc/redhat-release ]; then export OS=`cat /etc/redhat-release | sed s/[^0-9]//g`; if [(( $OS == 56 )) || (( $OS == 60 )) || (( $OS == 70 )) || (( $OS == 73 ))]; then CCTKPATH=/opt/dell/dcc; |
Previous Releases
Dell Command | Configure 3.1.2
- Windows download
- Linux downloads
- Documentation
- Windows download
- Linux downloads
- Documentation
Dell Command | Configure 3.0
- Windows download
- Linux downloads
- Documentation
Whitepapers/Technical Documents
- Configuring Remote Wake-Up using Dell Client Command Suite
- Configuring Dell Business Client Systems using Dell Command | Configure
- Securing Dell Commercial Client Systems with Trusted Platform Module (TPM) using Dell
Client Command Suite
Video
1. Activating the TPM with Dell Command | Configure
(Please visit the site to view this video)
2. Setting the BIOS defaults using Dell Command | Configure
(Please visit the site to view this video)
↧
Dell Command | Monitor
Dell Command | Monitor is designed for Dell Enterprise Client systems, Dell IoT Gateway systems, as well as for Dell Embedded PCs.
With Dell Command | Monitor, system administrators can remotely manage assets, monitor system health, and inventory deployed systems in an enterprise.
NOTE: Dell Command | Monitor was formerly Dell OpenManage Client Instrumentation (OMCI). After the OMCI version 8.2.1, OMCI is rebranded as Dell Command | Monitor.
Dell Command | Monitor interfaces with leading enterprise management consoles that support industry standards. This approach helps to ensure that Dell systems can be managed by a broad array of existing enterprise management tools. It also interfaces with the Dell Integration Suite for System Center 2012, Dell KACE K1000 Management Appliance, Dell OpenManage Essentials and our Client Management Pack for System Center Operations Manager (SCOM). Finally, tight integration with Windows Management Instrumentation (WMI) allows customers to take advantage of the rich scripting capabilities for collecting information and customizing system settings. This product is provided at no additional charge to Dell customers.
The latest version of Dell Command | Monitor is v9.3.
Downloads
-
Dell Command Monitor 9.3 for Linux
- Ubuntu Desktop 16.04 64-bit (Released - 08/03/2017)
- RHEL 7.0 64-bit (Released - 08/03/2017)
- RHEL 6.0 64-bit (Released - 08/03/2017)
(Please visit the site to view this video)
(Please visit the site to view this video)
Dell Command | Monitor Quick Links
Enhancements included in the latest release
New Bios Settings introduced in DCIM_BIOSEnumeration Class:
MAC Address Pass Through
AMD Turbo Core Technology
AMD Simultaneous Multithreading Technology
AMD-V Technology
AMD-Vi Technology
Rear USB 3.0 Ports
AMD CPU Core Configuration
Front USB Port Collection
Early Beep
Early Display
Early Keyboard Backlight
Mini SAS 0
Mini SAS 1
Mini SAS 2
Mini SAS 3
VMD technology
Rugged Desk Dock NIC PXE
Computrace
Serial ATA Drive 8
PCIe LinkSpeed
Allow BIOS Downgrade
Limit system memory to less than 1 TB
Tablet Button Illumination
Trusted Platform Module Clear
Installing Dell Command | Monitor
Installing Dell Command | Monitor manually is pretty simple. Just download the latest version (links above) and install with administrative rights.
To perform an unattended installation to be used with your favorite software distribution tool, perform the following steps:
- Download the latest version of Dell Command | Monitor (links above).
- Launch the executable with the following parameters:
Systems-Management_Application_240JD_WN32_9.2.0.135_A00-00.EXE /s
Previous Releases
Download Dell Command | Monitor v9.1 for Windows 32-bit (released 07/29/2015)
Download Dell Command | Monitor v9.1 for Windows 64-bit (released 07/29/2015)
Dell Command | Monitor v9.1 Documentation
Sample Scripts
↧
Dell Client Command Suite Webcast
Join our weekly webcast to discuss the Dell Client Command Suite and other systems management topics of interest to Dell customers.
When: Thursdays at 10am US Central Time (see schedule below for details) Download a calendar invite (.ics) here
Where: http://delltechcenter.adobeconnect.com/command/
Upcoming Webcast Topics
| Date | Topic |
| August 31st, 2017 | Dell Updates with SCUP 2017 Preview |
Previously Recorded Webcasts
↧
Dell Command | Power Manager
Dell Command | Power Manager replaces Dell Power Manager and is a part of the Dell Client Command Suite. It allows end users to maximize their battery life by configuring how the battery should be maintained based on their personal preferences. IT Admins can enforce specific settings or limit features that are available in Dell Command | Power Manager through the included Group Policy snap-in.
Download Dell Command | Power Manager 2.2.1 (released August 2017)
Enhancements
- Fixed an incorrect installation setting
- Added indication for Non-Dell battery
- Added USB type-C alerts
- Updated Group Policy Templates
↧
↧
Driver Pack Release Schedule
Below is the tentative schedule for Dell Driver Packs to be released. The new release date for monthly updates is the second Tuesday.
Note: Driver Packs will only be updated if new drivers are available. Cabs are maintained for Current and 2 previous generations of systems.
| Release Month | Jun-2017 | Jul-2017 | Aug-2017 | Sep-2017 | Oct-2017 | Nov-2017 | ||
| Generation | LOB | Model | ||||||
| N-2 | Precision | T5810 | 7, 10 | |||||
| N-2 | Precision | T7810 | 7, 10 | |||||
| N-2 | Precision | T7910 | 7, 10 | |||||
| N-2 | Precision | R7910 | 7, 10 | |||||
| N-2 | Latitude | E5250 | 7, 10 | |||||
| N-2 | Latitude | E5450 | 7, 10 | |||||
| N-2 | Latitude | E5550 | 7, 10 | |||||
| N-2 | Latitude | E7250 | 7, 10 | |||||
| N-2 | Latitude | E7450 | 7, 10 | |||||
| N-2 | Latitude | 3450 | 7, 10 | |||||
| N-2 | Latitude | 3550 | 7, 10 | |||||
| N-2 | Latitude | 5404 | 7, 10 | |||||
| N-2 | Tablet | 7140 | 10 | |||||
| N-2 | Latitude | 7350 | 10 | |||||
| N-2 | XPS | 9343 | 7, 10 | |||||
| N-2 | Latitude | 3150 | 7, 10 | |||||
| N-2 | Latitude | 3160 | 7, 10 | |||||
| N-2 | Latitude | 7202 | 7, 10 | |||||
| N-1 | Latitude | E7270 | 7, 10 | 7, 10 | ||||
| N-1 | Latitude | E7470 | 7, 10 | 7, 10 | ||||
| N-1 | Latitude | E5270 | 7, 10 | 7, 10 | ||||
| N-1 | Latitude | E5470 | 7, 10 | 7, 10 | ||||
| N-1 | Latitude | E5570 | 7, 10 | 7, 10 | ||||
| N-1 | Latitude | 3460 | 7, 10 | 7, 10 | ||||
| N-1 | Latitude | 3560 | 7, 10 | 7, 10 | ||||
| N-1 | Latitude | 3470 | 7, 10 | 7, 10 | ||||
| N-1 | Latitude | 3570 | 7, 10 | 7, 10 | ||||
| N-1 | Latitude | 3350 | 7, 10 | 7, 10 | ||||
| N-1 | OptiPlex | 7040 | 7, 10 | 7, 10 | ||||
| N-1 | OptiPlex | 5040 | 7, 10 | 7, 10 | ||||
| N-1 | OptiPlex | 3040 | 7, 10 | 7, 10 | ||||
| N-1 | OptiPlex | 7440 AIO | 7, 10 | 7, 10 | ||||
| N-1 | OptiPlex | 3240 AIO | 7, 10 | 7, 10 | ||||
| N-1 | Precision | 7510 | 7, 10 | 7, 10 | ||||
| N-1 | Precision | 7710 | 7, 10 | 7, 10 | ||||
| N-1 | Precision | 3510 | 7, 10 | 7, 10 | ||||
| N-1 | Precision | 3620 | 7, 10 | 7, 10 | ||||
| N-1 | Precision | 3420 | 7, 10 | 7, 10 | ||||
| N-1 | Precision | 5510 | 7, 10 | 7, 10 | ||||
| N-1 | Tablet | 5855 | 10 | 10 | ||||
| N-1 | Tablet | 5175 | 10 | 10 | ||||
| N-1 | Tablet | 5179 | 10 | 10 | ||||
| N-1 | Latitude | 7275 | 10 | 10 | ||||
| N-1 | Tablet | 5056 | 10 | 10 | ||||
| N-1 | XPS | XPS 13 9350 | 7, 10 | 7, 10 | ||||
| N-1 | XPS | 9250 | 10 | 10 | ||||
| N-1 | XPS | 9550 | 10 | 10 | ||||
| N-1 | Latitude | 7370 | 7, 10 | 7, 10 | ||||
| N-1 | Latitude | 7214 | 7, 8.1, 10 | 7, 8.1, 10 | ||||
| N-1 | Latitude | 7414 | 7, 8.1, 10 | 7, 8.1, 10 | ||||
| N-1 | Latitude | 5414 | 7, 8.1, 10 | 7, 8.1, 10 | ||||
| N-1 | IoT | PC 3000 | 7, 10 | 7, 10 | ||||
| N-1 | IoT | PC 5000 | 7, 10 | 7, 10 | ||||
| N-1 | OptiPlex | 3046 | 7, 10 | 7, 10 | ||||
| N-1 | Latitude | 3379 | ||||||
| N-1 | Latitude | 7380 | ||||||
| N-1 | Precision | T5820 | ||||||
| N-1 | Precision | T7820 | ||||||
| N-1 | Precision | T7920 | ||||||
| N-1 | Precision | R7920 | ||||||
| Current | XPS | 9360 | 10 | 10 | 10 | |||
| Current | XPS | 9365 | 10 | 10 | 10 | |||
| Current | XPS | 9560 | 10 | 10 | 10 | |||
| Current | Precision | 5520 | 10 | 10 | 10 | |||
| Current | Latitude | 5280 | 10 | 10 | 10 | |||
| Current | Latitude | 5480 | 7, 8.1 | 7, 8.1, 10 | 7, 8.1, 10 | |||
| Current | Latitude | 5580 | 7, 8.1 | 7, 8.1, 10 | 7, 8.1, 10 | |||
| Current | Precision | 3520 | 7, 8.1 | 7, 8.1, 10 | 7, 8.1, 10 | |||
| Current | Latitude | 7280 | 7, 8.1 | 7, 8.1, 10 | 7, 8.1, 10 | |||
| Current | Latitude | 7480 | 7, 8.1 | 7, 8.1, 10 | 7, 8.1, 10 | |||
| Current | Precision | 7520 | 7, 8.1 | 7, 8.1, 10 | 7, 8.1, 10 | |||
| Current | Precision | 7720 | 7, 8.1 | 7, 8.1, 10 | 7, 8.1, 10 | |||
| Current | OptiPlex | 5050 | 7, 8.1, 10 | 7, 8.1, 10 | 7, 8.1, 10 | |||
| Current | OptiPlex | 3050 | 7, 8.1, 10 | 7, 8.1, 10 | 7, 8.1, 10 | |||
| Current | OptiPlex | 7050 | 7, 8.1, 10 | 7, 8.1, 10 | 7, 8.1, 10 | |||
| Current | OptiPlex | 5250 AIO | 7, 8.1, 10 | 7, 8.1, 10 | 7, 8.1, 10 | |||
| Current | OptiPlex | 3050 AIO | 7, 8.1, 10 | 7, 8.1, 10 | 7, 8.1, 10 | |||
| Current | OptiPlex | 7450 AIO | 7, 8.1, 10 | 7, 8.1, 10 | 7, 8.1, 10 | |||
| Current | Latitude | 3380 | 7, 8.1, 10 | 7, 8.1, 10 | 7, 8.1, 10 | |||
| Current | Latitude | 3189 | 10 | 10 | 10 | |||
| Current | Latitude | 3180 | 10 | 10 | 10 | |||
| Current | Latitude | 5285 | 10 | 10 | 10 | |||
| Current | Latitude | 3480 | 7, 8.1, 10 | 7, 8.1, 10 | 7, 8.1, 10 | |||
| Current | Latitude | 3580 | 7, 8.1, 10 | 7, 8.1, 10 | 7, 8.1, 10 | |||
| Current | Latitude | 5289 | 10 | 10 | 10 | |||
| Current | Precision | 5720 AIO | 7, 10 | 7, 10 | 7, 10 | |||
| Current | Latitude | 7285 | 10 | 10 | 10 | |||
↧
Latitude 7212 Windows 7 Driver Pack
Current Driver CAB Summary | ||||||||||||||
| ||||||||||||||
This is the initial Driver Pack release. A delta report will be available with the next release | ||||||||||||||
↧
Latitude 7212 Windows 10 Driver Pack
Current Driver CAB Summary | ||||||||||||||
| ||||||||||||||
This is the initial Driver Pack release. A delta report will be available with the next release | ||||||||||||||
↧
Latitude 7380 Windows 7 Driver Pack
Current Driver CAB Summary | ||||||||||||||
| ||||||||||||||
This is the initial Driver Pack release. A delta report will be available with the next release | ||||||||||||||
↧
↧
Latitude 7380 Windows 8.1 Driver Pack
Current Driver CAB Summary | ||||||||||||||
| ||||||||||||||
This is the initial Driver Pack release. A delta report will be available with the next release | ||||||||||||||
↧
Latitude 7380 Windows 10 Driver Pack
Current Driver CAB Summary | ||||||||||||||
| ||||||||||||||
This is the initial Driver Pack release. A delta report will be available with the next release | ||||||||||||||
↧
Latitude 7389 Windows 10 Driver Pack
Current Driver CAB Summary | ||||||||||||||
| ||||||||||||||
This is the initial Driver Pack release. A delta report will be available with the next release | ||||||||||||||
↧
Dell Command | Deploy - Driver Packs for Enterprise Client OS Deployment
Below you will find Driver CABs for Dell Enterprise class systems (Latitude, Optiplex, Precision) to be used to simplify OS deployments on those systems with deployment tools like Microsoft System Center Configuration Manager (ConfigMgr/SCCM) or Microsoft Deployment Toolkit (MDT).
System CABs for Venue, XPS, Latitude, Optiplex, and Precision Workstations - are designed for deployment to a single model and are developed and supported by Dell
WinPE CABs are designed to provide required drivers for WinPE to boot a Dell Latitude, Optiplex, or Precision Workstation for the purpose of OS Deployment.
Family Driver Packs are designed for deployment to multiple models and are developed and supported by the Dell Configuration Services.
The links below will provide additional details on the CABs and a link to download.
If you are new to Dell Driver CABs, please check out the .CAB File Documentation and Walk-Throughs or the Win 7 Deployment video
You can also access the System CABs from http://support.dell.com -- Select Drivers & Downloads, and enter the system model. You will find the supported driver .cab file in the "Systems Management" section under "Driver Pack".
Automate your driver management by leveraging the Driver Pack Catalog.
Driver CAB's are grouped by product family and are listed with the most recent products at the top.
The Driver CABs are updated based on a release schedule which updates newer systems more frequently. New CAB download pages will include Delta Reports on what has changed in the CAB.
If you still have questions, check out the Deployment FAQ page or our discussion forums.
NOTE: Windows 8 CABs for older systems will be reviewed periodically to see if there are new drivers required. It is currently expected that Windows 8 will contain the drivers required for those systems.
WinPE - CAB Availability (follow the links for CAB details and to download)
| WinPE version | Current CAB |
| WinPE 10 | A04 (01/10/2017) |
| WinPE 5.x | A09 (02/14/2017) |
| WinPE 4.x | A06 (06/02/2015) |
| WinPE 3.x | A21 (02/14/2017) |
| WinPE 2.x | A00 (05/26/2009) |
XPS Systems - CAB Availability (follow the links for CAB details and to download)
| System | Windows 10 System CAB | Windows 8.1 System CAB | Windows 8 System CAB | Windows 7 System CAB |
| XPS 11 (9P33) | A00 (08/19/2015) | A00 (11/14/2013) | ||
| XPS 12 (9250) | A09 (08/08/2017) | |||
| XPS 12 (9Q33) | A00 (10/23/2013) | A00 (07/19/2013) | ||
| XPS 12 (L221x and 9Q23) | A01 (03/38/2016) | A01 (12/10/2012) | ||
| XPS 13 (9365) | A03 (07/11/2017) | |||
| XPS 13 (9360) | A04 (07/11/2017) | |||
| XPS 13 (9350) | A08 (07/11/2017) | A04 (07/26/2016) | A07 (07/11/2017) | |
| XPS 13 (9343) | A04 (05/09/2017) | A04 (02/09/2016) | A05 (11/08/2016) | |
| XPS 13 (9333) | A01 (03/08/2016) | A00 (11/22/2013) | A00 (11/22/2013) | |
| XPS 13 (L321x and L322x) | A01 (03/08/2016) | A02 (07/31/2013) | A04 (08/29/2013) | |
| XPS 14 (L421x) | A01 (03/08/2016) | A01 (02/25/2013) | A01 (02/25/2013) | |
| XPS 15 (9560) | A03 (07/11/2017) | |||
| XPS 15 (9550) | A10 (08/08/2017) | A06 (09/13/2016) | ||
| XPS 15 (9530) | A01 (01/12/2016) | A00 (10/23/2013) | ||
| XPS 15 (L521x) | A01 (03/08/2016) | A01 (02/25/2013) | A03 (02/25/2013) |
Internet Of Things - CAB Availability (follow the links for CAB details and to download)
| System | Windows 10 System CAB | Windows 7 System CAB |
| Embedded Box PC 3000 | A00 (02/14/2017) | A04 (07/11/2017) |
| Embedded Box PC 5000 | A01 (07/11/2017) | A04 (07/11/2017) |
Venue Systems - CAB Availability (follow the links for CAB details and to download)
NOTE: Detail on deploying Venue tablets can be found HERE
| System | Windows 10 System CAB | Windows 8.1 System CAB |
| Venue 11 Pro (7140) | A05 (04/11/2017) | A03 (01/12/2016) |
| Venue 11 Pro (7130 MS/ 7130 vPro/7139 vPro) | A03 (11/08/2016) | A07 (02/09/2016) |
| Venue 11 Pro (5130) | A02 (06/14/2016) | A08 (02/09/2016) |
| Venue 10 Pro (5056) | A08 (08/08/2017) | A03 (06/14/2016) |
| Venue 8 Pro (5855) | A08 (08/08/2017) | A03 (06/14/2016) |
| Venue 8 Pro (5830) | A02 (06/14/2016) | A07 (02/09/2016) |
Latitude Systems - CAB Availability (follow the links for CAB details and to download)
Optiplex Systems - CAB Availability (follow the links for CAB details and to download)
Precision Systems - CAB Availability (follow the links for CAB details and to download)
Family Driver Pack Availability.
Notice: The Dell Family Packs have moved here.
↧
↧
Dell Command | Deploy - FAQ
0) What is this FAQ about?
This FAQ is primarily about DELL COMMAND DEPLOY DRIVER PACK. It talks about issues a user might see with the driver packs and the reason why she/he would see that.
1) Why is the driver cab not having any Bluetooth drivers although the device supports it?
Bluetooth radio support comes with various devices and you would primarily see it with the WIFI cards. The Bluetooth driver isn’t included because they aren’t compatible with the INF-centric installation that is used by SCCM/MDT etc. Our driver cabs are primarily provided for automated deployment through software packages like SCCM/MDT …
2) I get a yellow bang on a Bluetooth device when I use this driver cab. What should I do?
Bluetooth drivers aren’t included in the driver cab for reasons said above. It is expected as of this writing that, with the currently available Operating Systems provided by Microsoft, an inbox driver (Generic Bluetooth Radio) will be installed for Bluetooth. There are inbox drivers for various Bluetooth profiles. However since you are seeing a yellow bang, you can look up for a Bluetooth driver package from support.dell.com. This package (DUP package) has to be installed manually. It shouldn’t be used by extracting the contents and then using the extracted contents (perhaps as part of a compressed file) for remote deployment.
3) Why do I not find “Thunderbolt” driver in the driver cab?
Thunderbolt drivers have similar issues as seen in Bluetooth drivers. They can’t be used in the SCCM environment or installed correctly using just the device manager. We are working with the IHV to fix this issue.
4) Why did my deployment of Windows 7 fails with the error message, "The computer restarted unexpectedly or encountered an unexpected error. Windows installation cannot proceed. To install Windows, click "OK" to restart the computer, and then restart the installation." OR I have components that didn't install drivers that are in my driver package?
example error in setuperr.log (from %windir%\Panther) shows the following failure information:
2013-08-29 13:09:40, Error CBS Startup: Failed to process advanced operation queue, startupPhase: 0. Primitives are still pending. [HRESULT = 0x80004005 - E_FAIL]
2013-08-29 13:09:40, Error CBS Startup: POQ has not been processed yet, aborting startup processing. Startup processing will be attempted again. [HRESULT = 0x80004004 - E_ABORT]
2013-08-29 13:09:40, Error [0x030149] CMI Callback_CBS_Do_OnlineInstall:Calling startup processing failed 0x80004004
2013-08-29 13:09:40, Error [0x030153] CMI Callback_CMI_ConfigInstall: CBS startup processing re-run failed.
A: You need the updated Kernel Mode Driver Framework (KMDF) 1.11 included in your base image
Reasons for failure:
- Windows 7 Operating system comes with KMDF 1.9 (Kernel Mode driver framework) as part of image. Any driver release which is built with newer version of KMDF requires reboot of system during the installation, this reboot is unexpected during OS Setup.
- If the Win7 image used contains any security update or patch affecting the KMDF components is used along with driver (which is built on newer version of KMDF) then deployment would fail. Example: KB2808735
Resolution:
Download and inject package (2685811) as part of the image preemptively. So that same image can be used for OSD. This will avoid the unexpected reboot during OSD.
Scope/Affected Drivers:
This issue is applicable to Window 7 OS:
- 1. If the Win7 cab includes any driver consisting of wdfcoinstaller01011.dll (initiates KMDF upgrade to 1.11).
- 2. If the image does not include any security updates or patches affecting KMDF components (example KB2808735) then OS deployment might not fail, but it will prompt for reboot when User logins for first time.
*List of devices Affected:
(i) ST Microelectronics Free Fall Data Protection (ii) Intel Smart Connect Technology
(iii) Intel Management Engine Interface (iv) Dell Touchpad
(v) Intel Dual Band Wireless AC7260 Bluetooth
5) I am getting a pop-up during the final stages of OS installation (via SCCM/MDT etc.). The error says the service couldn't start because msvcr100.dll is missing. However when I click "OK" it continues the installation. What has failed during installation?
A: msvcr100.dll is a run-time library version. This popup would appear if the OS being deployed doesn't have this runtime library. It is possible that one of the drivers being deployed relies on this DLL file. You can refer below links to understand the issue and get the fixes.
https://msdn.microsoft.com/en-us/library/ms235299%28v=vs.100%29.aspx (Talks about the redistributable versions that you may have to manually install)
At the time of this writing, the library can be downloaded using below links...
http://www.microsoft.com/en-in/download/details.aspx?id=5555
http://www.microsoft.com/en-in/download/details.aspx?id=13523
After installing the above, the missing driver can be installed by extracting it from the .cab file and pointing to the INF file. (with device manager)
6) I have installed Microsoft Windows 7 operating system. In the device manager I can see a yellow bang and the device id is shown as ACPI\MSFT0101. What driver am I missing?
A: With the introduction of TPM 2.0 Microsoft has released a hotfix, to support the new TPM modules for, Microsoft Windows 7 OS variants. The ACPI recognizes this device as ACPI\MSFT0101. The KB article and hotfix is available as of this writing at the below link
http://support.microsoft.com/en-us/kb/2920188
7) How to get native NVMe support for Windows 7?
A: If your platform supports NVMe for PCIe and the operating system is Microsoft Windows 7, it will need a hotfix to provide native support for NVMe for PCIe.
Below URL provides the advisory...
https://support.microsoft.com/en-us/kb/2990941
However installing this KB can also present a BSOD. Microsoft has provided a fix for this issue. Please refer below URL for the hotfix, for the STOP error (if you might see one) after installing KB2990941
https://support.microsoft.com/en-us/kb/3087873
8) Some Win10 drivers don't import correctly into SCCM 2012 SP2 or SCCM 2012 R2 SP1?
A: There is known issue for Windows 10 Driver Import in SCCM 2012 SP2\R2SP1. To resolve this, you must apply the KB: KB3074857
9) Is there anything special I need to do to prepare for Windows 10?
A: Yes, to properly prepare your systems for Windows 10, update the platform BIOS with latest update. The system components below are not supported with Windows 10, updating to latest BIOS will not show these devices in device manager
- Intel(R) Rapid Start Technology Application
- Intel(R) Smart Connect Technology Application
- For Windows 10 deployment using SCCM, follow the blog: System Center Configuration Manager Team Blog.
10) Some drivers are missing from the Win10 cab. Where do I get them?
A: Some drivers are only available through Windows Update and some are yet to be released and will be included in a future cab.
11) I am using Microsoft Windows 7 x64 operating system. One of the driver updates gets installed but there is a yellow exclamation mark seen on device manager. In another case the same driver is not installed at all and the logs complain a digital signature issue. Is this possible that driver cabs contain drivers that are not digitally signed?
A: Drivers are tested for being digitally signed well before they are made available to dell.com/support. They again go under rigorous testing before they are included in the driver cab. There are so many reasons why the system would complain that drivers are not signed. Ensure that the operating system’s certificate enrollment policy is not switched off. If you are connected to a domain then the enrollment pulls certificate information from the domain controller if configured so. There are this and many other settings to ensure the system "understands" the digital signature.
There is a new scenario that is being seen recently as Microsoft has released a security update for windows 7 x64 systems around March. Basically Windows 7 systems use SHA-1 as hash algorithm for digital signatures. This hashing algorithm is now considered less secure and hence they have provided a security update for allowing Windows 7 x64 systems to use SHA-2 that is available by default in later systems (Windows 8 and above). Some Hardware Vendors have considered changing the digital signature algorithm used for their drivers, where for Windows 7 drivers they are using SHA-2 as default hashing algorithm. Hence if you try to install these drivers in a Windows 7 x64 system they will fail.
Please check the problem system to see if KB3033929 has been pushed. If not, this might fix the issue. Relevant links are below...
https://www.microsoft.com/en-us/download/details.aspx?id=46148
https://support.microsoft.com/en-us/kb/3033929
12) Why is there an exclamation mark present on the device manager, for Intel 8260 Bluetooth device , after installation?
A: The latest versions of Bluetooth drivers provided for Intel 8260 Bluetooth modules may present an exclamation mark on device manager after install. This is because the driver tries to update the firmware and while doing so it looks for some related files in C:\ drive specifically. We are working with Intel on the bug-fix and we expect to bundle the fix in our upcoming driver cabs. Meanwhile, the work around is to force deployment of the Operating system to C:\ drive.
SCCM users can refer the below link to force installation of the Operating System to C:\ drive.
blogs.technet.com/b/configurationmgr/archive/2014/04/28/how-to-ensure-that-windows-installs-on-c-during-a-system-center-2012-configuration-manager-osd-task-sequence.aspx
For others who already have an OS deployed to a drive other than C:\ the below command could help
subst c: <actual drive:>
e.g.) subst c: d:\
Above command would make all references made to c:\program files\Intel, in an application, get redirected to d:\program files\Intel
13) Why is the Intel Phi co-processor driver not included in T7610/R7610/T7910/R7910 driver cabs?
A: Advanced workstations - T7610/R7610/T7910/R7910 provide support for Intel Phi co-processor card. However we do not provide factory Install or driver cab support for these drivers. Drivers won't be included in driver cabs for Windows 7, Windows 8, Windows 8.1 and Windows 10 operating systems. Inclusion of the drivers have presented BSODs in the past. Also to actually put this device to use one will have to install the entire MPSS software stack provide by Intel. MPSS should also install the necessary drivers required for this device to function. This driver is also available from dell.com/support for the respective products.
https://software.intel.com/en-us/articles/intel-manycore-platform-software-stack-mpss
14) My driver installation fails. The error in setup log suggests it has timed out. What would be the cause?
A. There are two cases of timeout one that is due to delayed activity of the co-installer supplied with the driver and second due to driver signature checking related activity. For the former, we would usually provide you with a better solution in the subsequent release of our cab. For the latter, Microsoft has already documented this fact. Please refer to below KB article.
15) Why is the driver cab missing Intel USB 3.0 switch component in the USB 3.0 driver?
Answer: Windows 7 USB driver stack is built to support USB 2.0 only. However USB 3.0 option was provided to vendors. Hence the entire USB 3.0 stack including support for innate USB 2.0 stack is provided by the vendor of the device through the driver they provide. Therefore for Windows 7 it was required that a switch be made from USB 2.0 to USB 3.0 as there was no direct support for USB 3.0. This is achieved by the iusbhcs.sys component provided in the Intel driver package. However it is also a requirement that this driver be installed only via “setup.exe” application or a similar driver installation program. This is against the INF-installation method that is supported by SCCM/MDT or even DPInst and such utilities. We have observed BSODs in case the “HCS” was included and installed via the INF file. Hence we do not pack this component. To achieve full USB 3.0 functionality one would still want to run the setup.exe application that DELL provides via the drivers available in support.dell.com (of the format Self-extractable installer executable – DUP).
16. Why does MDT have issues importing Driver Packs?
Answer:
Problem:
Unable to import Broadcom Control vault driver to MDT. While importing – user gets a “Length cannot be less than zero; Parameter name: length” error
Description:
The latest Control Vault drivers are packaged with both driver and firmware together. And there is a file named “current_version” in the firmware folder without a file extension. MDT does not recognize files without extensions hence this driver import fails.
Solution:
Broadcom is planning a driver update for addressing this issue. Meanwhile Control Vault applications can be installed as part of Task sequence.
17. Why Dell Command Integration Suit is failing to import some INF files from Display Link Dock Driver?
Answer:
It is a known issue with Dell Command Integration Suit which will be fixed in next release. As a work around, import the failed drivers manually to Configuration Manger Console and add to the Driver Packages. Kindly refer below URL to import Drivers manually.
https://docs.microsoft.com/en-us/sccm/osd/get-started/manage-drivers
18. Why ‘Apply Driver Package’ task is failing with Windows7 OS while installing one of the Drivers with ADK 1607?
Answer:
The issue is currently under investigation by Microsoft. The problem seems to be caused by DISM trying to load the registry of the offline OS when it has not finishing unloading the registry from a previous driver install registry load. This issue primarily happens on faster PCs with SSD drives, mainly SSD NVME drives, but can occur on any PC. For workarounds please refer to below link.
↧
Configure Keyboard Backlight Timeout
Hello, I want to configure Keyboard Backlight Timeout on Dell Latitude E6440. I'm using preinstalled Linux OS Dell Ubuntu 12.04.2.
I found this post http://en.community.dell.com/techcenter/enterprise-client/f/4448/p/19415396/19975858.aspx#19975858 from Warren Byle.
He wrote how to change Keyboard Backlight illumination level with tool CCTK. I downloaded CCTK for Red Hat Linux and looks like it working fine on Ubuntu too. With that --token commands I'm able to change Keyboard Backlight level which is good.
But I still do not know how to change Keyboard Backlight Timeout. Backlight is still turned off after 10 seconds. Is there some special --token for configuring this timeout?
According to other posts it looks like configring timeout to 5 minutes could be possible, because there are Windows applications which could do that (e.g Dell System Manager Application under Control Point)
http://en.community.dell.com/support-forums/laptop/f/3518/t/19524424.aspx
http://www.shadowsplace.net/376/hardware/dell-laptop-keyboard-backlighting-timeout/
http://forum.notebookreview.com/dell-latitude-vostro-precision/739154-e6440-owners-thread-5.html#post9698302
↧
Dell Client Command Suite Webcast
Join our weekly webcast to discuss the Dell Client Command Suite and other systems management topics of interest to Dell customers.
When: Thursdays at 10am US Central Time (see schedule below for details) Download a calendar invite (.ics) here
Where: http://delltechcenter.adobeconnect.com/command/
Upcoming Webcast Topics
| Date | Topic |
| Sept. 14th, 2017 | Sorry, No Webcast today! Please view a previously recorded webcast below. |
Previously Recorded Webcasts
↧