How to use a .ini file to deploy an application?

How to use a .ini file to deploy an application.
How to override the registry definition when starting Progress
How to override the registry definition when starting OpenEdge

Progress always checks for environment variables when starting up a session. The required information is read from the Windows Registry or from the progress .ini file (-basekey -ininame ) since Progress 8.2x. This applies for both client and server versions

In order to standardize settings for clients there are three options:

Option 1:  Create an .ini file for specific client settings and use the -ininame and -basekey client startup parameters
A template ini file can be used %DLC%\bin\Progress.ini 

Example:
Where:

• -ininame will establish an alternative to the registry.
• -basekey "INI" will force the configured content of the sales.ini file instead of the registry.
• The -ininame and -basekey parameters must be defined on the command line.

Option 2:  Use the %DLC%\bin\ini2reg utility to convert an .ini file to the registry

Option 3:  Manually modify the registry entries with regedit for each client PC (not recommended)

For further information refer to the Progress Documentation sets below.
 

References to Other Documentation:

OpenEdge Deployment: Startup Command and Parameter Reference : Startup Parameter Descriptions : Registry Base Key (-basekey):
https://docs.progress.com/bundle/openedge-startup-and-parameter-reference/page/Registry-Base-Key-basekey.html

OpenEdge Deployment: Managing ABL Applications: ABL and R-code Deployment and Management : Maintaining User Environments : Maintaining the Windows user environment : Using the INI2REG utility : Searching progress.ini and the Registry at startup:
https://docs.progress.com/bundle/openedge-abl-manage-applications/page/Search-progress.ini-and-the-Registry-at-startup.html