#97874 - 2003-01-22 11:21 AM
kix32 vs 2k/XP scripting
|
nick0055
Lurker
Registered: 2002-05-29
Posts: 3
|
I need some pointers as to why my company should go for kix32 rather than 2k/ XP scripting for logon scripts. We are NT4 at present but will upgrade beginning of 2004 to XP pro or 2k. Any for and against tips would help especially for kix32.
|
|
Top
|
|
|
|
|
#97876 - 2003-01-22 01:15 PM
Re: kix32 vs 2k/XP scripting
|
Radimus
Moderator
Registered: 2000-01-06
Posts: 5187
Loc: Tampa, FL
|
With all things being equal, either of them will do what you want.
However, all things are not equal. you will have to deploy kix to all of your clients (not hard, just one exe.. bext practice)
WSH is a bit harder to use/code and doesn't have the functionality that kix does... for the equivalent functionality, you would VBS... which is that much harder to code (but not much)
then you have support issues... you aren't going to get it for free for either product, except for boards like this one... and I'm not aware of any vbs boards, but there are undoubtedly some out there.
Your network, your call...
|
|
Top
|
|
|
|
|
#97878 - 2003-01-22 01:34 PM
Re: kix32 vs 2k/XP scripting
|
Radimus
Moderator
Registered: 2000-01-06
Posts: 5187
Loc: Tampa, FL
|
you can run it from netlogon... but that has had some issues, and in many cases running it locally is faster
|
|
Top
|
|
|
|
|
#97882 - 2003-01-23 12:08 AM
Re: kix32 vs 2k/XP scripting
|
Kdyer
KiX Supporter
Registered: 2001-01-03
Posts: 6241
Loc: Tigard, OR
|
Running scripts..
Copy the executable (KIX32.EXE) to the client..
We are using a modified version of KixnnnUpdate.EXE from http://home.wanadoo.nl/scripting/ .. The modified version just updates the client with the KIX32.EXE on the client for NT-Based client. If you are running a Windows 9x, it copies the DLLs (KX16,KX32,KX95).
Run the script from the server or otherwise, you will forever being trying to catch up the clients with what is out there..
Kent
|
|
Top
|
|
|
|
|
#97885 - 2003-01-23 04:46 AM
Re: kix32 vs 2k/XP scripting
|
Radimus
Moderator
Registered: 2000-01-06
Posts: 5187
Loc: Tampa, FL
|
We left WSH enabled, as we use it extensively in scripts (and the netadmin types are leery about disabling stuff on client desktops, YNK what a client may require)... but we do a few other preventative measures...
we keep AV updated on mailserver
we block all 'executable' and 'script' type mail attachments
we block access to hotmail, yahoo mail, and any other 3rd party mail site we can find.
AV is verified (engine, Dat and service) at every logon
etc.
|
|
Top
|
|
|
|
#97886 - 2003-01-25 04:31 AM
Re: kix32 vs 2k/XP scripting
|
MCA
KiX Supporter
Registered: 2000-04-28
Posts: 5152
Loc: Netherlands, EU
|
Dear,
Current available iexpress update packages are
- kix362update.exe
- kix363update.exe
- kix402update.exe
- kix410update.exe
- kix411update.exe
- kix412update.exe
- kix420update.exe (RC 1)
Question: can I installed only the required kixtart files on our client?
f.e. only kix32.exe for windows NT4/W2K/XP environment.
Answer: YES
How?
You only need to specify the environment variable kix-only-required
before calling iexpress update package.
For more information see next text (parts are a copy of earlier posts).
Based on the input from Kent Dyer & Les Ligetfa we
have extend the iexpress packages a little bit. Extensions since
August 2002 are
- implementation of "terminal service" model.
we are using drive based on "systemroot" registry setting. it solves
problems with unavailable C-drive.
for the temporary files it will use as prefix %tmp% environment
variable. - status of file association <b>.scr</b> untouch by another association.
- additional information will be written to debugging file. So you can
see what the actual registry settings for .K2K, .KIX, .SCR and .UDF are. - script returns now also a errorlevel- 0 = a complete installation done
- 1 = a incomplete installation done
this value can use in your BATch file.
f.e.
code:
@echo off
%0\..\kix410update.exe /q
if errorlevel 1 goto server
if errorlevel 0 goto client
goto server
:server
%0\..\kix32.exe %0\..\your_script.kix
goto end
:client
kix32 %0\..\your_script.kix
:end
@echo off
- in the NTx environment it isn't necessary to install the kx16.dll,
kx32.dll and kx95.dll.
we make it possible such installation, but for backward compatibility
we introduce the additional environment variable kix-only-required.
its value isn't important.
the control file shows the result of such installation.
Current environment variables to control packages are
- kix-debug
- kix-only-required
- kix-show
Examples:
- a standard installation
code:
[KiXtart]
kix32.exe=2002/08/14 02:35:01 -> 2002/07/08 20:41:12 225280 (build 099)
kx16.dll=2002/08/14 02:35:02 -> 2001/08/27 20:17:29 47104
kx32.dll=2002/08/14 02:35:02 -> 2002/03/29 12:38:08 49152
kx95.dll=2002/08/14 02:35:02 -> 2001/11/19 05:00:00 49152
KiXtart=installation completed at 2002/08/14 02:35:02 (+kix32.exe +kx16.dll +kx32.dll +kx95.dll) to "c:\windows\"
KiXtart release=ME -> kix 4.10
KiXtart mode=registry
kix-only-required specified.
code:
[KiXtart]
kix32.exe=2002/08/14 02:46:02 -> 2002/07/08 20:41:12 225280 (build 099)
KiXtart=installation completed at 2002/08/14 02:46:02 (+kix32.exe -kx16.dll -kx32.dll -kx95.dll) to "c:\windows\"
KiXtart release=NT4 -> kix 4.10
KiXtart mode=registry (only required files)
-kx16.dll, -kx32.dll and -kix95.dll were removed.
kix-only-required specified.
code:
[KiXtart]
kix32.exe=2002/08/14 02:57:36 -> 2002/07/08 20:41:12 225280 (build 099)
KiXtart=installation completed at 2002/08/14 02:57:36 (+kix32.exe ?kx16.dll ?kx32.dll ?kx95.dll) to "c:\windows\"
KiXtart release=NT4 -> kix 4.10
KiXtart mode=registry (only required files)
?kx16.dll, ?kx32.dll and ?kix95.dll aren't available on drive. - the debugging output when kix-debug & kix-only-required are specified
in a NTx environment:
code:
Kixtart 4.10 - NT4 debug mode (vs 3.07) 02:57:34
Informative INSTALL: copy x:\kix32.exe c:\windows\kix32.exe
size.old = 225280
size.new = 225280
time.old = 2002/07/08 20:41:12
time.new = 2002/07/08 20:41:12
company name
filedescription KiXtart main executable
fileversion 4, 10, 0, 0
internalname KIX32
language 0409English
legalcopyright Copyright Ruud van Velsen 2002
legaltrademarks $
originalfilename KIX32.EXE
privatebuild
productname KiXtart
productversion 4, 10, 0, 0
specialbuild Build 099
=> KiXtart - kix32.exe - 2002/08/14 02:57:36 -> 2002/07/08 20:41:12 225280 (build 099)
=> KiXtart - - installation completed at 2002/08/14 02:57:36 (+kix32.exe ?kx16.dll ?kx32.dll ?kx95.dll) to "c:\windows\"
Informative INSTALL: creation of KIX file associations.
=>
=> .kix kix32 document
=> .k2k kix32 document
=> .scr kix32 document
=> .udf kix32 document
=> kix32 document Edit
=>
=> KiXtart - KiXtart release - NT4 -> kix 4.10
=> KiXtart - KiXtart mode - registry (only required files)
logevent = Kixtart-UPDATE 3.07 script completed successfully (02:57:34 - 02:57:36) (+kix32.exe ?kx16.dll ?kx32.dll ?kx95.dll) to "c:\windows\"
Kixtart 4.10 update completed. ('X:\' -> 'c:\windows\')
- the debugging output when kix-debug & kix-only-required are specified
in a 95x environment:
code:
Kixtart 4.10 - ME debug mode (vs 3.07) 02:59:26
Informative INSTALL: copy x:\kix32.exe c:\windows\kix32.exe
size.old = 225280
size.new = 225280
time.old = 2002/07/08 20:41:12
time.new = 2002/07/08 20:41:12
company name
filedescription KiXtart main executable
fileversion 4, 10, 0, 0
internalname KIX32
language 0409English
legalcopyright Copyright Ruud van Velsen 2002
legaltrademarks $
originalfilename KIX32.EXE
privatebuild
productname KiXtart
productversion 4, 10, 0, 0
specialbuild Build 099
Informative INSTALL: copy x:\kx16.dll c:\windows\kx16.dll
size.old = 47104
size.new = 47104
time.old = 2001/08/27 20:17:29
time.new = 2001/08/27 20:17:29
company name
filedescription
fileversion
internalname
language
legalcopyright
legaltrademarks
originalfilename
privatebuild
productname
productversion
specialbuild
Informative INSTALL: copy x:\kx32.dll c:\windows\kx32.dll
size.old = 49152
size.new = 49152
time.old = 2002/03/29 12:38:08
time.new = 2002/03/29 12:38:08
company name
filedescription KiXtart 32 bit Thunk DLL
fileversion 3, 61, 1, 0
internalname KX32
language 0409English
legalcopyright Copyright Ruud van Velsen. 2001
legaltrademarks
originalfilename KX32.DLL
privatebuild
productname KiXtart
productversion 3, 61, 1, 0
specialbuild
Informative INSTALL: copy x:\kx95.dll c:\windows\kx95.dll
size.old = 49152
size.new = 49152
time.old = 2001/11/19 05:00:00
time.new = 2001/11/19 05:00:00
company name
filedescription KiXtart RPC client DLL
fileversion 3, 60, 0, 0
internalname KX95
language 0409English
legalcopyright Copyright Ruud van Velsen. 2001
legaltrademarks
originalfilename KX95.DLL
privatebuild
productname KiXtart
productversion 3, 60, 0, 0
specialbuild
=> KiXtart - kix32.exe - 2002/08/14 02:59:31 -> 2002/07/08 20:41:12 225280 (build 099)
=> KiXtart - kx16.dll - 2002/08/14 02:59:31 -> 2001/08/27 20:17:29 47104
=> KiXtart - kx32.dll - 2002/08/14 02:59:31 -> 2002/03/29 12:38:08 49152
=> KiXtart - kx95.dll - 2002/08/14 02:59:31 -> 2001/11/19 05:00:00 49152
=> KiXtart - - installation completed at 2002/08/14 02:59:31 (+kix32.exe +kx16.dll +kx32.dll +kx95.dll) to "c:\windows\"
Informative INSTALL: creation of KIX file associations.
=>
=> .kix kix32 document
=> .k2k kix32 document
=> .scr kix32 document
=> .udf kix32 document
=> kix32 document Edit
=>
=> KiXtart - KiXtart release - ME -> kix 4.10
=> KiXtart - KiXtart mode - registry
logevent = Kixtart-UPDATE 3.07 script completed successfully (02:59:26 - 02:59:31) (+kix32.exe +kx16.dll +kx32.dll +kx95.dll) to "c:\windows\"
Kixtart 4.10 update completed. ('X:\' -> 'C:\WINDOWS\')
- a Kix410registry.exe installation when .scr has already another
file association:
code:
Kixtart 4.10 - ME debug mode (vs 3.06) 01:30:11
Informative INSTALL: copy x:\kix32.exe c:\windows\kix32.exe
=> KiXtart - kix32.exe - 2002/08/08 01:30:18 -> 2002/07/08 20:41:12 225280 (build 099)
=> KiXtart - kx16.dll - 2002/08/08 01:30:18 -> 2001/08/27 20:17:29 47104
=> KiXtart - kx32.dll - 2002/08/08 01:30:18 -> 2002/03/29 12:38:08 49152
=> KiXtart - kx95.dll - 2002/08/08 01:30:18 -> 2001/11/19 05:00:00 49152
=> KiXtart - - installation completed at 2002/08/08 01:30:18 (+kix32.exe +kx16.dll +kx32.dll +kx95.dll) to "c:\windows\"
Informative INSTALL: creation of KIX file associations.
=>
=> .kix kix32 document
=> .k2k kix32 document
=> .scr kix32 document test
=> .udf kix32 document
=> kix32 document Edit
=>
=> KiXtart - KiXtart release - ME -> kix 4.10
=> KiXtart - KiXtart mode - registry
logevent = Kixtart-UPDATE 3.06 script completed successfully (01:30:11 - 01:30:19) (+kix32.exe +kx16.dll +kx32.dll +kx95.dll) to "c:\windows\"
Kixtart 4.10 update completed. ('X:\' -> 'C:\WINDOWS\')
- a Kix410update.exe installation when .scr has already another
file association:
code:
Kixtart 4.10 - ME debug mode (vs 3.06) 01:30:58
Informative INSTALL: copy x:\kix32.exe c:\windows\kix32.exe
=> KiXtart - kix32.exe - 2002/08/08 01:31:03 -> 2002/07/08 20:41:12 225280 (build 099)
=> KiXtart - kx16.dll - 2002/08/08 01:31:03 -> 2001/08/27 20:17:29 47104
=> KiXtart - kx32.dll - 2002/08/08 01:31:03 -> 2002/03/29 12:38:08 49152
=> KiXtart - kx95.dll - 2002/08/08 01:31:03 -> 2001/11/19 05:00:00 49152
=> KiXtart - - installation completed at 2002/08/08 01:31:03 (+kix32.exe +kx16.dll +kx32.dll +kx95.dll) to "c:\windows\"
=>
=> .kix
=> .k2k
=> .scr kix32 document test
=> .udf
=> kix32 document
=>
=> KiXtart - KiXtart release - ME -> kix 4.10
=> KiXtart - KiXtart mode - update
logevent = Kixtart-UPDATE 3.06 script completed successfully (01:30:58 - 01:31:03) (+kix32.exe +kx16.dll +kx32.dll +kx95.dll) to "c:\windows\"
Kixtart 4.10 update completed. ('X:\' -> 'C:\WINDOWS\')
- the control file when you are installation kixtart files on f.e. X-drive
code:
[KiXtart]
kix32.exe=2002/08/07 23:42:53 -> 2002/07/08 20:41:12 225280 (build 099)
kx16.dll=2002/08/07 23:42:53 -> 2001/08/27 20:17:29 47104
kx32.dll=2002/08/07 23:42:53 -> 2002/03/29 12:38:08 49152
kx95.dll=2002/08/07 23:42:53 -> 2001/11/19 05:00:00 49152
KiXtart=installation completed at 2002/08/07 23:42:53 (+kix32.exe +kx16.dll +kx32.dll +kx95.dll) to "x:\windows\"
KiXtart release=ME -> kix 4.10
KiXtart mode=registry
greetings.
btw: Still to go for a combine installation of kix32.exe & wkix32.exe
btw: symbol  on our homepage has been linked to related http://kixtart.org topic.
|
|
Top
|
|
|
|
|
#97887 - 2003-01-25 04:32 AM
Re: kix32 vs 2k/XP scripting
|
MCA
KiX Supporter
Registered: 2000-04-28
Posts: 5152
Loc: Netherlands, EU
|
Dear,
As input about VBScript.
- we replace VBS extension association with another
program f.e. notepad is possible. - we rename CScript.exe and WScript.exe to another
name without the creation of a file association link.
Possible for general computer users.
Sometimes a developper requires some programs on his
computer. A developper isn't in our opinion not a nor-
mal user and normally he knows what he is doing. - also we keep our virus scanner software up to date.
Not only with latest virus definition file, but also
with the set of files to check for. Normally only a sub-
set of files will be verified during computer usage.
Checking of all files will decrease your computer per-
formance dramatically. - also we check above issues each time a computer was
starting or an user was logging in.
(Significant) Changes will reporting automatically to
our support team.
greetings.
|
|
Top
|
|
|
|
Moderator: Arend_, Allen, Jochen, Radimus, Glenn Barnas, ShaneEP, Ruud van Velsen, Mart
|
0 registered
and 2220 anonymous users online.
|
|
|
![[Wink]](images/icons/wink.gif){kind=icon}
