By default, Windows LPO/GPOs do not run KiXtart scripts as e.g. startup/shutdown/logon/logoff scripts. Scripts are limited to Windows Scripting Host registered script extensions such as .WSH, .JS or Perl/PHP extensions if the appropriate AxtiveX scripting engine is installed. Kixtart does not offer this ActiveX integration into WSH. A standard workaround is to assign a batch file to the script to be launched via LPO/GPO.
However, there is a way to directly launch KiXtart scripts via LPO/GPO without the use of a batch file.
Two steps need ot be performed on the computer that is going to use the KiXtart script. These tow steps will result in the association of a KiXtart script extension with the KiXtart executable to be used to run the script. There are two options to achieve this, either via command-line or via registry modification.
The following two command-line commands will create this association and specify that files with the . KXS (KiXtart Script) are using the WKIX32.EXE (should be located in a directory listed in %PATH%, e.g. %WINDIR%. Otherwise, provide the full path to WKIX32.EXE) and that all command-line switches are being passed into WKIX32.EXE for further interpretation.
Code:
ASSOC .KXS=KiXtart.Script
FTYPE KiXtart.Script=wkix32.exe %1 %*
The same results are achieved by importing the following .REG file which also creates this association.
Code:
REGEDIT4
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\.kxs]
@="KiXtart.Script"
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\KiXtart.Script]
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\KiXtart.Script\Shell]
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\KiXtart.Script\Shell\Open\Command]
@="wkix32.exe %1 %*"
One can now copy KiXart scripts into the appropriate group policy subfolders and select these KiXtart scripts in the group policy MMCs.
A drawback of this method is that users can now execute .KXS scripts by just double-clicking on it.
Edited by sealeopard (2003-12-09 03:53 PM)
_________________________
There are two types of vessels, submarines and targets.
