Before adding devices to MyQ, complete the preparation steps that affect discovery, activation, and embedded terminal installation. Missing preparation can cause activation failures or unexpected behavior after rollout.
Network Readiness
Devices must be connected to the network and reachable from the MyQ server before discovery or manual addition can proceed. Confirm the following:
-
Devices are online, initialized, and idle – initial device setup must be complete before MyQ can manage them.
-
The MyQ server can reach each device over the network. If the server and devices are on different subnets, confirm that the relevant ports are open between them.
-
If devices use DHCP, use stable DNS names, DHCP reservations, or another stable addressing strategy. Avoid relying on changing IP addresses in configuration profiles.
TLS Compatibility
MyQ X 10.3 uses TLS 1.2 as the default minimum for secure communication. Older devices that support only TLS 1.0 or 1.1 may fail to connect or activate when secure communication requires TLS 1.2. Audit your device fleet for TLS support before starting activation – particularly relevant for older devices that may not have received firmware updates.
If legacy devices cannot be updated to support TLS 1.2, the minimum TLS version can be temporarily lowered via config.ini. This is not a recommended long-term configuration.
Clean Device State
Before installing a MyQ embedded terminal on a device, confirm the following:
-
There is no previous MyQ installation on the device and no leftover MyQ applications.
-
If the device has previously been used with another print management system, strongly consider a factory reset or resetting the web control panel settings to defaults before proceeding. Residual configuration from a previous system is a common source of terminal installation failures.
Licensing
There is no limit to the number of devices you can add to MyQ, but you can only activate as many embedded terminals as your license allows. Devices without an embedded terminal can be added and managed for free.
Terminal package updates, and server and component updates, require valid Software Assurance. If Software Assurance has expired, terminal activation will fail with the message "There is no free terminal license on the server." Confirm your license covers the number of terminals in scope and that Software Assurance is current before beginning activation.
Some functionality is licensed at half an Embedded Terminal license, for example Kyocera Lite Embedded Terminal. If your fleet includes devices using these lighter terminal variants, account for this when calculating the number of licenses required.
Consult your MyQ partner or reseller for licensing details.
Vendor-Specific Preparation
Embedded terminal installation varies by vendor. Some vendors require manual device-side configuration before MyQ can complete the remote installation. Common manual steps include:
-
Configuring authentication settings on the device.
-
Enabling specific functionality of the device's built-in platform.
-
Installing the security certificate, if not done automatically by MyQ or when manual certificate management is selected in MyQ Network settings.
-
Configuring the device to use MyQ as the primary login screen.
-
Configuring settings related to accounting.
Not all steps apply to every vendor – refer to the embedded terminal documentation for your specific device before starting installation.
See also: