I use Windows 95 on the clients and Kix2001RC3.

When I check @MaxPWAge or @PWAge in my script both appear to be 0.

Can anybody tell me why this is?

ANY help is appreciated!

Thanks,
Nicolaj
nra@ok.dk

[ 05 October 2001: Message edited by: nra ]

Is it a problem with the Windows 95 version we run?

ANY help is appreciated!

All the best,
Nicolaj

seems to be the kixrpc Service not being installed on your Domain Controllers

Jochen

Anyone help?

Thanks,
NIcolaj

Per page 6 of the 3.63 Manual...

quote:

---

To install KiXtart 95 on the network
To install KiXtart on the network, copy the required files to the NETLOGON share of the logonserver(s).
To install KiXtart 95 on a client
To install KiXtart on a client, copy the required files to a directory on the local hard disk. Optionally, the dynamic link libraries (DLLs) can be copied to the windows or the windows\system directory.

---

- Kent

I now installed the RPC Service on the logon server, the files kx16.dll, kx32.dll and kx95.dll is copied both to the netlogon share and the local c:\windows\system.

When I try to use INGROUP from Kix2001RC3 it doesn't detect the group-memberships, but when I use the old version 3.55 it works just fine.

What am I doing wrong?

Clients = Windows 95 (damn them)
Server = Windows NT 4.0

Can anyone help? I'm getting quite desperate as it works just fine on W2K...

All the best,
Nicolaj

hth

Jochen

Problem solved (I think )

If I looked at the kixtart.log file it gave some error when I tried to use the INGROUP in Kix2001RC3, something about the DLL being outdated. And come to think of it, the kix16, kix32 and kix95 DLL are ancient, just downloaded the newest ones and copied them to the client windows\system = do prob at all! Stupid me...

Can I place the dll files in the \netlogon share only or does they have to be placed in the client-side windows\system dir too? (I'll save a lot of copying if I it is enough to place the new files in the \netlogon share).

Thanks!

/Nicolaj

Btw, this forum is superb, just want to say thanks to all you guys (and girls ) !!!!

[ 05 October 2001: Message edited by: nra ]

It isn't really necessary to place the DLL's on the client-side, but our
advise is: do it. The \windows\system is always available in your
search path. Possible search for those DLL's will always be positive.

For the installation of kixtart we have prepare some iexpress packages,
which will automatically install kixtart on your clients.

This versions doesn't have any requirement.
For kixtart 3.63 version:

• kix363update.exe
  
• kix363registry.exe
  

• kix400update.exe
  
• kix400registry.exe
  

The registry versions install kixtart to your %systemroot%
folder and add file associations for kixtart to your HKCR registry
keys. So you have additional elements to your menu.
The update versions install kixtart also to your %systemroot%
folder and remove file associations for kixtart from your
registry.

Possible calls in your logon procedure can be:

• x:\kixtart\kix363update.exe /q
  
• %0\..\kix363registry.exe /q
  
• if not exist c:\kix363.ok %0\..\kix363update.exe /q
  

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.

Greetings.

BTW: packages contains an update of install.kix which you can
find also on site http://home.wanadoo.nl/scripting .

BTW: Symbol on our homepage has been linked to related http://kixtart.org topic.

BTW: we didn't create iexpress package for version kixtart 4.00 RC3 release.
see for comment on
http://kixtart.org/cgi-bin/ultimatebb.cgi?ubb=get_topic&f=3&t=000232