Skip to content
Knowledge base

Where is the imos.ini and what can I change?

The imos.ini lives in %APPDATA%, per user and per version. How to find it, how %APPDATA% works and which settings you can safely change.

Short answer: The imos.ini is stored per Windows user and per imos version in %APPDATA%\imos AG\iX CAD 2025\config (other versions use their own version number in the folder name). The settings you typically change are the paths to the shared imos folder, the database connection and a few feature switches. Leave the technical keys alone, and always make a copy first.

Information

Applies to

  • imos iX 2019, 2021, 2023 and 2025 (the folder name differs per version; for imos iX 2019, for example, imos iX CAD OEM 2019)
  • imos iX CAD with Microsoft SQL Server and a shared imos data folder on a mapped drive
  • Any integrations with ERP software (such as Proteus) and cutting software
  • Last reviewed: October 2026

Finding and opening the imos.ini

  1. Close imos iX. Changes are only read at the next start.
  2. Open Windows Explorer, type %appdata% in the address bar and press Enter.
  3. Open the folder imos AG\iX CAD 2025\config, or the one with your own version number.
  4. Copy imos.ini to a backup, for example imos_2026-10-27.ini.
  5. Open imos.ini in Notepad.
  6. Find the key with Ctrl+F and change only the value after the = sign.
  7. Save without changing the encoding, start imos and test: open an existing order and generate a CNC program.

What exactly does %APPDATA% do?

%APPDATA% is a Windows environment variable. Windows replaces it with the Roaming folder of the logged-in user: C:\Users\<username>\AppData\Roaming. Typing %appdata% therefore always takes you to your own folder, whatever the account is called.

The imos.ini uses the same idea for the user's own folders:

CONFIG=%USERPROFILE%\AppData\Roaming\imos AG\iX CAD 2025\config
TEMP=%USERPROFILE%\AppData\Roaming\imos AG\iX CAD 2025\TEMP

%USERPROFILE%\AppData\Roaming is the same folder as %APPDATA%. There's no user name in the line, so it works on every PC and for every user.

Shared data does not belong in %APPDATA%: the library, orders, CNC programs and cutting lists must be in the same place for everyone. Use the mapped drive letter, for example I:\, pointing to the same share \\SRV-FILE\imos on every workstation. A UNC path such as \\SRV-FILE\imos\Library also works, but ties every path to one server name. With a drive letter, a server migration only means changing the mapping.

Tip

The same config folder also holds the drawing template IMOS.dwt and the DrawingFlags. Keep a reference copy on the server and copy it to %appdata%\imos AG\iX CAD 2025\config on every PC.

What can you change?

SettingChange it?Why
SYSYesLibrary folder, for example I:\Library. Lines using <SYS> follow automatically.
PROJECT_PATH, DELETED_ORDERSYesOrders and deleted orders, for example I:\Factory\Imorder.
TRANSFERPATH, SIMXMLIN/OUT/ERROR, DownloadPathYes, when migratingExchange folders under [ORDERMANAGER] and [iFURN]; they must point to the right server.
IMOSDB_SERVER, IMOSDB_DATABASEYesSQL Server instance and database.
IMOSDB_USER, IMOSDB_PASSWDYes, per userOwn account per designer; the imos administrator account for the administrator only.
COLLISION_CHECK_CONNECTORSYesA value of 2 turns on the connector collision check.
DRAWER_FOREIGNFRONT_SEARCHYesWe set this to 3 as standard.
SECTION_WALL_HATCH_STYLEYesWall hatching in sections, for example imosWall; the .pat file sits in the library on the server.
NAME_ORDERINFO1 to 10YesLabels of the extra order info fields, such as Drawn by or Revision.
ILLEGAL_CHARACTERSCheckCharacters not allowed in names; check after an update.
BARCODEPreferably notSet up barcodes in imos itself where possible.
IMOS, CONFIG, TEMPNoSet by the installer.
DEV_LEVEL, APG_VERSION, NCCHECK_RELEASE, MigrationStateNoTechnical keys; only change them on advice from imos.

An excerpt with neutral example values:

[IMOS-SETTINGS]
SYS=I:\Library
PROJECT_PATH=I:\Factory\Imorder
IMOSDB_SERVER=SRV-SQL\IMOSSQL2022
IMOSDB_DATABASE=IMOS_DEMO
IMOSDB_USER=DESIGNER1
IMOSDB_PASSWD=<password>
COLLISION_CHECK_CONNECTORS=2

Switching between multiple databases

Do you work with more than one database, for example a production database and a test or training database such as IMOS_DEMO? Then every switch means changing the server, the database name and often the paths in the imos.ini. Doing that by hand easily goes wrong.

Wood Intelligence can supply a .bat script for this. You click the script for the database you want to work with, and all settings in the imos.ini are set correctly automatically. Then you start imos iX and work in the right environment straight away.

  • No manual editing of the imos.ini. No more typos in server, database or path names.
  • One script per database. For example as a shortcut on the desktop.
  • The same for every user. The script uses %APPDATA%, so it finds the right imos.ini on every PC and under every Windows account.
  • Close imos iX first. The new settings are read at the next start.

Would you like such a script for your situation? Get in touch with us.

When installing a new imos version

  1. Don't carry over the old imos.ini.
  2. Compare the old imos.ini side by side with the clean one the installer creates.
  3. Copy across only your own changes: paths, database, collision check and the other settings from the table.
  4. Compare the CNC programs of a reference order between the old and new version.

Why this approach?

Every user has their own imos.ini per version. That lets each designer work with their own database account. The database change log then shows who changed which item.

New versions bring new keys. Copy an old imos.ini and those keys are missing or carry outdated values. So always compare against a clean ini instead.

In practice, we often see images missing from the connector scan, or wrong hatching in sections. The cause is almost always a path to a local folder or an old server. When everything points to the mapped drive, it works the same on every PC.

Frequently asked questions

I can't see the AppData folder. How do I get there?

AppData is a hidden folder. Type %appdata% in the Explorer address bar and you'll land straight in the Roaming folder of your own account.

Are there other ini or configuration files?

Yes. An ERP integration such as Proteus may use its own imos.ini in that software's folder. The cutting list export often has its own .cfg file, for example in I:\CUT. Older CAM installations under imos iX 2019 also used a cms.ini and an imoscam.ini. Check them all when migrating.

Can I change the database settings without editing the ini?

Yes. The server and database name are also in the imos iX opties (imos iX options). You can switch the database account you work under in the imos iX settings menu, but only when logged in with the imos administrator account.

Can I switch quickly between a test and a production database?

Yes. Wood Intelligence can supply a .bat script that, when clicked, automatically sets all imos.ini settings for the chosen database. Close imos iX, click the script and start imos iX again.

Further reading

More than one solution

Almost every question in this knowledge base has more than one solution. The best fit depends on your workflow, machinery and integrations. Not sure which applies to you, or are you using software we don't (yet) support? Feel free to email Wood Intelligence. We're happy to think along with any challenge.

imos is a trademark of imos AG. Wood Intelligence is an independent consultancy.

Download access

Sign in to check whether this download is available.