But all images work, if I disable the other driver packages that aren't compatible with that machine currently being imaged. So I'm not building all different kinds of images.
I have the install media built from a VM so as to be very generic, I capture it to WDS, and break out driver packs based on machine models. If I disable all other driver packages except the one the model needs, and don't filter, it works great. Still seeing certain drivers not installing, or no drivers installed. I've tried the option to apply all drivers, and apply only applicable to the hardware. I even look up the model in msinfo32 and enter it exactly, still doesn't work. I enter the System Model into the filter, but it doesn't work. If you're wondering why WDS doesn't work for us, I can't explicitly define a driver repository to a certain model. Why would I use MDT/WAIK over WDS? Why do both exist? That doesn't make any sense because I'm building images in WDS (capture/boot images/install images/driver repositories/etc). An article said you use WDS for PXE boot, and build images in MDT. I've found that WAIK is for building unattended files, and is needed in MDT. I don't fully understand the differences between WDS and MDT. I basically need WDS with that kind of control. WDS performs well, but not being able to mess with tasks and specific drivers being applied to packages is a problem for us. We already have SCCM stood up, but there's just so much extra work that goes into it. So I know SCCM has everything rolled in, but that's way more work than our smaller environment can justify.