Dear,
Welcome to the board.
In next reaction we will return your complete script and logon.bat file.
Information for setup your server/client environment:
For an easy upgrade of your clients with f.e. kixtart 4.02 you can use
our installation package kix402update.exe. Always the correct
files will be installed on your clients.
At the moment there are six releases:
- kix362update.exe
- kix363update.exe
- kix400update.exe
- kix401update.exe
- kix402update.exe (final release)
- kix410update.exe (beta)
Each time it will verify the correctness of your release. Incorrect
files will be replaced and missing files will be added. Regardless of
file attributes.
To prevent running more times weare using a control files.
You can easily upgrade it with our iexpress package.
Questions: how?
A way of installing/updating kixtart of your clients: with only one additional statement
For the installation of kixtart at your local workstation we see many version of doing it.
Most statements in your BATch file are using for this duty.
But there is also a way of doing it with a single statement, which doesn't only copy
the required files, but also compare file version information. After completion a logfile
will be created at your local workstation.
Another way of installing/updating kixtart on your clients:
For installing or updating of your clients you can download our packages kix363update.exe,
kix400update.exe or kix401update.exe from our site http:\\home.wanadoo.nl\scripting.
Possible calls in your logon procedure can be:
As first line of your logon procedure you can use one of following formats:
- x:\kixtart\kix402update.exe /q
- %0\..\kix402update.exe /q
- if not exist c:\kix402.ok %0\..\kix402update.exe /q
- \\server\NETLOGON\kix402update.exe /q
Second line can be something like:
- kix32 %0\..\your_script.kix
- kix32 \\server\netlogon\your_script.kix
Results of your BATCH can be:
for network environments (= update package will transfer during each logging on)code:
@echo off
%0\..\kix402update.exe /q
kix32 %0\..\your_script.kix
@echo off
or for dial-up environments (= update package will transfer only once)
code:
@echo off
if not exist c:\kix402.ok %0\..\kix402update.exe /q
kix32 %0\..\your_script.kix
@echo off
or
code:
@echo off
if not exist %windir%\kix402.ok %0\..\kix402update.exe /q
kix32 %0\..\your_script.kix
@echo off
After using above programs there will be created a control
file c:\kix363.ok, c:\kix400.ok, c:\kix401.ok, c:\kix401.ok or
c:\kix402.ok. So it isn't necessary to run the installation
process again, but we advise to update (or better: verify)
kixtart files always.
Also those control files will put in the %windir% directory.
Reason: a security leak for running kixtart from clients.
remarks: SECURITY LEAK for running kixtart from clients
running kix32.exe from a local workstation can have also unwanted effects. An user
can modify or replace your kix32.exe file. f.e. not to run your script but for
reading your script.
For RAS users it is interesting not to download each time the kixtart required files,
but for other users we advise:
always check the kixtart files and update them when necessary before running your KIX scripts.
FIX for SECURITY LEAK:
In our case the first statement of our default logon procedure for network users is always:
%0\..\kix363update.exe /q
and it will guarantee that kix32.exe file will always the correct one.
remarks: performance
- only 150 KBytes will be transfered to your workstation. the package has been compressed.
- always the correct set of kixtart files will be used. during the execution of scripts
the user can already starts working. - during installation or updating kixtart you will not get share violation error or busy file
error. the install.kix scripts runs with his own kixtart version. - for RAS users we create additional authorizations which will run minimum set of script code.
for them the logon procedure containts as statement:
if not exist c:\kix363.ok %0\..\kix363update.exe /q
greetings.
btw: related kixtart topic http://kixtart.org/board/Forum2/HTML/000583.html
btw: be sure no other kix32.exe and DLLs are active on your clients.
