Firewall blocking Input Director before login
We are testing the use of keyboard and mouse sharing application Input Director. It works by installing it on a two separate PCs, a master and slave PC with the keyboard and mouse physically connected to the master PC which are shared to the slave PC via the application.
I've allowed the inbound ports in the firewall policy and it is working fine on WinXP and Win7, but it is working only after the user has logged into the slave PC. (which defeats the purpose because you have to connect another keyboard to log in the slave PC) It does not work pre-login, and when I log in manually, I notice it starts working immediately when the SEP client shield icon shows up in the system tray.
When I temporarily move the PC into a group in SEP without the firewall policy applied, the application works before login allowing them to mouse over to the slave PC and enter their login credentials (so Input Director apparently runs as a service).
In the firewall group, "Allow IP traffic" is selected in the "Unmatched IP Traffic Settings" area of Server Control, and "Block all traffic until the firewall starts and after the firewall stops" is not checked in the Security Settings tab of the group's General Settings.
Are there any other settings I can modify? I'm not looking to enable all traffic before the firewall stops, I'm just looking for it to apply my firewall policy ruleset pre-login so the rule allowing Input Director will take effect and allow Input Director to work properly.