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

Issue 794324 link

Starred by 2 users
Status: Assigned
Owner:
marcuskoehler@chromium.org
Cc:
atwilson@chromium.org
█ bartfab@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Turning on chrome management on the fly leaves ARC unmanaged

Project Member Reported by atwilson@chromium.org, Dec 12 2017 
1) Go to cpanel and turn off chrome management
2) Sign in with dasher acct on chrome book - no policies are enforced
3) Turn on chrome management
4) Sign in to chromebook to existing session - at this point, I believe we'll proactively check with DMServer to see if policy is enabled, and will enforce policy.
5) ARC will remain unmanaged because it's too late to setup a DO. I have no idea what will happen (will we crash due to unmet expectations around having a DO on the other end of the ArcBridge)?

We probably should wipe the ARC session if you bounce from unmanaged->managed.

Comment 1 by bartfab@chromium.org, Apr 11 2018

Cc: -dskaram@chromium.org bartfab@chromium.org
Owner: dskaram@chromium.org
Yes, if we want management to kick in, we must wipe all ARC++ data. There is no way to set CloudDPC as DO retroactively. Over to David to decide whether this is what we want to do.

Comment 2 by jingwee@chromium.org, May 3 2018

Status: Untriaged (was: Unconfirmed)

Comment 3 by benhenry@chromium.org, Aug 3

Status: Assigned (was: Untriaged)
This bug has an owner, thus, it's been triaged. Changing status to "assigned".

Comment 4 by dskaram@chromium.org, Aug 23

Owner: marcuskoehler@chromium.org
►

Sign in to add a comment