Identified as a problem in 2010, as expected!
https://www-secure.symantec.com/connect/forums/backup-vm-order
Thread was locked, unresolved.
Are we dealing with a broader resource order issue in the product here? :
https://www-secure.symantec.com/connect/forums/changing-order-selection-list-be2012
Thread was locked, unresolved.
Was identified multiple times in this Backup Exec 2012 product apology/update thread:
https://www-secure.symantec.com/connect/forums/impressions-backupexec-2012
Is anybody else out there rolling their eyes at these thread locks on unresolved cases that identify valid problems with the product? It seems that the result of thread locks is that it just kills open and honest discussions regarding problems that are ongoing in the product; even through multiple versions of the product. Fair enough if the thread is kind of pointless or senseless or correctly marked as resolved, lock it. But if the thread is about a valid issue that is still unresolved, even through multiple versions of the product, they should not be locked.
Keep it Open and honest!