Editing the station database (config.bog) file

Whether the station database file (config.bog) is considered to be a station backup or whether it is part of a replicated station (system image) backup dist, the suggested modifications to it are the same.

NoteBe sure to keep unmodified copies of config.bog files (from Station Copier) or saved backup .dist files before making modifications. Work from copies of these files.Test your changes — be sure your modifications accomplish what you intend. This is especially important if you will be relying on them for jobs or sharing with customers or clients.

To modify, you open the file offline in Workbench.

Figure 2. Edit config.bog file offline in Workbench


Edit config.bog file offline in Workbench

NoteModifications described here do not apply to a AX-3.8 system, but only on a system running an update release (AX-3.7u1 or later, AX-3.6u4 or later, AX-3.5u4 or later). See Station archive portablility improvements in AX-3.8.

The following modifications are recommended:

  1. Remove any User passwords that were changed from defaults

  2. Set “Force Reset At Next Login” for all Users (AX-3.7 and later only, recommended in many cases)

  3. Convert any encrypted passwords

  4. Revert any automated configuration

  5. Save the BOG file changes

Remove any User passwords that were changed from defaults

In some cases by logging into a template station to verify a “known good” configuration, you can be forced to change passwords from defaults (particularly true if an AX-3.7 station).

Figure 3. Changing password back to defaults


Changing password back to defaults

In an image, you’ll want to change such User passwords back to defaults.

Set “Force Reset At Next Login” for all Users

If using AX-3.7 or later, in many cases it is recommended that you set each User’s “Force Reset At Next Login” property (under Password Configuration) to true.

Figure 4. Set “Force Reset At Next Login” to true for every user


Set “Force Reset At Next Login” to true for every user

An exception to this may be if these are replicated JACE stations to be installed in a NiagaraNetwork where “network users” are configured. In this scenario, sometimes you may wish to reserve this setting for only the (source) network Users in the Supervisor station.

Convert any encrypted passwords

If you need client credentials in an image, they won’t work in a target host because of new encryption techniques. Your offline edit of a station config.bog should replace any “new format” encoded passwords with legacy passwords. Figure 5 shows such an offline edit in progress.

Figure 5. Editing a client password in offline config.bog file


Editing a client password in offline config.bog file

Note you may have to overtype the password with an incorrect password, save, then correct it and save again to ensure that it gets stored correctly.

Revert any automated configuration

Certain NiagaraAX services can configure themselves based on available hardware when their station is first run. You may wish to investigate for this. If found, revert any such configuration during your offline edit of the station config.bog.

Save the BOG file changes



When finished modifying, remember to save config.bog file changes!