12 Posts

942

June 1st, 2020 06:00

Help understanding dell drivers

I'm looking at the Dell drivers for a Latitude 5430. I understand what the separate drivers do, but I don't understand what the Dell Command | Deploy Latitude E5430 Windows 10 Driver Pack, and the Dell Command | Deploy WinPE 10.0 Driver Pack are, and what they're for. Can someone give me some information about how these two driver packs are used?

Thank you.

 

11 Legend

 • 

14K Posts

 • 

79.9K Points

June 1st, 2020 08:00

@acenyc  Unless you're building and deploying custom images because you're provisioning a lot of these systems, you don't need those driver packs.  But if you're curious anyway, the former is all of the drivers required for this system all packaged in "raw INF" format, i.e. not within installers as is often the case for drivers meant to be installed manually by individual users so they can step through a wizard.  The "raw INF" format allows them to be loaded into the database of a system image deployment solution like Microsoft SCCM.  In environments where SCCM is available, you can use it to (among many other things) install your corporate Windows image, which would contain various customizations and applications appropriate to your organization.  During that process, SCCM would check the model of the system the image was being pushed onto and include the necessary drivers for that particular system.  In order to do that, it needs to HAVE those drivers in its database.  The driver pack that Dell offers allows SCCM admins to quickly get an entire driver set for that system.

The WinPE driver pack contains the only the drivers that are necessary to even start the image process, not everything required to actually run full Windows.  WinPE stands for Windows Preinstallation Environment.  It is essentially a stripped down version of Windows containing just enough functionality to boot a system and install real Windows, as well as perform some recovery tasks.  Windows Setup actually runs on WinPE.  So the WinPE driver pack would include drivers for devices like network adapters, since obviously if you're going to download your corporate image from a server somewhere, you need your network adapter working even in this "mini OS".  The way that's achieved is by having customized "boot media" that contains the application necessary to start downloading that image, and of course any needed drivers.  The WinPE driver pack again gives SCCM admins all the drivers they need in order to get a given system model working well enough in WinPE, which they can bake into the "boot media" that they use for this purpose.

12 Posts

June 1st, 2020 09:00

Thank you for the detailed explanation. I'm using WDS/WDT only, so I will just download the main drivers for the 5430 as a test, then I will add more drivers if the driver deployment works. I do know what WinPE is, but I've never actually used it. I will figure it out.

Thanks again.

11 Legend

 • 

14K Posts

 • 

79.9K Points

June 1st, 2020 09:00

@acenyc  If you're using WDS, you are or will very soon be using WinPE.  The image capture environment that WDS uses is built on WinPE, as is the image deployment environment.

12 Posts

June 1st, 2020 10:00

Thank you.

0 events found

No Events found!

Top