Home / server / Questions / 485226
Accepted
Matt
Asked: 2013-03-07 05:49:58 +0800 CST

MDT capture process injecting drivers, Why?

  • 772

During the capture process from the MDT sequence, it will inject drivers into the sysprepped image, why would you need that?

I know you can prevent it from doing that simply by unchecking it, but why would you need to inject the drivers into the sysprepped image? I'm curious if I even need to do it or if I should do it. What scenario would you need an image with the injected drivers?

Thanks!

drivers

1 Answers

  1. Best Answer

    Injecting drivers at deploy time allows you to keep drivers out of the image. it gives you exponentially more flexibility with your image.

    So, lets say you have 12 different makes and models that you support. Instead of maintaining 12 different images that you have to update and/or rebuild every year, you build ONE image in a VM with no drivers.

    Then, you can organize all your drivers in MDT by make and then model and inject drivers at deploy time.

    It sounds like overkill, but once you have one image to rule them all, your life becomes much, much easier.

    • 0