I'm not satisfied with how kix402update.exe and wkix402update.exe operate. I tried to work through them with MCA but it fizzled out.

In an NT environment it's not really needed anyway. All you really need is to check for KIX32.EXE and WKIX32.EXE in %windir% if you choose to install local at all. Regular users don't normally have rights to install to %windir% anyway so you'd have to schedule an admin script to do it.

You could put it in your image but when you roll out the next version you're back to square one.

I use the following in my logon.bat to log update failures so my admin script can pick it up.

code:
%windir%\system32\fc.exe /lb1 "%windir%\kix32.exe" "\\ff_adm1\update\KiX4.02\kix32.exe" 1>nul 2>nul
IF ERRORLEVEL 1 GOTO ERRORLOG_NT
GOTO NT_OK

:ERRORLOG_NT
ECHO ======KIX 4.02 UPDATE FAILED====== >> \\ff_adm1\update\Logs\LogonError.log
NBTSTAT -S |FIND /I "<03>" >> \\ff_adm1\update\Logs\LogonError.log
ECHO ================================== >> \\ff_adm1\update\Logs\LogonError.log

:NT_OK
_________________________
Give a man a fish and he will be back for more. Slap him with a fish and he will go away forever.