Skip to main content

Deployment Models

Overview​

ScrewDrivers supports multiple deployment models to accommodate diverse enterprise infrastructure requirements, strategic directions, and migration paths. Organizations can choose the deployment model that best fits their current environment and future plans.

On-Premises Client-Server Deployment​

Architecture​

Traditional on-premises deployment with client and server components installed on enterprise-owned and managed infrastructure.

Components​

Client Components:

  • Installation Location: End-user devices (desktops, VDI sessions, terminal server sessions)
  • Footprint: Minimal resource consumption
  • Connectivity: Network connection to server components required

Server Components:

  • Installation Location: Enterprise Windows servers (physical or virtual)
  • Server Types:
  • Requirements: Windows Server operating system, network accessibility

Management Console:

  • Access: Web-based or thick-client application
  • Location: Installed on administrator workstations or accessible via web browser
  • Authentication: Active Directory integrated

Infrastructure Requirements​

Network:

  • Internal network connectivity between clients and servers
  • Standard TCP/IP protocols
  • No internet connectivity required for basic operation
  • Optional internet access for software updates and support

Active Directory:

  • Domain-joined clients and servers (recommended)
  • AD integration for user/group management
  • AD-based authentication and authorization

Storage:

  • Local server storage for print spooling
  • Network storage for centralized configuration
  • Backup infrastructure for disaster recovery

Deployment Process​

  1. Server Installation: Install server components on designated servers
  2. License Server Setup: Configure license server and install license keys
  3. Client Deployment: Deploy client software via GPO, SCCM, or manual installation
  4. Printer Configuration: Configure printers and printer assignments
  5. Policy Setup: Configure printer profiles, permissions, and policies
  6. Testing: Validate printing and scanning from test users
  7. Rollout: Phased or full deployment to user population

Benefits​

Control and Security:

  • Full control over all components and data
  • No data leaves enterprise network
  • Compliance with data residency requirements
  • Air-gapped operation possible (no internet dependency)

Performance:

  • Low-latency access (LAN speeds)
  • No internet bandwidth consumption
  • Predictable performance characteristics

Customization:

  • Deep integration with enterprise systems
  • Custom configurations and workflows
  • Integration with on-premises document management systems

Considerations​

Infrastructure Costs:

  • Server hardware acquisition and maintenance
  • Windows Server licensing
  • Data center space and power
  • Backup and disaster recovery infrastructure

Operational Overhead:

  • Server patching and maintenance
  • Hardware lifecycle management
  • Capacity planning and scaling
  • On-call support requirements

Cloud Deployment​

Architecture​

ScrewDrivers management and coordination services hosted in cloud infrastructure, with client components installed on-premises or in cloud-based virtual desktops.

Cloud Connector​

Purpose: Simplifies cloud-based print management resource setup and administration

Functionality:

  • Cloud-hosted management service
  • Centralized printer configuration repository
  • Policy distribution to clients
  • License management
  • Reporting and analytics

Hosting Options:

  • Tricerat-hosted cloud service (SaaS)
  • Customer-hosted cloud infrastructure (IaaS)
  • Hybrid hosting (some components cloud, some on-premises)

Components​

Cloud Services:

  • Management portal (web-based)
  • Configuration database
  • Policy engine
  • Reporting and analytics
  • License validation service

On-Premises Clients:

  • Client software installed on end-user devices
  • Internet connectivity to cloud services required
  • Local print job processing
  • Direct printer communication (serverless model)

Cloud-Based Virtual Desktops:

  • Azure Virtual Desktop (AVD)
  • Windows Virtual Desktop (WVD)
  • Citrix Cloud
  • VMware Horizon Cloud

Azure Integration​

Azure Virtual Desktop Support:

  • Optimized for AVD/WVD environments
  • Session host printing configuration
  • FSLogix profile integration
  • Azure AD authentication

Azure Remote Desktop Services:

  • RDS session printing
  • Per-session printer assignment
  • Azure-based print servers (optional)

Azure Network Integration:

  • VNet integration for hybrid connectivity
  • Azure ExpressRoute support
  • Site-to-site VPN compatibility

Deployment Process​

  1. Cloud Service Activation: Activate Tricerat cloud services or deploy to customer cloud
  2. Network Connectivity: Establish secure connectivity from clients to cloud
  3. Client Deployment: Deploy client software to endpoints
  4. Printer Configuration: Configure printers in cloud management portal
  5. User Assignment: Assign printers to users/groups via cloud console
  6. Policy Configuration: Define printer profiles and policies in cloud
  7. Rollout: Enable cloud-based print management for users

