Deploying DisplayFusion Compatibility Rules Using Group Policy Preferences

Save 25% on our desktop apps during our Black Friday/Cyber Monday sale, including DisplayFusion, ClipboardFusion, FileSeek, LogFusion, TrayStatus, and VoiceBot!

Title

Message

Confirm

No Yes

Confirm

Cancel Delete

<< Discussions << News Reply

If you're running DisplayFusion in a corporate environment and need to centrally add Compatibility rules for specific applications, you can do this using Active Directory Group Policy Preferences.

The steps below will walk you through creating a Compatibility rule for Chrome that will disable the DisplayFusion TitleBar Buttons.

Open the Group Policy Management Console.
Add a new Group Policy Object for DisplayFusion and open it for editing.
Expand the left tree down to User Configuration > Preferences > Windows Settings > Registry.

Right-click in the right pane and choose New > Registry Item.

Select "HKEY_CURRENT_USER" as the Hive, and set the "Key Path" to
```
Software\Binary Fortress Software\DisplayFusion\Compatibility
```
.

Set the "Value Name" to

App_1_Path

Set the "Value Data" to the path for the EXE you want to create the Compatibility settings for. You can also use wildcards, (e.g.

*chrome.exe

Add more Registry Items to the policy for the Compatibility Settings you want to enable for this application.

Make sure to replace "X" in the Value Name with the number that matches the "App_X_Path" value created in step 6. Set the Value Data to 1 to enable the Compatibility setting.

See the table below for a list of Compatibility settings and their Registry Value Name.

Repeat steps 4-8 for any other applications you want to create Compatibility rules for. Increase the number in the Value Names for whichever one you're working on. e.g. the second rule would be App_2_Path, the third rule would be App_3_Path, etc.

Link the GPO to an OU that has the DisplayFusion users in it so that they'll get the new policy the next time they logon.

If the user has already configured Compatibility rules, these settings can end up overriding them. It's best to block access to the Compatibility tab with the DisplayFusion Group Policy (ADMX) templates.

Compatibility Settings and their Registry Value Names

The following table lists the names of the settings in the Compatibility rule edit window, and the corresponding registry Value Name. All registry values are type "String (REG_SZ)" and all of them use 0 for disabled, and 1 for enabled. Make sure to replace "X" with the number that matches the "App_X_Path" value you're adding this setting for.

Setting Name	Registry Value Name
Disable TitleBar Buttons	App_X_DisableTitleBarButtons
Disable TitleBar Buttons (all applications)	App_X_DisableTitleBarButtonsAll
Disable Window Snapping	App_X_DisableWindowSnapping
Disable Wallpaper changes while running	App_X_DisableWallpaperChanges
Disable middle-click window moving	App_X_DisableWindowMoveMiddleClick
Disable maximized window dragging	App_X_DisableWindowMoveMaximizedDrag
Disable removing from Windows Taskbar	App_X_DisableWindowsTaskbarRemove
Disable Application Hooks	App_X_DisableAppHooks
Disable DisplayFusion Taskbars while running	App_X_DisableTaskbarsAll
Disable moving new windows to current monitor	App_X_DisableMoveNewProcessWindowsToCurrentMonitor
Use process file icon on DisplayFusion taskbar	App_X_ForceProcessTaskbarProcessIcon
Force DisplayFusion to treat this application as full screen	App_X_ForceTreatAsFullScreenWindow
Disable unfocused mouse scrolling	App_X_DisableMouseScroll
Use alternate Mouse Scroll method	App_X_DisableMouseScroll
Normal TitleBar Button Offset X	App_X_TitleBarButtonOffset
Normal TitleBar Button Offset Y	App_X_TitleBarButtonOffsetY
Maximized TitleBar Button Offset X	App_X_TitleBarButtonOffsetMaxX
Maximized TitleBar Button Offset Y	App_X_TitleBarButtonOffsetMaxY

Jun 26, 2019 (modified Aug 12, 2022) • #1

Was this helpful?

(-)

<< Discussions << News Reply