Hi All -
I couldn't find a forum for product suggestions, so I'm putting it here. 
A bit of my vRanger background..been using it since it was called esxRanger. Upgraded from 1.x->2.x->3.x and stayed there for a while due to the magnitude of issues with 4.x. Upgraded to 4.5 in the fall, then recently to 5.0.
I've come up with a list of suggestions for future versions of the product. I'm sure some of these have been mentioned in other threads, but I still felt it was important to list them all here.
In no order of importance...
1. Bring back the 'Only email on error' option for jobs. It's silly that the user needs to set up a rule in Outlook to dump any messages with "0 failed, 0 aborted, 0 canceled" in the subject line into Deleted Items in order to only see jobs that finished with errors. We get enough emails.. please only tell us when something goes wrong!
2. Alert the user when Fiber/iSCSI backup jobs failed and it had to revert to using the LAN. If you're looking at the GUI, there is a graphical display that LAN-free didn't work, but nothing in the status email that arrives. This condition SHOULD be grounds for receiving an email -- even if the job did ultimately complete successfully!
3. Do something about the GUI slugishness. Even on idle dual-quad core machines, the GUI can be painfully slow sometimes.
4. In the GUI, there should be some way to gracefully move VMs in between repositories. For example: We have VMs we have considered 'retired' but may need to be restored or have files extracted from them in the future. It would be great to move it to a repository that had low-cost, bulk storage hanging off it, rather than clog up our high-speed SAS arrays with huge files we may never touch again. I envision right-clicking the VM (under My Repositories), selecting "Change Datastore" and then walk through a few steps to complete the relocation.
5. Jobs work one day, but not the next. We began having this issue with 4.x (this was one of the reasons why we stayed on 3.x for so long) and it appears to mostly have been resolved. For example, in a job that backs up 24 VMs, one day 22 will work successfully, and 2 will fail with what appear to be random errors. The next day, everything works fine -- even though we made no changes. The errors include "Snapshot hardware mismatch" "SqlDateTime Overflow", etc..
That's all I have.. for now
Hope this helps. Please don't hesitate to ask if there are any questions.....
-Craig