There is a small network on a domain. Not too long ago a new machine was added. The OU that the user is linked to was part of an OU that is, among other things, not allowed to change desktop background. However, come to find out, the new computer user was able to change their background.
Unsurprisingly, this caused much angst among co-workers, so I worked furiously to correct the problem. I even went so far as to create a shiny new bg for everyone to use.
I went in and edited the policy for this OU to reflect the new settings. Upon running gpupdate and checking gpresult on the computer, a reboot led to the shiny new bg as expected. I did the same on another users computer (who had also managed to change their BG), but this time upon reboot, I was still met with their thumbnail sized bg staring at me.
After some time on that machine fiddling with registry settings and whatnot, I finally got into gpedit as admin and manually set the BG (I could NOT get rid of the background otherwise; had locked myself out of changing it via GP). Once the old one was gone, I went back in and reset the local gp desktop bg setting as not set. Rebooted, and the background was there as set in OU GP.
Today, though, I come in and the new computer is back to the BG they set before this all exploded. I run through RSOP on that user, and all checks out.
How could this computer not be complying with the OU GP? Am I missing a setting or something that allows (old) local policy to supersede the OU policy?