MyQ X can be deployed fully or partially in the cloud. This section covers the main cloud deployment models, network and communication requirements, and print delivery considerations specific to cloud environments.
Cloud Deployment Models
Hybrid Cloud – Central: The Central Server runs in a cloud-hosted virtual machine and acts as the central reporting and management point for site servers running in local on-premises networks. No VPN tunnel is required between the Central Server and site servers.
Hybrid Cloud – Combined: The Central Server and selected site servers run in the cloud, while the remaining site servers run on-premises. This model is common in organizations that prefer to keep large sites local while moving smaller or mid-sized sites to the cloud. On-premises site servers require no VPN tunnel to reach the Central Server. Cloud-hosted site servers require a VPN tunnel to communicate with printing devices and end-user devices on local networks.
Full Cloud: All MyQ X servers run in the cloud. VPN tunnels are required between each cloud-hosted site server and the local networks where printing devices and end-user devices are located.
Connection Requirements
A VPN tunnel is not required specifically for Site Server-to-Central Server communication. Since MyQ X 10.1, Site Servers can reach the Central Server through its public interface. Cloud-hosted Site Servers may still require a VPN or equivalent private connectivity to reach printers, end-user devices, and other services on local networks.
When reviewing port requirements, pay attention to embedded terminal vendor-specific ports. Kyocera and Kyocera Lite terminals require additional ports for the built-in PM Server component. On Print Server 10.2 and later, the FTP Server and SMTP Server can be disabled if the deployment does not require those incoming services.
Cloud-Friendly Printing
In cloud deployments, keeping print data local can reduce WAN traffic and avoid sending large print files to and from cloud-hosted servers. MyQ X supports two local spooling approaches:
-
Client Spooling
With the MyQ Desktop Client in Client Spooling mode, only job metadata is sent to the server. Print data stays on the user's workstation and is sent directly to the target device when the job is released. -
Device Spooling
With Device Spooling, jobs are sent directly to supported devices with compatible embedded terminals and can be released after user authentication. Support depends on the device vendor, model, and embedded terminal package – see the embedded terminal documentation or consult your MyQ partner.
Microsoft Universal Print
MyQ X supports Microsoft Universal Print, which can let end users print without a client-side VPN connection by exposing MyQ-connected printers through Microsoft Universal Print. In cloud-hosted MyQ deployments, server-side connectivity between the MyQ server and the local network may still require a VPN or equivalent private connection, depending on where printers and services are located.