Recommended Posts

I work for a high school as a computer technician. Me and the other tech want to set a specific wallpaper that will display on all computers when an user is logged in. We plan on using a GPO to enforce this.

We tried using a registry setting to change the wallpaper at login. However, after they log in, they can still change it. We have display properties disabled, but the students found several programs that still let them change the wallpaper.

Is there any way to absolutely force the wallpaper, with no way whatsoever to change it? A GPO is majorly preferred, but if there is something we would have to edit on the individual computers (like a third party program or something that can't be set through GPO), that wouldn't be too much of an issue.

Link to comment
https://www.neowin.net/forum/topic/699048-forced-wallpaper-via-a-gpo/
Share on other sites

Did you set it in

GP>User Config>Admin template>desktop>active desktop> allow only bitmapped wallpaper /active desktop wallpaper

GP>User Config>Admin template>control panel>display> prevent chaging wallpaper

I -think- thats how I stoped my users I can't see my GP as I got made redundant but looking on my 2k3 server it looks right.. let me know

Did you set it in

GP>User Config>Admin template>desktop>active desktop> allow only bitmapped wallpaper /active desktop wallpaper

GP>User Config>Admin template>control panel>display> prevent chaging wallpaper

I -think- thats how I stoped my users I can't see my GP as I got made redundant but looking on my 2k3 server it looks right.. let me know

It seems that we already tried all of those. I checked every setting in our group policy and all of those were already enabled and applied to the computer labs.

They do work quite well, but it seems that people are still able to override them. Even Firefox, if you right click on an image on a webpage, you can still set it as the wallpaper, even with those policies applied.

We just tried this GPO on a single pc:

User Configuration> Administrative Templates> Desktop> Active Desktop> Active Desktop Wallpaper

We enabled that, and than changed the path to a local wallpaper. It worked, and anything we threw at it couldn't change the wallpaper. However, it was logged in as a local account.

We logged out of the local account, and into a domain account (a test account with student permissions). The wallpaper didn't even apply, and we were able to change it with ease using the third party programs and Firefox.

Tony (the other tech) than logged in as his non-administrator account, and the wallpaper did apply, and he again was unable to change it.

It probably is worth noting that every account has redirected folders and roaming profiles. The tech people (Tony and I) are the only exception to this rule (we use flash drives instead).

So long story short:

1) We used a GPO to save this setting

2) The accounts that do not have redirected folders or roaming profiles are effected by this GPO, and can't change wallpapers, but that would be pretty much me and one other person.

3) Everyone else (who does have redirection and roaming) is not effected by this GPO.

It seems that the issue is with the roaming profiles and folder redirection. Any ideas?

The issue is not that you use roaming profiles and folder redirection, the issue is that the domain account overrode the local account settings you made in the local GPO. Make a test OU in the AD and do your tests with that. Never test a domain policy with a local account, nor ever test a policy made locally with your domain account. A test OU costs you nothing, so make them and use them. Test accounts, too.

That is what I thought at first, I thought the domain's GPOs were overriding the local ones, but like I said, the other tech was able to log into his account (domain user, non-administrator, no roam or redirect) and the local GPO applied to him. So we did manage to get the local GPO to apply to a Domain user.

We essentially did try that, to the same results.

We did try using the GPO on a domain level, and applying it to the container that our test computers are in, and seemed to have even worse luck than a local policy. We could not get the wallpaper to apply to a single account

What would happen if you created a new computer OU. created a new user & applied a group policy to that OU does that work?

Ah! If I remember correctly I had to apply the GPO to the User & Computer. I don't know why but I'm sure it worked.

BTW Joey H: where on Earth are you?

We essentially did try that, to the same results.

We did try using the GPO on a domain level, and applying it to the container that our test computers are in, and seemed to have even worse luck than a local policy. We could not get the wallpaper to apply to a single account

You can't apply a User Configuration GP to a computer. That would be a very large mistake. You apply User Configs to user objects, and Computer Configs to computers.

u2_storm: I'm on the part that isn't an ocean. More specifically, St. Louis metro.

On Tuesday and Wednesday, I had a few problems I had to deal with (one of our servers was down, and we had to get a computer lab moved), so I didn't pay much attention to the wallpapers. I'm gonna try the new computer OU on Monday and hope it works. I'll let you all know. But I do appreciate all the help so far. Thank you :)

