Running KiXtart

KiXtart can be run manually or automatically during the logon sequence.

To run KiXtart manually

At the command prompt, type the following command:


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". You can override this behavior by specifying one or more scripts after Kix32.exe on the commandline.



The global state of KiXtart is maintained as long as the KiXtart process runs. This means that if you specify multiple scripts on the commandline, any global variables and user-defined functions you have defined in a script will also be available to any subsequent scripts.


Default extensions

If you do not include an extension with a scriptname, KiXtart attempts to use two default extensions: .KX and ".KIX". Note that KiXtart 2010 no longer uses the ".SCR" extension.


KiXtart also supports declaring variables at the command prompt, as demonstrated in the following example:


kix32 Demo.kix $Key=HKEY_LOCAL_MACHINE\Software

For information about valid variable names and values, see "Dynamic Program Variables" later in this document.


KiXtart supports the following commandline switches:


Enables debug mode.


Refreshes the group-membership cache.


Invisible mode. Prevents KiXtart from displaying a console window.

Note: only available in the Windows version of KiXtart.


RPC search order. Determines the order in which KiXtart attempts to locate a KXRPC server. See the description of the KXRPC service for full details.


Tokenizing mode. This will cause KiXtart to pre-tokenize the script(s) instead of running them.

See the paragraph on pre-tokenizing for more details.


(Un-)lock password. This option enables you to specify a password to encrypt or decrypt a pre-tokenized script. The password can have any length.

See the paragraph on pre-tokenizing for more details.


Display KiXtart command line usage.


To run Kix32.exe automatically when a user logs on

On Windows 2000/XP:

1. Open Users and Computers and select the user.

2. Right-Click, select Properties, and then select the Profile tab.

3. In the Logon Script box, type "Kix32".

On Windows NT:

1. In User Manager, select the user.

2. On the File menu, click Properties, and then click Profile.

3. In the Logon Script Name box, type "Kix32".



For Windows 9x clients, do not specify a KiXtart script in the Logon Script Name box in the User Environment Profile dialog box in User Manager. To specify a script for Windows 9x clients, use a batch file as the logon script, and start KiXtart from the batch file.


Running KiXtart from a Batch File

Kix32.exe can be run from a batch file that is used as the logon script for the user. For example, if Kix32.exe is in the root directory of the NETLOGON share, the batch file might contain the following commands:







Use of the syntax %0\..\ is discussed in Knowledge Base article Q121387.


If Kix32.exe was installed on the client's local hard disk, you must refer to the local directory, for example: C:\Kixtart\Kix32.exe.


On computers running Windows 9x, KiXtart can also be started by using Lmscript emulation. For more information, see "Running KiXtart with Lmscript Emulation" later in this document.