Current Driver CAB Summary | ||||||||||||||
| ||||||||||||||
This is the initial Driver Pack release. A delta report will be available with the next release | ||||||||||||||
↧
Optiplex 7450 AIO Windows 10 Driver Pack
↧
Latitude 3380 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 3380 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 3380 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 3189 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 3180 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
Note: There is known issue for Windows 10 Driver Import in SCCM 2012 SP2\R2SP1. To resolve this, you must apply CU1 KB: KB3074857
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) | A07 (02/14/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) | A01 (02-14-2017) | |||
| XPS 13 (9360) | A01 (01/10/2017) | |||
| XPS 13 (9350) | A06 (01/10/2017) | A04 (07/26/2016) | A05 (01/10/2017) | |
| XPS 13 (9343) | A03 (11/08/2016) | 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) | A00 (01-17-2017) | |||
| XPS 15 (9550) | A07 (01/10/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 | A02 (10/11/2016) | |
| Embedded Box PC 5000 | A03 (02/14/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) | A04 (10/11/2016) | 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) | A05 (10/11/2016) | A03 (06/14/2016) |
| Venue 8 Pro (5855) | A06 (02/14/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.
↧
Embedded Box PC 3000 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 | ||||||||||||||
↧
Embedded Box PC 5000 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 | Update
Dell Command | Update replaces DCSU and is a part of the Dell Client Command Suite. It provides a 2-click solution for getting all the latest drivers, firmware, and BIOS updates for your Latitude, Optiplex, and Precision systems.
New features in version 2.3 include:
- Support for ISV drivers on Precision systems.
New features in version 2.2 include:
- Support for Dell Docking Solution
New features in version 2.1.1 include:
- Advanced Driver Restore feature updated to support the high performance commercial systems.
- Self-Update feature of Dell Command | Update changed to accommodate version 2.1.
New features in version 2.1 include:
- Support for Windows 10 operating system
- Ability to suspend Windows BitLocker for applicable updates
- Ability to provide feedback from application GUI.
- Support for additional languages: Chinese (Taiwan), Chinese (Traditional, Hong Kong SAR), Dutch (Netherlands), Italian
DownloadDell Command | Update 2.3 (released February 13, 2017)
↧
Latitude 7370 Windows 10 Driver Pack
Current Driver CAB Summary | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Delta Report for Previous Driver CAB v/s Current Driver CAB | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
(XVYFW-A06-11/07/2016) v/s (P8PX1-A07-01/10/2017) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
----Comparison Report---- | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
↧
64-bit BIOS Installation Utility
Our utility to allow for BIOS upgrades in a native 64-bit environment (WinPE) is now available.
Download it HERE
Install Instructions:
- Download the BIOS executable for the specific system that you are going to update and place it in a directory of your choice.
- Download Flash64W.exe and place it in the same directory as the BIOS executable.
- Open a Windows command prompt and go to the directory above
- Run Flash64W.exe /b=BIOSExecutableName.exe
- Ex: Flash64W.exe /b=XPS_9350_112.exe
NOTE: This is for Client systems only.
Please leave questions in the comment area below.
↧
Dell Precision Optimizer 3.0 Guide for IT Administrators
IT Administrator guide for Dell Precision Optimizer 3.0
↧
↧
Remote configuration of Dell Precision Optimizer with Microsoft Configuration Manager (SCCM)
Many customers want to pre-configure Dell Precision Optimizer with a management platform like Microsoft Configuration Manager (SCCM). Below is documentation and a video on how to accomplish this. The specific profiles that are available are details below as well.
Download the IT Administrator Guide -> Dell Precision Optimizer 3.0 - A Guide for IT Administrators
Demo video of DPO management through SCCM - http://delltechcenter.adobeconnect.com/p2kktfuobsf/
Profile Name | GUID |
| NX by Siemens | {11FD776F-94F3-4471-9CE4-118ECB71DE55} |
| SolidWorks by Dassault Systèmes | {2673B7BA-4FD6-4626-8251-56F0644765BB} |
| Illustrator by Adobe | {268C0BF4-BD15-48F5-96EE-FF790B376211} |
| Petrel by Schlumberger | {2788CCDF-B747-4B3C-8D67-053BFBFD8993} |
| Microstation by Bentley | {2BF4DDF8-EC6D-409F-B116-14F69CC3FD04} |
| After Effects CS / CC by Adobe | {2F066600-FA52-4F57-890D-2621D39B0BE9} |
| MotionBuilder by Autodesk | {37538CED-7A84-4DC8-ACBC-F1649C3D3E9C} |
| Premiere Pro CS / CC by Adobe | {385A1859-8397-44CD-B146-51EACD826F8A} |
| CATIA by Dassault Systèmes | {387EA83C-8FCF-46FF-8FD0-45A7DA5623F5} |
| Creo by PTC | {45FD78B6-CB78-4398-A19B-9BE1BE24FC4E} |
| 3dsmax Computational by Autodesk | {6AC89E78-5FDF-420C-AAFA-10A8353DA464} |
| MudBox by Autodesk | {6FF7F7A1-D807-4945-B84A-FB93ADD6B310} |
| AutoCAD by Autodesk | {7E08698E-5DF7-48D9-B975-4BE87A4CD8FB} |
| Fluent by ANSYS | {896F720A-20FA-4741-BEE6-74C7926CB06E} |
| Maya Rendering Model by Autodesk | {96F953C2-7DAF-4A64-8437-C1DE3D3ED950} |
| Revit by Autodesk | {B1BD4D20-7E51-4118-8BD6-0746108E391F} |
| Inventor by Autodesk | {B7F51224-03F0-4059-B3D9-0D9D7588266A} |
| 3dsmax Interactive by Autodesk | {C5721BA4-00A9-46F4-85E1-9F38E3BF5A04} |
| Media Encoder CS / CC by Adobe | {DC6300F3-7219-43B7-AC35-70315C79256C} |
| Photoshop CS / CC by Adobe | {E96256E1-483B-4814-AE66-3B412FBD0BE3} |
| SpeedGrade by Adobe | {ED0EE5E9-5D09-44DD-9A21-0D96D2CD12A0} |
| Media Composer by Avid | {FBFDA47F-3CCC-4C7A-A75D-DA28A561AEC1} |
| Workbench by ANSYS | {FEF69512-7D9A-4BA5-902B-790EC5F94673} |
↧
Latitude 7480 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 - 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.
↧
Dell Command | Update
Dell Command | Update replaces DCSU and is a part of the Dell Client Command Suite. It provides a 2-click solution for getting all the latest drivers, firmware, and BIOS updates for your Latitude, Optiplex, and Precision systems.
New features in version 2.3 include:
- Support for updating Independent Software Vendor (ISV) certified drivers.
- Support for selecting and installing all updates associated with Dell Docking Solution.
- Support for a new CLI return code: 5 to indicate that reboot and scan is required.
New features in version 2.2 include:
- Support for Dell Docking Solution
New features in version 2.1.1 include:
- Advanced Driver Restore feature updated to support the high performance commercial systems.
- Self-Update feature of Dell Command | Update changed to accommodate version 2.1.
New features in version 2.1 include:
- Support for Windows 10 operating system
- Ability to suspend Windows BitLocker for applicable updates
- Ability to provide feedback from application GUI.
- Support for additional languages: Chinese (Taiwan), Chinese (Traditional, Hong Kong SAR), Dutch (Netherlands), Italian
DownloadDell Command | Update 2.3 (released February 13, 2017)
↧
↧
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 |
| March 2nd, 2017 | No Webcast Today - Please view a recording below |
| March 9th, 2017 | Dell Command Suite Overview |
Previously Recorded Webcasts
| Date | Topic (Click the link below to view the recording) |
| February 23rd, 2017 | Open Discussion |
| February 16th, 2017 | Driver Management Strategies |
| February 2nd, 2017 | Dell Client Command Suite Overview |
| January 12th, 2017 | Managing UEFI settings for Windows 10 |
| January 5th, 2017 | Command Suite Overview |
| December 8th, 2016 | OS Deployment Basics |
| December 1st, 2016 | Command Suite Overview |
| November 17th, 2016 | Installation Demo - Part 2 |
| November 10th, 2016 | Installation Demo - SCCM integration |
| November 3rd, 2016 | Command Suite Overview |
| October 27th, 2016 | BIOS Configuration Deep Dive |
| October 20th, 2016 | Command Suite Overview |
| October 13th, 2016 | vPro Discussion |
| September 29th, 2016 | Open Discussion |
| September 22nd, 2016 | Dell Client Command Suite Overview and Demo |
| September 15th, 2016 | Dell Command | Update and Dell Command | Power Manager - Deep Dive |
| September 8th, 2016 | Dell Client Command Suite Demo |
| September 1st, 2016 | Dell Client Command Suite Demo and Discussion |
↧
Dell Command | Integration Suite for System Center
NOTE: We have done preliminary validation on the 1511, 1602, 1606 and 1610 versions of ConfigMgr and with the the exception of our vPro console, it works with the 4.2 version of our integration.
Note on the Warranty Tool: The webservice that the Warranty Tool uses was abruptly retired by the team that was overseeing it, so the warranty tool no longer works.
The Dell Command | Integration Suite for System Center 2012 replaces the Dell Client Integration Pack (DCIP) for Microsoft System Center Configuration Manager and is a part of the Dell Client Command Suite
Features include:
- Dell Command | Monitor Integration
- Dell Command | Configure Integration
- Warranty Integration Tool
- Dell Command | Intel vPro Out of Band Integration
Download the Dell Command | Integration Suite for System Center 2012 4.2 (released May 2016)
Documentation links (Installation Guide, User Guide, Warranty User Guide)
New Features in 4.2
Enhancements to Catalog and Driver Cabs for download and processing
Enhancements to OS and Database permissions
New features in 4.1:
• Support for System Center 2012 R2
• Updated GUIs
• Support for Windows 10 WinPE
• Support for Dell Command | Intel(c) vPro(tm) Out of Band 2.1.0
• Updated Dell Command | WinPE Driver Library Import
• Updated Dell Command | System Driver Library Import
• Support for Dell Command | Deploy Catalog (for WinPE Driver Libraries
and System Driver Libraries)
↧
WinPE 10 Driver Pack
Current Driver CAB Summary | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Delta Report for Previous Driver CAB v/s Current Driver CAB | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
(2K3RC-A03-04/16/2016) v/s (942XJ-A04-01/10/2017) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
----Comparison Report---- | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
↧