Skip to main content

Configuring Frame App

Frame App behavior can be configured on startup of the application (Command Line Arguments) and through configuration files/Windows registry keys.

Command Line Arguments

Command line arguments or “launch arguments” are parameters that are automatically passed to a program (via command line) to modify its behavior. Some organizations may choose to use these modifiers to better fit their use case. We will start by providing a list of the available command line arguments and then explain how to configure them based on your operating system.

To launch Frame App with certain command line arguments, start by opening command prompt/terminal on your local machine. Specify the file path for Frame App (include the executable). Append your command line argument(s) after file path.

You may launch Frame App with the specified parameters. Use the table below to understand command line argument options and their syntax.

Command Line ArgumentsDescription and Syntax Example
disable-mouse-lockBy default, Frame App will ignore mouse forward/back button events. If this argument is used, Frame App will respond to mouse forward/back button events. When a user is in session, these mouse events can cause the user to exit their session accidentally.

./Frame --disable-mouse-lock
displays-auto-arrangeFrame App will launch with virtual displays configured to match your local environment.

./Frame --displays-auto-arrange
kioskInstructs Frame App to launch in full screen, also known as “Kiosk mode.”

./Frame --kiosk
urlDesignates the startup URL, as you would on the “Preferences” page of Frame App.

x11-windowSwitch from GTK (default) to X11 Windows. This argument should be used with HP ThinPro OS clients.

./Frame --x11-window

User Preference Policies

Frame Administrators can enforce user preference policies across all installations of Frame App for Linux, Frame App for macOS, and/or Frame App for Windows through a preferences.conf file (Linux), plist (macOS), and group policy objects (Windows), respectively.

For Frame App for Linux 6.10 and greater, Frame administrators can control user preferences by creating and saving a configuration file at the location /etc/nutanix-frame/preferences.conf.

The conf file contains name-value pairs in the format KEY = VALUE. Spaces will be ignored. The list of supported keys and associated values are described in the following table.

Key NameDescriptionValue(s)
ADVANCED_USBFrame App will enable Advanced USB support when this argument is set to ON.

Default Value: ON
CHECK_FOR_UPDATES_ON_STARTUPFrame App will check for updates on startup when this argument is set to ON. If there is an update available, Frame App will ask the user if they wish to download and install the update.

Default Value: ON
CLEAR_CACHE_ON_STARTUPFrame App will clear the local cache on startup when this argument is set to ON.

Default Value: OFF
SEND_ERROR_REPORTSFrame App will not send error reports to Nutanix when this argument is set to OFF.

Default Value: ON
STARTUP_URLDesignates the startup Uniform Resource Location (URL).

Default Value:
preferences.conf Example

Local Cache

Frame App functions similarly to web browsers. Frame App contains a local cache that saves cookies, session tokens, and specific user preferences (e.g., automatically use all local displays). The cache can be deleted manually when required.

Follow the steps below based on the operating system on which Frame App is installed. Replace $USER with the name of your user.


The removal of the local cache will not remove the Startup URL value as this is stored either in the Preferences database or in the registry (for Windows).

Preferences Database

Frame App maintains its preferences in a SQLite database file in the following locations:


Log Location

Frame App writes its logs to the following locations. Replace username with the name of your user.