BlueZone provides a feature locking capability. You can distribute preconfigured versions of BlueZone that prevents your users from making changes to some or all of the BlueZone features. BlueZone feature locking is controlled by several settings in the setup.ini file.
When the setup.ini file is configured to lock features, all of those features are locked in the distributed sessions. If this is too restrictive, you can use command line switches to lock features in specific sessions. Refer to Locking features using command line switches for more information.
There are two levels of feature locking: dialog and sub-dialog level.
You can also determine whether or not you want the locked windows to be displayed. By default, if you lock a window, your users can still view the locked window and its current settings. By setting the show locked dialogs feature to No, your users cannot view any of the locked windows. If they try to view a locked window, an error message opens.
For a complete list of BlueZone windows that can be locked, refer to BlueZone feature locks.
Telnet Properties window
Refer to Configuring the Telnet locking feature for more information.
Display Options window
Refer to Configuring the display locking feature for more information.
If you are also using BlueZone Secure FTP client, you can configure the BlueZone Secure FTP client to inherit certain BlueZone lock values and can also prevent users from executing certain FTP commands.