Product code

Since version v1.0.0 to v2.0.0 Voice for Windows MSI installer package has been using the same product code to indicate that there should be only one version of the application installed on the user machine. From v2.0.1 onwards there will be a new product code assigned for the package and upgrade path defined so that the MSI package will allow upgrading from previous versions to a new one.

How this change affects the local installation?

When using the Setup.exe to install the application, everything from removing the old version to installing the new version is done automatically so in that case this does not affect local user installations.

How this change affects when using remote installation tools?

When using systems like SCCM/Endpoint Manager to deploy the MSI package to client machine this product code change should make it possible to detect the update need on target machine. Admin should check that if there is, for example, a custom script made to deploy the installation that it still works or if it is using a product code for removing the old installation, then change the installation procedure so that MSI package is directly used to deploy the installation/update.

What are the caveats with this MSI package?

Currently there is no way to reliable terminate the running BeneDesk.exe and BAPIWS.exe processes during the update so when deploying the update package admin should make sure that if application is running on target machine while update takes place that the running processes does not prevent the update. Improvement for this is planned on later date.

Is there a way to kill the processes when updating?

With some SCCM systems you can run for example a PowerShell script before MSI package is run.
Following commands can be used to kill the running processes.

taskkill /f /im BeneDesk.exe
taskkill /f /im BAPIWS.exe