So I've been evaluating a demo of TrueImage Enterprise Server 9.1.3633 (3602 before that) and I'm about ready to tear my hair out, which means it's probably time to take a look at a different product suite. Here's a list of problems I've run into that perhaps someone from support can comment on. 1. I have two administrator accounts. Depending on which one I create a scheduled task with, the other one can't start the job. I receive Error 1314: A required privilege is not held by the client. If I delete the task and make a new one, then it works (for that account but then not the other one). Why is the account I create the task with tied to task execution? And how about a more useful error message, LIKE WHICH PRIVILEGE IS BEING REQUESTED. This bug has been around forever, please enhance the error message and/or fix the issue! 2. Sometimes when trying to disconnect within the Management Console, if the connection has already been broken (like a network link down), the client just sits there forever trying to disconnect. There's some kind of network thread issue going on. When the link breaks, the client should realize this and terminate the connection, not sit on the disconnecting screen forever. I should never have to use End Task on the console, but it's often my only recourse. 3. None of the columns when connected to Backup Server are resizeable. Because of this, there is no way to see the full text of the backup location, etc. 4. The archive Description column in Backup Server Manage Archives is always blank and never populated with what I typed into the original backup task. 5. I only seem to be able to backup one target/task per machine to the Backup Server. Trying to backup two partitions as separate tasks results in the agent freezing (stuck at 0%) when it tries to run the second task. It doesn't matter which order I run them in, the first one works, the second one freezes. Is Backup Server only meant to handle one archive per computer? That would seem very odd, but if so, why can I schedule two different tasks on one workstation both pointing to the backup server? Trying to create a second task should fail or at least generate a warning so that I'm aware of the conflict. It should NOT just freeze a backup task with no displayed message. I have to say, if only one task per computer can backup to the Backup Server, that pretty significantly limits its utility. 6. On a computer that has 3 partitions being backed up within a single archive, I am only able to backup to the backup server once. It runs successfully, however, if I click to run the task again it just hangs at 0% and never proceeds. A single partition appears to work fine. 7. Cancelling a task hung at 0% is not possible. I click the button, acknowledge I want to cancel, the button grays out, but it never stops. That should never happen. CANCEL MEANS CANCEL! 8. I have periodically been unable to delete backups stored on the backup server. I go to the Administrator Profiles section, select the computer name, and select Clear. It tells me it's going to delete them. Then I check the location in Manage Backup Archives (and on disk) and they're still there. What gives? CLEAR MEANS CLEAR! 9. I am unable to edit any tasks created which backup to a backup server. When I click edit, I am greeted with the well documented bug here E00640064: Cannot resolve the destination path for the backup archive. The path is unusual, however, as it says: bsp://servername/\backupserver\BackupServer Whose brilliant idea was it to prevent someone from editing the task after an error like that? Strangely enough, the task will execute with this bizarre path and seems to work fine, but I can not edit the task. Every task on every workstation configured to use the backup server has the same issue. 10. Using the console to remotely edit the source folders of a task which backs up files and folders loses the original folder selection every time. You either have to edit the task using the local server client from that machine, or you have to sit there and reselect the original criteria. The management console should NOT lose the selections just because the task is being edited remotely. 11. Backup Server doesn't uninstall cleanly. I put it on a different machine to test if some of these issues were specific to the original server I selected, but all of the same issues were present with the backup server on a different machine. I uninstalled Backup Server, uninstalled Agent, rebooted, and reinstalled Agent but it still shows up in the backup server list from every other client. Why is it in the backup server list if Backup Server is no longer installed on it? UNINSTALL MEANS UNINSTALL! 12. E-mail notification does not send proper carriage returns so the message received is practically illegible. On top of that, the date/time stamp is not included, so the message always comes in with some 1969 year, placing it at the bottom of my inbox where it's unlikely to be noticed. 13. Scheduling time formats are inconsistent. I've noticed some screens use AM/PM, some use 24 hour format. Pick one. 14. VSS and Dynamic Disk support should be enabled in the Workstation Agent too. These are not Windows Server only features and should not be restricted to your Server only product line lest small business and home users feel like they're being taken advantage of. 15. For the backup of sensitive information, I have concerns about the security of the archives. The user names and passwords appear to be stored in various scripts and configuration files using what appear to be reversible symmetric algorithms. Assuming someone gains access to those files, it seems reasonable to assume those ciphers will be decoded and the archive password retrieved. In addition to the archive password, I don't like that my Backup Operator or Administrator accounts are also stored in this format. Asymmetric algorithms such as RSA are infinitely more secure than what appears to be this basic ciphered password approach. 16. Why aren't your release notes for each version made public? It's not a trade or government secret. We need to know what changes and fixes are made between version releases. From searching the forums, it seems like many of these issues have been around for some time, which boggles the mind considering how as a developer myself I know tweaking the resizability of a column, printing more useful error messages, or allowing editing of a task with a bad target path takes only 5 minutes to fix! In the past I've had good experiences with your Home edition, but your Workstation and Server editions have some serious flaws that don't seem to be getting noticed or corrected. I can't count the number of posts here where someone responds to these bug reports, "yes we're looking into that for a future version," and then I check the date and it's from 3 years ago and still hasn't happened. I urge you to devote some additional resources to Quality Assurance and to Development to nail down the growing defect list. As many of the ones I listed above are showstoppers, I can only recommend Acronis for casual home use at this time.