Skip to main content

Cloud Connector Setup

The ScrewDrivers Cloud Connector (also called a proxy) enables Print Server functionality in network architectures where session hosts can't directly initiate connections to print servers. You'll use Cloud Connector primarily in managed service provider (MSP) environments, certain cloud configurations, or any scenario where firewall rules or network segmentation prevent traditional Print Server communication patterns. This reference explains when you need Cloud Connector, how it changes communication flow, and where to install its components.

Overview​

In a typical ScrewDrivers Print Server installation, you install two components: the Print Server Session Agent on your session hosts (terminal servers, VDI machines) and the Print Server service on your print servers. The Session Agent initiates communication with the Print Server when users log in to create their printers. This works fine when session hosts can reach print servers directly across your network.

However, some environments can't support this communication pattern. Cloud-hosted session hosts might not be able to initiate outbound connections to on-premises print servers due to firewall policies. MSP environments might have multiple customer networks that need isolation. Azure Virtual Desktop or other cloud platforms might have network security groups that block the required ports.

Cloud Connector solves this by reversing the direction of initial communication. Instead of session hosts reaching out to print servers, the print servers reach out to a central Cloud Connector service running on your session host infrastructure. The session hosts then communicate with this local connector rather than directly with remote print servers. This reversal means you only need to allow outbound connections from print servers (typically easier to accomplish) rather than inbound connections to print servers from potentially untrusted networks.

Architecture and Components​

Cloud Connector requires installing two additional components beyond the standard Print Server installation. Understanding where each component goes and how they communicate helps you plan firewall rules and network configuration.

Internal Connector Component​

You'll install one Internal Connector component where your end users create printers—typically on or near your session hosts. This might be on your terminal servers themselves, on your VDI infrastructure control plane, or on a dedicated connector server in the same network segment as your session hosts.

During ScrewDrivers Enterprise installation on this location, you'll select the ScrewDrivers Cloud Connector service on the Features to Install page, then choose Internal mode on the Connector Mode page. The Internal connector acts as the central relay point that session hosts communicate with.

Remote Connector Components​

You'll install one Remote Connector component for each remote location hosting Print Servers. If you have print servers in three different customer sites or data centers, you need three Remote Connector installations—one at each site.

During ScrewDrivers Enterprise installation at each print server location, select the ScrewDrivers Cloud Connector service on the Features to Install page, then choose Remote mode on the Connector Mode page. Each Remote connector initiates an outbound connection to your Internal connector, establishing the communication channel that print jobs will traverse.

Communication Flow​

With Cloud Connector configured, communication works like this: When a user logs into a session host, the Print Server Session Agent queries the local Internal connector for available printers. The Internal connector has established connections from all your Remote connectors at print server sites. The query flows through the Internal connector to the appropriate Remote connector, which queries its local print servers and returns the printer list. Print jobs then flow back through this same channel—session host to Internal connector to Remote connector to print server.

This architecture adds a small amount of latency compared to direct Print Server communication, but it's usually negligible (typically under 50ms) and enables scenarios that wouldn't otherwise be possible.

Installation Considerations​

Before installing Cloud Connector components, you'll need to plan several aspects of your deployment to ensure reliable operation.

Network and Firewall Requirements​

The Remote connectors must be able to initiate outbound TCP connections to the Internal connector. You'll need to know the hostname or IP address of your Internal connector before configuring Remote connectors. If you have firewalls between Remote connector locations and your Internal connector, ensure the required ports are open for outbound connections.

The Internal connector doesn't need to initiate connections to Remote connectors—it only needs to accept their incoming connections. This greatly simplifies firewall rules in most scenarios because you're allowing inbound connections only to the Internal connector, not to every print server.

Connector Placement and Sizing​

The Internal connector handles all print server queries and print job traffic for your entire environment, so it needs adequate network bandwidth and server resources. If you're supporting hundreds of concurrent users, consider placing the Internal connector on dedicated hardware rather than sharing resources with session hosts.

Remote connectors handle traffic only for their local print servers, so they're typically less resource-intensive. You can often run a Remote connector on the same server hosting the Print Server service unless you have extremely high print volumes.

High Availability Considerations​

If the Internal connector becomes unavailable, your users can't print to any Print Server printers. For production environments, you'll want to plan for Internal connector redundancy. This might mean clustering the Internal connector service, using Windows failover clustering, or implementing load balancing with multiple Internal connector instances.

Remote connector failures affect only printers at that specific location. If you have redundant print servers at a location (for example, with Print Server failover configured), consider running multiple Remote connectors at that site for redundancy.

Post-Installation Configuration​

After installing both Internal and Remote connector components, you'll use the ScrewDrivers Connector application to configure and maintain proxy settings. This application installs automatically wherever you install a Cloud Connector component.

ScrewDrivers Connector Application​

The ScrewDrivers Connector application provides the management interface for your Cloud Connector deployment. You'll use it to configure connection parameters, monitor connector status, troubleshoot communication issues, and update connector settings after changes to your network infrastructure.

On Internal connectors, you'll configure listening addresses and ports, security settings for incoming Remote connector connections, and monitoring parameters. On Remote connectors, you'll configure the Internal connector address and connection retry behavior.

Verifying Connector Operation​

After configuring your connectors, verify they're communicating correctly before deploying to production. The ScrewDrivers Connector application shows connection status for each Remote connector. You should see all your Remote connectors listed as connected on the Internal connector.

Test print job flow by logging into a session host and verifying that print servers at all remote locations appear correctly in the user's printer list. Submit test print jobs to printers at each location to confirm end-to-end functionality.

When Not to Use Cloud Connector​

Cloud Connector adds architectural complexity and a small amount of latency to your printing infrastructure. Don't deploy it unless your network architecture actually requires it. If your session hosts can reach your print servers directly using standard network routing, stick with the standard two-component Print Server installation.

Common scenarios where Cloud Connector isn't needed include traditional on-premises data centers where everything's on the same corporate network, environments with site-to-site VPNs that allow direct connectivity, and situations where you can configure firewall rules to allow session hosts to reach print servers directly.