Skip to main content

ScrewDrivers Architecture Overview

Architectural Models​

ScrewDrivers supports two primary architectural deployment models, each optimized for different enterprise requirements and infrastructure preferences.

Traditional Client-Server Architecture​

Overview​

The client-server architecture represents the traditional print management deployment model, enhanced with ScrewDrivers' universal driver technology and performance optimizations.

Components​

The client-server architecture consists of three primary components that work together to deliver enterprise print management.

Client Component​

The client component is the ScrewDrivers session agent, which installs wherever applications run: RDS session hosts, Citrix VDAs, virtual desktops, or physical desktops. It provides Tricerat's virtual print driver, which captures print jobs from user applications and handles user preference collection, so the session host doesn't need manufacturer drivers. It's lightweight because it hands rendering off to the ScrewDrivers Print Server, where the manufacturer driver lives. Pro: Print Server Printing Architecture covers this model in depth.

Server Component​

Server components deploy on terminal servers, print servers, or dedicated management servers depending on your infrastructure. These servers handle the resource-intensive tasks of print job spooling, rendering, and routing. They also apply printer-specific profile settings and manage the connection between clients and physical printers. This server-side processing dramatically improves performance in VDI and terminal server environments.

Management Console​

Administrators use ScrewDrivers Administration, a console application installed on Windows servers or administrator workstations. The console provides centralized control over printer assignments, profile management, policy configuration, and job monitoring across the entire print infrastructure. You'll use it to map printers to users and groups, configure default settings, and troubleshoot printing issues.

  1. Job Initiation: User initiates print job from application
  2. Driver Processing: Universal driver captures print job and user preferences
  3. Spooling: Job spooled on terminal/print server (not client-side)
  4. Profile Application: Server applies printer-specific profile settings
  5. Job Routing: Server routes job to target printer (print server or direct IP)
  6. Printer Output: Job rendered and printed on physical device

Performance Characteristics​

Spooling Optimization:

  • Print job spooling hosted on terminal and print servers
  • Eliminates client-side spooling delays
  • Reduces network bandwidth consumption
  • Minimizes impact on user session performance

Server Benefits:

  • Reduced print spooler crashes through optimized spooling
  • Improved overall server performance
  • Faster print queue processing
  • Better resource utilization

Integration Points​

Print Server Integration:

  • Compatible with existing Windows Print Servers
  • Can leverage existing print queue infrastructure
  • Supports print server-based job management

Direct IP Printing:

  • Bypasses print servers for direct printer communication
  • Reduces server dependency
  • Maintains centralized management and policy enforcement

Serverless Architecture (Direct IP Printing)​

Overview​

The serverless architecture is Direct IP printing, the Pro and Enterprise model also known by its component name, ScrewDrivers Direct. It removes Windows print servers from the print path: session hosts send jobs straight to network printers over IP. It doesn't remove the rest of the ScrewDrivers infrastructure, though. You still manage printers and assignments centrally, and the session agent still builds printers in each session. Pro: Direct IP Printing Architecture covers this model in depth.

Components​

Direct IP printing uses the same management infrastructure as print server printing, minus the print servers.

SQL Server Database​

A Microsoft SQL Server database (full SQL Server or SQL Server Express) stores printer definitions (IP addresses, host names, ports), the native manufacturer drivers, printer assignments, and printer profiles. Every session host reads from the same database, so you configure assignments once.

ScrewDrivers Administration and the Tricerat License Server​

Administrators use ScrewDrivers Administration to create Direct IP printers, import manufacturer drivers into the database, and assign printers to users, groups, computers, IP ranges, or custom criteria. The Tricerat License Server licenses the session agents.

Session Agent​

The session agent installs on the session host: the RDS host, Citrix VDA, virtual desktop, or physical workstation where applications run. At sign-in it queries the database for the user's Direct IP printers and creates standard Windows Direct IP printers using the native manufacturer drivers, which ScrewDrivers distributes from the database to the session host as needed. Direct IP printing doesn't use Tricerat's virtual driver.

  1. Assignment: At sign-in, the session agent queries the database for the Direct IP printers assigned to the user
  2. Printer Creation: The session agent creates Windows Direct IP printers in the session with the native manufacturer driver, distributing the driver to the session host first if it isn't there yet, and applies any printer profiles
  3. Job Initiation: The user prints from an application, with the manufacturer's own print preferences
  4. Rendering and Spooling: The native driver renders the job on the session host, and the session host's Windows spooler spools it
  5. Direct Transmission: The session host sends the rendered job straight to the printer's IP address over Raw/port 9100, LPR (515), or IPP (631)
  6. Printer Output: The physical printer prints the job

Performance Characteristics​

Infrastructure Reduction:

  • Eliminates print server hardware and maintenance
  • Removes the print server as a hop in the print path
  • Keeps SQL Server, ScrewDrivers Administration, and the License Server for central management

Trade-offs:

  • Rendering moves to the session hosts instead of print servers
  • Each session host needs native drivers for the printers its users print to, distributed from the database

Network Considerations​

Printer Accessibility:

  • Requires IP-level connectivity between session hosts and printers, wherever the session hosts run
  • Cloud-hosted session hosts may need VPN or network peering to reach printers on office networks
  • Firewall rules must permit session host-to-printer traffic (typically TCP 9100, 515, or 631)
  • Session hosts also connect to SQL Server (1433) and the License Server (6200); see Ports and Firewall Rules

Hybrid Deployments​

ScrewDrivers supports hybrid architectures combining elements of both models:

Mixed Mode Operation​

  • Some printers accessed via print servers
  • Other printers accessed via direct IP
  • Centralized management across both modes
  • Policy-based routing decisions

