Glossary
One term, one meaning. This page defines the Tricerat-specific vocabulary and pins down how these docs use industry terms — not to settle industry debates, but so a word means the same thing on every page. When two names exist for the same thing, the bold form is the one the documentation uses.
ScrewDrivers product terms
Assignment — The link between an object and an owner in ScrewDrivers Administration: this printer (object) is assigned to this group (owner). Assignments flow through inheritance, and can be allowed, denied, or blocked.
Auto client update — The v7 mechanism where a client downloads the plugin matching the server's version at the start of each session, so client and server stay in step without a client rollout. See How Automatic Client Updates Work.
Badge release — Informal name for Secure Release (below). The docs use "Secure Release" for the feature and "badge" for the card the user taps.
Cloud Connector — The Enterprise service that relays print traffic for remote and cloud printing scenarios. See the Cloud Connector reference.
Direct IP printing (ScrewDrivers Direct) — Pro/Enterprise architecture where session hosts send jobs straight to network printers, with no Windows print server in the path. See Direct IP architecture.
Editions — ScrewDrivers v7 ships as Essentials (endpoint printer and scanner redirection), Pro (adds centralized management: Administration, Print Server, Direct), and Enterprise (adds Mobile, Connector, System Printers). See the product overview.
Hold-and-release — Print jobs held rather than printed immediately, released by the user at or near the device. The docs use this term for the general capability; Secure Release (below) is ScrewDrivers' implementation of it.
License Server (Tricerat License Server) — The service that manages concurrent license checkout. Licensing models: NLS (nodelocked — a key tied to one machine, no license server), CCU (concurrent user), CCS (concurrent server). See the license types overview and License Server Compatibility for per-release version requirements.
Maps (ScrewDrivers Maps) — Location-based printer assignment: users pick their location from a map or list and get that location's printers. See Maps.
Object — Anything assignable in ScrewDrivers Administration: printers, print servers, configuration settings, profiles. Objects are assigned to owners. See Managing Objects.
Owner — Who or what receives assignments in ScrewDrivers Administration: users, groups, organizational units, or clients. See Managing Owners.
Printer profile — Captured driver settings (tray, duplex, defaults) stored as a reusable object and assigned to owners. Created with ScrewDrivers Printer Discovery. See Printer Profiles.
ScrewDrivers Administration — The desktop management console for Pro/Enterprise (a .NET 4.8 application; called Simplify Console in v6). Its permissions are its own — separate from domain permissions — and initialize when the Database installer runs.
ScrewDrivers Database — The SQL Server database holding all Pro/Enterprise configuration, and the once-per-environment installer that creates and upgrades it.
ScrewDrivers Endpoint / Endpoint Client — The client-side component that redirects the endpoint's printers into remote sessions; the Endpoint Client is its workstation application. See the Endpoint Client reference.
ScrewDrivers Gateway — The Enterprise service enabling mobile printing and TCP/IP clients. See Installing the ScrewDrivers Gateway.
ScrewDrivers Print Server — The service installed on Windows print servers that routes ScrewDrivers jobs to their queues (called Simplify Printing in v6). See the Print Server overview.
ScrewDrivers Printers — The end-user application for choosing printers and maps (called the User Assigned Printers Tool in v6).
ScrewDrivers Reports — Print activity reporting and auditing (called Print Job Viewer in v6). See Reports.
ScrewDrivers Scanning / Scanning Client — Scanner redirection into remote sessions and its client application (Pro/Enterprise for scanning features; see edition notes on each page).
Session agent (Session Host Agent) — The ScrewDrivers component that builds and manages printers where applications run. It installs on remote session hosts (RDS, Citrix, VDI) and just as validly on desktops whose applications run locally. Installers call it the Session Host Agent.
Session settings — Configuration objects controlling how printers behave in sessions — creation, naming, rendering — assigned to owners like any object. See Endpoint Printer Session Settings.
Simplify — Tricerat's v6-era product branding (Simplify Printing, Simplify Suite, Simplify Console). v6 reached end of life December 31, 2025. The complete v6-to-v7 name mapping is in What Changed in ScrewDrivers v7.
Industry terms as these docs use them
One principle organizes several of these terms: printers are built where applications run. Applications running locally on a desktop → the session agent manages printers right there. Applications running in a VDI or RDS session → the session agent in that session builds the printers. And printing from that session to a printer only your local device knows about → that's redirection: session agent in the session, Endpoint Client on the device.
Endpoint — The physical device the user is sitting at: a workstation, laptop, or thin client. What runs on it follows from where applications run: if the user's applications run locally, the endpoint is itself the session host (the desktop form below) and runs the session agent; if applications run in a remote session, the endpoint runs the ScrewDrivers Endpoint Client while the remote session host runs the session agent — the redirection pairing.
Network printing — Printing to printers reachable over the network — through Windows print server queues or Direct IP — with no endpoint involvement required. Contrast with printer redirection.
Printer redirection (redirection printing) — Making a printer that's local to the endpoint available inside a remote session: the session agent in the session builds the printer, and the Endpoint Client on the local device delivers the job to the physical printer. Contrast with network printing.
Print queue — The Windows queue that accepts jobs for a printer, whether on a print server or a local machine. ScrewDrivers routes to queues; queue health is a Windows concern.
RDS — Microsoft Remote Desktop Services: session-based Windows desktops and apps. One of the delivery platforms ScrewDrivers supports, alongside Citrix and Omnissa Horizon.
Secure Release (ScrewDrivers Secure Release) — The Enterprise feature that holds print jobs until the user taps a badge at the printer and chooses what to print. Available as a beta starting in ScrewDrivers 7.10. See Setting Up ScrewDrivers Secure Release.
Session host — Wherever the user's applications actually run — and therefore where the session agent installs and printers get built. It takes two forms: a remote session host (an RDS session host, Citrix VDA, or virtual desktop on Citrix, Omnissa Horizon, or Azure Virtual Desktop) and a desktop (a physical computer or laptop whose applications run locally). Older pages may say App Server or VDI host for the remote form — same thing; these docs standardize on session host.
Thin client — A minimal endpoint device (IGEL and similar) that exists mainly to reach a remote session. ScrewDrivers supports thin clients via platform-specific clients; see ScrewDrivers on IGEL.
Universal print driver — See virtual print driver.
VDI — Virtual Desktop Infrastructure. These docs use it broadly for pooled or personal virtual desktops (Citrix, Omnissa Horizon, Azure Virtual Desktop) rather than any narrower definition — when precision matters, we name the platform. A "VDI host" in older pages means the virtual machine a user connects to; see session host.
Virtual channel — The side-channel within a remoting protocol (ICA, RDP, Horizon's protocols) that applications use to move data between endpoint and session. ScrewDrivers' client and session components communicate over virtual channels; see Client Security.
Virtual print driver (also called universal print driver — the terms are used interchangeably here; sales materials tend to say universal) — The single ScrewDrivers driver on the session host that virtualizes the actual printer driver: sessions print to one driver, and each job renders against the real driver where the printer lives. This is the core mechanism that removes per-model driver management from session hosts.
Spot a term used inconsistently, or one that belongs here? Tell support — this page is the tie-breaker for terminology across the docs.