The bat(ch) file should be in the sysvol/netlogon folder on each domain controller. All others you found do nothing at logon unless they are called upon by the login script or by some other app that might run at logon.

It could also be the bat(ch) file console window that stays open. What happens if you run the command below from a command prompt (I assume you are using Win2K or up and AD)? This way you will see if it is the kix console window or the batch console window that stays open. If all windows close then the console windows is the one screwing things up.
You could do without the batch file and call your kix script directly if there are no Win9x and/or WinNT4 clients left on the network.

 Code:
kix32.exe pathtoyourscript\script.kix (could also be .scr, .txt or whatever)
_________________________
Mart

- Chuck Norris once sold ebay to ebay on ebay.