It works on a Linux build (ToT=57.0.2985.0).  Later I'll take a look on a real device.

Works for me on 57.0.2984.0 / 9198.0.0 (chell canary).  Does ot still repro for you?

I tested on 58.0.2990.0 (built image with latest code). Reloading policy in Chrome only reloads user policy.

Testing on 58.0.2990.0 / 9215.0.0 (with latest authpolicyd).  In guest mode, there's device policy fetch both during login and when clicking "Refresh policies".

And the same happens for a real user, again both during login and when hitting "Refresh policies":
2017-01-26T14:21:43.342348+01:00 INFO authpolicyd[4461]: Received 'RefreshDevicePolicy' request
[...]
2017-01-26T14:21:44.950388+01:00 INFO authpolicyd[4461]: Received 'RefreshUserPolicy' request

Back to Lutz again.  Please provide detailed repro steps.

After offline discussion: The issue only repros for the very first login after enrollment.  (Reducing priority because of limited scope.)

Offline discussion with Roman: DevicePolicyManager doesn't get started after enrollment.

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

commit ac371d7a8f048986b667636aba153714157dc4e0
Author: tnagel <tnagel@chromium.org>
Date: Tue May 02 10:03:07 2017

Restart browser after Chromad enrollment

The current factoring of BrowserPolicyConnectorChromeOS only allows to
swap out the device policy provider at initialization time, not at run
time.  As a consequence, we end up with the wrong device policy provider
after Chromad enrollment.  A browser restart is the easiest way to fix
this.

BUG= 681817 

Review-Url: https://codereview.chromium.org/2842163002
Cr-Commit-Position: refs/heads/master@{#468592}

[modify] https://crrev.com/ac371d7a8f048986b667636aba153714157dc4e0/chrome/browser/chromeos/login/enrollment/enrollment_screen.cc