New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 607683 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: May 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Feature



Sign in to add a comment

I want to over-write user settings on managed chromebooks

Reported by 000017...@coyote.csusb.edu, Apr 28 2016

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.86 Safari/537.36

Steps to reproduce the problem:
1. Register managed chrome device
2. Move device to device organization
3. Log in to chrome device with user account

What is the expected behavior?
I want to be able to override user settings for managed devices only.  Personal (unmanaged) devices should keep user's settings.

What went wrong?
User settings in managed chrome device's organization is not applied after user signs in.

Did this work before? N/A 

Chrome version: 50.0.2661.86  Channel: n/a
OS Version: OS X 10.11.4
Flash Version: Shockwave Flash 21.0 r0
 
Status: Untriaged (was: Unconfirmed)
Considering this issue as Feature-Request and marking it as untriaged, so that it will be addressed to dev team for further assistance.

Thanks!
Components: Enterprise
Labels: -OS-Mac OS-All
[mac triage]

Comment 3 by tnagel@chromium.org, May 12 2016

Owner: dskaram@chromium.org
Feature request --> dskaram@
Cc: dskaram@chromium.org
Just to understand the ask

Device enrolled in school.edu.
User policies applied on users from school.edu

Personal users signs in to the managed device

Expectation is that user policies are applied on the personal user's session?

Comment 5 Deleted

Comment 6 Deleted

I imagine having generic User Settings in user OU and having custom User Settings in device OU so that only managed devices in device OU get User Settings from the same OU.
Status: WontFix (was: Untriaged)
OK so I think we are on the same page. Unfortunately, there is a very clear user and device separation in Chrome OS. We allow admins to turn off personal usage by restricting sign in to non-managed users. But if admins make the decision to indeed allow unmanaged users on the device, then we don't give them the ability to apply any management to those users.

If admins are uncomfortable with unmanaged users, then they should turn that feature off. If they want to allow it, then it's a fully unmanaged session. We are very unlikely to change our stance on this issue.

Sign in to add a comment