Vista - Startup Script Via GPO... Where Are Parameters Stored?

I might need to go to another group, but I know there are smart dudes
that patrol this one...

If I am setting up a startup script in a gpo, it gives the option to
pass some parameters to the script. Does anyone know where these
parameters are stored?

If you want to help me solve the greater problem, I am trying to write
a script that will change the local admin password on all computers,
but prevents the password from having to be in clear text and
accessible to the user. Obfuscation is not sufficient, and hashing
doesn't work as the key will be in plain text in the script. Any
ideas on this problem?

Thanks!

"trading_jacks" <MARKFERGASON@xxxxxx> wrote in message
news:a353790f-9c7e-4ee6-8617-8e6371f9fd59@xxxxxxI don't know where the parameters are stored, but I would recommend changing
the local administrator passwords yourself remotely. You could could a
VBScript program to do this in bulk. I have an example linked here:

http://www.rlmueller.net/Reset_Local..._Passwords.htm

This assumes you want the same password on all workstations. The program
reads a text file of computer NetBIOS names. Any computers that could not be
reached are written to another file, which you can use as input when you run
the program again (until the password has been changed on all computers). If
there is no text file of computer names, the program queries for all
computers where the OS does not include the string "server". Or, you can
start with your own text file of computer names, for example if you only
want to change the password for computers in one or a few OU's. The person
running the script must be a member of the local Administrators group, but
by default members of "Domain Admins" are members.

The advantages of this approach:

1. No security issues (except to keep your one script secure).
2. Most passwords are changed immediately.
3. You know which computers have had the password changed and which not.
4. You know when the process is completed.
5. The password is changed once on each computer, not everytime someone logs
on.

The only catch is that the computers must be authenticated to the domain
when you run the script, but there is no need for anyone to be logged on.

--
Richard Mueller
MVP Directory Services
Hilltop Lab - http://www.rlmueller.net
--