Hmmm.

The only problem I see with doing this is that if you have someone read your script then run with KiXtart:

$password = $Crypto.Decrypt("4rI92Hrk22pkl")

It's just a hair better than putting in a plain text password. If someone figures out how to read the file from the netlogon share, they may also figure out how to use KiXtart to get the password?

A way around this hmmm?
How about:
When Encrypting the password, add the expected modify date and name of the script file:
[code]
;logonscript.kix
;date 2002/5/31
$encryptedpassword = $Crypto.Encrypt("password")

would encrypt based on the current date and the name of the file. So, after the script's first day in operation, the password would be secure.

Is this feasible?

Brian