As you know, Batch Versions can have the Print Queue Name overwritten at the Version level. This override is stored in a database BLOB and is not accessible through SQL. On the other hand, there may be many reasons why it needs to be overwritten, as well as why it may need to be changed:
Until now, there was no easy way to bulk-update this setting, because it is hidden deep inside BLOB fields in the Database.
Update Queue Names In Versions changes that. You do not need to know what Versions have the old Queue Name overwritten - it finds them all. The whole process typically takes less than a minute. Here's a screenshot of the tool:

All actions are conveniently reported in PDF format for your reference. The Trial Run facility and the UBE / Version Selection Criteria provide for the ultimate flexibility and safety. A Trial Run with blank selections is a way to document all of your existing Queue assignments - it will produce a PDF file, listing all existing UBE's and VER'sions along with the currently assigned Queue Names. Due to an ERP9 bug, Version Revisions program in ERP9 does not show the Queue Names assigned in Versions, so this tool is the only means to actually find out what queue names are assigned to what versions.
Update Queue Names In Versions also allows to bulk-update the Print Data Selections on the Cover Page flag in the affected Versions, so that every time any such Version is run, it's actual Data Selection Criteria will automatically print on the Cover Page - these DS can be different from the standard DS, if the user made any changes when submitting the job. This is done independently of the Queue Name update, so that either or both can be done in any combination.
Sample PDF's:
Updating all R421* Versions to use QBATCH Queue
Updating all R425* Versions to use QB7333 Queue
Updating all R42* Versions to remove Queue Overrides
A Limited Trial version is available upon request - limited to changing <BLANK> Queue Names to literal "TRIAL" and the other way around, in a small number of standard versions.
There are no hardware dependencies, as all Updates are done through OneWorld/EnterpriseOne® API's (but not by using Check-Out/Modify/Check-In sequence, that's why it's so incredibly fast), ensuring consistent results.
Many reference sites are available worldwide.