I am usually working with VBR from week to week, not VBO. Why does this happen to me? Because VBR is our primary product and VBO a secondary product. I cannot count the number of times I have opened VBO and double-clicked on a job to get a better view of the results, only to have it open the edit workflow. If Veeam wants customers to use as many of Veeam's products as possible, then there needs to be consist UI design principles in place. It's frustrating when an intuitive action produces a non-intuitive result. I understand VBO and VBR are two different products, but the "look and feel" should be consistent. Double-clicking a job should bring up a better view of the run state, whether present or past, of the job. If I want to edit it, I should right-click it and choose Edit or some menu item. Double-clicking a job should NOT edit the job. While I'm venting, let me share another UI issue.
The latter listens to end users complaining about "human-computer interaction" issues, also known as UI issues. To be frank, the very need for this post and having to resemble what amounts to the proverbial "squeaky wheel" is revealing a big difference between the VBO product development team and the VBR production development team. The next time I use the wizard to create logs, the path reverts to the default.
Problem 2: If I change this, it is not persistent. Problem 1: This defaults to an obscure path instead of C:\Temp\Logs like BNR. Yes, most definitely because I am not referring to the source log path but the destination log path! That is, when the wizard is used, one of the steps is to choose a destination log path.
0 kommentar(er)
