Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

My company just deployed a dozen Windows XP touch screens in conference rooms to control video conferencing systems. We're using all-in-one PCs with no keyboard or mouse attached, so the only way to wake from screensaver is to touch the screen, which is of course interpreted as a click.

The problem we're having is that the click is passed through to the top app -- our video conf control system -- causing the user to take some action (like hangup) that they didn't intend.

We do need to have a screensaver, the PCs are turned on 24x7, and the control app is visually very static. We expect a simple bouncing image screensaver to significantly lengthen the productive life of the system.

Is this something we can tweak? The screensaver content is a single bouncing image, so I'd be open to replacing the screensaver, or tweaking the registry, or (best) pushing the change via Active Directory (all the affected systems are already grouped into a specific OU).

share|improve this question
add comment

5 Answers

It sounds ridiculously obvious but... disable the screensaver for those machines via Group Policy?

EDIT:

Why not change to a screensaver that still displays the desktop, but obscures it to help prevent burn in. This would allow the user to see a clean place to "press", and would still protect the display. A perfect example would be the Bubbles screensaver. There are many more like this.

Bubbles Screensaver Screenshot

share|improve this answer
    
We do need to have a screensaver to prevent burn in, since the PCs are on all day, looking at the same app. –  Jeremy Wadhams Nov 3 '09 at 22:17
    
Edited......... –  Izzy Nov 3 '09 at 22:23
add comment

If the touch screen is LCD based then a screensaver is not actually necessary to prevent burn in. You may still be required to use one for security reasons but should not just to increase the life of your LCD.

share|improve this answer
    
Beat me to it by seconds. I was going to say that I haven't run long term burn tests on a modern flat panel computer monitors but I have a number of monitors that display highly static status displays 24x7 and I haven't noticed any burn in\image persistence problems. –  Helvick Nov 3 '09 at 22:33
    
I have a feeling he's going to have a tough time convincing Management of this, regardless of whether it's true or not. –  Izzy Nov 3 '09 at 22:41
1  
This may well vary between makes and models but our local library uses quite recent LCD touch screens and the burn in from the static front page is very obvious, even after just one week. Despite that they refuse to use screen savers, claiming it "confuses people". –  John Gardeniers Nov 3 '09 at 22:50
add comment

OK since we seem to have established that not using a screensaver at all may actually be a bad idea, here's a few left field ideas.

Since this seems like a reasonable problem that needs to be solved ask the vendor to update their app so that it integrates a screensaver behavior that consumes the wake up tap action.

This might sound a bit silly but if you set the screensaver delay to a time that is longer than the average duration of the meetings that use the rooms then the risk of users accidentally tripping an unwanted action should drop substantially.

Tape an overlay to the side of the screen with "Wake up" or "ON" with an arrow pointing to a spot on the screen where no action will be taken. Or a label that looks like the iPhone unlock screen with "Slide to unlock". Obviously not being able to overlay it on top of the touchscreen might present some usability problems.

If you have any half way smart programmers in the company they should be able to throw together a screensaver that will consume the wake up tap for you.

share|improve this answer
add comment

Just a thought... What happens if you wipe the finger along the screen instead of just touching it? It seems to me that should be equivalent to moving the mouse, rather than clicking it. If so, perhaps a little sign or user education might be all that's needed. Hardly an ideal solution but perhaps a workable one?

share|improve this answer
add comment

You could change the screen saver to add a password after it wakes up, that way the click would send you to the password screen rather than the app.
Also this would add security the the situation of always having the computers on.

share|improve this answer
    
The problem I can see with this is that video conferencing rooms in large organisations are used by large numbers of people, and they rarely log into the control machines as themselves (usually perma-logged in using a generic account). You then have to ensure that everyone knows that password, and managing this dissemination of information is a pain. Users often forget their own passwords, let alone some random generic account password. That would leave the option of taping the password to the display, which defeats the security angle –  Izzy Nov 3 '09 at 22:58
    
The computer is only a replacement for what the old infrared remotes could do. If you're in the room, you're allowed to do anything that machine is allowed to do, your presence is authorization enough. –  Jeremy Wadhams Nov 4 '09 at 0:09
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.