MSI installers have same ProductCode

Backup agent for Microsoft Windows servers and workstations (formerly Veeam Endpoint Backup FREE)

MSI installers have same ProductCode

Veeam Logoby dennisabbott » Wed Jun 21, 2017 6:31 pm 2 people like this post

There are two MSI files embedded in the setup: Veeam_B&R_Endpoint_x64.msi & Veeam_B&R_Endpoint_x86.msi
Both of these have the exact same GUID in the ProductCode. The purpose of the product code(Global Unique Identifier) is to uniquely identify installers. The two MSI's obviously contain different files and different settings based on the OS type. This is highly problematic when you are using any of the major software deployment infrastructures. For example System Center Configuration Manager. These software deployment systems key into that GUID and use that to differentiate unique products throughout a network. When they inventory or run detection rules on assets they would assume that this software is one and the same, but they are not, I know that they are slightly different because you made a decision to split them into two different MSI's. If I ran a hashcheck it would come back as not being the same. This is dire misstep that goes against a known established standard. It makes it very difficult to manage this software across multiple managed machines. You could have chosen to have one MSI that worked on both x86 and x64. I think you took the right path in splitting these off into two different MSI's but you absolutely need to make that ProductCode unique. There's that word unique again.....hmmm. These are two different files, you should mark them that way. ... 60(v=vs.85).aspx

If the purchasing decision was up to me I would have passed on this product due to this issue. This is an extremely easy issue to fix, should take about 30 seconds when you are compiling the MSI's for the next version. Also please lay out your lifecycle for patching the product, you should be releasing MSP's for minor releases and then a new set of two MSI's for major releases (3.x). Deployment engineers have to look at the entire lifecycle of all these versions and your current GUID decision makes that very difficult. We will have to reference the ProductCodes and UpgradeCodes for years, please make this easier for us.

Lastly you need to stop using so many CustomAction objects as errors in those will not get fully recorded in the install log file. If you need to write a registry entry use the Registry table instead of your custom dll. That would make install issues much easier to troubleshoot. Then I would know if it was permissions or some other common registry issue.

this is black box to me because you did a simple reg entry with a homegrown dll instead of following standards:
Code: Select all
MSI (s) (B0:5C) [10:14:26:653]: Invoking remote custom action. DLL: C:\windows\Installer\MSI8201.tmp, Entrypoint: _VmACreateRecoveryMediaUpdateValue@4
Action 10:14:26: VmACreateRecoveryMediaUpdateValue. Setting Recovery Media update requirement flag...
***Veeam***  Storage name: 'C:\ProgramData\Veeam\Setup\Temp\{39C68361-38C1-4528-8064-AA5A182DBE0B}\VmCreateRecoveryMediaUpdateValue'.
Failed to create RecoveryMediaUpdateRequired registry value.
MSI (s) (B0!D8) [10:23:20:465]: Product: Veeam Agent for Microsoft Windows -- Failed to create RecoveryMediaUpdateRequired registry value.
Action 10:23:20: .
CustomAction VmACreateRecoveryMediaUpdateValue_Collect returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
Action ended 10:23:20: VmACreateRecoveryMediaUpdateValue_Collect. Return value 3.
Action ended 10:23:20: INSTALL. Return value 3.
Posts: 1
Liked: 2 times
Joined: Wed Jun 21, 2017 5:35 pm
Full Name: Dennis Abbott

Re: MSI installers have same ProductCode

Veeam Logoby Dima P. » Wed Jun 21, 2017 10:47 pm

Hello and welcome to the community Dennis,

Thanks for the great feedback I’ll discuss it with our setup team and get back to you. Cheers!
Dima P.
Veeam Software
Posts: 7015
Liked: 507 times
Joined: Mon Feb 04, 2013 2:07 pm
Location: SPb
Full Name: Dmitry Popov

Return to Veeam Agent for Windows

Who is online

Users browsing this forum: Google Feedfetcher and 1 guest