Issue metadata
Sign in to add a comment
|
Directory variables for the "Set the roaming profile directory" GPO do not work
Reported by
chris.po...@kqf.com,
Jun 14 2017
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:54.0) Gecko/20100101 Firefox/54.0 Steps to reproduce the problem: 1. Set the "Enable the creation of roaming copies for Google Chrome profile data." GPO to Enabled 2. Set the "Set the roaming profile directory" GPO to Enabled and provide a path that includes a directory variable What is the expected behavior? A profile.pb file should be created in the specified path What went wrong? No folder or profile.pb is created in the specified path if it includes a directory variable Did this work before? N/A Chrome version: 59.0.3071.86 Channel: stable OS Version: 10.0 Flash Version:
,
Jun 15 2017
Kiran@ Could you please take a look in to this issue?
,
Jun 15 2017
Able to reproduce the issue on Windows server(AD) with chrome #59.0.3071.86 as per steps mentioned in comment #0, #1
Observed that folder is created with variable(${user_name}) name not with the actual username.
Attaching the screen-cast for reference.
Thank You...
,
Jun 15 2017
chris.pontus@ could you confirm that this issue you are facing ?
,
Jun 15 2017
Yes, that is the issue. The same directory string with the variable works properly with the 'Set user data directory' GPO setting.
,
Jun 15 2017
Thank you for providing more feedback. Adding requester "kkaluri@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 15 2017
This is fixed in latest Chrome Beta version. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by chris.po...@kqf.com
, Jun 14 2017Update: I am using the ${user_name} variable and it gets created on the server instead of the expected actual username. Example: c:\Temp\${user_name}\Google instead of c:\Temp\username\Google