Enterprise: Remote Printing & Cloud Printing Architecture
Overview
When you move virtual desktops to Azure or another cloud, the printers stay behind. They sit in offices, clinics, warehouses and branch sites, on networks the cloud-hosted session hosts can't reach. The usual fixes are a site-to-site VPN, ExpressRoute, or opening inbound firewall rules at every site, and each brings cost, change control and risk.
ScrewDrivers solves this with the Cloud Connector. It connects print servers in remote networks back to the servers and desktops running in the cloud. A remote connector at each print server site makes an outbound connection to an internal connector that runs beside your session hosts, and print traffic flows over that connection. The print server sites don't need inbound firewall rules, and you don't need network-level connectivity between the sites and the cloud.
The Cloud Connector is part of ScrewDrivers and runs entirely on servers you own. There's no third-party or Tricerat-hosted service in the path.
The cloud printing challenge
In a standard print server deployment, the ScrewDrivers Print Server Session Agent on each session host contacts the print servers when a user logs on, builds that user's printers, and sends print jobs to the print servers. That assumes the session hosts can open connections to the print servers.
Cloud hosting often breaks that assumption:
- Azure Virtual Desktop with on-premises printers. Session hosts run in Azure; print servers and printers stay on-premises, with no route between them unless you build one.
- Central VDI with remote sites. Citrix or Omnissa desktops run in one data center, and print servers sit at sites the data center can't reach directly.
- Managed service providers. One hosted environment serves many customer networks that have to stay isolated from each other.
- Locked-down network segments. Security policy blocks session hosts from opening connections into the network where the print servers live.
In each case the print server sites can usually make outbound connections, even when nothing is allowed in. The Cloud Connector builds on that.
Architecture components

