Docs

WND Terminal documentation

Guides for the IT teams who install, configure and license WND Terminal, and for anyone moving sessions over from another emulator.

In short

The WND Terminal docs show IT how to install and license it on Windows and Mac, and how to set rules people can’t change with Group Policy, Intune or a Mac configuration profile. They also cover importing PCOMM and Reflection files and sending the audit log to Splunk or Microsoft Sentinel.

Install

Set rules people can’t change

  • Group Policy. Copy the ADMX and ADML templates, find the settings and write connection lines.
  • Microsoft Intune. Deploy the MSI as an app, then set the policy by importing the ADMX or writing the registry values.
  • Policy settings reference. Every setting with its Group Policy name, type and effect, plus the connection format and code pages.

License

  • Licenses. The license key setting, where license files go, trials, expiry and the license usage dashboard.

Move from another emulator

Everyday use

  • Keyboard maps. The default 3270 keys, the keymap editor and the app’s own shortcuts.
  • Macros. Record, write, import and run macros, with the full command list.

Security

What you need before you start

  • The installers. WND-Terminal-Windows.msi for IT, WND-Terminal-Windows-setup.exe for one person, and WND-Terminal-Mac.dmg for Macs with macOS 11 or later.
  • Your license key. It’s the line starting with wnd1. under Your license on the customer portal.
  • The policy templates, WNDTerminal.admx with WNDTerminal.adml for Windows and WNDTerminal.mobileconfig for Macs.
  • The host name and port of each mainframe, and whether it has an encrypted port such as 992.

A typical rollout

  1. Download the installers and your license from the downloads page of the WND customer portal.
  2. Write the policy before you deploy the app. Put in the license key and your mainframe connections, so the first launch already has both.
  3. Deploy the MSI to Windows PCs and the app to Macs with the tools you already use.
  4. Point the audit log at your SIEM and the usage log at a share for the license usage dashboard.
  5. Let people import their own PCOMM or Reflection files, or run the Migration readiness report on the share that holds them.

Where things are

WhatWindowsMac
InstallerWND-Terminal-Windows.msi or WND-Terminal-Windows-setup.exeWND-Terminal-Mac.dmg
App (MSI install)C:\Program Files\WND TerminalApplications folder
Managed policyHKLM\SOFTWARE\Policies\WND Software\WND Terminal/Library/Managed Preferences, domain com.wndsoftware.terminal
policy.jsonC:\ProgramData\WND Software\WND Terminal\policy.json/Library/Application Support/WND Terminal/policy.json
License fileC:\ProgramData\WND Software\WND Terminal\/Library/Application Support/WND Terminal/
Trusted certificates, usage log%APPDATA%\com.wndsoftware.terminal~/Library/Application Support/com.wndsoftware.terminal
Saved connections, keyboard maps, display settings%LOCALAPPDATA%\com.wndsoftware.terminal~/Library/WebKit/com.wndsoftware.terminal

Questions

Where do I download WND Terminal?

From the downloads page of the WND customer portal at portal.wndsoftware.com. Trial users get their license on the trial page.

Does WND Terminal need internet access?

Not to run. The license is checked on the computer. On Windows, the installer needs internet access once, and only on a PC that doesn't already have Microsoft Edge WebView2.

Which systems does WND Terminal run on?

Windows, and macOS 11 or later on Apple Silicon or Intel. Citrix and Azure Virtual Desktop are supported, and a browser version runs through a gateway you host.

See it on your own mainframe.

Install WND Terminal on a handful of PCs or Macs, import your sessions and keymaps, and let a real team use it next to what you run today. Free, two to four weeks.