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.

This driveletter is used by KIX in the initial running of the script.

What is in the variable %LOGONSCRIPTPATH% ?

Are you sure that all domain controllers have the same files in their NETLOGON share?

Could you post (some of) the script 'UPDATE.KIX' ?

------------------
Greetz,

Roger the Young
------------------------
The code is out there...
------------------------
http://home.wanadoo.nl/r.s.m.s.dejong/Kixtart

------------------------

[This message has been edited by DrillSergeant (edited 29 January 2001).]

When the logon script runs fine I notice that the z: is mapped to the logonserver\netlogon. (when it doesn't work I don't see the z: or any other network drive mapped)

The part of the logonscript that maps the netlogon directory is
:OS_IS_NT
Set LOGONSCRIPTPATH=%LOGONSERVER%\NETLOGON

Apparently all the domain controllers have the same files on them.

I'll have to check for the update.kix to see if I can get the code for it. Do you have any suggestions on what I should look for in the update.kix? (you mentioned that kix uses z: "This driveletter is used by KIX in the initial running of the script.")

Thanks,
T.

Explanation courtesy of TechNet
------
Basically %0 is the current file along with its path (absolute or relative (UNC) path). The \..\ will back you off of a file, the same way that it backs you down a directory tree.
So if I read Ben's scenario correctly...
during logon having :
\\ADomainController\NETLOGON\users\Logon.bat

running the command:
Call %0\..\ThatFile.bat

will be translated to:
Call \\ADomainController\NETLOGON\users\Logon.bat\..\ThatFile.bat

which is the same as running the command:
Call \\ADomainController\NETLOGON\users\ThatFile.bat
---------------------------------