Psexec argetComputer -w 'C:Program FilesBatchPatchdeploymenttemp' msiexec.exe /i 'C:Program FilesBatchPatchdeploymenttempMicrosoft Report Viewer Redistributable 2008.msi' /q Psexec argetComputer -s -w 'C:Program FilesBatchPatchdeploymenttemp' msiexec.exe /i 'C:Program FilesBatchPatchdeploymenttempMicrosoft Report Viewer Redistributable 2008.msi' /q The second command will deploy in the regular user account that you’re using. BP would run the equivalent of the first command to perform the installation in the SYSTEM account for maximum permissions. Then from the BP computer try running the following two commands to see if either one works. MSI on the target computer in “C:Program FilesBatchPatchdeploymenttemp” Maybe that’s where the problem is occurring. I think the next step would be to test running the installation remotely with PsExec. This is the first time I have ever heard of an issue deploying a. To be honest, I’m at a bit of a loss here.

Verify that the package exists and is accessible, or contact the application vendor to verify that this is a valid Windows Installer package. This installation package could not be opened. Sounds to me like there is a problem with the MSI package. Are you saying that even when it comes back as SUCCESS (exit code 0), the installation has not actually occurred? That’s certainly a weird one. You said it doesn’t complete but it comes back as either SUCCESS (exit code 0) or exit code 1619.

Batch file to install msi