Nick

Nick

Forum Replies Created

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • Nick
    Participant
    Post count: 4

    The Toolkit automatically generates a verbose log under the “C:\windows\logs\software” folder. So all you need is Execute-MSI -Action ‘Install’ -Path “$InstallPath\DRAInstaller.msi” -Transform ‘DRA.mst’ -Parameters “ADDLOCAL=Client_UserConsole /qb!”

  • Nick
    Participant
    Post count: 4

    You may have to use the serviceUI so you can see the box. In Task sequences you can use the following command so the boxes wil display. Not sure if InTune works the same way or not. Make sure serviceUI.exe is present in the same folder as deploy-application.exe

    Command –> ServiceUI.exe Deploy-Application.exe Install

  • Nick
    Participant
    Post count: 4

    As an example you want to use the -WaitforMSIExec parameter since it is probably calling the MSI from within the EXE.

    Execute-process -Path “$dirFiles\setup.exe” -parameters “/s /f1$dirFiles\setup.iss” -WaitForMsiExec -WindowStyle Hidden -IgnoreExitCodes “3010” -ContinueOnError $true

    • This reply was modified 7 months, 2 weeks ago by  Nick.
    • This reply was modified 7 months, 2 weeks ago by  Nick.
  • Nick
    Participant
    Post count: 4

    You can also use other parameters if if the EXE has an embedded MSI. I would recommend putting a path with a space in a variable.

    Execute-process -Path “$dirFiles\setup.exe” -parameters “/s /f1$dirFiles\setup.iss” -WaitForMsiExec -WindowStyle Hidden -IgnoreExitCodes “3010” -ContinueOnError $true

    • This reply was modified 8 months ago by  Nick.
Viewing 4 posts - 1 through 4 (of 4 total)