Benefits​

Infrastructure Reduction:

  • No on-premises server infrastructure required
  • Reduced capital expenditure
  • Elastic scalability
  • Reduced data center footprint

Operational Simplification:

  • No server patching or maintenance
  • Automatic updates and feature releases
  • Built-in high availability
  • Disaster recovery included

Accessibility:

  • Remote worker support without VPN
  • Global access to print management
  • Mobile device integration
  • Multi-site deployments simplified

Considerations​

Internet Dependency:

  • Requires reliable internet connectivity
  • Internet outage impacts print management
  • Bandwidth considerations for distributed locations

Data Residency:

  • Print metadata stored in cloud
  • Compliance and regulatory considerations
  • Evaluate data residency requirements

Connectivity Requirements:

  • Clients must reach cloud services
  • Firewall configuration for outbound connections
  • May require VPN for printer access

Serverless Deployment​

Architecture​

Eliminates traditional print servers by leveraging direct IP printing with centralized cloud or on-premises management.

Core Concept​

Direct IP Printing: Client devices communicate directly with network printers using IP protocols, bypassing print servers entirely.

Centralized Management: Management service (cloud or on-premises) provides printer configurations and policies without handling print jobs.

Components​

Management Service:

  • Lightweight management application (cloud or on-premises)
  • Printer configuration repository
  • User/group printer assignment policies
  • License validation
  • Minimal resource requirements (no print job processing)

Client Components:

  • Universal print driver
  • Direct IP printing capability
  • Policy retrieval from management service
  • Local print job processing and transmission

Network Printers:

  • IP-connected printers
  • Standard printing protocol support (IPP, LPR, RAW/Port 9100)
  • No server dependency

Network Requirements​

Connectivity:

  • IP routing between clients and printers (direct or via router)
  • DNS resolution for printer discovery (optional)
  • Firewall rules permitting client-to-printer communication
  • Standard printer protocols (TCP ports 515, 631, 9100)

Infrastructure:

  • Network switches and routers (standard infrastructure)
  • DHCP or static IP addressing for printers
  • Optional: DNS records for printer names
  • No dedicated print servers

Deployment Process​

  1. Management Service Setup: Deploy management service (cloud or on-premises)
  2. Network Preparation: Ensure IP connectivity between clients and printers
  3. Printer Registration: Register printers in management service with IP addresses
  4. Client Deployment: Install client software on endpoints
  5. Printer Assignment: Assign printers to users/groups in management console
  6. Policy Distribution: Configure and distribute printer profiles
  7. Validation: Test direct IP printing from client devices

Benefits​

Infrastructure Elimination:

  • No print servers required
  • Reduced hardware costs
  • Eliminated server licensing costs
  • Simplified infrastructure

Performance:

  • Reduced print job latency (no intermediate server)
  • Better scalability (no server bottleneck)
  • Improved reliability (fewer failure points)

Operational Efficiency:

  • No server maintenance or patching
  • Simplified troubleshooting (fewer components)
  • Reduced complexity
  • Lower total cost of ownership

Considerations​

Network Design:

  • Requires proper network routing for client-to-printer connectivity
  • May require network changes for segmented networks
  • Firewall rules must permit necessary protocols

Printer Requirements:

  • All printers must be network-connected with IP addressing
  • USB/local printers not supported in pure serverless model
  • Older printers may lack required protocol support

Management Service Placement:

  • Cloud vs. on-premises management service decision
  • Internet connectivity requirements for cloud-based management
  • High availability considerations for management service

Hybrid Deployment​

Architecture​

Combines multiple deployment models to accommodate complex enterprise requirements, migration scenarios, or multi-site architectures.

Common Hybrid Scenarios​

Mixed Server/Serverless​

  • Some printers accessed via print servers
  • Other printers via direct IP (serverless)
  • Unified management across both modes
  • Policy-based routing (server vs. serverless)

Use Case: Large enterprise with legacy print infrastructure transitioning to serverless model

Cloud Management with On-Premises Infrastructure​

  • Cloud-based management and policy service
  • On-premises clients and printers
  • Internet connectivity for management
  • Local network for print job transmission

Use Case: Organization reducing data center footprint while maintaining local printing

