Automated removal of User-Installed versions when installing enterprise version
Reported by
xerxes2...@gmail.com,
Feb 28 2018
|
||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.186 Safari/537.36 Steps to reproduce the problem: 1. Install Google Chrome as a standard user. 2. Install googlechromestandaloneenterprise.msi as a user with administrative rights What is the expected behavior? According to the Chrome Deployment Guide (page 9), under the heading "Test Your Installation Process", (Chrome will install for all users and leave the user data untouched). The expectation is that it should remove any user installed version of Chrome, "%User Data%\Google\Chrome\Application", and replace the installation with the enterprise or system install. What went wrong? The user installation still exists, regardless of the fact that the enterprise version was installed. Did this work before? N/A Chrome version: 64.0.3282.186 Channel: stable OS Version: 10.0 Flash Version: This is not typically an issue, however with growing network security concerns, old versions in the user directory could potentially be exploited.
,
Mar 1 2018
,
Mar 1 2018
As this is Enterprise related and cannot be done by ET team adding TE-NeedsTriageFromHYD. Could someone from Inhouse team please have a look at this issue. Thanks!
,
Mar 5 2018
Greg, wasn't the expected behavior for the MSI be to remove user installed versions when installing the MSI?
,
Mar 5 2018
No. The next launch of per-user Chrome will cause it to self-destruct and launch the per-machine install, however. It would be quite difficult to remove per-user installs during installation of per-machine Chrome since the installer does not run at user context in that case. Do we have documentation that implies that the act of installing per-machine Chrome will remove per-user Chrome? If so, we should fix that.
,
Mar 5 2018
@grt Thanks for the update. Are there any plans to work on creating something to “find and remove” those per-user installations? The next launch of chrome-user sounds promising, but only for future installations. And yes, the context of the chrome enterprise deployment guide alludes that it will only keep user data. It doesn’t state that the application won’t be removed. Thanks for following up.
,
Mar 12 2018
considering this issue as feature request and marking it as untriaged. Please undo it if it not the case?
,
Apr 23 2018
Assigning to privard@ for triage. tl;dr: OP would like installation of per-machine Chrome to automagically remove all per-user installs or, failing that, a tool to find and remove per-user Chrome installs on machines that have received per-machine installs. One crazy thought: per-machine Chrome could have a "proactive clean" mode where Active Setup is used to remove per-user installs on the next user logon. So rather than waiting for Alice (a fictional enterprise user with per-user Chrome) to launch per-user Chrome for it to self-destruct, Alice's next Windows log on would run something in the per-machine install that would remove Alice's per-user install straight away. This isn't quite the same as a tool that finds and removes all per-user installs, but it would hasten the cleanup of per-user installs.
,
Apr 24 2018
Leaving this as a feature request but reducing the priority. This isn't currently on our roadmap and doesn't seem to be blocking any deployments, but leaving this open to collect more feedback.
,
Jul 5
Marking as WontFix. Some enterprises may rely on the existing behavior in their deployments. It's also possible for admins to handle this with 3rd-party tools, so there's a viable workaround. |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by xerxes2...@gmail.com
, Feb 28 2018