Cameron,

You can do what you need through a combination of techniques.

First, create a simple Kix script that updates the registry with standard WriteValue() commands. Test it to verify that it works as intended.

VERY IMPORTANT!!! Use Dim to declare all of your variables in your script!
You can use the commands that Shane presented earlier. You don't need to set Break On/Off as this is inherited from the main script. If you read the manual, you will see that external scripts that are CALLed are most efficient, but care should be taken to insure your variable names are unique. A simple way to do this is to insert an underscore at either the beginning or end of your var name. For example: $_Null or $Null_. You can view the latest version of the manual on my web site.

Once your script to update registry values has been tested, simply copy it to the NetLogon share where the Kixtart.Kix file is and then edit the LOGIN.INI file, adding the following section:
 Code:
[REG_UPDATE]
CLASS=COMMAND
METHOD=CALL
PATH=regupdate.kix
This will run the "regupdate.kix" script by calling it directly from the login script. This eliminates the need to invoke Kix32 again and results in faster processing. It also depends on full variable declarations and no global varname conflicts. See the README.TXT file for a full list of variable and function names used in the script.

The example above runs for all users on all computers. Use the appropriate parameters to control execution by group, OU, computer OU, etc..

Also, the following isn't quite correct:
 Code:
[COMMAND definitions]
CLASS=COMMAND
PATH=\\pcc-trackit2\TrackIt8\Audit32.exe
PRIV=null
COMPUTEROUS=!servers,!Domain Controllers,!pamplincom\servers
GROUPS=domain users,
"COMMAND Definitions" should be a unique name, such as "Audit32". Also, PRIV should be either GUEST or ADMIN. If it isn't required, remove it.

Glenn
_________________________
Actually I am a Rocket Scientist! \:D