When considering where to install the KiXtart RPC service, you must decide how KiXtart locates servers running the KiXtart RPC service. The simplest choice is to install the KiXtart RPC service on all the logon servers in the logon domain, which automatically provides load balancing.
If the KiXtart RPC service cannot be installed on all logon servers, KiXtart must be directed to the server(s) running the service. This can be achieved using one of the following options:
· Setting an environment variable before running KiXtart .
· Adding a subkey to the registry of Windows 9x clients.
· Adding an initialization file to the KiXtart startup directory.
These methods are described in full in the following sections.
By default, KiXtart tries the methods in the order specified above. If none of the methods result in a connection with a KXRPC service, KiXtart attempts to connect to the KXRPC service on the logonserver. Optionally, the order in which the methods are attempted can be changed using the RPCSearchOrder commandline parameter (‘/r’).
The RPCSearchOrder parameter expects a string of characters indicating the search order, where each method is represented by a single letter:
e environment
r registry
i INI file
l logonserver
Examples:
KIX32
<script> /r=li ;
attempt logonserver first, then INI file
KIX32
<script> /r=er ;
attempt environment first, then registry
KIX32
<script> /r=r ; attempt only the
registry
Note that previous versions of KiXtart always first attempted to connect to the KiXtart RPC service on the logon server, followed by the settings in the environment, registry and/or INI file.