|
|
|||||||
Howdy! Currently I have the KIX32.EXE and DLLs residing on the NETLOGON share of our 2000 server and all the clients run KIX32 from this location via the login.bat file: %0\..\kix32 \\server\share\lgs.kix I'm wondering if I should copy the EXE and DLLs to all the client PCs. The only reason I can think of to do this is that perhaps it would speed things up. But it would require a bit of permanent script that checks the client for the files and then the version number and then copies over the files if the version is wrong. That seems like a pain compared to my current procedure of doing nothing at all. Is there an advantage to having the EXE and DLLs local vs. on the NETLOGON share? Thanks. |
||||||||
|
|
|||||||
Hello Shane, Here is a program done by MCA who is a contributer of this board. It is a file that contains all the updated files from kix. Just add this into your login script and everytime someone logs into the network, it will check and update if necessary the kix files on their computer. The file is ony 178k and it take a second to run it. The advantage to this is it runs quicker from the local hard drive and takes less time to find the correct files and avoids mismatched files. [ 07 January 2002: Message edited by: Will Hetrick ] |
||||||||
|
|
|||||||
Shane, The textbook way of calling the script is %0\..\kix32 %0\..\lgs.kix provided the script resides in NetLogon. If you have Wintendo (9x/ME) or dial-in users, you should consider copying the executables and DLLs to %windir%. Wintendo has issues with its redirector that this will allieviate and performance on dial-in is a concern. This can be handled within the logon script or by using MCA's tools. p.s. only WIntendo needs the DLLs. [ 07 January 2002: Message edited by: LLigetfa ] |
||||||||
|
|
|||||||
Will: I've seen the Kix401registry tool and I'd surely like to use it, but it associates .kix and .scr files with menu context stuff and I don't want that to happen (not on the client PCs anyway). I can't figure out how to modify the scripts inside kix401registry.exe, though. Can I use this outside of the EXE? I can extract all the files into a directory and modify START1.KIX and START2.KIX not to run KIXEDIT.REG. Would I just call INSTALL.KIX from my login script? Would that work? les_ligetfalvy: |
||||||||
|
|
|||||||
Shane, Then you want this one which, i do believe, does not update the .kix and .scr files to the registry. Kix Update |
||||||||
|
|
|||||||
Here is the old way I used to update kix on the hard drives. code: This might be of use if you do not want to mess with the registry either. This is for Winnt, on windows 9x you would have to copy the dll's to the windows\system directory. |
||||||||
|
|
|||||||
Dumb question: Would I run the kix401update file from a script like so: code:SHELL ("%COMSPEC% /C \\SERVER \SHARE\kix401update.exe /Q") Thanks! [ 07 January 2002: Message edited by: Shane ] |
||||||||
|
|
|||||||
Here's what I use in my logon.bat code: |
||||||||
|
|
|||||||
I actually run it from the login.bat file right before I call the kix file. code: There are a bunch of people that say to use the %0\..\kix32.exe %0\..\rv-login.kix but this does not work for me. |
||||||||
|
|
|||||||
If the clients have KIX32.EXE locally, do I need to modify the LOGIN.BAT file from: code:%0\..\kix32 to... code:kix32 I don't want to remove KIX32.EXE from the NETLOGON shares because someone who doesn't have KIX32 locally is bound to logon sooner or later. How do you keep the client from running KIX32 from the NETLOGON share if the file is local, but still provision for folks who haven't had KIX32.EXE copied local yet? ########################################### [ 07 January 2002: Message edited by: Shane ] |
||||||||
|
|
|||||||
Here is an example of something you can do to run it from the netlogon share first if they don't have it and also copy it down for the next login. code: [ 07 January 2002: Message edited by: Will Hetrick ] |
||||||||
|
|
|||||||
Dear, We advice you to use kix401update.exe for the normal users. You batch file can be something like: code: Each time it will verify the correctness of your release. Incorrect files will be replaced and missing files will be added. (previous published information) An easy way of installing kixtart on your clients is by using our iexpress
You can easily upgrade it with our iexpress package. 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. Another way of installing/updating kixtart on your clients: For installing or updating of your clients you can download our packages kix363update.exe,
As first line of your logon procedure you can use one of following formats:
Second line can be something like:
Results of your BATCH can be: code: or for dial-up environments (= update package will transfer only once) code: After using above programs there will be created a control
running kix32.exe from a local workstation can have also unwanted effects. An user FIX for SECURITY LEAK: In our case the first statement of our default logon procedure for network users is always:
greetings. btw: related kixtart topic http://kixtart.org/board/Forum2/HTML/000583.html btw: it is not necessary to modify the script of iexpress package. by possible |
||||||||
|
|
|||||||
Dear, We have create an iexpress package which contains the wkix32.exe file. missing files will be added. incorrect files will be replaced. [/list] The file on our site http://home.wanadoo.nl/scripting is wkix401update.exe A possible call in your logon batch file can be: code: We didn't create file association entries with wkix32.exe, because the way The actual iexpress packages are:
Any question, comment or remark is welcome. greetings.
|