Hi,
FYI: I am not the one at my work who makes changes to the logon script but I have been working with someone who does and I just want to get some opinions on my problem.

Scenerio:
1. This problem only happens on Windows NT workstations (SP 3 and higher)
2. Doesn't always occur - it happens on and off

The problem is that once our login script starts it eventually gets to a portion where it executes kix32.exe
(%windir%\Kix32 %LOGONSCRIPTPATH%\Update.kix)
Then it hangs (the cursor is flashing but nothing is happening)
BUT then I can shut down restart and it could then work fine (or not).

Things that we've tried:
1. Make sure the path evir has c:\winnt at the beginning
2. Ran Kix32 from a cmd prompt - and it's ok
3. Make sure all the kix files are there (sometime we delete them and reboot - the script checks for them then copies them back in - the script will work fine for the next 4 -5 logins then the problem reappears.

Any hints??? Things for me to check on? (very strange that it will work sometimes then other times not a chance)
I have noticed that when it doesn't work the mapped drive (early on in the logon script it suppose to map (set logonscriptpath=%logonserver%\netlogon) is not there. Is there an issue with NT having mapping problems???

Thanks for the help and as I mentioned I am not the one who will be changing the script so please be somewhat 'general' in your replies.

T.