Cannot use "Google Roaming Profile" to restore profile extensions if "Configure the list of force-installed extensions" group policy is set
Reported by
daniel.w...@cemaust.com.au,
May 30 2017
|
||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36 Steps to reproduce the problem: 1. Configure "Configure the list of force-installed extensions" in user or computer group policy. Add an extension. 2. Configure Roaming Profiles group policies 3. Log in as user and open chrome. Create the profile and close chrome. 4. Delete profile directory files and folders 5. Open Chrome and the extensions will be marked as not found with the puzzle-piece icon. 6. Removing these policies and rerunning the above process provides the expected results. What is the expected behavior? Profile is recreated and extensions are re-installed. What went wrong? Profile is recreated and extensions are not operating correctly and are not regenerated. Did this work before? N/A Chrome version: 58.0.3029.110 Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version:
,
Jun 1 2017
I just tried to reproduce this issue and for me it worked as expected. I tried two things - delete the whole User Data directory and delete only the Default profile directory. In both cases the profile was correctly populated from the roaming profile data and both force-installed and user-installed extensions were reinstalled in both cases. Please provide the information I asked for in the admin forum thread you started so that we can try to investigate this further.
,
Jun 1 2017
To run the test I deleted the chrome user directory and the profile.pb, created a new profile and signed into chrome adding my extensions. Next I deleted the Chrome directory, logged out of the session and started a new one. Extensions installed correctly, but account was not signed into chrome.
,
Jun 2 2017
Signed-in state is not preserved in the roaming profile set for now. This is a conscious decision for now but depending on user feedback we might decide to change it in the future. What is preserved though is saved passwords and autofill data so getting back on track should be much more painless process then with a fresh profile. If you wish to have it please file a new feature request here as this one discusses the availability of extensions when the roaming profile feature is turned on which seems to have been resolved. If you agree with this conclusion I will close this bug and can continue the discussion on the new one.
,
Jun 4 2017
As a Gsuite customer this feature would greatly assist us to manage our domain and encourage our users to stay logged into Chrome. Using Citrix roaming profiles the way this currently works requires users to log into their Chrome browsers each session (every login) to receive Chrome Management "Recommended Apps and Extensions" and similar policies. This is rather cumbersome and I believe the user is more likely not to log in at all, hindering our ability to manage their browsers using the gsuite tools. Storing the entire chrome profile directory in the users roaming profile adds significant time to logins but it looks as though this may be our only option. I will raise this feature request; we are fine to close this bug as it is by design. Thanks for your assistance.
,
Jun 6 2017
Thanks for the cooperation. Feedback like this is crucial for us to work on what really matters! Best, Julian |
||
►
Sign in to add a comment |
||
Comment 1 by pnoland@chromium.org
, May 31 2017