When creating our Windows 2000 setup we wrote a number of scripts and configurations files we are happy to share with you. They are referenced throughout this website.

VBScript for setting ACLs
	MS is not very forthcomming with tools to manipulate ACLs. There is xcacls.exe, but it works only on files. So we write a little script which does this gruesome task. Read more about this in our ACL section. Check out Helge Kleins setacl it is a much more complete implementation of what we try to achieve with the dacl script.

Local Customisation for ntreg.dat
	As described in Profile Management document we are customizing the User Registry of the normal Default User. And supply this customized registry as default for new users. In order to customize the registry we log in and execute the .reg file listed above, logout again and then use the resulting ntreg.dat file as default for new accounts.

Make sure CDROM is called R:
	One of the minor nuisances with windows is, that drive letters tend to change when ever you attache new devices to the system. To help this sytuation we write the little script which makes sure that the CDROM drive gets assigned drive letter R:. R: is sufficiently fahr away from C: so that new devices which may get attached to the computer find ample space in between.

ISG::ParseConfig 1.9
	A generic configuration parser that is used by all our specific configuration parsers such as ISG::Win32::Config and ISG::Win32::BootConfig. (reference documentation)

ISG::Util
	Subroutines we find useful. (reference documentation)

ISG::Win32::ActiveDirectory 1.3
	Using ADSI from within perl is rather pooly documented. Once you get the hang of it, its quite simple to work from VBS or C++ documentation, but getting started is a bitch. Looking at our perl module should give you ample inspiration. Read more about this in our ADSI section.

ISG::Win32::Config
	Configuration parser for user and host configuration used by the usermgr and bootmgr scripts. Read more about it in the User and Host Management section. (reference documentation)

ISG::Win32::BootConfig 1.13
	Configuration parser for configuration used by the bootmgr script. Read more about it in the Magic Boot Scripts section. (reference documentation)

ISG::Win32::Util 1.0
	Subroutines for Windows that we find useful. (reference documentation)

Boot Manager: bootmgr.pl
	Run boot scripts based on text configuration files. Read more about it in the Magic Boot Scripts section. (reference documentation)

Login Manager: loginmgr.pl
	Run login scripts based on text configuration files. Read more about it in the Magic Login Scripts section. (reference documentation)

User Manager: usermgr.pl
	Manage users in the Active Directory based on text configuration files. Read more about it in the User and Host Management section. (reference documentation)

Host Manager: hostmgr.pl
	Manage hosts in the DHCP database and Active Directory based on text configuration files. Read more about it in the User and Host Management section. (reference documentation)

User Manager: win32-lusermgr.pl
	Manage local users based on text configuration files. Read more about it in the User and Host Management section. (reference documentation)

User Profile Management: win32-userinit
	A flexible way to create an inital user profile. Read more about it in the User Profile Management section. (reference documentation)

AppsReport: appsreport_update.pl
	Update list of installed application for license management. Read more about it in the License Management section. (reference documentation)

AppsReport: appsreport_update_unix
	Update list of installed application for license management. On the Linux platform. Read more about it in the License Management section. (reference documentation)

AppsReport: registry_collector
	Convert the directory structure of windows profile on a SAMBA share in a Windows like directory structure. Read more about it in the License Management section. (reference documentation)

AppsReport: appsreport_send.pl
	Send mail about installed application for license management. Read more about it in the License Management section. (reference documentation)