Control script passwords
Scripts that contain passwords can be shared with other users. The automatic password prompting feature prevents scripts from being recorded with actual passwords. Without this feature, a user can record a logon script and save it. Then this user can share the script with another user. If that user runs the logon script, they would be logging on with the original author's user name and password. You are depending on the author to be savvy enough to remove his or her password before sharing the script.
When the automatic password prompting feature is enabled, and when a hidden field is encountered during the recording process, the password (or hidden text) is not actually stored as part of the script. Instead, the BlueZone Script Recorder automatically inserts an "Input Command" with the label "BlueZone Recorded Prompt", with the "hidden" attribute turned on. The password that was entered during the recording process is discarded.
The end result of using this feature is that when the script is run, and a hidden field is encountered, the script prompts all users, including the author, for a password.
Essentially this is the same as manually inserting a "prompt for password" command into the script in lieu of the actual password.
Note
In BlueZone text-based scripts, the actual command that is inserted into the script is a little different, but the end result is the same.
Disabling the automatic password prompting feature
If you want to disable the automatic password prompting feature and allow BlueZone to capture and record passwords during the script recording process, the BlueZone administrator must edit the ScriptRecordHiddenText entry in the SETUP.INI file. The following text is the default value in the SETUP.INI file:
[BZSetup]
ScriptRecordHiddenText=No
To disable the automatic password prompting feature:
1. Open SETUP.INI in Notepad.
2. Locate the ScriptRecordHiddenText entry in the [BZSetup] section.
3. Change ScriptRecordHiddenText=No to ScriptRecordHiddenText=Yes.
4. Save and close the file.
Note
Any changes made to the SETUP.INI file only take effect after SETUP.EXE is run and BlueZone has gone through the installation process. Refer to Creating a distribution image and Installing BlueZone for more information.
Refer to BZSetup section for more information on the editing the SETUP.INI file.
This is a global feature and affects all types of BlueZone scripting regardless of the script format: proprietary or text-based.