Group: Forum Members
If your drivers are provided as EXEs, then you'd need a way to extract the actual INF files out of them. Some vendors like Dell and Lenovo provide driver packages as EXEs but include the option to simply extract the driver packages, in which case that's what you would want. If your EXE installers don't offer that, it becomes rather more difficult.
There are two completely distinct cases where drivers and Rescue Media come into play. One is to allow Rescue Media to see and work with the necessary hardware on your system. Those drivers are loaded and used within the WinPE/RE "mini-OS" environment that Rescue is running, for the specific purpose of allowing Reflect to work with that hardware in that environment. That has nothing to do with ReDeploy.
The second case where drivers come into play is for ReDeploy. The purpose of ReDeploy is to allow the restored Windows environment to boot on your new hardware. That environment is of course completely separate from the WinPE/RE environment that you're running Reflect on. ReDeploy runs within WinPE/RE, but what it's doing is reconfiguring the (currently offline) full Windows located on the hard drive so that IT will be able to boot properly on this new hardware. Sometimes it's possible to just transplant a hard drive or image backup into a new PC and have Windows boot on that new hardware without any fuss. But that isn't a guarantee. Basically, when Windows is first installed, it performs a full hardware enumeration and records some details about what devices are there and therefore what drivers need to be loaded to allow it to boot. And then to save time on all subsequent boots, it just assumes that all of that hardware will still be there and that those drivers will still be the correct ones to load. In most cases, that's a valid assumption since relatively few people transplant whole Windows environments to different PCs. But of course that's exactly what you'd be doing here, and in THAT scenario, Windows might blue screen trying to start because it's loading an incorrect/incomplete driver set for the hardware it's now trying to start on. Windows does NOT automatically correct itself in those situations. That's what ReDeploy is designed to deal with. So when you run ReDeploy, it looks at the hardware of the system it's running on and then reconfigures the Windows environment installed on the target drive to load the appropriate drivers for that new hardware. If that Windows environment already has drivers appropriate for all of that hardware in its library, then it's easy because ReDeploy just says, "Make sure you load this driver at startup now, instead of this other driver for your previous hardware environment." But if Windows does NOT currently have appropriate drivers for your new hardware in its library, then ReDeploy will ask you to provide them. In this case, the drivers you're providing are NOT so that the Rescue environment can work with your hardware, but rather so that ReDeploy can inject them into the restored Windows installation to allow IT to work with that hardware properly.
Does that clarify things?