| Task | How |
|---|---|
| Install the app on Windows | Add WND-Terminal-Windows.msi as an app. It needs no repackaging. |
| Set the policy | Import the ADMX template, or write the registry values with a script. |
| License every PC | Set the License key setting (registry value License). |
| Manage Macs | Deploy a configuration profile for com.wndsoftware.terminal. See Install on Mac. |
Deploy the MSI
Intune can deploy the MSI as it is. In the Intune admin center, add it as a line-of-business app, upload WND-Terminal-Windows.msi and assign it to your device groups. It installs into C:\Program Files\WND Terminal for everyone on the PC.
If a tool asks for the commands, these are the silent install and uninstall.
msiexec /i WND-Terminal-Windows.msi /qn
msiexec /x WND-Terminal-Windows.msi /qnTo upgrade, upload the newer MSI. It replaces the older version in place. Windows 10 and 11 already include Microsoft Edge WebView2. On a PC without it, the installer adds it, which needs internet access once.
Set the policy by importing the ADMX
Intune can import the WND Terminal ADMX template. In the Intune admin center, go to Devices > Configuration, open Import ADMX, and upload WNDTerminal.admx with en-US\WNDTerminal.adml. Then create a configuration profile from the imported template and assign it.
The settings keep their Group Policy names, under WND Software > WND Terminal. Lists such as Mainframe connections take one line per item, in the same format as Group Policy. See Group Policy for the connection line format.
Set the policy with registry values
WND Terminal reads its policy from HKLM\SOFTWARE\Policies\WND Software\WND Terminal. Group Policy writes exactly these values, and a PowerShell script deployed with Intune can write the same ones. This example requires encryption, blocks self-trusted certificates, limits people to two connections and adds the license key.
$key = 'HKLM:\SOFTWARE\Policies\WND Software\WND Terminal'
New-Item -Path $key -Force | Out-Null
Set-ItemProperty -Path $key -Name RequireEncryption -Value 1 -Type DWord
Set-ItemProperty -Path $key -Name AllowUserTrust -Value 0 -Type DWord
Set-ItemProperty -Path $key -Name AllowOtherHosts -Value 0 -Type DWord
Set-ItemProperty -Path $key -Name License -Value 'wnd1.your-license-key' -Type String
New-Item -Path "$key\Connections" -Force | Out-Null
Set-ItemProperty -Path "$key\Connections" -Name '1' -Value 'Production|mvs.example.com|992|secure' -Type String
Set-ItemProperty -Path "$key\Connections" -Name '2' -Value 'Test|mvstest.example.com|992|secure' -Type StringIn the script’s settings in Intune, set Run script in 64-bit PowerShell host to Yes.
Value types
- Switches are DWORD values, 1 for on and 0 for off. The Allow values mean the opposite of the Group Policy names, so
AllowPrint= 0 turns printing off. CodePageandLicensedSeatsare DWORD numbers.- Every other single value is a string, such as
License,UsageFolderorAuditSyslog. - Lists (
Connections,TrustedCertificates,MaskPatterns) are subkeys with one string value per item, named 1, 2, 3 and so on.
The policy settings reference lists every value name.
Build the connection list from your current emulator
The Migration readiness report reads a share of PCOMM, Reflection, BlueZone and ACS files. It writes the distinct connections as WNDTerminal.reg, policy.json and a Mac profile. Review WNDTerminal.reg, then set the same values with Intune.
Check a PC
reg query "HKLM\SOFTWARE\Policies\WND Software\WND Terminal" /sIn WND Terminal, the “Managed” badge lists what’s set. If a policy exists but can’t be read, the app applies strict rules (encryption required, no trusting certificates) and says so.