Issue 430514 in chromium: RestoreOnStartup and RestoreOnStartupURLs do not accept "Not Configured" after they have previously have been set to a defined value.

[chro...@googlecode.com]

Status: Unconfirmed
Owner: ----
Labels: Type-Bug Pri-2 Cr-Enterprise

New issue 430514 by eland...@appirio.com: RestoreOnStartup and
RestoreOnStartupURLs do not accept "Not Configured" after they have
previously have been set to a defined value.
https://code.google.com/p/chromium/issues/detail?id=430514

Version of Google Chrome (Wrench-> About Google Chrome): 38.0.2125.111 m
Version of MSI (if applicable): 64-bit
Using group policy settings? Yes

Using the Windows GPO we originally pushed the following settings:

RestoreOnstartup =
4

RestoreOnStartupURLs =
mail.google.com,
calendar.google.com,
drive.google.com,
mail.google.com/mail/mu/?mui=ca

We decided to change this to "Not Configured" to allow our users to
personalize their startup experience. So we change the both of these
settings to the following:

RestoreOnStartup =
Not Configured

RestoreOnStartupURLs =
Not Configured

We have waited over 24 hours and ran the "gpupdate /force" several times
and Chrome still shows under "Chrome://policy" that there is a machine
setting for both settings and its still shows up as:

RestoreOnstartup =
4

RestoreOnStartupURLs =
mail.google.com,
calendar.google.com,
drive.google.com,
mail.google.com/mail/mu/?mui=ca


Is there a new GPO template that we should be using?

Please Assist

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[chro...@googlecode.com]

Updates:
Labels: TE-NeedFurtherTriage

Comment #3 on issue 430514 by ashej...@chromium.org: RestoreOnStartup and

RestoreOnStartupURLs do not accept "Not Configured" after they have
previously have been set to a defined value.
https://code.google.com/p/chromium/issues/detail?id=430514

(No comment was entered for this change.)

[chro...@googlecode.com]

Comment #4 on issue 430514 by pasta...@chromium.org: RestoreOnStartup and

RestoreOnStartupURLs do not accept "Not Configured" after they have
previously have been set to a defined value.
https://code.google.com/p/chromium/issues/detail?id=430514

Setting any Chrome policy to not configured will effectively delete the
registry key associated with it.

It is quite probable that you have set the policy through a second channel
as joaodasilva suggested. Check in the registry in which hive (HKLM vs
HKCU) the policy is still present and verify the GPO for another policy
linked in and active that might be setting Chrome policies there.

[chro...@googlecode.com]

Comment #5 on issue 430514 by eland...@appirio.com: RestoreOnStartup and

RestoreOnStartupURLs do not accept "Not Configured" after they have
previously have been set to a defined value.
https://code.google.com/p/chromium/issues/detail?id=430514

We are only setting policies via GPO and Cloud.

[chro...@googlecode.com]

Comment #6 on issue 430514 by pasta...@chromium.org: RestoreOnStartup and

RestoreOnStartupURLs do not accept "Not Configured" after they have
previously have been set to a defined value.
https://code.google.com/p/chromium/issues/detail?id=430514

But you can have GPO applied on a per user and per machine base and also
even inside one of those the same set of policies can be applied through
multiple policy entities.

Please check where in the registry this policy is still present in
HKLM/Software/Policies/Google/Chrome or
HKCU/Software/Policies/Google/Chrome - this will let you narrow down where
your policy that still has these settings might be lurking.

[chro...@googlecode.com]

Updates:
Labels: OS-Windows

Comment #7 on issue 430514 by scunning...@chromium.org: RestoreOnStartup

and RestoreOnStartupURLs do not accept "Not Configured" after they have
previously have been set to a defined value.
https://code.google.com/p/chromium/issues/detail?id=430514

Does not happen on Chrome OS. Marking OS-Windows.

[chro...@googlecode.com]

Comment #9 on issue 430514 by eland...@appirio.com: RestoreOnStartup and

RestoreOnStartupURLs do not accept "Not Configured" after they have
previously have been set to a defined value.
https://code.google.com/p/chromium/issues/detail?id=430514

We have just the GPO policy and the Google Cloud Policy.

We have hundreds of thousands of users and we cannot create multiple
policies it would be an admin nightmare.

[chro...@googlecode.com]

Comment #10 on issue 430514 by aclav...@tms.com.co: RestoreOnStartup and

RestoreOnStartupURLs do not accept "Not Configured" after they have
previously have been set to a defined value.
https://code.google.com/p/chromium/issues/detail?id=430514

What's the solution for this problem?

[chro...@googlecode.com]

Updates:
Labels: TE-NeedsFurtherTriage

Comment #11 on issue 430514 by ashej...@chromium.org: RestoreOnStartup and

RestoreOnStartupURLs do not accept "Not Configured" after they have
previously have been set to a defined value.
https://code.google.com/p/chromium/issues/detail?id=430514

(No comment was entered for this change.)

[chro...@googlecode.com]

Updates:
Labels: -TE-NeedFurtherTriage

Comment #12 on issue 430514 by ashej...@chromium.org: RestoreOnStartup and

[chro...@googlecode.com]

Updates:
Status: WontFix

Comment #14 on issue 430514 by pasta...@chromium.org: RestoreOnStartup

and RestoreOnStartupURLs do not accept "Not Configured" after they have
previously have been set to a defined value.
https://code.google.com/p/chromium/issues/detail?id=430514

(No comment was entered for this change.)