I have created a totally modular logon script, and want to share it with the board.
http://kix.isorg.net/other_scripts/AdminScripts/Kix_Logon_script.zip

The Modular Logon Script was designed using Kix2001 (and is not backwards compatible), and is performing excellent under the current beta 2a release.

One of the cool features about this logon script is that everything that it can do is controlled by a central config.ini file (anyone want to create a GUI interface for the confg.ini file??)

The Modular Logon Script is broken down into (at the moment) 8 modules.

they are

• CTRL_C (turn break on/off)
  
• legal_notice (display a legal notice with the option to force accpetiance)
  
• Welcome (Display a welcome notice)
  
• PWExpire (display a Password is old notice X number of days before it expirs)
  
• Set_Clock (set the systemclock to match a server)
  
• Drives (map drives, based on an extensive group membership rules!)
  
• Path (add AND remove paths from the %path% statment, Not fully tested on win9x computers)
  
• Other_scripts (run custom standalone kix scripts)
  

I am trying to come up with a Whitepaper on how to create a module, so that others can help out if they want...

Also there are extensive OS and Group membership rules available to customize how the logon script preforms.

here is the Logon-ReadMe.txt file

code:

---

--Modular logon script--
Everything that this logon script can do is controlled by the config.ini.
You can control what modules run by editing the [Module_run_order] entries.  

The two major settings are "OS Type" and "Group Membership"
OS type: this can be 
	Win9x|		All Win95, Win98 and Windows ME
	NT|		All NT 4.0 computers
	Win2k|		All Windows 2000 computers
	NTx|		Both NT and windows 2000 computers
	ALL|		All computers regardless of OS
Group membership:
There are 6 types of group memberships avaliable
	l = local groups
		|L!Administrators|		would be only for users that have local admin
		|L!\\server\group|		Would check for membership in a Local group on 
						a remote computer
	G = Global groups
		|G!Domain Admins|		would only execute for users in the "Domain Admins"
						global group
		|G!MIS\users|			Will only execute if a member of the trusted domain
						"MIS" and in the global Users of that domain
	U = Username
		|U!smithb|			would only execute for user smithb
	W = Workstation name
		|W!testcomputer1|		would only execute if ran on "testcomputer1"
	I = ip#	
		|I!128.2.0.0/255.255.0.0|	would only execute for computers in the 128.2.0.0 subnet
		|I!128.2.10.11/255.255.255.255|	would only execute for the ipaddress 128.2.10.11
In addition to [Module_run_order], you can also use "OS Type" and "Group membership" for 
the modules [Drives] and [Other_Scripts] for added extra control.

Example:
For your Win9x users you want to map a s: to \\server1\accounting, and you want your NT users 
to map their s: to \\server2\accounting

mapping1 = win9x|G!domain users|\\server1\accounting|s:
mapping2 = NT|G!domain users|\\server2\accounting|s:

---

This script is still in beta..... But I would really like some input on this, and if anyone can think of a module that would be a good thing to add, please let me know.

The next module I am going to write is add/remove/edit reg entries.

Many thanks to this board... with out all of yall.... I would never have been able to create this.

3-4-2002:
Fixed the security issues that NT vs Win9x issues when writting to the reg config key.

Fixed Local Group bug due to change in kix4.x

Bryce

[ 04 March 2002: Message edited by: Bryce ]