BlueZone has a powerful feature that automatically opens a pre-configured BlueZone configuration file. By being able to distribute BlueZone with a pre-configured configuration file, you greatly ease the task of distributing and installing BlueZone, as well as eliminating end user installation problems and avoid unnecessary Help Desk calls.

When BlueZone is initially launched, it checks the Windows Registry for a valid configuration. If a configuration is not found, the BlueZone directory is searched for a file labeled START.ZMD.

Once BlueZone has loaded the configuration information from the START file, the configuration is then saved to the Registry when the end user exits the BlueZone application. These Registry settings are used the next time BlueZone is launched. The START file can be deleted, however a saved version can be used to recover the configuration if the Registry becomes corrupted.

System Administrators can distribute completely pre-configured BlueZone Setup diskettes by including the START file. After installation, the first time BlueZone is launched it loads the values stored in the START file. Each new instance, or session of BlueZone uses this START file when initially launched, and is configured identically to the first.

As an option, you can choose to use this variant of the START file. This option is useful when you need to distribute BlueZone with more than one pre-configured configuration. To use this option, name the configuration Sx.ZMD, were x is the session identifier. Sx files work exactly like START files except they only configure a single session the first time a session is launched and no valid configuration is found in the Windows Registry.

For example, S1.ZMD automatically loads the configuration for Session S1 and S2.ZMD automatically loads the configuration for Session 2.

Additionally, you have the option using the SxLOCK START file, where x is the session identifier. SxLOCK.ZMD files work like Sx.ZMD files except they are loaded every time BlueZone is launched regardless of the configuration saved in the Registry. These files are designed to update BlueZone when Global Configuration lock is enabled.