Often we get an error "msiexec is in use" when we want to start an installation. Mostly seen when the user logs in to the device (our "force run" bundles are set to "Launch at ZENworks Login").
At PC start there are other sources outside of ZENworks that will use msiexec to (Virusscan updates or others).

One should be able to configure that an "msiexec bundle action" ("install msi" or "launch executable") should wait for msiexec is available or should at least be configurable to retry the action before giving up.

by: Frank T. | over a year ago | Application Mgmt