Rights to Run LoadRunner
Submitted by Alexander Podelko on Sun, 02/03/2008 - 21:35.
Mercury LoadRunner | performance testing | performance testing tools
Where the myth that you can use LoadRunner with a regular user came from? I got a client who refused to give me admin rights and I should research this question again. I did it before – but, in my practice, I usually return to the same question after such period of time that the only thing I remember about it is that I researched it before.
Well, it took some time. Doesn't look like the new Mercury knowledgebase is a major search improvement.
Finally I found the knowledgebase entry What user permissions are needed on a machine to install and run LoadRunner, document ID 40664 (I am afraid that you need a valid contract to register). Looks like everything mentioned there should be implemented to use LoadRunner (installed, of course, using local admin rights): power user, full access to the file system, full access to Mercury registry keys, adding "Create global objects" policy.
The Microsoft article "Unable to Connect to Machine" Error Message When You Try to View Remote Counters describes what exactly you should set to monitor remote machines.
By the way, where are the good old days when somebody from Mercury called you the same day you submitted the request? It doesn't look like HP is going to support this harmful practice undermining permanent honing of your research abilities. At least I haven't received any feedback so far for a couple of requests I submitted (except incident number).
Well, it took some time. Doesn't look like the new Mercury knowledgebase is a major search improvement.
Finally I found the knowledgebase entry What user permissions are needed on a machine to install and run LoadRunner, document ID 40664 (I am afraid that you need a valid contract to register). Looks like everything mentioned there should be implemented to use LoadRunner (installed, of course, using local admin rights): power user, full access to the file system, full access to Mercury registry keys, adding "Create global objects" policy.
The Microsoft article "Unable to Connect to Machine" Error Message When You Try to View Remote Counters describes what exactly you should set to monitor remote machines.
By the way, where are the good old days when somebody from Mercury called you the same day you submitted the request? It doesn't look like HP is going to support this harmful practice undermining permanent honing of your research abilities. At least I haven't received any feedback so far for a couple of requests I submitted (except incident number).