Install modes
The Configurator writes Install Files\Install.ini for you during a GUI-driven fresh install, so you do not normally edit the file manually.
Table: Install modes
Scenario | Edit Install.ini manually? | ApplicationKey |
|---|---|---|
GUI fresh install - new database | No | Generated automatically; do not set ApplicationKey= |
GUI fresh install - use existing DB | No (11.2+) | Enter in Configurator; written to |
GUI upgrade | No | Read from installed central Config\; not prompted in UI |
Do not set ApplicationKey= for a new database. The installer generates a new key and removes any leftover Config\ folder from a previous uninstall.
Set UseExistingDatabase=1, then supply the ApplicationKey by using one of the following methods:
ApplicationKey=<hex key from nsscmd -getconfig on source server>
LegacyProgramFolder=C:\path\to\old ProgramFolder
If you use LegacyProgramFolder, it must contain a readable
Config\machine.secrets.encfile from the source install. Alternatively, if you uninstalled a previous install to the same target ProgramFolder, the installer reads the key from the leftover Config\ folder there.The installer resolves the ApplicationKey in this order: ApplicationKey=, ApplicationKeyFile=,
LegacyProgramFolder\Config, then{ProgramFolder}\Config.Also set DatabaseName, AdapterDatabaseName, and the SQL credentials (MainDBUserName, MainDBPassword, AdapterDBUserName, AdapterDBPassword) to match the existing databases. When possible, the installer verifies the ApplicationKey against SYS_APP_KEY_CHECK. For an upgraded database that has a stale check value, a warning may appear; the installer refreshes the value at the end of the install.
Note:
When you select , the Configurator hides the Main and Adapter database username and password fields and generates the credentials automatically.