Docs

Deploy WND Terminal settings with Group Policy

The ADMX template puts every WND Terminal setting under Administrative Templates, for computers and for users. People see the settings as locked.

In short

Copy WNDTerminal.admx to C:\Windows\PolicyDefinitions or your Central Store, and WNDTerminal.adml to the en-US folder there. The settings then appear under Administrative Templates > WND Software > WND Terminal.

FileCopy to
WNDTerminal.admxC:\Windows\PolicyDefinitions, or your domain’s Central Store at \\<domain>\SYSVOL\<domain>\Policies\PolicyDefinitions
en-US\WNDTerminal.admlThe en-US folder in the same place

Install the templates

  1. Copy the two files as shown above.
  2. In Group Policy Management, edit a Group Policy Object.
  3. Open Computer Configuration or User Configuration, then Administrative Templates > WND Software > WND Terminal.
  4. Set the policies you need and link the GPO.

Use Computer Configuration to cover every user of a PC. Use User Configuration to target people wherever they sign in.

The settings

Settings named “Turn off”, “Prevent” or “Only allow” write 0 to an Allow value when you enable them. Enabling Turn off printing sets AllowPrint to 0. The policy settings reference has the full detail for each one.

Group Policy settingRegistry valueEffect
Require encrypted connectionsRequireEncryptionEvery connection uses TLS 1.2 or later. The Secure switch is locked on.
Prevent users from trusting certificatesAllowUserTrust = 0Only certificates Windows trusts or that you list are accepted.
Only allow the connections set by ITAllowOtherHosts = 0People pick from your list instead of typing an address.
Mainframe connectionsConnections subkeyThe connections offered to everyone, one per line.
Trusted mainframe certificatesTrustedCertificates subkeySHA-256 fingerprints to trust, one per line.
Turn off “Explain this screen” AIAllowAI = 0No screen text goes to an AI model.
AI model serverAIEndpoint, AIModelThe model server and model everyone uses.
Turn off usage recordingRecordUsage = 0No session log on the PC.
License usage collectionUsageFolder, PeopleFile, LicensedSeatsData for the license usage dashboard.
License keyLicenseYour license key.
License fileLicenseFilePath to the license file.
DepartmentDepartmentDepartment recorded with usage.
Mainframe character set (code page)CodePageDefault EBCDIC code page.
Hide card numbers on screensMaskCardNumbersCard numbers show only the last four digits.
Other values to hide on screensMaskPatterns subkeyRegular expressions, one per line.
Turn off copying from the screenAllowCopy = 0No Copy or Copy as table.
Turn off pasting into the screenAllowPaste = 0No pasting.
Turn off printingAllowPrint = 0No printing the screen.
Turn off file transferAllowFileTransfer = 0No IND$FILE transfers.
Turn off the audit logRecordAudit = 0No audit log.
Audit log destinationsAuditFolder, AuditSplunkUrl, AuditSplunkToken, AuditSyslogFolder, Splunk HEC and CEF syslog.
Sign in with smart cards (client certificates)SignInWithCertificate, CertificateIssuerSign in with the person’s certificate.

Write mainframe connections

Mainframe connections takes one line per connection, in the form Name|host|port|secure.

Production|mvs.example.com|992|secure
Test|mvstest.example.com|992|secure

The port and secure are optional. Without a port, 992 is used for secure connections and 23 for the rest. A connection marked secure is always encrypted. Add these at the end of a line when you need them.

AddExampleWhat it does
|cp1141Frankfurt|mvs.de.example|992|secure|cp1141Sets this connection’s host code page.
|backup=Production|mvs1.example.com|992|secure|backup=mvs2.example.com,10.1.2.3:992Backup addresses, tried in order when the main one doesn’t answer. The main port is used when one is left out.
|lu=CICS|mvs1.example.com|992|secure|lu=TCPPOOL1Connects as that terminal name (LU) or pool.
|smartcardPayroll|mvs1.example.com|992|secure|smartcardSigns in with the person’s certificate on this connection only.

Check what a PC received

Group Policy writes the values under HKEY_LOCAL_MACHINE\SOFTWARE\Policies\WND Software\WND Terminal, or the same path under HKEY_CURRENT_USER for user policy. Ordinary users can read these keys but can’t change them. Lists go in subkeys (Connections, TrustedCertificates, MaskPatterns) with one numbered value per line.

gpupdate /force
reg query "HKLM\SOFTWARE\Policies\WND Software\WND Terminal" /s

In WND Terminal itself, the “Managed” badge lists every setting that applies.

Computer policy and user policy

WND Terminal uses the first policy it finds and doesn’t mix them. Group Policy for the computer comes first, then Group Policy for the user, then policy.json. On a PC with computer policy for WND Terminal, user policy for it isn’t read.

If a policy exists but can’t be read, the app applies strict rules (encryption required, no trusting certificates) and says so.

Limits of any policy

A person with administrator rights on their own PC can remove any policy, for WND Terminal or any other program. To prevent that, don’t give staff administrator rights. You can also turn off the mainframe’s unencrypted port, so no one can connect without encryption.

Questions

Where do the WND Terminal ADMX and ADML files go?

WNDTerminal.admx goes in C:\Windows\PolicyDefinitions or your domain's Central Store. WNDTerminal.adml goes in the en-US folder there.

Can I set WND Terminal policy per user?

Yes, under User Configuration. If a PC also has computer policy for WND Terminal, the computer policy is used and the user policy isn't read.

What happens to settings I don't configure?

They keep their normal behaviour. Encryption is optional, people may trust certificates and any host is allowed.

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.