Roaming Profile: Policies are available, but not working
Reported by
schlo...@gmail.com,
Dec 29 2017
|
|||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.108 Safari/537.36 Steps to reproduce the problem: 1. Enable Roaming Profiles via GPO (https://www.chromium.org/administrators/policy-list-3#RoamingProfileSupportEnabled) and define a profile location (https://www.chromium.org/administrators/policy-list-3#RoamingProfileLocation). 2. Launch Chrome, change something (e.g. create a bookmark). 3. Check if the changes have been saved to the location defined in the policies or in the standard path (%localappdata%\Google\Chrome\User Data\) What is the expected behavior? Quoting the Chromium Policy List regarding RoamingProfileSupportEnabled: "If you enable this setting, the settings stored in Google Chrome profiles like bookmarks, autofill data, passwords, etc. will also be written to a file stored in the Roaming user profile folder or a location specified by the Administrator through the Google Chrome policy. Enabling this policy disables cloud sync." What went wrong? It was stored in the regular profile path (%localappdata%\Google\Chrome\User Data\). Did this work before? N/A Chrome version: 63.0.3239.108 Channel: stable OS Version: 10.0 Flash Version: - Tested on Windows 10 1607 (Build 1493.1884), Windows 7 (Build 7601: SP1) and Citrix. - Maybe there is another policy interfering with the Roaming Profile, therefore I uploaded a JSON export. My most obvious guess was the SyncDisabled. I have abandoned this thought after reading the SyncDisabled description: "This policy should not be enabled when RoamingProfileSupportEnabled policy is set to enabled as that feature shares the same client side functionality. The Google-hosted synchronization is disabled in this case completely." (source: https://www.chromium.org/administrators/policy-list-3#SyncDisabled). - This has been observed by other users: https://productforums.google.com/forum/#!msg/chrome-admins/IKLGAStKOzU/yEIwe6pgBAAJ .
,
Jan 1 2018
,
Jan 8 2018
,
Jan 8 2018
Hi, indeed you have to remove the SyncDisabled policy (or set it to false) for the Roaming Profiles feature to work. Also it is worth mentioning this feature will not stop Chrome from using its local profile folder but it will *additionally* start maintaining a streamlined version of the profile in the location you picked for your roaming data that can then be discovered and loaded from other computers and used to populate the local profile with data from another computer.
,
Jan 8 2018
Hi, Ok, thank you. We will work on another workaround for Citrix in this case. We want the users' profile on a filer, but it seems that Chrome cannot find the PepperFlash folder anymore if it has been redirected to a network drive (e.g. https://bugs.chromium.org/p/chromium/issues/detail?id=572131 or https://bugs.chromium.org/p/chromium/issues/detail?id=581062#c26). That was why we left the UserDataDir (https://www.chromium.org/administrators/policy-list-3#UserDataDir) untouched and only redirected the RoamingProfileLocation.
,
Jan 9 2018
Chrome + roaming profiles is a headache - we used to have our User Data folder redirected but multiple logged in PCs with the same user breaks that method. We now have everything stored in the %appdata%\Roaming - GPO jiggery-pokery can exclude most of the bloat (extensions, PepperFlash, pnacl, SwReporter) which can be regenerated on opening Chrome (I can confirm this is the behaviour for a locally-redirected User Data folder but not sure about a network one).
,
Jan 9 2018
Sorry, should have mentioned we're running Version 63.0.3239.132 (Official Build) (64-bit) and transitioned from filer-based redirected User Data to roaming redirected User Data.
,
Jan 11 2018
This seems to be Enterprise related. Hence adding TE-NeedsTriageFromHYD label Thanks!
,
Jan 11 2018
Actually I think we can close this request as it seems to have been a misunderstanding of the definition of the policy and the original reporter has replied that they will consider another option. |
|||||||||||||
►
Sign in to add a comment |
|||||||||||||
Comment 1 by meh...@chromium.org
, Dec 29 2017