Similar issue for Public Session  crbug.com/895031 

Adding a couple people to CC to help find an owner as this issue is marked as RBB.

My guess is OOBE is not checking IsPinDisabledByPolicy, https://cs.chromium.org/chromium/src/chrome/browser/chromeos/login/quick_unlock/quick_unlock_utils.h?l=37&rcl=756ebd67af1e8c3f97c8d1c6f2987f4faf1dda21.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/1e48a0bb40e77cbd22d1da2f86945c438e798b41

commit 1e48a0bb40e77cbd22d1da2f86945c438e798b41
Author: Alexander Alekseev <alemate@chromium.org>
Date: Fri Nov 02 21:30:47 2018

Chrome OS: First run PIN setup should be shown only when not disabled by policy.

Bug:  901107 
Change-Id: Ieb943ad33a824318ea391b626285e6c4b8a71fc4
Reviewed-on: https://chromium-review.googlesource.com/c/1313929
Reviewed-by: Jacob Dufault <jdufault@chromium.org>
Commit-Queue: Alexander Alekseev <alemate@chromium.org>
Cr-Commit-Position: refs/heads/master@{#605056}
[modify] https://crrev.com/1e48a0bb40e77cbd22d1da2f86945c438e798b41/chrome/browser/chromeos/login/screens/discover_screen.cc

This bug requires manual review: M71 has already been promoted to the beta branch, so this requires manual review
Please contact the milestone owner if you have questions.
Owners: benmason@(Android), kariahda@(iOS), kbleicher@(ChromeOS), govind@(Desktop)

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Please keep this open until it is merged to 71. We absolutely cannot ship this bug in 71, edu and enterprise customers are already hitting it often on beta.

+ kbliecher m71 release manager.

- we absolutely should not ship m71 stable with this issue.
- we really need to get the fix in a m71 beta respin asap so we can confirm it solves for customers.

+ Naveen and Drew for awareness on this one. We need to make sure this is fully resolved for m71 stable or it will quickly become another fire.

Merge approved for ChromeOS M71

Merge of #5 actually depends on merge of  issue #900233 .

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/19e57136c1f9c2098202d9c43aa527ace6d79c15

commit 19e57136c1f9c2098202d9c43aa527ace6d79c15
Author: Alexander Alekseev <alemate@chromium.org>
Date: Wed Nov 07 02:50:35 2018

Chrome OS: First run PIN setup should be shown only when not disabled by policy.

TBR=alemate@chromium.org

(cherry picked from commit 1e48a0bb40e77cbd22d1da2f86945c438e798b41)

Bug:  901107 
Change-Id: Ieb943ad33a824318ea391b626285e6c4b8a71fc4
Reviewed-on: https://chromium-review.googlesource.com/c/1313929
Reviewed-by: Jacob Dufault <jdufault@chromium.org>
Commit-Queue: Alexander Alekseev <alemate@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#605056}
Reviewed-on: https://chromium-review.googlesource.com/c/1321673
Reviewed-by: Alexander Alekseev <alemate@chromium.org>
Cr-Commit-Position: refs/branch-heads/3578@{#558}
Cr-Branched-From: 4226ddf99103e493d7afb23a4c7902ee496108b6-refs/heads/master@{#599034}
[modify] https://crrev.com/19e57136c1f9c2098202d9c43aa527ace6d79c15/chrome/browser/chromeos/login/screens/discover_screen.cc

The following revision refers to this bug: 
https://chromium.googlesource.com/chromium/src.git/+/19e57136c1f9c2098202d9c43aa527ace6d79c15

Commit: 19e57136c1f9c2098202d9c43aa527ace6d79c15
Author: alemate@chromium.org
Commiter: alemate@chromium.org
Date: 2018-11-07 02:50:35 +0000 UTC

Chrome OS: First run PIN setup should be shown only when not disabled by policy.

TBR=alemate@chromium.org

(cherry picked from commit 1e48a0bb40e77cbd22d1da2f86945c438e798b41)

Bug:  901107 
Change-Id: Ieb943ad33a824318ea391b626285e6c4b8a71fc4
Reviewed-on: https://chromium-review.googlesource.com/c/1313929
Reviewed-by: Jacob Dufault <jdufault@chromium.org>
Commit-Queue: Alexander Alekseev <alemate@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#605056}
Reviewed-on: https://chromium-review.googlesource.com/c/1321673
Reviewed-by: Alexander Alekseev <alemate@chromium.org>
Cr-Commit-Position: refs/branch-heads/3578@{#558}
Cr-Branched-From: 4226ddf99103e493d7afb23a4c7902ee496108b6-refs/heads/master@{#599034}

Verified pin unlock menu is not shown to enrolled user.  Fix was verified on veyron tiger flashed with M71 Beta 11151.24.0 71.0.3578.45

Hello team,

I was wondering if there's any update on this issue?

Issue has been fixed and merged to M-71. Are we getting any other user reports here?

I'm still getting this PIN number screen when the chromeboxes start up. I don't see any way to turn that off in our "Marmot" OU, our "OPACS" OU, or our "PUBLIC" OU. 

All of my chrome devices are public session machine. We don't have users logging into them.

On my test chromebox:

Beta Channel gets me to Google Chrome Version 71.0.3578.27 (The PIN issue remains)
Development channel gets me to Google Chrome Version 72.0.3609.3 (The PIN issue is gone, but I am not moving over 100 chrome devices to the development channel)

If you could provide me with a way to get to the Google Chrome Version 71.0.3578.45, I would appreciate it.

Beta channel should now be on 71.0.3578.71 for almost all boards - which chromeboxes do you have?

ASUS Chromebox CN60
ASUS Chromebox CN62
Maybe a few others of the same chassis type

The CN60 should have 71.0.3578.71 Beta available for update now.
Looks like the CN62 is still on 71.0.3578.27 Beta, but it should be receiving an update soon.

Those seems to be good to go now, but I do still have several Samsung Chromebook 2 13" that are still on 71.0.3578.27 (beta channel)