By default, users can save configuration changes to their BlueZone emulation clients to their local workstations. BlueZone saves any configuration changes made by the user, such as screen size, color, font selection, keyboard mapping, and so on, to a file located on the user's workstation in the BlueZone working directory.
If you want to prevent your users’ from saving their configuration changes:
The following table lists the results of the possible combinations of the local save feature and base registry configuration options.
Conditions | Result |
---|---|
Allow User to Save Changes Locally = Enabled Base Registry Mode = 2 (default) |
If you make a change to a configuration file, save the new file to the web server, and increment the BlueZone Version Control feature, the next time the user starts the associated session, BlueZone Web-to-Host pushes out the updated configuration file to the user and BlueZone starts using this updated configuration file. If the user does not want to use the settings contained in this new configuration file, the user can select Backup of version of their configuration file. | from the BlueZone menu bar and open a previously saved configuration file or the
Allow User to Save Changes Locally = Enabled Base Registry Mode = 0 or 1 |
If you make a change to a configuration file, save the new file to the web server, and increment the BlueZone Version Control feature, the next time the user starts the associated session, BlueZone Web-to-Host pushes out the updated configuration file to the user but will be ignored by the BlueZone emulation client. |
Allow User to Save Changes Locally = Disabled Base Registry Mode = 2 |
BlueZone will not allow the user to save any configuration changes. The | and options are disabled.
Allow User to Save Changes Locally = Disabled Base Registry Mode = 0 or 1 |
BlueZone will not save any configuration changes into the Windows Registry, nor will the user be able to save their BlueZone configuration to a file. The | and options are disabled.