http://support.microsoft.com/kb/327998

Following the above instructions, they will not be able to change the wallpaper in IE but will be able to in Firefox. Even of they change it in Firefox, the wallpaper will reset back to gpo defined wallpaper after reboot or logoff/logon. I have the same problem at my job so I feel your pain :/

Edited by VRam

Or just leave it alone. what harm to work can a picture on a desktop do? They allow users to feel relaxed and will allow them to work in an environment that is familiar to them, increasing their productivity. Forcing a boring same wallpaper every login is silly and boring.

Or just leave it alone. what harm to work can a picture on a desktop do? They allow users to feel relaxed and will allow them to work in an environment that is familiar to them, increasing their productivity. Forcing a boring same wallpaper every login is silly and boring.

Its a distraction. Our kids should be focusing on their work and not searching the net for a the latest pic of 50 cent or the newest Ferrari to set as their wallpaper. People also tend to frown on their PC greeting them with a pornographic image when booted. I like keeping all the machines uniform and neat and since I'm the one who has to fix what they screw up, I feel I have a right to make it so.

Or just leave it alone. what harm to work can a picture on a desktop do? They allow users to feel relaxed and will allow them to work in an environment that is familiar to them, increasing their productivity. Forcing a boring same wallpaper every login is silly and boring.

Leaving it to the user could contravene the company's AUP. Don't spout crap about a work environment you don't understand.

Not sure why the wallpaper can be changed despite the group policies, but how about overriding the default permissions for the registry key (whatever it is) that defines the wallpaper currently in use? I would *think* that if a user doesn't have sufficient rights to update the key--whatever the means used--then a new wallpaper couldn't be specified...

I thought I found the magic bullet when someone on the net suggested unregistering the shimgvw.dll (removes the "set as desktop background" context menu, but found that also disables the Windows picture and Fax viewer which makes the trick useless. I guess you could install another picture viewer, but thats just another program to maintain. Microsoft should fix the group policy setting to do what it claims to do prevent changing wallpaper.

Or just leave it alone. what harm to work can a picture on a desktop do? They allow users to feel relaxed and will allow them to work in an environment that is familiar to them, increasing their productivity. Forcing a boring same wallpaper every login is silly and boring.

We have many complaints from teachers about wallpapers. There are some students who spend way too much time looking for new wallpapers and not paying attention to their classwork. Also, alot of students seem to have no sense of decency. I've seen wallpapers containing nudity, pornography/hentai, racism, sexism, drug use, just about everything that someone could find highly offensive. The teachers do send students out of class when something like this comes up, and the students do receive discipline, but we don't want it there in the first place. Even if it is not inappropriate, students like to show off their wallpapers, which creates distractions in class.

Not sure why the wallpaper can be changed despite the group policies, but how about overriding the default permissions for the registry key (whatever it is) that defines the wallpaper currently in use? I would *think* that if a user doesn't have sufficient rights to update the key--whatever the means used--then a new wallpaper couldn't be specified...

To my understanding, registry editing is pretty much restricted. The users can't directly access the registry, and the fields that they can edit are very limited in number. I would believe that the registry strings that control the wallpaper would be locked, but if they aren't, that could be a pretty big hole right there. That is defiantly something I will talk to the other tech about, and we'll investigate it.

Edited by Joey H
To my understanding, registry editing is pretty much restricted. The users can't directly access the registry, and the fields that they can edit are very limited in number. I would believe that the registry strings that control the wallpaper would be locked, but if they aren't, that could be a pretty big hole right there. That is defiantly something I will talk to the other tech about, and we'll investigate it.

I don't suspect that students are directly editing the registry, but whatever means they use to change the wallpaper, would run using the same security privileges as that user.

So if you remove the privileges for the registry key for UserX, then it doesn't matter *how* UserX tries to change the wallpaper (desktop properties, Use As Wallpaper in a browser, etc)--all those methods should fail because the process that attempts to write the new value is also running as UserX.

We did eventually manage to stop people from changing their wallpapers. It's a fairly crude method, but it does work well.

There were two ways people were changing wallpapers:

1) Mozilla Firefox

2) Third party wallpaper managers

