Change MSI from a wrapper to "full" MSI
|Reported by vadimr...@gmail.com, Jan 4 2011||Back to list|
Version of Google Chrome (Wrench-> About Google Chrome): Version of MSI (if applicable): Using group policy settings? Yes/No Att: Glenn Wilson Glenn, in the blog you wrote: "We’ve created an MSI installer that enables businesses who use standard deployment tools" Not quite. What you created is not an MSI installer, it's MSI wrapper around the setup executable, and as such, it's missing most advantages of the true Windows Installer-based installation. Good installation is much more than just group policy as deployment engine. Competent administrator will have to repackage it into true MSI installation in order to deploy. I certainly will.
Jan 4 2011,
Jan 4 2011,
Correct, the current MSI is a wrapper. That said, we'd love to have a full-fledged 'true' MSI This will require a sizable re-write of the installers / setup. Robert, do we already have a bug tracking the "full" MSI feature request?
Jan 5 2011,
I actually went ahead and indeed repackaged it into true MSI, you can take a look at www.vadimrapp.com/chrome/GoogleChromeStandaloneEnterprise2.msi It's quite a draft, and would require more work, but Chrome works. 90% of the difficulties were with GoogleUpdate; speaking of which, I think, Google Update should rather not be in the package for the environment where all deployment is controlled. In this installation, I separated it into a separate feature, not installed by default. I did not find anything GU-related in the ADM template, either - I think, it definitely should be there.
Mar 1 2011,
Any updates on this?
May 31 2011,
Issue 84318 has been merged into this issue.
Jul 15 2011,
Issue 89405 has been merged into this issue.
Jul 15 2011,
Jul 19 2011,
A true MSI installer without Google update bundled in would greatly improve my estate rollout, and increase Chrome's enterprise'ness. Currently I'm having repackage to strip GU out each time. Google update does not work in my locked down enviroment as normal users cannot modify or create binary files (I wouldn't want it to if it did) but rolling out a new MSI via SCCM is easy :) Enterprise administrators in the most part do not want Chrome to auto update, we have to test things like this before they go live.
Mar 10 2013,
Mar 26 2014,
Oct 21 2015,
Could you guys move this issue forward, please?
Oct 20 2016,
This issue has been available for more than 365 days, and should be re-evaluated. Please re-triage this issue. The Hotlist-Recharge-Cold label is applied for tracking purposes, and should not be removed after re-triaging the issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
This issue requires no re-triage. You just need to fix it and not wait years. Nothing has changed until today.
Sign in to add a comment