Here's the general idea:

To start, create a file using notepad. Give it a reasonable name, with a .INI extension. It should look something like this:
[CONFIG]
ValueName1=data
ValueName2=data

Each "ValueName" represents one of the config parameters from your script, and the "data" is the initial definition. The CONFIG section contains all of the script-common data values, like MailServer, MailUser, MailSendTo, and so on.. You could create workstation-specific sections:
[PCNAME]
Skip=1
for workstation values - in that example, if you read the Skip value from the @WKSTA section and determined that the value was "true" (see my Bool() UDF), you could skip that PC. Would also make other customizations possible, like WeekendOnly or MaxDays.

Replace your $VarName=Value declarations in the script with
$VarName = ReadProfileString($ConfigFile, 'CONFIG', 'ValueName')
commands. - then test. Change some of the INI settings and verify that the changes are accepted.

Then, you can add some code that determines if the config file is present. If it isn't, it can prompt for the required data and create the config file with WriteProfileString commands.

I find that creating config files is often an evolutionary process, so I don't create tools to create/manage them until i feel they are complete.

Glenn
_________________________
Actually I am a Rocket Scientist! \:D