Hey everyone, need some help here.
We have a couple of Windows ARM devices. I pushed a hexnode policy mainly for personalization-related settings, but users are suddenly unable to change their wallpaper and screensaver options.
What’s confusing is I didn’t actually intend to configure anything related to wallpaper or screensaver. I only remember going into that section while reviewing the policy. Any idea why it’s behaving like this?
44 Views
I’m not completely sure, but I’ve seen policies behave like that sometimes.
Even if a setting looks “not configured”, Windows can still behave like something is controlling it once the profile hits the device.
Could be one of those silent restrictions.
That’s what I assumed too. I went back and tried explicitly allowing it, even set a wallpaper just to test. But it still didn’t take effect on the device.
Users still couldn’t change wallpaper, and nothing seemed to apply properly.
Just to confirm one thing. In the Windows policy, did you click on the Configure button for the wallpaper or screensaver section, but leave it without setting anything and then associate the policy to the devices?
In Hexnode, if you open a section using configure, the platform can treat it as “configured” even if you didn’t fill in values, and that can end up applying restrictions.
For the current devices, also try restarting once after the policy change. Some personalization settings don’t reflect immediately without a reboot.
That explains it. I did click configure, but I thought it wouldn’t count as a change unless I actually set something.
Restarting worked as well. Thanks for clearing this up, @stevenhere.
Don't have an account? Sign up
