| Item | Detail |
|---|---|
| Installer | WND-Terminal-Mac.dmg, from the downloads page of the WND customer portal |
| macOS | 11 or later |
| Processor | Apple Silicon or Intel. One app runs natively on both. |
| Preference domain | com.wndsoftware.terminal |
| Example profile | WNDTerminal.mobileconfig |
Install the app
- Open
WND-Terminal-Mac.dmg. - Drag WND Terminal onto Applications.
License the Mac
Set License to your license key in the configuration profile. The key is the line starting with wnd1. under Your license on the customer portal.
To use the license file instead, copy it to /Library/Application Support/WND Terminal/, or set LicenseFile in the profile to the file’s path. To license one Mac by hand, open WND Terminal, choose Add a license and select the file. See Licenses.
Deploy settings with a configuration profile
WND Terminal reads managed settings from the preference domain com.wndsoftware.terminal. macOS keeps them in /Library/Managed Preferences, which people can’t change. The app shows a “Managed” badge that lists what’s set.
Jamf, Microsoft Intune, Kandji, Mosyle and other device managers can deliver the settings in either of two ways.
- Upload
WNDTerminal.mobileconfigas a custom profile. Edit it first and give it newPayloadUUIDvalues. The example has two, one for the profile and one for its settings payload. - Enter the same keys in the device manager’s “Application & Custom Settings” payload for the domain
com.wndsoftware.terminal.
The example profile installs at System scope with PayloadRemovalDisallowed set to true.
Example settings
These keys require encryption and stop people trusting certificates on their own. They also limit people to IT’s connections and license the Mac.
<key>RequireEncryption</key>
<true/>
<key>AllowUserTrust</key>
<false/>
<key>AllowOtherHosts</key>
<false/>
<key>License</key>
<string>wnd1.your-license-key</string>
<key>Connections</key>
<array>
<dict>
<key>Name</key>
<string>Production</string>
<key>Host</key>
<string>mvs.example.com</string>
<key>Port</key>
<integer>992</integer>
<key>Secure</key>
<true/>
</dict>
</array>Key names match the registry values Group Policy writes and the keys in policy.json. Switches are booleans, port numbers and code pages are integers, and lists are arrays. Each connection is a dictionary with Name, Host, Port and Secure. It can also carry BackupHosts, LUName, CodePage and SignInWithCertificate. The policy settings reference lists every key.
Without a device manager
Put a policy.json at /Library/Application Support/WND Terminal/policy.json with the same keys. Make the folder writable by administrators only.
Which policy wins
WND Terminal uses the first policy it finds and doesn’t mix them. It checks the configuration profile for the Mac, then the profile for the user, then policy.json. If a policy exists but can’t be read, the app applies strict rules (encryption required, no trusting certificates) and says so.
Uninstall
Drag WND Terminal from Applications to the Trash. Each person’s settings stay behind, so a reinstall keeps them. To remove everything, also delete ~/Library/Application Support/com.wndsoftware.terminal (trusted certificates and the usage log) and ~/Library/WebKit/com.wndsoftware.terminal (saved connections, keyboard maps and display settings).