If an executable is the only way a driver is available, it must be imported as an application into MDT, and installed via task sequence. Many drivers are distributed as packages, which come in the form of an executable. The basic INF files are what MDT needs for driver injection. It is called “Out-of-Box-Drivers” (OOBD). To do this, MDT has a folder/section in the deployment share that is dedicated to organizing and storing drivers. When a matching driver is found, it is injected into the image before it is applied to the computer’s hard drive. During a task sequence, MDT runs a plug and play check, for hardware at a couple of different points to determine what drivers, if any, are needed. This makes the captured image applicable to many different types of hardware.
When generalizing an installation of Windows for capture with sysprep, all but the most basic drivers are removed. Anyone who has ever had to troubleshoot a piece of hardware on Windows knows this. Drivers are a big part of getting Windows to work properly.
0 kommentar(er)
