The "work" parameter had done its job. The deployment was complete.
If you are deploying via an automated administrative script, handle the execution space carefully to ensure parameters pass smoothly to the underlying subsystem: powershell
This is the name of the MSI file you are installing. This file must be available on the local machine, on a network share, or embedded within the deployment tool. The command syntax assumes it is in the current working directory; you can replace it with the full path (e.g., "C:\Deployment\SophosOutlookAddInSetup.msi" ) to avoid errors. msiexec qr i sophosoutlookaddinsetupmsi t1 ec3 c1 i1 work
This switch defines the User Interface (UI) level during installation. /q stands for quiet.
msiexec /i <path-to-msi> [PROPERTY=Value ...] [/qn | /qb | /qr] [/l*v <logfile>] The "work" parameter had done its job
If the installation fails or hangs, consider the following troubleshooting vectors:
One highly specific command frequently utilized by system administrators is: msiexec /qr /i SophosOutlookAddinSetup.msi /t1 /e /c3 /c1 /i1 WORK This file must be available on the local
: Specifies the built-in Microsoft Windows command-line utility used to manage the installation, maintenance, and uninstallation of software compiled in .msi formats.