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

Issue 681812 link

Starred by 2 users
Status: Verified
Owner:
tnagel@chromium.org
Closed: Jan 2017
Cc:
rsorokin@chromium.org
█ krishna...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Test Chromad with a 3.18 kernel

Project Member Reported by tnagel@chromium.org, Jan 17 2017 
... when build and device are available.

Comment 1 by tnagel@chromium.org, Jan 19 2017

Owner: tnagel@chromium.org
Status: Fixed (was: Available)
Successfully tested enrollment and policies on chell 57.0.2984.0 / 9198.0.0 (canary).

Comment 2 by krishna...@chromium.org, Feb 1 2017

Status: Verified (was: Fixed)
Tested this on Lars:9202.11.0;57.0.2987.19.
Kernel v3.18.0.
Was successfullay able to do a AD Domain Join and Device policies were loaded. 
Was able to sign into an user- User polices were loaded and applied.
Policy Reload of User and Device policies worked.
Will test another device with a 3.18 Kernel when we run our 'multiple device Chromad sanity test pass'.
►

Sign in to add a comment