We're having a problem with View (version 5.2, client version 5.3) in that the host machine is running a screen saver, and we don't have on the virtual desktop. If the VM is left unattended for the timeout limit, the screen saver on the host machine starts, but the View desktop fights to remain on the screen and in focus. You can see a very quick blip of the screen saver right at the timeout. What's driving the users nuts is trying to type after this event is nearly impossible because View and something on the host machine are fighting for focus.
I would hope that a host screen saver would simply cover View, and go away when anything was touched, returning focus to View. Our physical machine screen savers are set with a GPO, so users can't even manually disable it before launching View. Granted, when the keyboard entry is acting up, all the users need to do is minimize the desktop, which ends the local screen saver, and reopen. But for some of the users, they're having to do this dozens of times a day, and I can see how it's very frustrating.
So, without disabling all host screensavers, nor changing the behavior of the users, is there a way to make View play nicer?