We are currently using Kixtart on an NT 4.0 sp6a and are upgrading our current servers to new ones. My question is regarding the migration to a new server to keep the current Kixtart configuartion intact, also the version of Kixtart that we are using is 3.51, will this work on a Windows 2000 server?

TIP - You should also test your Login script before rolling out to the whole enterprise under the new version.

HTH,

- Kent

[ 10 November 2001: Message edited by: kdyer ]

Thanks for your code. Your kixtart version is very old. Without any
problem you can upgrade to kixtart 3.63 version. Only extension were
made to your version. This was already published a long time ago.

We advise you to install your kixtart binaries on your clients.

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
or kix400update.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\kix363update.exe /q
  
• %0\..\kix363update.exe /q
  
• if not exist c:\kix363.ok %0\..\kix363update.exe /q
  

• kix32 %0\..\your_script.kix
  

Results of your BATCH can be:

code:

---

@echo off
 %0\..\kix363update.exe /q
 kix32 %0\..\your_script.kix
@echo off

---

code:

---

@echo off
 if not exist c:\kix363.ok %0\..\kix363update.exe /q
 kix32 %0\..\your_script.kix
@echo off

---

After using above programs there will be created a control
file c:\kix363.ok or c:\kix400.ok. So it isn't necessary to
run the installation process again, but we advise to update
(or better: verify) kixtart files always. Reason: a security
leak for running kixtart from clients.

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: Kdyer make a good point about testing your script in the new
windows 2000 environment. Mostly a problem can be: an unknown access right to
a part of your old NT environment and possible type-problems with new names
of server and shares.
Your script will only act on its environment.