Configuration Lock

The Configuration lock functionality ensures that only one person at a time can make changes to the setup of your device.

As soon as you start to update any part of your configuration, the Configuration lock displays:

Optional, in Add a reason, enter the reason for the configuration lock being triggered, this can help inform other users of the device what action is being taken.

Tip - Add a reason is only shown to other users whilst the lock remains in place. Any comments added here disappear once the proposed changes are submitted or reverted and no record is retained.

Select Confirm to continue and claim the Configuration lock.

Once the Configuration lock is claimed, Configuration Locked displays on the status bar for all users and configuration changes can now only be made by that user, until they either:

Submit their changes, see Reviewing and Submitting Changes for details, or
Release the lock without confirming any changes having reverted all proposed/draft changes to their original values, see Releasing a Configuration Lock for details.

Tip - If a user has the Configuration lock but then logs out without submitting or reverting their changes, then the Configuration lock remains with this user until they log back in and relinquish the lock.

Tip - A user can switch between local and remote sessions maintaining the Configuration lock and associated changes.

Note - Configuration lock does not affect any running processes.

Releasing a Configuration Lock

To release a Configuration lock with no impact:

From the status bar, select Configuration Locked .
The Configuration Lock screen displays:

Select Unlock Configuration .

The configuration is released.

Note - Unlock Configuration

is not available once Review pending change(s)

displays. For details on reverting these changes, see Reverting Changes.

Last Update - July 26