You've copied kix32 to the clients, but where abouts on the client? I presume this is to "speed up" execution. just make sure that the batch file calls for the kix32.exe from the appropriate location.

By default, when logging in, the netlogon share of the domain Controller is always mapped as the last available drive letter, and hence is *usually* Z:. (I always make my CD-ROM Z: so regardless what other extra HDD's and removeable media I add, the CD always stays the same)

Hence, the example given by Microsoft will "usually" work, but not necessarily always. you should ideally use:
%0\..\kix32.exe %0\..\scriptname.kix
or %windor\kix32.exe %0\..\scriptname.kix (if thats where the .exe & .dll's reside)

What "doesn't seem to work"? No script executio at all? Script fails?

------------------
Paul Moxey
POS & Senior Network Administrator
Taubmans Pty Ltd
Paul_Moxey@taubmans.com.au

_________________________
Paul Moxey POS & Senior Network Administrator BarloworldCoatings (AUST) Pty Ltd