How to replicate the Desktop Client configuration? – Network Optix

If you have multiple computers running the Desktop Client in the same system, you can standardize their configurations. To do this, configure a reference device, collect its configuration files, and deploy them to your target devices.

Note: Configuration folders are operating system (OS) dependent. You must replicate configurations for each OS in your system separately.

Step 1: Create a reference configuration

Set up the Desktop Client on a reference computer exactly how you want it configured across your other devices.

Launch the Desktop Client application on your reference computer.
Go to the Main menu and select Local Settings.
Adjust the settings across the tabs.
Apply your changes and close the Desktop Client to ensure the system writes the settings to your local disk.

Step 2: Collect the configuration files

On your reference computer, locate and copy only the specific option files you want to replicate.

1. Locate the settings folder

Open the settings folder for your operating system:

Windows: %LOCALAPPDATA%\Network Optix\Network Optix HD Witness Client\settings\
Linux: ~/.local/share/Network Optix/Network Optix HD Witness Client/settings/
macOS: ~/Library/Application Support/Network Optix/Network Optix HD Witness Client/settings/

2. Select individual files

Each file inside these folder is named after a specific option and contains a single plain-text JSON value.

Tip: Review the client-generated readme.md file for a full list of options, descriptions, and default values to identify the exact files you need.
Important: Copy only the specific option files you want to replicate. Do not copy the entire folder.

Files to exclude

Never replicate the following items, as they contain machine-specific data or session states:

local/pcUuid: Uniquely identifies the computer for Video Wall and usage statistics. Duplicating this file breaks Video Wall item ownership.
local/lastUsedConnection, local/lastLocalConnectionUrl, local/autoLogin: Contains connection and session states specific to the machine and operator.
settings/client_core/cloudCredentials, systemAuthenticationData, systemAuthenticationCacheData, digestCloudPassword, lastConnection: Encrypted against the local computer's keychain or credential store. They cannot be decrypted on another computer.
settings/client_core/knownServerConnections, recentLocalConnections, recentCloudSystems, searchAddresses, forgottenSystems, PreferredCloudServers, tileScopeInfo: Connection history specific to the reference computer.
The {site-id} folders: Contains per-site and per-window session states.

What these files do not contain

Server-side user settings are not stored on the local computer and cannot be replicated using this procedure. These settings follow the user account to any computer they sign in to and include:

Objects tab search states (camera and time selections, object types, attribute filters, area, and display mode).
Per-item resolution modes on cross-site layouts.

Step 3: Apply the configuration to target devices

Follow these steps to deploy the collected files to your target computers.

Close every Desktop Client window on the target computer. Verify in your system's process manager that no client processes are still running.
Open the same OS-specific settings/ path on the target computer.
Copy your collected configuration files into the target folder, overwriting any existing files.

Additional configuration tips

Resetting options: To reset a specific setting back to its factory default on a device, delete its corresponding file. The client automatically recreates the file with default values the next time it starts.
Cross-platform compatibility: The configuration file format is identical across all operating systems. You can apply a file collected on Windows to Linux or macOS devices. However, you must manually update any settings that hold file system paths (such as mediaFolders, backgroundsFolder, and last*Dir) to match the target platform's structure.