|
According to the user manual, "By default, KiXtart automatically looks for a personal script for the current user ("Username.KIX"). If it does not find one, it looks for the default script, "KIXTART.KIX"."
We do not have any user scripts, we use ONLY the KIXTART.KIX script. Previously, we simply had to enter "[server name]\NETLOGON\KIX32.EXE" at Start\Run or at a Command prompt and it found KIXTART.KIX and ran perfectly. Now, for unknown reasons, it is not running any script at all unless we add "KIXTART.KIX" to the end of the command line. Does anyone have any ideas why this is so?
We are running KIX32 version 4.51 on Windows 2008 R2 servers. Clients are all Windows XP SP3. There are four KIX scripts in the NETLOGON folder: KIXTART.KIX, NEWKIXTART.KIX (will replace KIXTART when we get a new SAN with paths in the very near future), MAPUSER.KIX (used to manually map drives for people in specific situations) and NEWMAPUSER.KIX which will replace MAPUSER when we get the new SAN up and running.
Also in the NETLOGON folder are these files: kix32.dll, kixtart.KX, kx16.dll, kx32.dll and kx95.dll.
| 