Multi-Site Architecture​

  • Different deployment models per site
  • Centralized cloud management
  • Site-specific infrastructure decisions
  • Unified reporting and policies

Use Case: Global enterprise with varying infrastructure capabilities per location

VDI + Physical Desktop Hybrid​

  • Virtual desktops (VDI/RDS) with server-based printing
  • Physical desktops with serverless or direct IP printing
  • Unified printer management
  • User printer assignments follow across environments

Use Case: Enterprise with mix of virtual and physical desktop deployments

Migration Scenarios​

Server-to-Serverless Migration​

Phase 1: Coexistence

  • Deploy serverless infrastructure alongside existing servers
  • Pilot departments on serverless model
  • Validate functionality and performance

Phase 2: Department Migration

  • Migrate departments sequentially
  • Maintain server access for unmigrated users
  • Monitor and troubleshoot

Phase 3: Server Decommission

  • Complete migration to serverless
  • Decommission print servers
  • Optimize network for direct IP printing

On-Premises-to-Cloud Migration​

Phase 1: Hybrid Management

  • Deploy cloud management service
  • Maintain on-premises servers initially
  • Dual management capability

Phase 2: Workload Migration

  • Migrate printer configurations to cloud
  • Transition user policies to cloud service
  • Validate cloud-based management

Phase 3: Server Retirement

  • Decommission on-premises management servers
  • Full cloud-based management
  • Optimize for cloud architecture

Hybrid Benefits​

Flexibility:

  • Choose optimal deployment per site/department
  • Accommodate infrastructure constraints
  • Support diverse business requirements

Risk Mitigation:

  • Gradual migration reduces risk
  • Fallback options during transition
  • Validate new model before full commitment

Cost Optimization:

  • Leverage existing infrastructure investments
  • Transition to lower-cost models over time
  • Optimize per location/requirement

Hybrid Challenges​

Complexity:

  • Multiple deployment models to manage
  • Different troubleshooting procedures
  • Staff training on multiple architectures

Consistency:

  • Ensure consistent user experience across models
  • Unified policy management
  • Centralized reporting across architectures

Deployment Decision Factors​

Infrastructure Preferences​

Existing Infrastructure:

  • On-premises: Leverage existing servers, prefer on-prem deployment
  • Cloud-first: Choose cloud or serverless deployment
  • Hybrid: Mixed deployment based on existing investments

Strategic Direction:

  • Cloud migration path: Start with cloud or plan hybrid transition
  • Infrastructure reduction: Choose serverless model
  • Maintain control: On-premises deployment

Regulatory and Compliance​

Data Residency:

  • Strict requirements: On-premises deployment
  • Flexible requirements: Cloud deployment acceptable
  • Regional variations: Hybrid with regional deployment models

Audit Requirements:

  • All models support comprehensive logging
  • On-premises provides maximum control over audit data
  • Cloud models may require evaluation of vendor compliance

Performance Requirements​

Latency Sensitivity:

  • Critical latency: Serverless (fewest hops)
  • Moderate sensitivity: On-premises client-server
  • Tolerant: Cloud deployment acceptable

Scalability:

  • Rapid growth: Cloud or serverless (best scalability)
  • Stable environment: On-premises adequate
  • Variable demand: Cloud elastic scaling

Cost Considerations​

Capital vs. Operational:

  • Prefer CapEx: On-premises infrastructure investment
  • Prefer OpEx: Cloud subscription model
  • Minimize both: Serverless with minimal infrastructure

Total Cost of Ownership:

  • On-premises: Higher upfront, lower ongoing (if infrastructure exists)
  • Cloud: Lower upfront, predictable ongoing subscription
  • Serverless: Lowest infrastructure cost, minimal ongoing maintenance

Operational Capabilities​

IT Staff Skills:

  • Strong server administration: On-premises
  • Cloud expertise: Cloud deployment
  • Limited IT staff: Cloud or serverless (reduced maintenance)

Support Model:

  • 24/7 operations: Cloud (vendor-managed infrastructure)
  • Business hours: On-premises acceptable
  • Minimal staff: Serverless or cloud deployment

Summary​

ScrewDrivers supports diverse deployment models including traditional on-premises client-server, cloud-based management, serverless direct IP printing, and hybrid combinations. Organizations can select the deployment model aligned with their infrastructure strategy, compliance requirements, performance needs, and operational capabilities, with migration paths available to transition between models as requirements evolve.