Terminal upgrades are expected over the lifetime of a deployment. New MyQ releases can include updated terminal packages, and keeping terminals current can be important for security, compatibility, and access to new features. The recommendations here apply to any terminal upgrade, whether a minor patch or a major version change.
Before You Upgrade
-
Check the release notes
Before doing anything practical, read the release notes for the terminal version you are upgrading to. Release notes specify improvements, behavioral changes, bug fixes, and – critically – known limitations and compatibility restrictions for the new package. Surprises during a terminal upgrade are almost always things that were documented in the release notes. -
Verify TLS compatibility
If the upgrade involves a server-side update as well as a terminal package update, re-confirm that all devices in scope meet the TLS requirements of the new server version. See Preparing Your Device Fleet above. -
Confirm Software Assurance is current
Terminal package updates require valid Software Assurance. Confirm this before scheduling the upgrade window, because an expired entitlement can block or delay terminal activation or updates. -
Test on a limited group first
Before upgrading the full fleet, run the new package on a small, representative group of devices, ideally covering each device model in your fleet. Monitor the MyQ main log for errors and test all configured terminal actions on each device.
During the Upgrade
Start with batches of low-priority, low-traffic devices where possible. After testing the batch and reviewing logs, proceed to the next batch after a batch is confirmed stable. Avoid upgrading the full fleet in a single operation unless the fleet is small and you have a clear recovery or rollback plan.
When upgrading using the Replace option, some device-side configuration may not be retained. Check the upgrade or uninstallation guide for the terminal vendor before proceeding. For example, HP terminals have specific package-replacement limitations documented in HP Update and Uninstallation.
After the Upgrade
-
Check the Main Log
After each batch upgrade, review the MyQ Main Log for errors or warnings related to the upgraded terminals. Address any issues before proceeding to the next batch. -
Test configured functionality
Verify that all terminal actions, authentication methods, and scan destinations are working as expected on upgraded devices. Pay particular attention to any functionality that was flagged as changed or limited in the release notes. -
Monitor user feedback
In the days following a rollout, monitor helpdesk traffic for terminal-related issues. User-reported problems after rollout can reveal device-model, workflow, or usage issues that were not caught during testing.
For terminal package upload, assignment, and upgrade steps, see the MyQ X Server guide and the embedded terminal documentation for your device vendor.