All documentation

T27 eXpress Enterprise — Administrator Guide

Plan, package, and lock down a T27 eXpress Enterprise rollout — settings location, configuration lock, and centralised distribution.

Last updated February 1, 2010

Role of the Administrator

The T27 eXpress Enterprise Administrator builds the master configuration that every workstation receives. It covers connection routing, screen layouts, keyboards, macros, scripts, printers, and the lock options that prevent end users from undoing centrally-managed settings.

Settings location and configuration lock

Each Windows system can store T27 eXpress Enterprise settings either per user (default) or in a shared All Users profile. When you switch to All Users, enable the configuration lock so end users cannot modify the shared file. Emulator settings and eXpress Connect transport settings move between locations independently.

Defining the master configuration

  • Define routes and virtual destinations in eXpress Connect (or Component Configuration).
  • Create one screen per role: terminal type, rows, columns, pages, palette, font, keyboard layout, macros/scripts, and printer assignments.
  • Build appearance, keyboard, and character-translation schemes once and reuse them across screens.
  • Configure trace folders and a default trace level appropriate for your support workflow.
  • Set the Control Panel preferences end users will see — dock side, auto-hide, screen color tags, transparency, start-with-Windows.

User Restriction model

Restriction Settings determine which menus, dialogs, and actions remain available to end users. Use the eXpress User Capabilities at a Glance summary to verify the resulting role before rolling out. Enable/Disable Features lets you toggle individual capabilities without rewriting the whole restriction set.

Distribution

Once the master configuration is verified on a reference machine, package it for rollout. Two patterns are common: copy the configuration files into the All Users profile during installation and lock them, or push them through your software-distribution tool. Either way, end users should not have write access to the shared configuration directory.

Maintenance

  • Hold an unlocked golden image on an admin workstation and re-export after each change.
  • Use Settings Location in eXpress Connect / Component Configuration to compare per-user vs. All Users state when troubleshooting drift.
  • Uninstall the previous emulator before upgrading to avoid orphaned components — existing configuration files survive the uninstall.