Command line parameters
O&O DeskInfo accepts two parameters. Both are aimed at automated deployment: they point the application at a prepared configuration and at a fixed interface language without touching the user profile.
OODeskInfo.exe [/cfg:<file path>] [/lang:<code>]
/cfg — use a specific configuration file
OODeskInfo.exe /cfg:"C:\IT\OODeskInfo.cfg"
Loads the configuration from the given path instead of from the default locations. The path must point to an existing file; if it does not exist, O&O DeskInfo shows an error message with the usage text and exits.
Enclose paths containing spaces in quotation marks.
For a portable installation you do not need this parameter at all. If a file named OODeskInfo.cfg sits next to OODeskInfo.exe, it is used automatically — see Where the configuration file is stored.
/lang — set the interface language
OODeskInfo.exe /lang:en
Sets the language of the user interface. The code is the two-letter language code:
| Code | Language |
|---|---|
en | English |
de | German |
fr | French |
Without this parameter, O&O DeskInfo uses the language from the Language setting, and if that is empty, the Windows display language.
Combining parameters
Both parameters can be used together, in any order:
OODeskInfo.exe /cfg:"C:\IT\OODeskInfo.cfg" /lang:en
Error handling
If a parameter is unknown, malformed, or refers to a file that does not exist, O&O DeskInfo shows a message box with the offending command line and the usage text, and then exits. This is intentional: in an automated rollout a silently ignored parameter is far worse than a visible failure.
Typical usage in a rollout
A logon script or a shortcut in the startup folder that starts the application with a central configuration:
"%ProgramFiles%\OODeskInfo\OODeskInfo.exe" /cfg:"\\fileserver\it$\deskinfo\OODeskInfo.cfg"
More about preparing that configuration is in Enterprise deployment.