This section addresses common questions about MQTT (Message Queuing Telemetry Transport) and its role in Zebra printer management with Workspace ONE UEM, covering how the protocol works, how the broker fits into the architecture, and what you need to know to get started with MQTT-based printer management.
What is MQTT?
MQTT (Message Queuing Telemetry Transport) is a lightweight, open-standard messaging protocol designed for devices that require efficient, low-overhead communication over a network. It is widely used with IoT devices, printers, sensors, and other embedded equipment.
Unlike traditional communication methods, MQTT keeps a persistent, resource-efficient connection between a device and a server, allowing the device to send status updates and receive commands in near real time — without the overhead of repeated connection requests.
What is an MQTT Broker?
An MQTT broker is the central message server in an MQTT system. It sits between devices and applications, receiving messages from connected clients and delivering them to the appropriate subscribers.
In the context of Omnissa UEM, the broker acts as the intermediary between your Zebra printers and Workspace ONE UEM, enabling seamless two-way communication:
Zebra Printer ←→ MQTT Broker ←→ Workspace ONE UEM
The broker handles three core responsibilities:
| Broker Function | Description |
|---|---|
| Accept connections | Devices such as your Zebra printer connect to the broker over the network. |
| Authenticate clients | The broker verifies that the connecting device is authorized, using credentials or certificates. |
| Route messages | The broker delivers messages to the correct MQTT topics, ensuring they reach the right destination. |
Do I need my own MQTT Broker?
No — you have two options:
- Use your existing MQTT broker — if your organization already operates one, it can be configured to work with Workspace ONE UEM. If not, you can deploy a new broker in your environment.
- Use the Omnissa-provided MQTT broker — available at no additional cost, with no infrastructure required on your end.
Why MQTT and not another protocol?
MQTT has become the industry standard for device communication — not just for printers, but also for RFID sleds and a wide range of IoT devices. It offers several advantages in this context:
- No device agent required. Unlike Android device management, MQTT-based printer management does not require an agent installed on the device. The printer simply needs to be configured to connect to the MQTT broker.
- Lightweight and efficient. MQTT is designed for constrained devices and low-bandwidth environments.
- Standards-based. As more OEMs adopt MQTT, it provides a consistent management path across device types.
Once configured, MQTT acts as the communication layer between the printer and Workspace ONE UEM.
Is there a limit to the number of printers that can be managed simultaneously?
No practical limit applies under normal conditions. MQTT is a highly lightweight protocol, and the scalability constraints associated with managing printers through the legacy Zebra Connector do not apply to MQTT-based management.
What printers can be managed with Workspace ONE UEM via MQTT?
Workspace ONE UEM supports management of thermal and thermal transfer printers — both mobile and label printers — from OEMs such as Zebra. These printers must support MQTT and run a compatible firmware version (Link-OS 6.7 or later for Zebra devices).
Contact your printer manufacturer to confirm whether their devices support MQTT-based management.
Was this page helpful?