Group Policy rollout for registry defaults

Configure TwinPane default settings at scale using Group Policy registry preferences for HKLM and HKCU paths, including license and server behavior flags.

This guide explains how to use Group Policy to roll out TwinPane registry defaults across domain-joined endpoints and session hosts.

When to use Group Policy

Use GPO when you want centrally managed defaults for:

  • License and install path values.
  • Server feature flags (Mirror Mode, shell folder behavior).
  • Per-user overrides in HKCU.

For full key reference, see Registry keys (Client and Server).

1. Choose your policy scope

Use separate GPOs for clarity:

  • TwinPane Client Defaults (workstations/user endpoints).
  • TwinPane Server Defaults (AVD/RDS/Citrix hosts).

Link each GPO to the correct OU and start with a pilot OU first.

2. Configure machine-wide defaults (HKLM)

In Group Policy Management:

  1. Edit the target GPO.
  2. Go to Computer Configuration > Preferences > Windows Settings > Registry.
  3. Add registry items for TwinPane keys.

Example server defaults

Path: HKLM\SOFTWARE\FileSyncBridge\Server

  • LicenseKey (REG_SZ): your license key
  • MirrorModeEnabled (REG_DWORD): 1
  • ShellFolderRedirection (REG_DWORD): 1
  • StartVirtualDriveOnConnect (REG_DWORD): 1
  • InstallHandlerAutomatically (REG_DWORD): 1

Use item-level targeting if only certain host pools need these settings.

3. Configure user defaults (HKCU)

For user-level overrides:

  1. Go to User Configuration > Preferences > Windows Settings > Registry.
  2. Add values under:
    • HKCU\SOFTWARE\FileSyncBridge\Client
    • HKCU\SOFTWARE\FileSyncBridge\Server (if needed)

Use HKCU only when you intentionally need user-specific behavior.

4. Ordering with installer deployment

Recommended sequence:

  1. Deploy TwinPane binaries (Intune/SCCM/script).
  2. Apply GPO defaults.
  3. Validate keys on pilot devices.

If you are deploying installers silently, see Silent install (Client and Server).

5. Verification steps

On a target machine:

  1. Run gpupdate /force.
  2. Verify keys with regedit or reg query.
  3. Confirm TwinPane behavior matches configured defaults.

For server hosts, validate with a real user session:

  • File opening path
  • Mirror Mode behavior
  • Virtual drive startup behavior

6. Change control and rollback

For safe changes:

  • Test in pilot OU first.
  • Version your GPO changes in change tickets.
  • Keep rollback as “set previous value” or “remove value” actions.

Avoid changing many registry flags at once in production.

Common mistakes

  • Applying server settings to all endpoints accidentally.
  • Setting only HKCU when machine-wide HKLM policy is intended.
  • Enforcing conflicting values in both GPO and install-time scripts.

Related guides

Related guides

Intune deployment for TwinPane (Win32 app step-by-step)

Deploy TwinPane Client and Server through Microsoft Intune as Win32 apps, including install commands, detection rules, assignment strategy, and rollout tips.

Registry keys (Client and Server)

Reference for the Windows registry keys and values used by TwinPane Client and Server for settings, license, and deployment.

SCCM deployment with detection rules

Deploy TwinPane through Microsoft Configuration Manager (SCCM/MECM) with silent install commands, robust detection rules, and phased collection rollout.