Running enterprise installer in maintenance mode breaks DisplayVersion updates |
||
Issue description
With some version of enterprise Chrome already installed, running:
msiexec /l*vx msi.log /fvomus GoogleChromeStandaloneEnterprise.msi
causes the ClientState\EnterpriseProduct{GUID} value to be lost, which breaks updating the DisplayVersion. This is inconvenient for admins.
In fact, Chrome itself is uninstalled and reinstalled in this case. We should do a simple overinstall instead without deleting anything.
,
Jun 27 2017
It turns out that the MSI had some flaws that caused installation and removal of Chrome to happen when it shouldn't have. Performing a repair with /fvomus is only meant to function when that exact MSI has already been installed. Otherwise, the operation should be a no-op. This has been broken with Chrome's enterprise installer since its inception. I have a change under way that will fix this. With this change, "msiexec /fvomus GoogleChromeStandaloneEnterprise.msi" will either do nothing at all (if that MSI was not previously installed) or will properly perform an overinstall without first uninstalling Chrome.
,
Jun 28 2017
thanks for feedback on issue. i have one more question if there some google desktop installed, is google chrome enterprise cover this possibility as well ?
,
Aug 1 2017
The current enterprise installer contains the fix for this. Existing installs will need to be updated via the .msi in order to receive the fix -- it's not sufficient to let them auto-update. Re comment #3: could you elaborate on your question? |
||
►
Sign in to add a comment |
||
Comment 1 by grt@chromium.org
, Jun 22 2017Status: Started (was: Available)
Digging... Chrome's ClientState key (which contains the EnterpriseProduct{GUID} value) is being deleted by Google Update as a result of the existing Chrome being uninstalled before the new version is installed. Still looking into what the right path forward should be.