I would discourage to copy the kix32.exe and the kix script to the system32 directory for logon scripts. Copy them to the \\domain\netlogon share (On your domain controller, that is the directory %SystemRoot%\SYSVOL\sysvol\domain.extension\scripts)
If you really wish to work with a batch file, you first try to find out if a Wndows 9x or a Windows NT is login on
for Win9x, you use
%0\..\wkix32 %0\..\KIXTART.KIX
for Win NT, you use
wkix32 KIXTART.KIX
Here is an example of how to veify for the operations system:
Frequently Asked Questions Regarding The Windows 2000 Command Processor
Q. What commands can I use in a logon script?
A. A logon script can use any command supported by the client O/S.
If you have a mixture of Windows NT-based clients and other Windows clients, you can test if the client platform is Windows NT-based by including the following statement:
if "%OS%"=="Windows_NT" goto winnt
If you need to test for a specific operation system, the following commands should work on all Microsoft operating systems:
ver | find "Windows XP" >nul
if not errorlevel 1 goto WXP
ver | find "Windows 2000" >nul
if not errorlevel 1 goto W2000
ver | find "Windows NT" >nul
if not errorlevel 1 goto WNT
ver | find "Windows 98" >nul
if not errorlevel 1 goto W98
ver | find "Windows 95" >nul
if not errorlevel 1 goto W95
ver | find "Windows ME" >nul
if not errorlevel 1 goto WME
ver | find "OEM Service Release" >nul
if not errorlevel 1 goto WOEM
ver | find "MS-DOS" >nul
if not errorlevel 1 goto DOS
::Unknown
echo ERROR - What are you running?
goto END
:WXP
goto end
:W2000
goto end
:WNT
goto end
:W98
goto end
:w95
goto end
:WME
goto end
:WOEM
goto end
:DOS
:end
