Selecting Printing Methods

MyQ X supports multiple methods for submitting print jobs. The right combination depends on your user population, device types, network topology, and security requirements. Select methods during planning – some require infrastructure decisions (Mobile Print Agent placement, queue configuration, certificate trust) that need to be made before rollout.

Printing Methods

About Printing Methods

Server spooling via LPR/IPPS is the standard path for managed Windows and macOS workstations. Jobs are submitted through a print driver pointing at a MyQ queue. IPPS is a strong choice for new deployments because it uses TLS, can support authenticated printing where the client platform supports it, and aligns with the Windows Protected Print mode transition.

Client Spooling keeps job data on the user's workstation and sends only metadata to the server. The job is delivered directly to the device at release. Use this where WAN bandwidth to the Print Server is limited, where print data should stay local, or where a cloud deployment should avoid transferring large print files through a cloud-hosted server. Requires MyQ Desktop Client.

Device Spooling sends jobs directly to the device where they are held for release. The server is not involved in job transfer – only metadata and release signals pass through. Use this at branch offices with limited connectivity, or as a resilience measure combined with Offline Login. Supported on Kyocera and Ricoh embedded terminals only.

IPPS (driverless) allows clients computers to submit jobs to MyQ through an IPP-based queue URL. Depending on the client platform and driver model, this can reduce or remove the need for vendor-specific print drivers. This is the path forward as Microsoft phases out third-party print drivers through Windows Protected Print Mode. IPP/IPPS-based queue access is also relevant for mobile and driverless printing methods such as Mobile Client, AirPrint, and Mopria. Plan certificate trust for IPPS – clients must trust the MyQ server certificate to connect without warnings.

Mobile Client gives iOS and Android users authenticated access to MyQ queues, job management, and QR code terminal login. Where Microsoft sign-in is configured, users can sign in to the Mobile Client with their Microsoft account. If Entra ID MFA is enforced, that MFA step is handled during Microsoft sign-in. Requires an IPPS queue with mobile device access enabled. If remote Mobile Client access is required, verify the supported publishing method, such as Microsoft Entra Application Proxy, and test authentication, certificate trust, and queue access before rollout.

AirPrint and Mopria expose MyQ pull print queues as natively discoverable printers on the local network. Users on iOS, macOS, and Android can print without installing an app or configuring a queue URL. Requires Mobile Print Agent or DNS-SD configuration that allows mobile devices to discover the published MyQ queues on the relevant network. Queues must have mobile device access enabled. Plan Mobile Print Agent placement as part of your network architecture – it needs to be reachable from both the Print Server and the Wi-Fi segment used by mobile devices.

Web Upload is a driverless option for users who can reach the MyQ Web Interface, where Jobs via Web is enabled and the user has rights to the Web queue. Users log in, upload a supported file, and the job is queued for release. It is useful for guests, contractors, and platforms where driver installation is not practical.

Jobs via Email allows users to submit print jobs by sending email attachments to a designated MyQ address. Useful for guests, remote users, and BYOD scenarios where network access to the Print Server is not available. Can also drive automated guest account creation when combined with self-registration. Requires a configured inbound mail connection (POP3, IMAP, Exchange Online, or Gmail).

Microsoft Universal Print bridges MyQ queues to Microsoft's cloud print infrastructure. Users on Entra ID-joined devices can print without a VPN connection to the Print Server. MyQ retrieves jobs from Microsoft Universal Print and processes them through the configured MyQ printing workflow. Relevant primarily for cloud-first and hybrid deployments. Requires an Azure app registration and a Universal Print license.

Chromebook and Chrome Extension printing is supported via IPPS queues. Queues can be distributed to managed Chromebooks through Google Admin Console, or users can install the MyQ X Chromebook Client extension directly. The extension provisions IPPS queues automatically for signed-in users and works for both managed and BYOD Chromebooks.

BYOD and Guest Printing

For users who are not on managed workstations – personal laptops, mobile devices, guests, contractors – plan which methods are appropriate before rollout.

Pull print queues with a single well-known IPPS URL cover most BYOD workstations without requiring driver installation. The Mobile Client covers iOS and Android users who need authenticated access. AirPrint and Mopria cover native mobile printing without an app. Web Upload and Jobs via Email cover users who cannot join the network or install anything.

Platform coverage. Not all methods are available on all platforms, and authentication support varies. Standard IPP printing works on Windows, macOS, iOS, and Android, but authentication is not available on iOS and Android via this path. Mobile IPP (AirPrint/Mopria) adds authenticated access on macOS, iOS, and Android. For iOS and Android users who need authenticated access to MyQ functions, the Mobile Client is usually the clearest option. Validate the exact authentication behavior of IPP, AirPrint, Mopria, and Mobile Client for the platforms in scope before rollout.

Network reach. Several methods – Standard IPP, Mobile IPP, Mobile Client, and Web Upload – require the client device to reach the Print Server on the local network. Jobs via Email does not require the user device to reach the MyQ Print Server directly. Users only need to send email to the configured print mailbox, while the MyQ server must be able to retrieve jobs from that mailbox through the configured mail connection. The Mobile Client additionally supports internet access via Microsoft Entra Application Proxy, which extends authenticated mobile printing beyond the local network without requiring a VPN.

Certificate trust is a common BYOD pain point. If your server uses a certificate from a non-public CA, BYOD devices will receive trust warnings or fail to connect. For environments with significant BYOD usage, consider a publicly trusted certificate for the MyQ server.

Queue design for BYOD. A single pull print queue with a well-known IPPS URL can be enough for many BYOD scenarios. Where different user groups need different release options or restrictions, two or three queues – for example, one for employees and one for guests – provide flexibility without significantly increasing administrative overhead.