#23160 - 2002-06-14 12:33 AM
upgrading to Win2K Domain (using kixtart 3.47 as current version. upgrade required?)
|
Mystic Mike
Fresh Scripter
Registered: 2002-03-13
Posts: 14
Loc: El Toro, CA
|
Hello-
I'm going to upgrade our domain to win2k. We currently have an NT 4.0 domain with Kixtart 3.47 version running on our NT 4.0 PDC and BDC. I didn't install Kixtart and really don't know much about it. I imagine the version we are running won't be compatable with Windows 2000 Server, I'm keeping both the pdc and bdc NT4, what I will do is install a new server as a bdc NT4, then promote it to PDC then upgrade it to windows 2000. So.. will I need to upgrade the kixtart versions on the NT4 bdc boxes, can I install the newest version on the win2k pdc and leave the nt4 boxes alone? Can anyone shed some light about how kixtart will be effected by a win2k upgrade? Appreciated.
-Mike
(MCA: complete description)
[ 18 June 2002, 12:25: Message edited by: MCA ]
_________________________
Thanks everyone,
Mike
|
|
Top
|
|
|
|
#23166 - 2002-06-19 12:21 AM
Re: upgrading to Win2K Domain (using kixtart 3.47 as current version. upgrade required?)
|
MCA
KiX Supporter
Registered: 2000-04-28
Posts: 5152
Loc: Netherlands, EU
|
Dear,
For an easy upgrade of your clients with f.e. kixtart 4.02 you can use
our installation package kix402update.exe.
BUT we first we advice to upgrade to KiXtart 3.63 release. So you can see
your scripts are still running in a correct way. The jump from your cur-
rent to 3.63 is very big. It is the latest version which should be
downwards compatible with your current version.
After completon a succesfull test you can upgrade to latest kixtart 4.02
release. This version is no longer downwards compatible for all kixtart
functions f.e. OLExxx functions are removed and COM techniques are intro-
duced since Kixtart 4.00 release.
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.
|
|
Top
|
|
|
|
|
#23167 - 2002-06-18 02:46 PM
Re: upgrading to Win2K Domain (using kixtart 3.47 as current version. upgrade required?)
|
Kdyer
KiX Supporter
Registered: 2001-01-03
Posts: 6241
Loc: Tigard, OR
|
Mike,
I will echo the same type of format from Jens. Test, Test, Test. ![[Big Grin]](images/icons/grin.gif)
Be sure that your client workstations can use the script and get/execute the proper files on login.
Personally, In in addition to MCA's deployment tool for Kix32 and related files, I would also recommend his Kixstrip tool as well.
Please visit the FAQ Forum and specifically this topic" How do we check and format code for scripts?
As an FYI...
We are also going through this as well. We are going from 3.63 to 4.x (would like to go to 4.10 as it support nested groups with INGROUP). Here is a post I asked for comments on - Change Management Process - RFC.
HTH,
Kent
|
|
Top
|
|
|
|
|
#23168 - 2002-06-18 02:50 PM
Re: upgrading to Win2K Domain (using kixtart 3.47 as current version. upgrade required?)
|
MCA
KiX Supporter
Registered: 2000-04-28
Posts: 5152
Loc: Netherlands, EU
|
|
|
Top
|
|
|
|
#23169 - 2002-06-19 11:41 PM
Re: upgrading to Win2K Domain (using kixtart 3.47 as current version. upgrade required?)
|
Mystic Mike
Fresh Scripter
Registered: 2002-03-13
Posts: 14
Loc: El Toro, CA
|
Thanks Kent and MCA for the additional comments, loads of info. I think it was above my requirements though. Kixtart isn't installed on the clients, just in the netlogon folder (sys32\repl\..). Before reading your comments I downloaded the 4.02 version and replaced the files with the new ones. I also replaced the kxrpc service on all DCs. At first I was getting the dreaded 'Failed to locate kx16.dll' error on a client, although others were fine. I made one (I think insignificant) change to the users profile, and the error went away. At the moment it seems everything is okay. The only thing we are using kixtart for is to map drives on 9x clients and it is successfully serving that purpose. I'm hoping the 'failed to locate' error doesn't come up again. Now on to the domain upgrade. Thanks for the help everyone- please let me know if I've completely missed something. The readme file with the upgrade instructions made it seem as though it was as simple as replacing files, which is essentially all I have done.
_________________________
Thanks everyone,
Mike
|
|
Top
|
|
|
|
|
#23170 - 2002-06-20 01:09 AM
Re: upgrading to Win2K Domain (using kixtart 3.47 as current version. upgrade required?)
|
MCA
KiX Supporter
Registered: 2000-04-28
Posts: 5152
Loc: Netherlands, EU
|
Dear Mike,
Great anything is working great. A simple advice: using kixtart from dial-up connections will work much
faster when kix32 is installed on your client. Of course it isn't necessary for a correct way of running.
We are using kix32 from our clients also to do all kind of tasks before user is logging on to
any server.
New question, we are always welcome.
greetings.
|
|
Top
|
|
|
|
Moderator: Jochen, Allen, Radimus, Glenn Barnas, ShaneEP, Ruud van Velsen, Arend_, Mart
|
0 registered
and 2220 anonymous users online.
|
|
|
![[Wink]](images/icons/wink.gif){kind=icon}
Any links to docs would be great, and thanks so much for the promt response.
