Using Multiple Terminal Packages for the Same Vendor

In certain situations, it may be necessary or helpful to utilize multiple terminal packages from the same vendor, for example, when staggering updates to a large fleet, or because certain devices are not compatible with the latest terminal packages.

In order to run multiple terminal packages from the same vendor, one of those terminal packages must normally be a terminal version 10.2 or higher. Certain 10.1 terminal versions also support this feature.

Installation

To install a second package, use the Add option in MyQ > Settings > Printers & Terminals.

Then upload the terminal package and click OK.

Managing Terminal Packages

In MyQ > Settings > Printers & Terminals you can add new terminal packages, or replace or delete the existing ones.

Steps to Change the Package Version

Go to MyQ > Printers and right-click the printer you want to change. Click on Choose terminal version…
Select the desired package version.
Confirm the selection. After confirmation, the installation of the new package will begin automatically.

This option is only available with more than one package installed for the same brand.

Use Cases

In dynamic and complex operational environments, managing embedded terminals effectively requires flexibility and careful planning. Whether it’s minimizing downtime during updates, ensuring compatibility across a diverse fleet, or testing new features safely, running multiple versions of terminal software simultaneously can provide practical solutions to common challenges.

The following use cases illustrate how maintaining multiple software versions can help organizations manage risk, support legacy infrastructure, and optimize their transition to new technologies—all while ensuring uninterrupted operations.

Staggered Updates for Large Terminal Fleets

In large organizations with extensive printer networks, rolling out updates to all devices simultaneously can be risky. Your organization has hundreds of terminals spread across various locations. Deploying updates to all terminals at once risks bringing down the entire system if the new package introduces unexpected issues.

By running multiple versions, you can test the new software on a small scale while keeping the majority of terminals functional. This ensures that if the new version causes issues, the operational impact is limited to the test group.

Instead of updating the entire fleet simultaneously, we recommend you install the updates in a manner similar to this:

A smaller, low-priority group receives the new update first to identify potential issues.
Once the initial group proves stable, the next batch of terminals is updated.
This process is repeated until all terminals are running the new package.

By staggering the updates and maintaining multiple versions during the transition, your organization ensures the majority of terminals remain operational, reducing the risk of widespread service interruptions. This phased approach balances system stability with the need to stay current.

Testing New Versions Safely

When introducing new terminal software, organizations must ensure compatibility and stability in their specific operational environment before full deployment.

MyQ has released a new terminal package with promising features, but it hasn’t been tested in your organization’s environment. A system-wide rollout could disrupt critical operations.

Running multiple package versions enables you to compare the performance of the new software against the current version in a live setting. This side-by-side testing identifies potential issues while minimizing disruption to ongoing operations.

A pilot program can be established:

A select group of terminals is updated with the new package in a controlled environment, such as a corporate office.
A separate group continues using the older version for comparison.
Performance data and user feedback from the test group inform adjustments to configurations before a broader rollout.

This approach allows your organization to identify and resolve issues in a low-risk setting. Running multiple versions ensures that existing operations remain unaffected while validating the new software’s performance. The transition is smooth, and disruptions are minimized.