Left to their own devices, users will unintentionally sabatoge themselves, the net admin and other users.... that's just our human nature. I've been a net admin since 1991 and EE since the late 70's. A lot of water has passed under the bridge. So, this is said from experience. Personally, I like wallpapers and screen savers but either or both can introduce failure points and service disruptions in a pc whether networked or not.
For instance, a background image, if it gets corrupted, can make a windows machine unbootable and you may never stumble onto the cause or solution in a reasonable amount of time. This has happened twice at my customer locations in the last 15 years. For a second instance, background images CAN consume a lot of graphics memory. Not an issue in newer machine since graphics memory has increased with new architectures.... but something to keep an eye on. What you want to be on the watch for is making sure some Lone Ranger (usually a guy type) doesn't use porn images for the background. Check your organization's IT policy. If it ain't in writting, then as an Net Admin, it may not be your place to block the event. Use common sense.
ScreenSavers can be both good and bad. If a user processes database info and a long query is running, a screen saver set to launch in 1 minute might not be a wise choice. Even 5 or 10 minutes may not be wise during a long, interactive database query. ScreenSavers usually are designed to do exactly that... save the screen! The underlying rules often say that all other processing will be either suspended or interrupted. Bottom line? A 7 minute query takes 45 minutes or never finishes and the user wants to blame someone or convince the boss to buy a new, more powerful computer.... go figure...
ScreenSavers downloaded from the web and installed by a user OFTEN contain a lot more than just screen saving images. Running in the background, it isn't unusual to find malware functioning on its own.
The policy I recommend is to disallow non-approved screensavers and set the screensaver timeout at the server (Active Directory Policy Management) to 15 minutes or more depending on the client. It gets locked down and the users cannot alter the launch time. An enforced written policy, to me, is the best approach. You can and should do only so much regarding policies. It's best to have upper level management sign-off on the written policies. The company, the employees and the net admins all know better where they stand and how policies can be administered and enforced.
Larry Martin
DataCom Systems
Austin, TX