In this article

Users with admin permissions or higher use this article to reference configuration options for the Windows Roaming Client. This guide includes both legacy Windows registry keys and current appsettings.overrides.json settings for version 3.0.0 or higher.

Local configurations Windows agent v3.0.0+

Starting with Windows Roaming Client v3.0.0, local configuration changes are managed through a JSON override file instead of the Windows registry.

Configuration file overview

Local configuration overrides are applied by creating an appsettings.overrides.json file. This file does not exist by default and must be created manually when overrides are required.

File locations:

• Branded agent: C:\ProgramData\DNSFilter, Inc\Settings
• Whitelabel agent: C:\ProgramData\DNSAgent\Settings

Only users or processes with write access to the ProgramData directory (typically local administrators) can create or modify this file.

Create an override file

To customize configuration locally, create a separate override file:

{
 
}

Start with an empty JSON object, then add only the specific keys to override, using the same structure and formatting shown in appsettings.defaults.json.

This ensures only the intended values change without overriding the full configuration chain.

🚨 Important: A malformed override file can prevent the Roaming Client from starting or cause it to behave unexpectedly. If troubleshooting configuration issues, Support may request a copy of the override file.

Combine related settings

When multiple configuration values belong to the same section, combine them in a single block as shown below:

"LoopbackProxy": {
  "IgnoredVpnInterfaceNames": [
    "vpn1",
    "sonicwall2"
  ],
  "IgnoredVpnInterfaceDescriptions": [
    "vpn1",
    "sonicwall2"
  ],
  "UpstreamProtocolTypeOrder": "StandardUdp, StandardTcp, DnsOverTls"
}

JSON vs registry and MSI settings

• Runtime agent configuration settings now use JSON instead of registry keys
• Most legacy registry-based runtime settings have JSON equivalents
• Install-only settings (such as ARPSYSTEMCOMPONENT) remain in the registry and do not have JSON equivalents
• MSI command-line parameters behave the same as in earlier versions and still apply during installation

Legacy Registry configurations

Edit any of the settings listed below via the Registry for agent versions 2.2.1 and older.

Locate Registry Keys

• HKLM\SOFTWARE\DNSFilter\Agent

• HKLM\SOFTWARE\DNSAgent\Agent

Registry Key definitions

Use this table to understand Windows Roaming Client Registry settings, their values, and definitions. "Agent" refers to the Windows Roaming Client.