0
votes

We have a msi installer which we have created using the wix installer. This installer also includes certain device drivers that need to be installed. We install the device drivers via a custom action. This custom action executes a .bat file that contains the utility dpinst64 to install the driver package. I have used the following option with the dpinst64

@if /I "%PROCESSOR_ARCHITECTURE%" == "AMD64" (
  rem echo Installing driver from 64-bit installer on Windows 7
rem  dpinst64.exe /SW /S /PATH W7
  dpinst64.exe /q /se /PATH W7
) else if /I "%PROCESSOR_ARCHITECTURE%" == "X86" (
    rem echo Installing driver from 32-bit installer on Windows 7
    dpinst32.exe /q  /se /PATH W7
  )
)

What happens is when the user double clicks on the msi, the user gets a prompt to enter his / her credentials. After this installation proceeds OK. When the time comes to install the drivers, the user is again prompted with the credential window. I would like to know how can I avoid this coming again. I was thinking since I have already provided my credentials, this should remain for the rest of the session. However this seems to be not the case.

1

1 Answers

2
votes

Batch Files Considered Harmful: Batch files must be avoided at all cost for MSI deployment. They are clunky, obsolete and almost without error handling and generally feature no rollback.

WiX Driver Element: Recommend you try to use the WiX Driver Element instead. It uses the DIFx framework under the hood - as far as I know. A small, practical example found on github.com.

Previous Answer: Maybe see this previous answer for more on the difx:Driver construct:

<Component>
   <File ... /> 
   <difx:Driver ... />
</Component>

Links: