I guess that does not get you any closer...
I almost have to wonder if maybe in your testing, you are finding another copy of your BATch file on your path so never get to see the changes.

First off, I don't think you should alter the path and location to the batch file. IMHO it must remain in the default folder for the GPO. In my case that is:
\\mycompany.com\SYSVOL\cacc.local\Policies\{8F913AA1-8559-40E6-893C-776A5EF68637}\User\Scripts\Logon

My GPO logon BATch file is called LOGON.BAT

In my company, each OU gets their own folder under \NetLogon.

Within your LOGON.BAT, put one line that calls (you would probably leave out the OU\ part):
\\mycompany.com\NetLogon\OU\KiX32.exe \\mycompany.com\NetLogon\OU\test.kix

Within TEST.KIX, put simply:
Code:
Break On
MessageBox('Hello World','KiX',36)


Works for me!
_________________________
Give a man a fish and he will be back for more. Slap him with a fish and he will go away forever.