Page 1 of 1 1
Topic Options
#325 - 1999-08-25 04:53 AM Scripts
Anonymous
Unregistered


I have been put in charge of the scripts of Kixtart.
At this time in the usermanager a batchfile is called which see if the kix32.exe is in the right directory and than starts it. If it is not it will copy the exe and dll's to the system directories. Further every user has an own little script ending with .scr which only update the Virusscanner and attach shares (drives and printers). These scripts are placed in the same directory as the batchfile.

Is this the way to make it work. It seems that when you have to make changes for several people you will have to change every script seperatly.

Or can you make 1 large script which is called by all users and when need to make a change use groups in the usermanger on which a variable in the script decide if a certain part of the script must be run.

All clients are win95.

Top
#326 - 1999-08-31 06:36 PM Re: Scripts
Anonymous
Unregistered


It sounds like you have the answer to your own question. Global groups are a good way to go if you wish to use a centralized script. Using the IF-ENDIF you can test if a user belongs to the group (having similar resource needs) and execute the appropriate lines of code.
Top
#327 - 1999-09-08 03:15 PM Re: Scripts
Anonymous
Unregistered


Using Groups is the best way to divide the users and their resources. Use a single common "HEADER" file that sets global variables and exports common settings to DOS (for Win95 / 98). Then use the SELECT command ( a CASE statement)to find the group and call another group specific script. In this way you control the scripts without a long and messy IF.. ELSE .. ENDIF.

The main logon script - my HEADER - is very short and the Group scripts are specific so making changes to one script does not cause problems elsewhere - except if you are passing Global Variables and decide to change them (which you should't do) in one of the sub scripts.

All scripts are kept in \servername\netlogon and Kix is on the workstation. Use NT replication to send you scripts to all BDC's. Means you have to use Change Control to keep track of changes so you can fix any errors that appear before you do another replicate. Don't forget to put all the scripts, Kix, Win95 Policy files and anything else to be replicated in the EXPORT\SCRIPTS directory of the PDC. It will copy to the IMPORT\SCRIPTS directory of the PDC and then to the IMPORT\SCRIPTS of all BDC's - IMPORT\SCRIPTS is shared as \\server\netlogon.

Top
Page 1 of 1 1


Moderator:  Jochen, Allen, Radimus, Glenn Barnas, ShaneEP, Ruud van Velsen, Arend_, Mart 
Hop to:
Shout Box

Who's Online
0 registered and 1343 anonymous users online.
Newest Members
Viginette, ManuvdWielNL, Sir_Barrington, batdk82, StuTheCoder
17888 Registered Users

Generated in 0.047 seconds in which 0.022 seconds were spent on a total of 12 queries. Zlib compression enabled.

Search the board with:
superb Board Search
or try with google:
Google
Web kixtart.org