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

Issue 856865 link

Starred by 2 users
Status: WontFix
Owner:
msnoxell@chromium.org
Closed: Jul 18
Cc:
█ tjvarghese@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Feature



Sign in to add a comment

[FR] Provision CfM to User OU on Enrolment

Project Member Reported by msnoxell@chromium.org, Jun 27 2018 
Description:
In the same manner as any other Chrome device, on enrolment allow the option to provision CfM devices to a given OU based on the enrolment user location. Currently, CfMs are always enrolled in the top level OU regardless of which OU the enrolment user is located in.

Use case:
Any customer enrolling CfMs may find this FR useful, especially when trying to manage a large fleet or enrolment program.

Motivation:
Large enterprise customer is more than doubling the size of their CfM fleet (~400 > ~900). CfMs are being deployed to remote locations and will be enrolled by on site staff. Operational IT staff want to provide enrolment credentials to streamline the process, removing the requirement for an admin to move it afterwards.

Existing workarounds:
Requires manually moving CfM units via CDM.

Comment 1 by pmarko@chromium.org, Jun 27 2018

Owner: evep@chromium.org
+Eve for PM
Please reassign / do we have a PM with CfM focus who could prioritize this?
Thanks!

@mxnoxell:
Regarding
>> "In the same manner as any other Chrome device, on enrolment allow the option to provision CfM devices to a given OU based on the enrolment user location."

IIRC it's configurable that on enrollment, the enrolling user can provide a textual location and/or a textual asset ID. There is no OU selection dialog.
Or is there some server-side matching logic deriving the OU from the textual location?

Comment 2 by msnoxell@chromium.org, Jun 28 2018 

Any device that uses the standard enterprise enrolment flow (CTL+ALT+E) respects a user policy to enrol a device in the OU in which that user is located. (In CDM: Device Management > Chrome > User Settings > Enrollment controls> Device Enrollment)

Enrolling a CfM (either as a device shipped specifically as a CfM or by CTL+ALT+H) always puts the device into the root level OU. The OU of the user or whether the enrollment policy is defined doesn't make a difference.

The customer in this case wants the behaviour of CfM enrollment to be the same as any other device.

Comment 3 by roy...@google.com, Jul 18

Cc: tjvarghese@chromium.org
Owner: msnoxell@chromium.org
Matt: Can you file this in buganizer ?
- This is a backend change, so needs to be on the other system.
- Route it to @tjvarghese once filed.

Comment 4 by msnoxell@chromium.org, Jul 18 

Filed, closing this as WontFix.

Comment 5 by msnoxell@chromium.org, Jul 18

Status: WontFix (was: Untriaged)
►

Sign in to add a comment