Applies to:
@RISK, Evolver, NeuralTools, PrecisionTree, and StatTools, releases 5.x and Up
RISKOptimizer 5.x (merged in @RISK starting with 6.0)

 

Enforcing Consistent Settings in @RISK and DecisionTools Suite

Audience: Site Administrators

You can ensure consistent settings by using a policy file.

When present, this file automatically applies settings at startup and prevents users from changing them.

How Policy Files Work

Create a file named RiskSettings.rsf and place it in the RISK5, RISK6, or RISK7 folder under the installation directory. When @RISK starts, it silently imports these settings and locks applicable options.

Settings included:

• Default Simulation Settings (e.g., iterations, CPU usage): applied to new models but can be overridden and saved per model.

• Global Options (e.g., welcome screen, saving results): frozen and cannot be changed by users.

Create a Policy File for @RISK

1. Launch @RISK.

2. Go to @RISK Utilities > Application Settings.

3. Adjust desired settings.

4. Click Reset/File Utilities → Export to File.

5. Save as RiskSettings.rsf.

6. Copy the file to the RISK5/6/7 folder in the user’s installation directory.

Optional (User-Importable) Settings

To allow users to choose whether to apply settings, do not place the file in the RISK folder. Users can import it via Application Settings > Reset/File Utilities > Import from File.

Policy Files for Other Applications

Application	Settings File	Folder
@RISK	RiskSettings.rsf	RISK(version#)
Evolver	EvolverSettings.rsf	Evolver(version#)
NeuralTools	NeuralToolsSettings.rsf	NeuralTools(version#)
PrecisionTree	PTreeSettings.rsf	PrecisionTree(version#)
RISKOptimizer	RISKOptimizerSettings.rsf	RISKOptimizer(version#)
StatTools	StatToolsSettings.rsf	StatTools(version#)

Note: RISKOptimizer 6/7 settings are included in RiskSettings.rsf. BigPicture and TopRank do not support policy files.

Related Article:

Transferring Settings to Other Models or Computers