I would like to upgrade to version 3.60 but I have some questions:

1. Does the old version work with te new KIXRPC service?

2. How can I upgrade my 250 Win95 clients without walking to every machine?

I thought the next procedure might work:

A. Upgrade the KIXRPC service by stopping the old ones, replacing the files on the server with new ones and starting te service again. Remote servers can be upgraded by stopping the service via service manager, connect to the remote kix drive and upgrading the files.

B. Win95 clients log in normally with the old version which is placed in the c:\windows\system dir.

C. In the config.pol I have added a batch file under Standard Computer \ Run Once, which copies the new files from the netlogon dir to the machines.

The procedure might go wrong at the point where the script connects to the new RPC service.
WILL THIS WORK?

Hoping you all can give me some hints,

Patrick Rutten
The Netherlands

------------------

Greetings,
Patrick Rutten
<-PR->

We work with around 300 W95 clients which have KIX32.EXE, KX16.DLL and KX32.DLL in their \windows\system directory.

At this time have have set the upgrade to go automaticly.

First I have made a share for the update in which I have placed the files for the \windows\system directory.

On the NETLOGON I have placed a batchfile which is started at the Logon. This batchfile looks if there is a file called kixtart.upd in the \windows\system directory. If not it will copy the files for KIXtart to this directory.

Every user has his own script this script set the time to the domaintime. Then the virusscanner will be upgraded and the share and printers are connected.
After this a subscript is started which looks if there is a program update ready for the user usually a SMS.
This subscript also has a subscript which compare the KIX32.EXE in the \windows\system directory with the one on the update share. If these are the same it places a file called kixtart.upd on the local drive this is done for the batchfile.

The only thing which I am working on is that a few of our notebooks have problem with starting the scripts. The error I am getting is:

Can not find KX16.DLL these must be in %path% or %windir%.

The \windows\system directory is in the path of autoexec.bat.

Files:

kixtart.bat:
@echo off
if not exist c:\windows\system\kix.upd goto 1verder
goto 2verder
:1verder
net use j: \\FILESERVER\update$ /y
copy j:\kix32.exe c:\windows\system > nul
copy j:\kx16.dll c:\windows\system > nul
copy j:\kx32.dll c:\windows\system > nul
net use j: /d /y
:2verder
echo The shares are being connected ......
c:\windows\system\kix32.exe

Userscript:
settime "TIMEDOMAIN"
shell "\\SERVER\share$$\AUTOPCC.EXE"
use i: "\\SERVER\shareA"
use n: "\\SERVER\shareB"
call update.scr

Update.scr:
use j: "\\Server\update$$"
if exist ("j:\"+@userid+".scr")
call ("j:\"+@userid+".scr") ; a script calling a SMS or copies some files
del "j:\"+@userid+".scr"
endif
call updatekx.scr
use j: /delete
exit

updatekx.scr:
$VER=GetFileTime ("c:\windows\system\kix32.exe")
$UPD=GetFileTime ("j:\kix32.exe")
IF $VER=$UPD
copy "j:\update" "c:\windows\system\kix.upd" ; J:\update is a file containing some tekst
goto end
else
if exist ("c:\windows\system\kix.upd")
del "c:\windows\system\kix.upd"
endif

:end
EXIT

He has a sophisticated way of upgrading the kix files on a client.

Hopelijk heb je hier wat aan (I hope this will work for you)

------------------
:) Michiel

In the batch file you have to call

%windir%\kix32.exe in stead of c:\windows\system\kix32.exe

PLEASE ignore !!!!!!!!!

As you know %windir% is the same as c:\windows.
Per mistake the Kix files were also in this directory.

Using xnet I stopped all RPC's
Then I copied the new RPC to the servers.
Now I started the RPC again.

I copied the new kix files to the netlogon dir

In de loginbatch (in which I call a Kixscript) I put some lines copying the new kixfiles to the clients.