A DriverPack is a collection of all drivers for a specific hardware model.
If your Driver Packs during the automated Windows installation are a combination of all drivers (software for controlling hardware) of a specific device, for example to have them installed automatically during the automatic installation of Windows.
Each hardware vendor has a different way of delivering these driver packages for IT administrators so that they can import them into their MDT and SCCM/MECM environment.
Below I have made an overview of the most common hardware suppliers with references to Driver Packs that can be used with, for example, MDT or SCCM.
Drivers are injected with DISM during a Windows installation.
Overview manufacture of hardware for SCCM Driver Packs
Download from website: http://www.acer.com/sccm/
Download from website: Dell command deploy driver packs for enterprise client OS deployment
Download from website: http://support.ts.fujitsu.com/content/sccm.asp
Download from website: HP WinPE Driver Packs
Download from website: HP Driver Packs (x86 bits)
Download from website: HP Driver Packs (x64 bits)
Download software to create the latest driver packages locally: HP SoftPaq Download Manager
Download from website: https://support.lenovo.com/us/en/documents/ht074984
Download software to create the latest driver packages locally: Lenovo Update Retriever
Download from website: https://builder.b2b.toshiba.com/
Method of using DriverPack
- Download the drivers from the vendor’s website and extract or archive the driver’s files (mostly .EXE or .CAB file extension);
- Add or copy the entire driver’s folder directory to the manual collection;
- Under OS Deployment select Driver Repository;
- Select Manual collection driver repository and click on update driver repository;
- Create a bootable media and check whether the drivers are getting listed;
- When the bootable media is created, boot the target machine and deploy the image.