[Feature Request] Incompatible Upgrade MSI's with multiple products on same server

[Glenn.R.Bundy]

Posting this on behalf of one of our clients, he opened ticket 04365068.

He has both Veeam Explorer for Office 365 and VCC installed on the same server and was upgrading VBR to 10a. As he explained it (and I followed along with my own research), the 10a upgrade expects the following keys:

[HKEY_CLASSES_ROOT\Installer\Products\32D5322D88D3BC9499505326938CF789\SourceList]
"PackageName"="VeeamExplorerForExchange.msi"

[HKEY_CLASSES_ROOT\Installer\Products\5F69CCC7A89F7D6449D9101D9B1B505E\SourceList]
"PackageName"="VeeamExplorerForSharePoint.msi"

But the Veeam Office 365 installation changes the keys to:

[HKEY_CLASSES_ROOT\Installer\Products\32D5322D88D3BC9499505326938CF789\SourceList]
"PackageName"="VeeamExplorerForExchange_4.0.1.519.msi"

[HKEY_CLASSES_ROOT\Installer\Products\5F69CCC7A89F7D6449D9101D9B1B505E\SourceList]
"PackageName"="VeeamExplorerForSharePoint_4.0.1.519.msi"

The result is an installation error. It can be resolved by changing the keys back to the top values.

The client asked to have this addressed in future releases so that installations do not require a manual registry edit!

[Polina]

Hi Glenn and welcome to Veeam Forums!

Thank you for the heads up. Our QA engineers are on it.