I don't know exactly how, but the other tech managed to lock "firefox wallpaper.bmp", so that if someone tried to change their wallpaper in firefox, it would not change. I think he found a way to make the file read only, and so that people can't change the read-only status. I don't know how he pulled that off, I wasn't there that day.

The third party programs were easy. Students don't have permission to write any data to program files, they only have read only access. The same goes for the windows directory. So the easiest solution was to use a GPO to block all programs not located in C:\Program Files, C:\Windows, or specific read-only shares located on one of our file servers.

It's not the best solution, but so far it seems to be taking very good care of the wallpaper issues. Furthermore, students were installing games into their documents folder, and that took care of those games too.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • A 13 billion year old secret about our Universe's origin was revealed by Sayan Sen Image by Pascal Küffer via Pexels Researchers at the Max-Planck-Institut für Kernphysik (MPIK) in Heidelberg had recreated a key chemical reaction from the early universe, producing results that could change scientists' understanding of how the first stars formed. The study focused on the helium hydride ion (HeH⁺), which is widely regarded as the first molecule to form in the universe. Scientists believe HeH⁺ appeared around 380,000 years after the Big Bang, when the universe had cooled enough for electrons and atomic nuclei to combine into neutral atoms in a period known as recombination. This marked the beginning of chemistry in the cosmos. Immediately after the Big Bang about 13.8 billion years ago, the universe was extremely hot and dense. As it expanded and cooled, hydrogen and helium became the dominant elements. Once neutral helium atoms formed, they could react with ionised hydrogen nuclei, or protons, to create helium hydride ions. Although simple in structure, HeH⁺ played an important role in the young universe. It was the first step in a chain of reactions that eventually produced molecular hydrogen (H₂), a molecule made up of two hydrogen atoms and now the most abundant molecule in the universe. Molecular hydrogen later became a key ingredient in the formation of the first stars. At the time, the universe had entered a phase often called the cosmological "dark age." Matter had become transparent to light following recombination, but there were still no stars or galaxies producing visible light. Several hundred million years would pass before the first stars appeared. For those first stars to form, large clouds of gas had to collapse under their own gravity. To do that, the gas needed to cool by releasing energy. While hydrogen atoms can help with this process at high temperatures, they become less effective below about 10,000 degrees Celsius. Molecules can continue the cooling process by releasing energy through rotational and vibrational motions. Scientists have long considered HeH⁺ a potentially important coolant because of its comparatively large dipole moment, a property that describes how electric charge is distributed within a molecule and allows it to release energy efficiently. The amount of helium hydride present in the early universe may therefore have influenced how easily the first stars could form. At the same time, HeH⁺ was constantly being destroyed. Under primordial conditions, its main destruction mechanisms were recombination with free electrons and chemical reactions with hydrogen atoms. These reactions ultimately helped produce molecular hydrogen, linking the formation and destruction of HeH⁺ to the chemistry that shaped the early universe. For many years, theoretical studies suggested that reactions between HeH⁺ and hydrogen atoms would become much slower at low temperatures. Scientists believed there was an energy barrier along the reaction pathway that reduced the chances of the reaction taking place in the cold conditions of the early universe. The new study suggests otherwise. To investigate the process, researchers recreated a closely related reaction using deuterium, a naturally occurring isotope of hydrogen that contains one proton and one neutron in its nucleus. When HeH⁺ collides with deuterium, it forms an HD⁺ ion and a neutral helium atom. This allows scientists to study the reaction in a controlled way while closely mimicking the behaviour of the original reaction involving hydrogen. The experiments were carried out at the Cryogenic Storage Ring (CSR) at MPIK, a specialised facility designed to recreate conditions similar to those found in space. Researchers stored HeH⁺ ions in the 35-metre storage ring for up to 60 seconds at temperatures just a few kelvins above absolute zero and merged them with a beam of neutral deuterium atoms. By adjusting the speeds of the two particle beams, the team measured how the reaction rate changed with collision energy, which is directly related to temperature. The researchers found that the reaction rate remains almost constant as temperatures decrease. In other words, the reaction does not slow down at low temperatures as earlier models predicted. “Previous theories predicted a significant decrease in the reaction probability at low temperatures, but we were unable to verify this in either the experiment or new theoretical calculations by our colleagues,” explained Dr Holger Kreckel of MPIK. “The reactions of HeH⁺ with neutral hydrogen and deuterium therefore appear to have been far more important for chemistry in the early universe than previously assumed,” he continued. According to the researchers, the reaction appears to be barrierless, meaning there is no energy obstacle preventing it from taking place efficiently even at very low temperatures. The findings support recent theoretical work led by physicist Yohann Scribano, whose group identified an error in a widely used potential energy surface, a mathematical model used to describe how the energy of a system changes during a chemical reaction. The error appears to have caused previous studies to significantly underestimate reaction rates under primordial conditions. The new calculations closely match the experimental results. Together, they suggest that helium chemistry in the early universe may need to be re-evaluated. Because molecules such as HeH⁺ and molecular hydrogen played an important role in cooling primordial gas clouds, the findings could help scientists build more accurate models of how the first stars formed. By showing that helium hydride was likely destroyed more efficiently than previously thought, the study offers new insight into the chemical processes that shaped the universe during its earliest stages and helped set the conditions for the emergence of the first stars. Source: Max-Planck Institute, EDP Sciences This article was generated with some help from AI and reviewed by an editor. Under Section 107 of the Copyright Act 1976, this material is used for the purpose of news reporting. Fair use is a use permitted by copyright statute that might otherwise be infringing.
    • "What an interesting smell you've discovered"
    • It could EASILY be 70 for the base game BUT + lots of FOMO to make it up to 100-120, like a few days Early Access, online money, pre-order bonus cars, weapons, missions, clothing, avatars or profile stuff, etc... And still WAY TOO MANY people would buy those and make Rockstar insane money.
    • Just to understand: your solution to getting rid of an online password manager is...another online password manager?
    • Cjam 2.5.0.0 by Razvan Serea Cjam is a lightweight and fast MP3 editor for Windows that lets you cut, join, and edit MP3 files without re-encoding. This means your audio quality remains untouched, and edits happen instantly. Cjam is ideal for quick, lossless edits—whether you're trimming music, combining tracks, or preparing audio for learning tools or podcasts. It features batch processing, scripting support, cue and playlist file handling, and a simple interface. Cjam is perfect for anyone who needs efficient MP3 editing without the complexity of full audio suites. Cjam requires a PC running Windows 10 or later and Microsoft .NET 6.0 or later. Key features for Cjam: No Re-encoding: Edit MP3 files without losing quality. Cut and Join MP3: Easily cut, trim, and combine MP3 tracks. Batch Processing: Edit multiple files at once for faster workflows. Scriptable Interface: Automate tasks with a custom command language. Cue and Playlist Support: Handle CUE and playlist files for seamless audio management. Fast and Lightweight: Quick processing with minimal system resources. Lossless Audio Editing: Ensure your edits don't affect audio quality. Simple User Interface: Clean, intuitive design for easy navigation. File Format Support: Works with MP3, Cjam-specific file formats (CJAMC, CJAMJ, CJAM). Cjam 2.5.0.0 changelog: Added clipboard-based import/export support for mp3DirectCut Added clipboard-based export support for REAPER Added support for naming IMP3 elements Changed the Reset behavior to preserve Undo/Redo history; use Shift key + Reset button to clear it Added a new command parameter (qcp) Added 8 new entries to lang.txt (main_c124-126, main_d150-151, main_m082, vme_c014, vme_d005) Fixed a bug where the il parameter was incorrectly applied when pasting VMP3s into the main list Fixed several other minor bugs Download: Cjam 2.5.0.0 | 1.4 MB (Freeware) Links: Cjam Home Page | Cjam Manual | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • Dedicated
      JuvenileDelinquent earned a badge
      Dedicated
    • First Post
      DrWankel earned a badge
      First Post
    • Reacting Well
      DrWankel earned a badge
      Reacting Well
    • Week One Done
      Supreme Spray LV earned a badge
      Week One Done
    • Week One Done
      Genuinetonerink- Dubai earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      504
    2. 2
      +Edouard
      163
    3. 3
      PsYcHoKiLLa
      91
    4. 4
      Steven P.
      75
    5. 5
      Michael Scrip
      72
  • Tell a friend

    Love Neowin? Tell a friend!