I was involved in its onboarding. It was easy. Because we did not plan to migrate anything, in our case, it was easy. We had ten years of data, but when we moved, we decided to not migrate that data because we wanted to start fresh. For us, it was very easy, but I do not know what options people have if they plan to migrate their data.

With nearly 400 virtual machines to migrate, transitioning from on-premises to the cloud wasn't quick, but it proved to be a smooth process.

It was difficult and time-consuming. We have great folks who are working with our value-added reseller and OpenText, but the challenge that we are finding is that we like to be a self-serve shop. They do send us articles about how to do something, which is cool, but they are not technical enough. They are missing details. We understand that their documentation needs to be at that general level for the people who are not so technical, but they need to have a second level that gets down into every port in security concerns. We need much deeper technical documentation available so that we do not have to constantly go back and ask. Overall, it was difficult. It could be worse. I am not unhappy, but there is room for improvement. 

The initial setup was definitely difficult in the earlier version. My team was sometimes not comfortable with the earlier version because there were a lot of issues with regard to the spinning of loads and data. There were limited options in terms of reporting. Also, there were very few graphs where you can monitor online compared to those in the current one. The current version is more mature and better.

Because we don't own anything, we created our account and then got started with the license.

OpenText LoadRunner Cloud’s setup is straightforward. I rate the process a nine out of ten. Although, I rate the process for the on-premises version a seven out of ten as we face challenges there. The on-cloud setup takes four to five hours to complete. It takes longer if there are some additional protocols included.

The initial setup of the cloud version is easy compared to using it on-premises. In the on-premises deployment, you have to set up all of the servers starting with bare metal and it will take no less than three months to deploy. However, with LoadRunner Cloud, all you have to do is buy the resources and execute it from there.

We initially had some problems with the setup as we had an issue while configuring load generators with the tool. In the end, everything went well. We raised it with the Micro Focus team, and they resolved our issue.

I'd rate the initial setup a four out of five in terms of the ease of implementation. 

The only problem with setup is that there might be some problems with the firewalls, configuring SSH and other things. We were initially using OpenText SiteScope but we had some issues getting all the metrics. With New Relic and Dynatrace, we stopped using SiteScope. Other than that, we didn't have any issues. It's pretty straightforward. You install LoadRunner, configure your virtual users, and create the environment.

Our initial deployment of the on-prem solution took a week to get everything done, including setting up the firewall, configuration files, and the protocols. The migration to Loadrunner Cloud is nothing. You can start triggering whatever code you had on-prem in the cloud. There really isn't any migration involved. It's pretty straightforward.

I was involved in the initial setup. It was straightforward and there was a lot of good information available, but I did not need it. I didn't go through any support to set it up. The documentation itself was good.

The installation is not difficult, but it is a pretty lengthy process.

The solution's setup process was easy. Although, we encountered a few issues sometimes.

The initial setup was straightforward, and it took approximately a day.

In terms of integration and configuration of the product in our AWS environment, it is the easiest Micro Focus tool I have ever used.

I wasn't involved in the deployment.

It is simple - just registering with HP SaaS platform called pronq.com.

It was straightforward, we just needed to register on the site. In comparison to other HP products, it was very user-friendly.

It was difficult because the Amazon stuff didn't work. I don't like to use Microsoft stuff. I was forced to put it onto Azure Cloud because that was the one that just worked out of the box. The Amazon launching died somewhere in the process. There was another error there as well.

As StormRunner Load is a web-based application, it's simple setup, just registering users through an HP site.

It's very east to set up. I did it directly myself just once.

Setup was straightforward.

There was no set-up required.

That's where the documentation could be really helpful, apparently I had an older version on my machine, which was creating conflict. If everything had gone as supposed to would have been simple but the documentation could have better and clearer.

It is complex. You need to convince the leadership and the IT security team. You need to solve all these issues. There are a lot of things that you have to go through.

The initial setup is normal and I have not found any complexity with it.

No, it was straightforward. It was very easy to implement and to have a load test.

Initial setup was straightforward…cloud based solution with a simple, flexible UI.

The initial setup is straightforward.

Very intuitive.