Skip to main content

Driver Injection (Acronis Universal Restore) - How does it actually work?

Thread needs solution

Hi,

Trying to find some information on how the drivers are detected during deployment exactly?

When i first started using the Driver Location page on a deployment within template creation i would select the local disk/folder locations of these drivers and after some deployments that would reach windows OS but have no drivers installed i investigated logs and realised that the Snap Deploy software could not access for example "D:\Driver Packs" because it thinks "D:\" is part of the deployed machine, and not the deployment server.

So i changed my templates to be "\\DEPLOYMENTSERVER\DRIVERS\" and 80 percent of the time the drivers work..

I had a deployment where i deployed 7 machines using the exact same driver path, and 4 of them worked and the rest didn't?

Is there a proper folder structure that needs to be followed with this? the KB articles are not specific at all.

How many sub folders get scanned in a driver location before it would fail? 

Are all in the .INF files supposed to be in a root directory etc?

The driver deployment function seems a bit touchy.

Any info would be great!

Thank you.

0 Users found this helpful