Software Deployment

Have a look at the reply I did for this note.

As you will see, I suggested using the Difx 2 merge module for this purpose. In your case, you will need to modify the flags field in the MsiDriverPackages table and set the flags to 12, indicating a legacy (i.e. non-signed) driver installation.

Following installation you may still get a prompt for administrator credentials when any physicals device(s) to which the drivers relate to are attached to the system. The exception to this are printers which use a different "server-side" mechanism and avoid the need for non-admin users to enter credentials.

I think the above restriction is pretty much unavoidable (although if other forum members have any workarounds, I'd be delighted to hear from them [:)]) However, if everything else has been done correctly, then at least your users should not be prompted for the location of the drivers as everything else should take place automatically.

Regards,

Spartacus

DPinst.exe is included in "Driver Install Frameworks Tools 2.0" which can be downloaded from http://www.microsoft.com/whdc/archive/DIFxtls20.mspx

When using DpInst.exe, and you are installing unsigned drivers, ensure to use the Legacy Mode. The switch to use is /lm for this.
I think newer releases of DpInst.exe might have an option aside from the command line switch to control unsigned driver installations.

Have in mind that you will still have the problem with prompt for administrator credentials when using Unsigned drivers.
Try create a Catalog (CAT) file for it and sign that with your own Certificate (CER) file.

I didnt find anything in the above link but this helped.

http://www.deploymentresearch.com/Blog/tabid/62/EntryId/63/Sign-your-unsigned-drivers-Damn-It.aspx

Can you explain how to go about creating a CAT file that is signed with your own CER file?

Thanks,

Mike

Have a look at http://itninja.com/question/how-do-you-roll-out-new-machines?0873&mpage=1