Internal connector
You install one internal connector where users' printers are created: on or near your session hosts, in the same network as them. In Azure, that's typically a Windows VM in the same virtual network as your AVD host pool. You install it by selecting the ScrewDrivers Cloud Connector service in the ScrewDrivers Enterprise installer and choosing Internal mode.
The internal connector only accepts connections. Remote connectors connect to it, and session hosts on the same network talk to it instead of trying to reach remote print servers.
Remote connectors
You install one remote connector at each remote location that hosts print servers, choosing Remote mode in the installer. If your print servers are in three offices, you install three remote connectors.
Each remote connector makes an outbound connection to the internal connector and keeps it open. That connection is the channel print traffic travels over. Because the remote connector always starts the connection, the print server site needs only an outbound rule to the internal connector.
Print Server Session Agent
The Print Server Session Agent on each session host works the same way it does in any print server deployment: it builds each user's assigned printers at logon and sends their print jobs on. With the Cloud Connector in place, it talks to the local internal connector instead of contacting print servers directly.
Print servers
The ScrewDrivers Print Server service runs on your Windows print servers at each remote site, alongside that site's remote connector (often on the same server). Print servers keep the manufacturer drivers and print jobs with them, exactly as they do without the Cloud Connector.
Database and administration
Like other Pro and Enterprise deployments, the ScrewDrivers Database holds printer assignments, settings and job logs, and ScrewDrivers Administration manages them. You manage the Cloud Connector itself with the ScrewDrivers Connector application, which installs wherever you install a connector: on the internal connector you set the listening addresses, ports and security settings for incoming connections, and on each remote connector you set the internal connector's address and the retry behavior.
How it works
Setting up the connection
- You install the internal connector beside your session hosts and note its hostname or IP address.
- At each print server site, you install a remote connector and point it at the internal connector.
- Each remote connector authenticates to the internal connector and holds an outbound connection open. The ScrewDrivers Connector application on the internal connector lists each remote connector and whether it's connected.
Logon and printer creation
When a user logs on to a session host, the Print Server Session Agent asks the local internal connector for the user's printers. The internal connector passes the request to the remote connector at the right site over that site's open connection, the remote connector queries its local print servers, and the answer comes back the same way. The agent then creates the user's printers in the session.
Printing
When the user prints, the job travels the same channel: session host to internal connector, internal connector to the remote connector, and the remote connector to the print server, which prints it with the manufacturer driver. To the user, it's an ordinary printer. To the print server, it's an ordinary ScrewDrivers print job.
The extra hop adds a small amount of latency compared with direct print server communication, typically under 50 ms, which users don't notice when they print.
Security considerations
Outbound-only from the remote sites
Remote connectors only ever make connections; the internal connector only ever accepts them. Print server sites need no inbound rules at all, which suits sites you don't fully control, such as clinics, branch offices and customer networks. You open inbound ports only on the internal connector, not on every print server.
The ports are listed in Ports and Firewall Rules: remote connectors connect to the internal connector on TCP 5551 to authenticate, and the connectors use TCP 5550 (or 5553) for their connections with print servers.
Encryption and authentication
ScrewDrivers uses TLS 1.2 on the network connections it manages, including the connections between connectors. Remote connectors authenticate to the internal connector before any print traffic flows, and user access to printers still follows the assignments and permissions in ScrewDrivers Administration.
Infrastructure you control
The internal and remote connectors run on your servers, in your networks and cloud subscriptions. Print data doesn't pass through any service outside your environment.
Audit logging
Print jobs that cross the Cloud Connector are logged the same way as any other ScrewDrivers job, so your job records cover remote sites too.
Deployment scenarios
Azure Virtual Desktop with on-premises printers
This is the most common scenario. Install the internal connector in the Azure virtual network alongside your AVD session hosts, and a remote connector at each on-premises site with print servers. Users in AVD get their on-premises printers without ExpressRoute or a site-to-site VPN, and the sites open nothing inbound.
Central VDI with remote sites
When Citrix, Omnissa or RDS desktops run in one data center and print servers sit at sites the data center can't reach, put the internal connector in the data center and a remote connector at each site.
Managed service providers
An MSP can run one internal connector beside its hosted session infrastructure and a remote connector in each customer's network. Each customer site connects out to the MSP, and no customer network needs to accept connections from the hosting environment.
Limitations and considerations
The internal connector is a dependency
If the internal connector is unavailable, users can't print to any printers that go through the Cloud Connector. Plan redundancy for production: Windows failover clustering or multiple internal connector instances behind a load balancer.
A remote connector failure affects only printers at that site. Where a site has redundant print servers, consider more than one remote connector there too.
Sizing
The internal connector carries the printer queries and print jobs for every remote site, so give it adequate bandwidth and resources. For hundreds of concurrent users, run it on a dedicated server rather than sharing a session host. Remote connectors carry only their own site's traffic and can usually share the print server.
More moving parts
The Cloud Connector adds components to install, monitor and document. If your session hosts can already reach your print servers, through standard routing or a VPN you already have, use the standard print server deployment instead.
Deployment best practices
- Pilot with one site. Connect one remote site, confirm its print servers' printers appear in a test session, and print to each before adding more sites.
- Confirm the network path first. From the actual remote connector server, check that it can reach the internal connector's address and port. Subnet-level rules can block it even when other traffic flows.
- Monitor the connectors. Watch the connection status in the ScrewDrivers Connector application on the internal connector and alert when a remote connector drops.
- Harden the connector servers. Use least-privilege service accounts, keep Windows and ScrewDrivers patched, and limit inbound access on the internal connector to the remote sites that need it.
Technical requirements
- Connector servers: Windows Server 2016 or newer with .NET Framework 4.8, running the ScrewDrivers Cloud Connector service from the ScrewDrivers Enterprise installer.
- Internal connector: reachable from each remote connector on TCP 5551, and on the same network as the session hosts.
- Remote connectors: outbound access to the internal connector, and access to the local print servers.
- Session hosts: the Print Server Session Agent.
- Print servers: the ScrewDrivers Print Server service.
See Ports and Firewall Rules for the full port list and Cloud Connector Setup for installation details.
Comparison with other architectures
Remote printing vs. print server printing: Standard print server printing needs session hosts to reach print servers directly. Remote printing adds the Cloud Connector for when they can't. If they can, use standard print server printing.
Remote printing vs. Direct IP: Direct IP printing needs the session hosts to reach the printers. Remote printing reaches printers through print servers on networks the session hosts can't reach.
Remote printing vs. TCP/IP client: The TCP/IP client solves a missing virtual channel (for example, HTML5 clients). Remote printing solves missing network connectivity between the session hosts and the print servers. You can use both in the same environment.
Related documentation
- Cloud Connector Setup - Installing and configuring the internal and remote connectors
- Ports and Firewall Rules - Cloud Connector ports and traffic direction
- Architecture Overview - Comparison of all ScrewDrivers architectures
- Pro: Print Server Architecture - Print server printing when session hosts can reach print servers
- Enterprise: TCP/IP Client Architecture - Printing without a virtual channel
Summary
The Cloud Connector lets cloud-hosted and centrally hosted session hosts print through print servers on networks they can't reach. Remote connectors at each print server site connect out to an internal connector beside the session hosts, so the sites open nothing inbound and you don't need a VPN or ExpressRoute to print. Everything runs on servers you control, and printing works the way it does in any ScrewDrivers print server deployment, with the manufacturer drivers on the print servers.