It seems like this is expected. The policy is marked as 'external', which seems to mean that our cloud servers attach some data that a Windows admin would not be able to set easily. The ADMX writer ignores external policies:
if policy_type == 'external':
# This type can only be set through cloud policy.
return
For the wallpaper policy, the cloud server computes a SHA-256 hash of the wallpaper image, so that Chrome can verify if the image is actually the expected one. This is a security feature.
Right now, all 'external' policies are images + hashes. There are actually online tools available to compute SHA-256 hashes. I'm wondering whether an AD admin could just use these to compute the hashes and the 'external' flag could be waived.
Afaiu, the definition of "external" types is really just a hash and an URL. Any Windows admin could re-create them, it's just a little more work compared to using CPanel which does it automatically. Thus I think you're right and we should include "external" policies in our ADMX template.
Comment 1 by tnagel@chromium.org
, Aug 17 2016