Enterprise Deployment Guide

What Display EX supports for enterprise

• Silent installation via command-line switches (no UI, no user interaction)
• MSI wrapper support for use with Group Policy Software Installation
• Pre-configured profile deployment via JSON files and logon scripts
• Per-machine and per-user install modes
• Automatic update suppression for managed environments
• Analytics/telemetry disabled by default — no data sent without user consent
• Compatible with SCCM, Microsoft Intune, PDQ Deploy, Ansible and similar tools

Silent installation

The Display EX installer accepts standard NSIS silent install switches. Run the installer with administrator rights for a per-machine install.

Basic silent install

CDXWin64v1.10.33.exe /S

Installs Display EX silently to the default path (%ProgramFiles%\DisplayEX) with no UI and no reboot prompt.

Custom install directory

CDXWin64v1.10.33.exe /S /D=C:\Tools\DisplayEX

The /D switch must be the last argument. The path must not be quoted even if it contains spaces.

Silent uninstall

"%ProgramFiles%\DisplayEX\uninstall.exe" /S

All installer switches

Switch	Description
/S	Silent mode — no installer UI shown
/D=path	Custom install directory (must be last argument, no quotes)
/NODESKTOP	Skip desktop shortcut creation
/NOSTARTMENU	Skip Start Menu folder creation
/NOTRAYSTART	Do not launch Display EX in tray after install
/NOUPDATE	Disable automatic update checks (recommended for managed deployments)
/NOTELEMETRY	Disable analytics/telemetry consent prompt and opt out by default

Deployment tool examples

SCCM / Configuration Manager

Create a new application, set the deployment type to Script Installer and use the following install/uninstall commands:

# Install command
CDXWin64v1.10.33.exe /S /NOUPDATE /NOTELEMETRY

# Uninstall command
"%ProgramFiles%\DisplayEX\uninstall.exe" /S

# Detection method: File exists
%ProgramFiles%\DisplayEX\DisplayEX.exe

Microsoft Intune (Win32 app)

Package the installer as an .intunewin file using the Microsoft Win32 Content Prep Tool, then configure:

# Install command
CDXWin64v1.10.33.exe /S /NOUPDATE /NOTELEMETRY

# Uninstall command
"%ProgramFiles%\DisplayEX\uninstall.exe" /S

# Detection rule: File or folder exists
Path: %ProgramFiles%\DisplayEX
File: DisplayEX.exe

PDQ Deploy

Create a new package, add an Install step with the installer path and parameters /S /NOUPDATE /NOTELEMETRY. Set the success exit code to 0.

Pre-configuring display profiles for users

Display EX stores profiles as JSON files in the user's AppData folder. You can create profiles on a reference machine, export them, and deploy them to all managed machines via logon script or Group Policy.

Profile file location

%APPDATA%\DisplayEX\profiles\

Export a profile from a reference machine

On your template machine, configure Display EX with the desired profiles, then open Display EX → Profiles → Export all profiles. This produces a profiles-export.json file.

Deploy profiles via logon script

# Example PowerShell logon script
$src = "\\fileserver\it\displayex\profiles-export.json"
$dst = "$env:APPDATA\DisplayEX\profiles"
New-Item -ItemType Directory -Force -Path $dst
Copy-Item $src "$dst\profiles-export.json" -Force

Display EX will import profiles from profiles-export.json on next launch if no local profiles exist yet.

Locking profiles (prevent user modification)

To prevent users from creating or deleting profiles in managed environments, set the following registry value after deployment:

HKLM\SOFTWARE\DisplayEX
Value: LockProfiles = 1 (DWORD)

Enterprise system requirements

Display EX has no special dependencies for enterprise deployment beyond the standard requirements. No .NET Framework, VC++ redistributables or third-party runtimes are needed.

• Windows 10 version 1903+ or Windows 11 (64-bit) on target machines
• Administrator rights for installation (standard user rights for operation)
• Outbound HTTPS only required if auto-update is enabled (disabled with /NOUPDATE)
• No inbound firewall rules required
• Disk space: approx. 50 MB per installation

Full system requirements →