Unable to enable crostini on managed Pixelbook in dev channel

[Dusty Wilson]

I have a Pixelbook that is running dev channel 69.0.3464.0, not in developer mode.  It is managed via G Suite Device Management.  Device re-enrollment is disabled (set to "not forced").  Are there any policies I can set (or unset) that would be necessary?  I'm hoping I don't need to remove it from management in order to enable "Linux (beta)" in Settings.  I have not tried a powerwash and would rather not if possible.

[Mike Frysinger]

[ +tbuckley ]

not sure what the admin status looks like for gsuite devices

-mike

On Tue, Jun 26, 2018 at 10:25 PM Dusty Wilson <dusty....@scjalliance.com> wrote:

I have a Pixelbook that is running dev channel 69.0.3464.0, not in developer mode.  It is managed via G Suite Device Management.  Device re-enrollment is disabled (set to "not forced").  Are there any policies I can set (or unset) that would be necessary?  I'm hoping I don't need to remove it from management in order to enable "Linux (beta)" in Settings.  I have not tried a powerwash and would rather not if possible.

--
--
Chromium OS Developers mailing list: chromiu...@chromium.org
View archives, change email options, or unsubscribe:
https://groups.google.com/a/chromium.org/group/chromium-os-dev

[Bartosz Fabianowski]

There are no policies for managing Crostini yet. The only policy coming
in the medium term is to turn it off completely. Until that lands, it
should be available for all users, including managed users.
+Dennis to confirm.

- Bartosz

On 27/06/18 04:31, Mike Frysinger wrote:
> [ +tbuckley ]

>
> not sure what the admin status looks like for gsuite devices
> -mike
>
> On Tue, Jun 26, 2018 at 10:25 PM Dusty Wilson
> <dusty....@scjalliance.com <mailto:dusty....@scjalliance.com>> wrote:
>
> I have a Pixelbook that is running dev channel 69.0.3464.0, not in
> developer mode.  It is managed via G Suite Device Management.
> Device re-enrollment is disabled (set to "not forced").  Are there
> any policies I can set (or unset) that would be necessary?  I'm
> hoping I don't need to remove it from management in order to enable

> "Linux (beta)" in Settings.  I have /not/ tried a powerwash and

> would rather not if possible.
>
> --
> --
> Chromium OS Developers mailing list: chromiu...@chromium.org

> <mailto:chromiu...@chromium.org>

[Yanzhu Du]

Hi Mike,

Bartosz is correct. Admins cannot set policy to disable Crostini yet. You should be able to use Crostini by following go/crostini-ui-instructions

Yanzhu Du | Software Engineer | y...@google.com | 425-893-4862

On Fri, Jun 29, 2018 at 10:01 AM, Yanzhu Du <y...@google.com> wrote:

Hi Mike,

Bartosz is correct. Admins cannot set policy to disable Crostini yet. You should be able to use Crostini by following go/crostini-ui-instructions

Yanzhu Du | Software Engineer | y...@google.com | 425-893-4862

On Fri, Jun 29, 2018 at 9:52 AM, Dennis Kalinichenko <dka...@google.com> wrote:

+Yanzhu

On Fri, Jun 29, 2018 at 5:57 AM Bartosz Fabianowski <bar...@chromium.org> wrote:

There are no policies for managing Crostini yet. The only policy coming
in the medium term is to turn it off completely. Until that lands, it
should be available for all users, including managed users.
+Dennis to confirm.

- Bartosz

On 27/06/18 04:31, Mike Frysinger wrote:
> [ +tbuckley ]
>
> not sure what the admin status looks like for gsuite devices
> -mike
>
> On Tue, Jun 26, 2018 at 10:25 PM Dusty Wilson
> <dusty....@scjalliance.com <mailto:dusty.wilson@scjalliance.com>> wrote:
>
>     I have a Pixelbook that is running dev channel 69.0.3464.0, not in
>     developer mode.  It is managed via G Suite Device Management.
>     Device re-enrollment is disabled (set to "not forced").  Are there
>     any policies I can set (or unset) that would be necessary?  I'm
>     hoping I don't need to remove it from management in order to enable
>     "Linux (beta)" in Settings.  I have /not/ tried a powerwash and
>     would rather not if possible.
>
>     --
>     --
>     Chromium OS Developers mailing list: chromiu...@chromium.org

>     <mailto:chromium-os-dev@chromium.org>

[Dusty Wilson]

Following instructions to enable did not result in the setting becoming visible to enable "Linux (beta)" in chrome://settings.

Actions:

1. Stable channel, out of box (unknown what version at the time)
2. Added to G Suite domain as managed device
3. Used for several months as primary device for myself, on stable channel
4. chrome://flags/#enable-cros-container was set to enabled prior to upgrade to dev channel
   
5. chrome://flags/#enable-experimental-crostini-ui was set to enabled prior to upgrade to dev channel
   
