MyQ supports running multiple terminal packages from the same vendor simultaneously, allowing different devices in the same fleet to run different versions of the terminal software.
Use this capability to roll out terminal updates gradually. Testing a new package on a limited group before broader deployment reduces the risk that compatibility issues or unexpected behavioral changes affect the entire fleet.
Plan a Staged Rollout
Avoid updating a large fleet in a single operation.
Start with a small, representative group of devices. Where possible, include each device model and important workflow used in the production environment. A low-traffic location can be useful for an initial pilot, provided it still represents the devices and workflows you need to validate.
Monitor the pilot for an appropriate period based on print volume and business risk. Once the package is stable, update additional groups in stages until the full fleet is covered.
Running multiple terminal versions during this period lets most devices remain on the known working version while the new package is validated.
Check Package Compatibility
Before starting the update:
-
Review the release notes. Check for improvements, behavioral changes, known limitations, and compatibility requirements for the target terminal package.
-
Confirm device compatibility. Verify that the target terminal package supports the device models in scope.
-
Verify TLS compatibility. If the terminal update accompanies a MyQ server update, confirm that the devices support the TLS requirements of the target server version.
-
Confirm Software Assurance is current. Terminal package updates can require valid Software Assurance. Verify the entitlement before scheduling the update window.
To run multiple terminal packages from the same vendor, at least one package normally needs to be version 10.2 or later. Some 10.1 terminal packages may also support this behavior. Check the Embedded Terminal documentation for the vendor and package versions in scope.
Check Settings Retention
When you update a terminal package using Replace, MyQ uploads and installs the new package and reactivates the affected devices.
Settings stored in the MyQ configuration profile are generally retained, but device-side settings and vendor-specific configuration might not be.
Before replacing a package, check the update and uninstallation documentation for the terminal vendor.
For HP terminals, see HP Update and Uninstallation and HP Package Manager, because package replacement and retained settings can differ from other vendors.
Test the Initial Group
Update a small, representative group first.
After updating the devices, verify:
-
terminal activation and connectivity,
-
configured authentication methods,
-
terminal actions,
-
scan destinations and workflows,
-
any vendor-specific functionality used in your environment,
-
the MyQ Main Log for relevant errors or warnings.
Pay particular attention to functionality identified as changed or limited in the release notes.
Resolve any issues before expanding the rollout.
Roll Out in Stages
After the initial group is confirmed stable, update additional batches.
Where possible, begin with lower-priority or lower-traffic devices. After each batch, review the MyQ Main Log and validate the updated devices before proceeding to the next group.
Avoid updating the entire fleet at once unless the fleet is small and you have an appropriate recovery or rollback plan.
After the Update
After each stage of the rollout:
-
Review the MyQ Main Log. Check for errors or warnings related to the updated terminals and resolve them before continuing.
-
Test configured functionality. Verify authentication methods, terminal actions, scan destinations, and other workflows used on the updated devices.
-
Monitor user feedback. Issues reported after rollout can expose device-model, workflow, or usage combinations that were not covered during testing.
Continue to the next rollout stage only after the current group is operating as expected.
For terminal package upload, assignment, replacement, and update procedures, see the MyQ X Server guide and the Embedded Terminal documentation for your device vendor.