No derailment - just taking a siding. 
Replacing the login.bat content with a call to Kix is a step in the right direction, and a step that required little effort to implement (the .KIX login script not withstanding). This allowed you to easily migrate an entire environment to a new script in one step.
The next step would be to change a few users to reference the script directly, eliminating the batch file. A few minutes to hour of effort to eliminate the bat file from the remaining users reduces unnecessary complexity. The benefit will be when you need to troubleshoot a problem. Fewer layers means easier troubleshooting.
FYI - the reason that the leading "\" isn't needed and that simply specifying "kix32.exe kixtart.kix" in the user login profile works is that the netlogon share (\\domain\netlogon) is inserted at the beginning of the PATH variable during logon, so that is the FIRST place that the OS looks for commands. (this is one of the reasons that subfolders are discouraged - they won't be searched!)
Thus, if all files relative to the login process are directly in the Netlogon share, the commands can be called without any explicit path parameters and will execute as expected.
Glenn
_________________________
Actually I
am a Rocket Scientist!
