Skip to main content

Superprefs Fileset

What

When you create a Custom Client installer, the FileWave Client preferences are packaged into that installer: server name, ports, Boosters, and related client settings. That is useful for the base configuration, but one preference set is not always right for every device.

A Superprefs file lets you deploy selected FileWave Client preference changes to macOS or Windows devices after the client is installed. You can use one Superprefs Fileset for a broad change, or multiple Superprefs Filesets for different groups of devices.

Only the settings included in the Superprefs file are changed. Settings that are not included remain untouched on the client.

When to use this

  • Changing client logging level for troubleshooting
  • Adjusting Booster or communication preferences for a specific group of devices
  • Applying a new client preference without rebuilding and redeploying the Custom Client installer
  • Returning temporary troubleshooting settings back to standard values after testing

Ingredients

  • FileWave Clients on macOS or Windows
  • FileWave Superprefs Editor
  • FileWave Central Admin App

Create the Superprefs plist

The Superprefs Editor is installed with the FileWave Central Admin App:

macOS/Applications/FileWave/Superprefs Editor.app
WindowsC:\Program Files (x86)\FileWave\FileWaveSuperPrefsEditor.exe

When the editor opens, it may ask you to open an existing plist. Cancel that window if you are creating a new Superprefs file.

When creating a new Superprefs file, only settings that you add or edit in the Superprefs Editor are written into the plist. When opening an existing file, review all included settings before deployment: existing keys can remain in the saved file even if you do not edit them.

Remote Control (TeamViewer) in FileWave 17.0+

Use the FileWave 17.0 Superprefs Editor to configure TeamViewer access for macOS and Windows Clients. Remote Control (TeamViewer) is one selector rather than two independent checkboxes:

  • Disable TeamViewer access — do not allow TeamViewer remote access through FileWave.
  • Prompt user for access — require the end user to approve access. This does not also enable sessions without a prompt.
  • Don't prompt user for access — allow a session without requesting end-user approval. In Central, the administrator can still choose the prompted Remote Session action.

The Superprefs Editor also offers Leave unchanged. Use that choice when this Fileset should not change the Client's TeamViewer access setting; it is not the same as disabling access.

Choose Don't prompt user for access only when your organization's remote-support policy permits access without the user's approval. Selecting an access setting does not install the TeamViewer Agent or establish a remote session.

Select the intended choice, save the file as fwcld.newprefs.plist, and reopen it to confirm the saved choice. Then continue with Package the plist in a Fileset. The Debug Level example below is a separate example; you do not need to enable debug logging to change TeamViewer access. After the pilot Client receives and activates the Fileset, confirm its effective setting in Client Monitor before expanding the Deployment.

Opening an existing Superprefs file in 17.0+

The native preference keys have not been renamed. An older file containing vncManaged=1 and vncPromptClient=1 (the old “both checked” combination) opens as Prompt user for access, not as permission for both prompted and unprompted sessions. A file containing vncManaged=0 and vncPromptClient=1 opens as Disable TeamViewer access.

If an older file contains only vncManaged without the paired prompt key, the editor displays Leave unchanged. Review the intended setting instead of interpreting that display as the Client's effective permission.

The 17.0 editor uses Heartbeat Interval (seconds) and Verify Interval (minutes). These remain the native tickleInterval and fileCheckInterval preferences; the native verification interval is stored in seconds. The unused priority field is no longer offered by the editor, but an existing unknown key can remain in a saved file. Saving an old file is not a cleanup of all obsolete keys.

Example: set Debug Level to 99

Debug Level has three common values:

10Standard logging (default)
99Debug logging
101Trace logging

To enable debug logging, open the Superprefs Editor, cancel the Finder or Explorer window if you are creating a new file, go to the Options tab, set Debug Level to 99, and save the file.

The file must be named fwcld.newprefs.plist.

Superprefs Editor Options tab with Debug Level set to 99 and saved as fwcld.newprefs.plist

For this example, start with a new Superprefs file and change only Debug Level. The saved plist should contain only this key:

Dict {
    debugLevel = 99
}

Package the plist in a Fileset

The fwcld.newprefs.plist file can be placed in any reasonable path inside the Fileset. A dedicated Superprefs folder makes the purpose clear and lets you keep separate folders for different preference sets.

macOS/usr/local/etc/Superprefs/debug/fwcld.newprefs.plist
WindowsC:\ProgramData\FileWave\Superprefs\debug\fwcld.newprefs.plist

You can add the file to an existing Fileset, but a dedicated Fileset is usually easier to target, test, and remove later.

From the FileWave Central Admin App:

  • Create a new Empty Fileset and name it clearly.
  • Open the Fileset and disable Hide unused folders.
  • Select or create the desired location for the plist file.
  • Drag fwcld.newprefs.plist from Finder or Explorer into that location in the Fileset.

Using the debug logging example for macOS, the Fileset could look like this:

Fileset contents showing fwcld.newprefs.plist in a Superprefs debug folder

Creating the Fileset alone does not select devices or publish the change. In Deployments in FileWave Central, add the Superprefs Fileset and one intended test device or small pilot group, review the targets and installation settings, and save the Deployment. Coordinate with the other administrators, review pending changes, and run Update Model. This commits pending work from all administrators, not only your Superprefs change.

Only after the pilot Client receives and activates the Fileset should the included preferences change. In the debug logging example, confirm that Debug Level is 99 on the Client and that its log reflects the change. Do not use the Server model number alone as proof. Keep the Deployment limited to the pilot until you verify the intended settings; then expand its targets as needed.

For temporary troubleshooting, create a matching Superprefs Fileset that returns Debug Level to the standard value of 10 when analysis is complete.

GUI observation

Some Superprefs Editor entries are Boolean values, such as Booster Routing. Boolean entries can be set to True, set to False, or left unset. A dash means the value is not included in the Superprefs file.

The illustration below shows the earlier Boolean controls. In FileWave 17.0+, use the TeamViewer selector described above; the dash still means unset for Boolean settings such as Booster Routing.

Superprefs Editor Privacy tab showing Boolean settings with unset values

The three states appear as:

Unchecked Boolean value

False

Checked Boolean value

True

Unset Boolean value

Unset