Wait… what? What makes DCU incompatible with Bitlocker?
From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Katherine M. Moss Sent: Tuesday, August 1, 2017 7:45 AM To: mdtosd@lists.myitforum.com Subject: RE: [MDT-OSD] RE: Missing Dell Drivers Good to know the caution about Bitlocker. I have a laptop with DCU on it … was thinking of putting Bitlocker back on; appears I can’t do that. From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of David Landry Sent: Tuesday, August 01, 2017 9:48 AM To: mdtosd@lists.myitforum.com<mailto:mdtosd@lists.myitforum.com> Subject: RE: [MDT-OSD] RE: Missing Dell Drivers Hi All, Thanks to all for sharing their solutions to the problem with Dells drivers. They all should work just fine. I didn’t mention this, but the problem I am facing is not just at my site … but I also need to find a solution that will fit some 50+ MDT servers on a global scale. Drivers has always been a thorn in my side as it seems Dell does in fact change hardware on their business class systems on occasion. Then I have to go out and download the latest CAB files to get the missing driver(s). When I spoke to their Tier 3 support, he recommended running Dell Command Update as an application which will automatically scan the system, identify the model and the hardware in it, then go out and grab the latest CAB file and install the missing drivers. Because DCU has this capability, I am thinking of only supporting LAN and storage drivers in MDT and then use DCU to finish the driver installs. The biggest problem with that is, I need to uninstall it after it completes during the MDT process. Leaving DCU on a system, specifically a laptop will be problematic when we start bitlocking laptops. I have only been testing in North America for about a week, so if this works in Asia and Europe it will be one solution to fit all. If this doesn’t pan out, then I can fall back to the great ideas you guys have found. FYI: I asked Dell if the DCU will download CAB files from that region or come back to the US for the drivers. The answer was that DCU is the same application globally. It has logic built in to determine the closest source to retrieve the CAB files. If anyone wants / needs information of how to get DCU to work in MDT just let me know. Thanks for sharing guys. Best Regards, Dave Landry From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Stephen Owen Sent: Friday, July 28, 2017 9:51 AM To: mdtosd@lists.myitforum.com<mailto:mdtosd@lists.myitforum.com> Subject: Re: [MDT-OSD] RE: Missing Dell Drivers +1 to Arif's recommendation. I don't import the entire CAB anymore for Dell laptops. Instead, I unzip it and import chipset, audio, storage and LAN, then image and see what else is missing. I only import the missing drivers after that. I'm not sure what's happening with their CAB files but I've seen this issue as well. On Fri, Jul 28, 2017 at 9:24 AM, Usman, Arif <arif.us...@merrillcorp.com<mailto:arif.us...@merrillcorp.com>> wrote: If you extract cab drivers from dell, remove CV folder under Security folder, and import drivers to MDT. Install controlVault as application driver (Dell_CV_SW_Update_x64_7250.exe /S /v/qn).. Thanks From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com>] On Behalf Of Sean Chapman Sent: Friday, July 28, 2017 7:40 AM To: mdtosd@lists.myitforum.com<mailto:mdtosd@lists.myitforum.com>; 'mdtosd@lists.myitforum.com<mailto:mdtosd@lists.myitforum.com>' Subject: [MDT-OSD] RE: Missing Dell Drivers I have 7480s that deploy fine with MDT. I do not use the control vault driver so this would make sense. From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Keith Garner Sent: Thursday, July 27, 2017 10:17 PM To: mdtosd@lists.myitforum.com<mailto:mdtosd@lists.myitforum.com>; 'mdtosd@lists.myitforum.com<mailto:mdtosd@lists.myitforum.com>' Subject: [MDT-OSD] RE: Missing Dell Drivers TL;DR: MDT LiteTouch can’t import the Dell ControlVault Driver. Details: https://keithga.wordpress.com/2017/07/27/dell-latitude-xx80-drivers-wont-import-into-mdt-litetouch/ I let Dell and MSFT know about my findings. From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of David Landry Sent: Thursday, July 27, 2017 12:54 PM To: 'mdtosd@lists.myitforum.com<mailto:mdtosd@lists.myitforum.com>' Subject: [MDT-OSD] Missing Dell Drivers Hi All, Just curious what everyone / anyone has done with the Dell driver problem they have with the new Latitude XX80 series laptops. I imported their CAB files into MDT and got error. Didn’t know how bad so I imaged a 7280 or 5480 and lots of stuff came up missing. I called Dell and they informed me that they are having problems with drivers not importing into MDT and then everything after that fails to import. Control Vault drivers was the worst. But each model is different. They recommended using Dell Command Update. So I got that into MDT and it runs first.. but I am still missing touchpad drivers for the 5480, and who knows what else I haven’t discovered yet. They actually pulled all their Windows 7 and Windows 10 drivers off their website a few weeks ago. I thought a server went down … but it wasn’t the server. Has anyone else seen the driver issues at Dell? What is everyone else doing to resolve this? Best Regards, Dave Landry ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The information contained in this communication and all accompanying documents from Coilcraft may be confidential and/or legally privileged, and is intended only for the use of the recipient(s) named above. If you are not the intended recipient you are hereby notified that any review, disclosure, copying, distribution or the taking of any action in reliance on the contents of this transmitted information is strictly prohibited. If you have received this communication in error, please return it to the sender immediately and destroy the original message or accompanying materials and any copy thereof. If you have any questions concerning this message, please contact the sender.