Cloud-Hybrid Architecture​

  • Session hosts on-premises, in the cloud, or both
  • Cloud Connector (Enterprise) relays print traffic to print servers for remote and cloud sites (see Enterprise remote and cloud printing)
  • Mix of on-premises and cloud-accessible printers
  • Unified management in ScrewDrivers Administration

Gradual Migration​

  • Phased transition from server-based to serverless
  • Coexistence during migration period
  • Printer-by-printer or department-by-department migration
  • No disruption to end users during transition

Spooling Architecture​

Server-Side Spooling (Client-Server Model)​

Benefits:

  • Offloads spooling from client devices
  • Improves user session responsiveness
  • Reduces client resource consumption
  • Better suited for thin client and VDI environments

Process Flow:

  1. Client sends print job to server
  2. Server spools job to disk
  3. Server renders job for target printer
  4. Server transmits rendered job to printer

Session Host Spooling (Direct IP Model)​

Benefits:

  • Removes the print server from the print path
  • Distributes rendering across session hosts

Process Flow:

  1. Native manufacturer driver on the session host renders the job
  2. Session host's Windows spooler spools the job
  3. Session host transmits the rendered job directly to the printer's IP address

Printer Discovery and Assignment​

Active Directory Integration​

User-Based Assignment:

  • Printers assigned based on AD user account
  • Assignment follows user across different devices
  • Automatic printer mapping at logon

Group-Based Assignment:

  • Printers assigned to AD security groups
  • Simplified management for department/role-based printing
  • Inheritance from nested group memberships

Workstation-Based Assignment:

  • Printers assigned to specific computer objects
  • Location-based printing (conference rooms, kiosks)
  • Override user-based assignments when necessary

Printer Profiles​

Configuration Management:

  • Default printer settings stored in profiles
  • Applied automatically based on user/group/workstation
  • Override manufacturer defaults with organizational policies

Per-Session vs. Per-User:

  • Per-session profiles: Apply to individual user sessions
  • Per-user profiles: Follow user across sessions and devices
  • Granular control over printer behavior

Session Management​

Per-Session Printer Assignment​

VDI and Terminal Server Optimization:

  • Printers assigned dynamically at session creation
  • Different users on same server see different printers
  • Automatic cleanup when session terminates

Benefits:

  • Reduces printer enumeration time
  • Minimizes memory consumption
  • Improves multi-session server performance

Data Flow and Communication​

Client-to-Server Communication (Client-Server Model)​

Protocols:

  • Proprietary Tricerat protocols for print job submission to the ScrewDrivers Print Server (TCP 5550–5553, TLS 1.2)
  • SQL Server connections for assignments and configuration (TCP 1433, TLS 1.2 enabled driver)
  • Standard Windows printing protocols where applicable

Security:

  • Encrypted communication channels
  • Authentication via Active Directory
  • Authorization via policy engine

Session Host-to-Printer Communication (Direct IP Model)​

Protocols:

  • Standard printer protocols (Raw/Port 9100, LPR on 515, IPP on 631)
  • Direct IP addressing

Discovery:

  • Static IP addresses or DNS host names (DNS names recommended)
  • Network discovery from ScrewDrivers Administration, or printer objects created manually
  • Printer definitions stored in the ScrewDrivers SQL database

Scalability Considerations​

Client-Server Scalability​

Vertical Scaling:

  • Add server resources (CPU, memory, disk)
  • Optimize for increasing print job volume
  • Limited by single server capacity

Horizontal Scaling:

  • Deploy multiple print/terminal servers
  • Load distribution across server farm
  • Geographic distribution for multi-site deployments

Direct IP Scalability​

Session Host Scaling:

  • No print server bottleneck
  • Printing capacity scales with session host capacity
  • Limited by network connectivity and printer throughput

Management Infrastructure:

  • Session hosts still connect to SQL Server and the Tricerat License Server
  • Database size grows with the driver library (1–10 GB is typical)

Diagram: Architecture Comparison​

Client-Server Architecture Flow​

[User Application]
|
v
[ScrewDrivers Universal Driver]
|
v (Print Job)
[Terminal/Print Server]
| |
v v
[Print Server] [Direct IP]
| |
v v
[Physical Printer]

Serverless (Direct IP) Architecture Flow​

[Session Agent] <-- (Assignments and drivers at sign-in) -- [SQL Server Database]
|
v (Creates Direct IP printers)
[User Application]
|
v
[Native Manufacturer Driver + Windows Spooler on Session Host]
|
v (Print Job - Raw/9100, LPR, or IPP)
[Physical Printer]

Choosing the Right Architecture​

Client-Server Model Best For:​

  • Environments with existing print server infrastructure
  • Organizations requiring centralized job rendering
  • Thin client deployments with limited client resources
  • Compliance requirements for print job interception/logging
  • Networks where client-to-printer communication is restricted

Serverless Model Best For:​

  • Organizations seeking to reduce infrastructure overhead
  • Modern cloud-first or hybrid environments
  • Deployments where session hosts have reliable printer connectivity
  • Environments prioritizing infrastructure simplification
  • Cost-sensitive organizations seeking to eliminate server licensing

Hybrid Model Best For:​

  • Large enterprises with diverse printing requirements
  • Organizations transitioning from legacy to modern architectures
  • Multi-site deployments with varying network topologies
  • Environments requiring mix of centralized and distributed printing

Summary​

ScrewDrivers' flexible architecture supports both traditional client-server and modern serverless deployment models, enabling organizations to choose the approach that best fits their infrastructure, performance requirements, and strategic direction. The platform's ability to support hybrid deployments provides a migration path and maximum deployment flexibility across diverse enterprise environments.