#29226 - 2002-09-18 04:13 PM
Total NEWBIE - a little explanation needed
|
dg72
Lurker
Registered: 2002-09-18
Posts: 3
|
Hi all,
please bear with me, I gues, it's been asked before I just can't seem to find the answer.
I wnat to know, how does kixtart knows which script to run at user's login.
I have filled kix32 in profile setting of the user at win2k server, and the script runs (although minimized - found solution :-) ) but I want to know what will it do, when there's 20 scripts in netlogon share.
tia,
dg
|
|
Top
|
|
|
|
#29228 - 2002-09-18 04:34 PM
Re: Total NEWBIE - a little explanation needed
|
dg72
Lurker
Registered: 2002-09-18
Posts: 3
|
WEll, the battlefield is:
Win2k Server SP2
Win2k Pro client
I'm trying to create a domain and set up login scripts for users to do some stuff.
So now, I have created a user, assigned him login script as described in guide "kix32" and it works. It runs the only .kix script in netlogon directory.
I have tried to set it to "kix32 mylogin.kix" and it worked. Now I'm confused, I don't want to create a separate login script for every user, and I plan to make one for all of my users. But what happens if I don't specify a name for kix login script and there will be more than one?
Which script will run? Does kixtart have some scheme he scans for script in netlogon dir?
I mean what happen if I don't specify script name as a parameter in user's properties and I'll have script1.kix, script2.kix in netlogon directory? Which will run?
tia,
dg
|
|
Top
|
|
|
|
|
#29229 - 2002-09-18 04:39 PM
Re: Total NEWBIE - a little explanation needed
|
Breaker
Hey THIS is FUN
Registered: 2001-06-15
Posts: 268
Loc: Yorkshire, England
|
Probably the best way to go, rather than having many different scripts on a per user basis is to have one script that performs different tasks depending on the user running the script at logon.
For example, have one central logon script, called logon.kix. In User Manager, set all the users who will run a logon script to use "kix32.exe logon.kix".
The main script would have sections for all users, for seperate groups, and for individual users, using conditions and the INGROUP() function - something like this:
code:
? Welcome to test Kix script.
If InGroup("Domain Admins")
? "You are an administrator in this domain."
Use x: "\\server\adminshare"
Endif
If InGroup("Application Users")
? "You are a user of the xxx application."
Use y: "\\server\applicationshare"
Endif
If @USERID = "joebloggs"
? "You are user Joe Bloggs."
Use z: \\server\usershare"
Endif
? "Logon script complete."
Exit
If you set up a test script like this and try logging on as different test users with different group memberships, you can see that you can handle different users and groups seperately from within a single script.
As far as possible I try to avoid having too many scripts, to make editing them easier - although I relax this for my admin scripts and functional scripts that are called by the central logon script itself. All in, however, I probably have less than twenty seperate scripts, in my Netlogon folder, which caters for over two and a half thousand users.
Hope this helps a little...
_________________________
================================================
Breaker
|
|
Top
|
|
|
|
#29230 - 2002-09-18 04:50 PM
Re: Total NEWBIE - a little explanation needed
|
dg72
Lurker
Registered: 2002-09-18
Posts: 3
|
Yeap, that could be a solution, but not the answer I wanted :-)
Nevermind, I was going to do it this way. I just wanted to know what's behind the curtain... :-))
Anyway thanx for the help, and I'm afraid, there'll much more... ;-|
thanx,
dg
|
|
Top
|
|
|
|
|
#29231 - 2002-09-18 04:55 PM
Re: Total NEWBIE - a little explanation needed
|
Shawn
Administrator
Registered: 1999-08-13
Posts: 8611
|
The manual covers this a little bit ... is this where heading with this question:
quote:
By default, KiXtart automatically looks for a personal script for the current user (“Username.KIX”). If it does not find one, it looks for the default script, “KIXTART.KIX”. You can override this behavior by specifying one or more scripts after Kix32.exe on the commandline. If an extension is not specified, KiXtart attempts to use two default extensions: ”.KIX” and “.SCR”.
|
|
Top
|
|
|
|
Moderator: Jochen, Allen, Radimus, Glenn Barnas, ShaneEP, Ruud van Velsen, Arend_, Mart
|
0 registered
and 837 anonymous users online.
|
|
|
