Topic: Kix Login scrip

[Tom Veitch]

Any one tryed Kix login script with SME

[Tyrone C. Miles]

Kix-Start? I thought you had to have the Kix-start application on any NT or 2000 server to run that? (Which you can't install on e-smith)

[Tom Veitch]

I got it working on SME just trying to rember how to do group drive maping

[Bobby]

I have used Kix in the past.  Very good little application.

It matters not that the server host is; Linux, Windows, or some un-named product.  The workstation has to be able to run .exe applications if you are wanting to use it for log-in scripts.

What I did was:

- workstation logs in
- login script checks for existance of Kix is local system dirctory
- copies Kix if needed
- executes log-in script on client

In my example the server was just a file server.  Kix only resided there, as any other file.  

/B

[Tom Veitch]

do you know where i can get some sample scripts for group drive mappings

eg

if member of sales then map (drive) = sales (Ibay)

[Steven Curren]

I set up a perl script to generate a .bat that is run when a user logs on. That way you can write group specific drive mappings for win95/98 that do not seem to be able to recognise groups. After the login script is run it is deleted and regenerated when a given user logs on.

You add a 'preexec' and pass the %U (user) %L (net bios name) to the perl script that in turn generates the logon script for the user. The add a 'postexec' to remove the logon script ie root postexec = rm /location/of/script/%U.bat.

The preexec and postexec are added to the [netlogon] section.

[Mike Raaijmakers]

Have kix 2001 running like a baby on an E-Smith Server.
Try the SetFocus and Sendkeys funktions.
I needed that that to get the Seagate backup utility running unattended in Windows'98SE at night on a client.
We also use an older version of kix at work in a big Windows NT network.
Going to upgrade to kix 2001 there too.
O.K., Let's give an example.

Make a Kix Ibay with the neccessary rights on it.
Make a bat-file that you can run from the client (startup dir or so), something like login.bat or so:
CONTENTS:
>net use z: "\logonserver\kix.ib"
>START WKIX32.EXE z:\login.kix
>exit

Then make sure you have a login.kix and a variable.kix in the Kix Ibay with the neccessary rights on it for the user. The contents of that could be something like this:

CONTENTS:
 :Variablesearch
  CALL "\homeserver\kix.ib\variable.kix"

 CLS ? " Connecting Drives ... "

 :connectingdrives
  use h: "\$homeserver\$ibayA"
  use k: "\$homeserver\$ibayB"

You could allso ad something like:
   copy "z:\files\*.*" "%windir%\system"
  md "c:\batch"
   copy "z:\batch\*.*" "c:\batch"
  md "c:\kix"
   copy "z:\*.kix" "c:\kix"
To have the server copy al files to the client so that client always gets the newest logon files if he or she logs in.
Have not used something like:
     IF INGROUP("some group")
     RUN @ldrive + "\some\command.cmd"
on the E-Smith Server yet, have to try that out if that works well on E-Smith.

Also make sure you make one variable.kix where you define your variables that you call in the beginning of all kix scripts that require them.
Also think of 8.3 naming. If you use names longer than 8 characters you might wonder why some part of your script doesn't work.
If you downloaded kixtart 2001, have a look at KiXtart.chm.
You will find almost anything you need in there.

Good luck