Locking Centralized Configuration File Parameters

In some cases, you might want to keep users from changing corporate configuration files in their local WDIR area.

For instance, Server Manager provides administrative tools, such as killing servers and defragmenting a project’s database, that you want to limit most users from being able to run. While you can set permissions for using these tools in the ServerManager.cfg file (see Setting Permissions for Server Manager Tasks), a user can overwrite those permission settings at the local WDIR copy of the configuration file.

To make sure local WDIR configuration files do not overwrite critical parameters, you can lock those parameters in your corporate WDIR configuration files with an asterisk (*) after the parameter name.

For example, KillServer* = no set in a corporate configuration file disallows any user who has a WDIR environment variable pointing to that corporate configuration file from overwriting the KillServer permission in the local WDIR configuration file.