To answer your question, yes we are trying to simulate a mouse movement or a key stroke. But using a command from a sendkey application via a logon script has proven unsuccessful. Citrix still thinks the client is idle.
I will ask out Citrix team about your second question, though they came up with the entire separate farm idea so the exclusion policy doesn’t seem likely.
What you can try is to change the idle timeout directly on ICA listener (MS Terminal Services Configuration console) and then assign the kiosk systems to that server
Not that nice, but maybe a solution. I haven’t tried that myself but the local setting should have a higher priority as the farm setting.
If this does not work a second farm is needed as idle timeout cannot be set via policy (as I found out). So, my first thought will not work. 🙁