6. Got new device (Acer Chromebox), so Pixelbook is now available for experimental use
7. Set G Suite org unit policy to push dev channel to Pixelbook device
8. Device upgraded to dev channel.  Currently running version: 69.0.3473.0 official build via dev channel
9. Device was rebooted after upgrade
10. "Linux (beta)" does not appear as an option (not even in a disable fashion) in the chrome://settings UI
11. chrome://flags/#enable-cros-container no longer appears in flags as an option
    
12. chrome://flags/#enable-experimental-crostini-ui is an option, and is enabled, but does not appear to have an effect
    
13. After power cycled for good measure, "Linux (beta)" does not appear as an option in settings UI.
14. `vmc start testvm` returns "This command is not available."
15. In chrome://flags UI clicked "Reset all to default" and then power cycled
16. "Linux (beta)" does not appear as an option in settings UI.
17. Changed policy to allow user to select channel, refreshed policy, verified channel can be changed (but didn't change it)
18. "Linux (beta)" does not appear as an option in settings UI.
    

I am not a Googler, so I do not have access to any go/ addresses, but following the directions at https://developer.android.com/topic/arc/studio does not do the job.

+Yanzhu

>     <mailto:chromiu...@chromium.org>

[Mike Frysinger]

if the policy isn't in the admin console, what does Chrome itself default to ?  does it default the setting to off ?  i vaguely recall that being the behavior.

-mike

+Yanzhu

>     <mailto:chromiu...@chromium.org>

[Dusty Wilson]

I have opted to remove G Suite management on this device and will return the device to managed mode once the option to do so becomes available.  This has made available the "Linux (Beta)" option to enable, and I have done so.  Thanks!

[emmaly...@scjalliance.com]

Has there been an update on this?  I didn't find any policy settings in the G Suite Admin UI regarding anything labelled Linux or Crostini, and chrome://policy I find "CrostiniAllowed" is "Not set".  I'm hoping that we'll be able to enable Crostini use on our dev users' Chrome OS devices.  Right now (in order to allow Crostini) those are just not being managed on the system level, which is unfortunate.

[Amruta Gulanikar]

The policy for enabling/disabling Crostini on managed devices is right now in trusted tester.  We can add you to the trusted tester and whitelist your domain if that works.

[emmaly...@scjalliance.com]

Yes, please do.  I would greatly appreciate that.  Do you have the information you require for this to be done simply from this email?  Technically our primary domain is different than the domain of my email address, but it is a properly registered domain on our G Suite domain.

[Dan Blah]

Any sense of when this will be an available policy for admins to enable? Re-confirming the above outcomes, that enrolling a device for G Suite Device Management removes the Linux/Crostini ability, regardless of device compatibility. Aside, lots of Chromium OS love from over here as we transition to this as our primary env. This is the last thing that's held us up.

[ry...@derivita.com]

I would also like to get on the trusted tester list for using crostini on managed devices

[Amruta Gulanikar]

+ Brennan

Ryan - Looping in Brennan to help get you added to the trusted tester program.

Thanks,

Amruta

--

--
Chromium OS Developers mailing list: chromiu...@chromium.org
View archives, change email options, or unsubscribe:
https://groups.google.com/a/chromium.org/group/chromium-os-dev

---
You received this message because you are subscribed to the Google Groups "Chromium OS Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-os-d...@chromium.org.

--

Thanks!

Amruta

[Dan Blah]

Could we also be considered here for inclusion? 

[Francis de Wet]

I too would like to be added to the trusted tester program.  

[Amruta Gulanikar]

+Brennan Alvarez  - Who can help whitelist your domain.

--

--
Chromium OS Developers mailing list: chromiu...@chromium.org
View archives, change email options, or unsubscribe:
https://groups.google.com/a/chromium.org/group/chromium-os-dev
---
You received this message because you are subscribed to the Google Groups "Chromium OS Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-os-d...@chromium.org.

--

Thanks!

Amruta

[dunne...@prairiesouth.ca]

I too would like to have our domain whitelisted. I personally do not need the feature, however we have an Innovation Club that would like to use this.

[ry...@afdahl.net]

I've a personal domain on GSuite and would LOVE to enable Linux for my PixelBook from the Admin Console. It seems I'm out in the cold ( un-managed ) with my Pixelbook.  : (

It would be amazing to be white-listed/invited to this Trusted Tester if available. I would be a great +1 as I would give great feedback. :)

On Tuesday, June 26, 2018 at 7:25:20 PM UTC-7, Dusty Wilson wrote:

[dus...@fullstory.com]

Good afternoon. We would also like to join the trusted tester list for this feature. This is the final piece holding us back from broader ChromeOS/Pixelbook deployment in our enterprise. 

Thank you!

-Dustan

On Thursday, November 8, 2018 at 3:15:33 PM UTC-5, Amruta Gulanikar wrote:

[Robert Brown]

I would also request that my domain be added to the trusted tester program. Happy to both test and provide thorough feedback on usage. Thank you in advance.

[Daniel Erat]

The majority of people on this mailing list are developers who don't have any involvement with the trusted tester program. Please email Brennan directly for requests (unless he suggests a better way).