I rate the solution's initial setup process as a six. It takes a week to deploy it.

The initial setup was easy. I would rate it nine out of ten.

The solution is easy to deploy and doesn't require much effort. The solution's documentation helped us to do the installation and configuration.

The initial setup is easy. The setup time depends on the scale, but it can be as short as a few hours. Once the valet solution is deployed, you must link it to the infrastructure. This process takes a few hours, as the key must pull data from all the infrastructure components. In most cases, the valet solution will remove the entire infrastructure into CRM within a few hours or less.

I rate the initial setup an eight out of ten. 

The setup for VMware vRealize Operations (vROps) was easy. After getting used to it, setting it up was easy enough. It also became easy to navigate and use. How the solution was set up was that it was connected to the vCenter, then the adapters were set up, then you get the data to synchronize across that, and that's okay.

The complexity of the initial setup depends on the smoothness of the upgrade process. If any issues arise, resolving them may require a significant investment of time—many hours or even days—addressing nuances to establish a good, proper configuration.

The initial setup process is fairly simple, especially if you are only setting up a standalone instance. However, if you are setting up a multi-tenant or multi-cluster environment, the setup process can take longer.

Our clients have hosted it on cloud as well as on-premises. 

The initial setup has gotten a lot better over time. The last one we did, we were able to talk to Google, Azure, and AWS altogether.
Cloud foundation software helped a lot during setup with remediation, prevention, and troubleshooting. It had not always been that way.

The initial setup was straightforward at my previous company. We downloaded the OVF, then implemented the integration with vCenter and other products, such as vRealize Log Insight, and that was really straightforward. 

I personally didn't face any problems. The tricky part is there are two ways of implementing vROps. The first way is using vCenter. There is a part of vCenter where you can specify, "I want to implement this in vROps." If you go that way, it will be a little different than implementing the OVF yourself, then going through the wizard and using the VMware documentation.

Once, when I had a problem with vCenter, I went to vCenter, and I said, "Okay, I want to implement vROps." The problem was that vCenter and vROps were not integrating. The usernames and passwords were not synced, so I couldn't log into vROps. However, that was the only problem. Later on, I switched to implementing the OVF directly. In that way, the problem was solved. Generally, the implementation was straightforward and the VMware documentation, for this part, was good.

It took an hour or two to implement one node and integrate it with vCenter. It was just a simple implementation for vROps without customizations. 

Our implementation strategy: We wanted to test this feature. At first, we wanted to make sure that we needed this product. We then went into a testing and researching phase. We implemented it because we found it really useful. Then, we began customizing it, making sure that the dashboards and everything else worked best for us.

It is not difficult but sometimes requires extensive reading and knowledge to install it. It's not a complex task, but I need to fully comprehend everything in order to install it. Sometimes network-related issues can complicate matters, and having a strong background in network infrastructure, including switches and routing, is crucial for successful execution. If there's a preference, I'd appreciate guidance on which one to install. Also, it would be convenient if I didn't have to create everything from scratch on the switch. Some elements may need to be set up physically, and then I can connect them to two switches for network installation, requiring a three-step installation process. The deployment is scheduled for two months to complete the installation and server replacement. This timeframe should encompass all aspects of the solution.

It's not particularly challenging, but it's important to remain close to the users, ensuring that the data is functioning correctly. We need to verify its operation for a week. Out of ten servers, everything is working fine. Then, I'll proceed to another server, following a similar approach, to ensure it is safely set up. We won't be dealing with desktop servers; it's more about efficient and timely execution.  

I would rate it six out of ten.

The initial setup is very easy because VMware provides 24/7 online support to us. Everything is much easier for us, because of their support.

The deployment took about one to two days. You would need one or two people, such as IT managers, for deployment and maintenance.

The initial setup isn't complex.

I have been using different versions of the tool for a long time. Thus, the initial setup process was relatively easy and error-free. It is deployed both on-premise and on the cloud. It took a couple of hours to configure all the prerequisites.

The initial setup was not that complex. It was easy to set up and integrate.

The initial setup was just a couple of virtual machines, so it was a very basic installation. It was very fast. However, the implementation of the infrastructure takes months because we need to see how the system works, then decide what to monitor and report. This takes at least a couple of months.

The initial setup was a complex process, and it is still a complex process. There are too many products: the UI, database, and you have to properly size it according to your requirements, otherwise it does not work well.

Our deployment was a one-year project.

We took a full suite of licenses for all the VMs which we had. And that time we had some 600 VMs. We took two types of licensing, advanced and enterprise, where we were trying to achieve our application monitoring in the enterprise licensing. The advanced was used to create dashboards and other kinds of reporting.

Besides this, we used one more product, VMware Compliance Manager, which they have now stopped. That is one area which they have now integrated into vROps, but we have not tried it so far.

The initial setup is straightforward, not complex.

Initially, because we were not familiar with vRealize Operations, it took us a while to get it set up. Our infrastructure is dependent on multiple volumes, ESX clusters and the storage. It took us seven to 10 days to have a fully functional deployment of the solution. The initial setup took us less time, but setting out and defining the policies, the baseline and advanced policies, happened within 15 days of the deployment.

The initial setup was very straightforward. To pull in an OVA, it was very easy to consume it. It was very easy to scale. There wasn't really much trickiness to setting it up. Do your homework, read through documentation, understand how the product is used with the different types of nodes and how they work. But it was very straightforward.

If you study the guidelines, the setup process is very clear. We didn't have any specific problem installing and implementing vROps in our projects. If you have experience in the installation of vROps, there are no problems.

The deployment took about one month. We studied and reviewed the features and implemented a pilot environment in our company. In terms of the specific plan that we provide to customers, we implement vROps and start a one-month period where it is in a test environment. The day after that we move vROps into the production environment.

While the initial setup was somewhat straightforward, there is some complexity. Going forward, I would like there to be more clarity in the process. Because to complete the setup process, our team had to open up a case with the technical support, and they had to guide us through the process.

Initial setup is pretty easy.

The solution is easy to deploy. We have a lot of configuration, so it takes a lot longer. However, the basic installation takes 20 to 30 minutes. One engineer is more than enough to deploy the tool. It is reasonably easy to maintain the product.

The initial setup is quite easy and straightforward.  The majority of the time, implementing vROps is not time-consuming. 

However, if you are migrating from one vROps version to another, you may need to take care of a few things, such as downloading the new configuration and other necessary changes. But overall,  vROps implementation is pretty simple.

The initial setup is straightforward.

VMware has introduced the Server Appliance, which allows you to deploy very quickly. We just need to import the appliance VM and deploy it. Traditionally, we had to create a Windows machine, and there were several things to configure, but they now have their own operating system called Photon OS. It shortens the length of time required for deployment.

The initial setup of vCloud Director is a bit complex. Sometimes when we have a problem with it, we can't fix it. VMware themselves suggest raising a ticket when an issue arises, and they will come in to fix it.

When we first implemented this product, we came up with a plan and submitted it to VMware. The VMware team reviewed it and advised us of the best practices. We developed a set of instructions that includes deployment and updating the solution and re-submitted it to them for review. It was finalized and we follow this plan whenever we deploy it. Whenever we encounter problems, we raise a priority one ticket and they come to help us with the problem.

One of the issues that we've had in between the versions is that the set up for it has gotten a little bit more difficult. It doesn't always tell you right away that you'll need to do something different with this version versus a past version which has become an issue. It's now something that we're aware of. From what I've been hearing today, the new setup should be relatively simple in comparison.

The initial setup was fairly straightforward. There were instructions for it that were easy to follow. There's video tutorials and things like that online, so it was fairly easy to set up. We didn't need any support to get it installed.

The initial setup was extremely straightforward; download the product, install the product, put a key on it, add the host to it. Absolutely very straightforward.

The setup is pretty straightforward now. It used to be much more involved and a not very intuitive deployment at all, but now it's really nice.

The initial setup was straightforward.

With newer versions of vROps, VMware has improved the setup experience drastically. The new versions of the product install very quickly, very cleanly. Adding additional nodes to the environment is very fast, very easy to do.

I was involved in the initial setup a long time ago. 

Now, the lifecycle product has provided some things which are very easy to roll out within the vRealize suite. It is just check things out and roll it out, then it sort of monitors the application. This has greatly enhanced our ability to roll out vCOPS quickly and augment it too.

I’m involved mostly with the engineering of how we're going to use it. Most of their products are really easy to install.

The initial setup was fast. I downloaded the standard version from a virtual environment. I had a workstation on my laptop and that was where I tried it out. Ease of setup is awesome. In the production environment, as long as you adhere to the minimum hardware requirement, you won't have an issue.

The initial setup is easy, and it can be deployed by a single person. It's not a very difficult tool. It's a pre-configured appliance provided by VMware, and you just deploy it in your existing VMware cluster and assign the license. You can have it deployed in your environment in two to three hours or four hours at the most.

To maintain the solution, you will need two people at most.

The initial setup of vROps was pretty straightforward, but I have been working on VMware stuff for the last six or seven years. Deployment takes about 30 minutes.

In our data center, we have a NOC monitoring team and we have a system team. Those are the two departments that are using the solution. And it doesn't require much staff for deployment and maintenance.

This solution is very easy to deploy.

It is deployed on-premises but with the latest version, they introduced vROps on the cloud as well. This means that they now have a SaaS offering in addition to the on-premises solution.

When deploying in a production environment, it will take between one and two hours to complete. The implementation plan depends on the SMEs that are working on the project and how stable your insight is. The timeline is very personal and it can really vary.

When we talk about deployment, there is no fixed plan when we talk about vROps. The reason is that it's a very customizable tool and the entire sizing depends upon the sizing chart that is provided by VMware. Essentially, whatever the requirements of customers are, we plan according to that, and then we follow the deployment rules or the deployment process that is given by VMware to deploy the tool.

The initial setup was pretty straightforward.

The initial setup and configuration take a little work but once it is set up properly it is very intuitive.

Overall, the setup is pretty straightforward. We have been using vRealize Operations for quite some time and, with every iteration of it, when the vRealize product line rolled out, it became easier, took the complexity out of initial setup and configuration. We're very happy with the way it's working right now.

Every time a new version comes out we're upgrading. The process is very easy. It's painless. When an upgrade comes out it's just one of those things that you put on the calendar and do. It's not anything that we need long, drawn-out planning for. We're confident that when there is an update we won't have any problems getting that update done.

Initial setup was complex. We have a very old environment, so there were a lot of issues – mainly our issues, not the tool itself – getting access to service accounts, the infrastructure stood up, and all of that. We needed a project manager from VMware and a project manager from our company to basically work together and it still took a long damn time; a month.

vROps is very, very straightforward to stand up. I would say, much more straightforward than some of the previous iterations. That's one of the other things I appreciate about the products VMware is bringing to market. They're making their products easier to deploy.

I have previously worked with VMware, the installation was not difficult, I did not have any problems.

We have our partial script to repair and deploy the solution in the environments quickly.

The initial setup was not complex but a little hard.

The initial setup of this solution is complex and takes a couple of weeks to deploy in our environment. We require six administrators for the deployment and maintenance.

We have it deployed on-premises but I have also deployed it in a hybrid cloud environment. I was not personally involved in the initial setup.

The solution is very user friendly. In one step it is ready to deploy. We don't need to configure anything on the OS level. You just deploy it and power-on. We only need to configure in, vCenter, which infra we are monitoring. When we start to onboard, it's very simple to manage. Anybody can deploy and configure it. It is easy to deploy. There are a lot of publicly available articles that we can refer to. There was a great article on end-to-end setup.

Based on the virtual infrastructure size, we decide which appliance size is needed. Do we need to go for tiny, medium, large, or extra-large. The decision is based on our environment's capacity, how many objects we have within the virtual infra. We first deploy the master, then the master replica, and then the data nodes. We can run with one master node, but if we deploy master and replica and data nodes, it gives us more resilience. So even if we have a failure on the master, the master replica makes it a high-availability solution.

Deployment takes just 15 minutes, and we can have vROps up and running in 30 minutes.

There are five members on our team and everyone has knowledge of vROps. Everyone is certified. There is no segregation of roles. Everyone takes care of the entire product life cycle, whether it's upgrading, troubleshooting, or streamlining. We use it day in and day out. Our key job is tracking of vROps' health and alerts-monitoring, to make sure it's running fine. It's part of our daily work.

Yes, Engineered by Blue Medora and validated by VMware, the True Visibility Suite included an extensive knowledge portal and includes 24/7/365 individualized technical support

The setup of vROps and Log Insight is very easy. It's not intensive or very complex. I did it about four years back when we deployed it in my previous organization and it was very easy for a standard VMware environment.

The amount of time it takes depends on how big your VMware environment is. There's no benchmark value. If you have a small environment it shouldn't take more than one or two days. But in a bigger environment, the scanning of data takes time because it has to talk to vCenter, pull all the data, wait for all the data to come in, and see if there are any recommendations. But that should not take more than a week and you should be able to see everything, even in a much bigger environment.

To deploy, you need to have a VMware guy and it depends on where the data is being integrated to. If it's only a VMware environment, you need only one or two people, max.

The initial setup was very straightforward. We spent a few days setting it up, then it was up and running. We haven't done many changes since then.

The initial setup was out-of-the-box.

It comes up petty clean, but the layers of complexity that we introduced into the environment obviously changed some of those parameters. It's a learning experience, as with any other VM port tool.

I was somewhat involved in the initial setup. I have a main guy that does it. I was overseeing the project. I know that initial setup was fairly complex, but I don't think that it was ridiculous.

The initial setup was very easy. 

It was pretty straightforward. Obviously, we had VMware help us through it, but most of it was pretty straightforward.

I would advise to make a design before starting actual setup.
A few examples of design considerations:

• More than one vCenter to monitor.
• Need for high availability.
• Need to migrate historical data from previous version.

The initial setup is very straightforward and relatively easy. Depending on design you can have certain choices during installation to fit your needs.

The initial setup of VMware vRealize Operations (vROps) was very minimal.

The initial setup was straightforward.

I was involved in the initial setup of vROps. It was pretty straightforward. Most of the VMware products are pretty straightforward to install.

In terms of the implementation strategy, we have always followed the documentation provided by VMware.

The initial setup was very easy. We do not have a huge environment, we have eight ESX hosts, so it was pretty straightforward. It was easy to do.

The initial installation was very easy, straightforward. Getting it to do the three things that I wanted it to do, in terms of emailing for those specific metrics, that was very easy to do. Beyond that, when I started looking at some other things it can do, it gets very complex very fast. There is a lot more to it.

I initially deployed the solution for our company. It's relatively straightforward. There's a lot of good online documentation and there's YouTube.

It seemed fairly straightforward, but I have very complex engineers.

We use professional services to do the setup; that definitely helped us there. We did have configuration issues. There were some things that maybe weren't apparent at the time we went through the install. Over time, support realized there were some issues and made some different recommendations. I'll say using professional services definitely gave us a good foundation that we at least were doing things according to best practice at that time.

Initial setup was pretty straightforward, although you have to think about the overall size of your environment and do a little planning. It requires a little bit of thought.

It was a pretty simple setup. It just takes a while to gather useful information out of it. They even say it's about 30 days before you can actually really do anything with the information coming out of it.

It’s very straightforward as the installation is done via OFV provided by VMware or easily available for download from VMware site.

The initial setup is straightforward. It took about two weeks to deploy it.

We had a team of one or two engineers for the implementation process.

We've done the setup a number of times, so from our standpoint, it was pretty straightforward. But for someone just starting out, you really have to spend a lot of time with the documentation and understand the various configuration parameters and how they affect the operation of it. The setup is reasonably complex for a client.

Overall, the quality of VMware's documentation tends to be fairly dreadful. And so, you do a lot of searching around and bouncing back and forth. One of the biggest improvements they could make would be to actually use illustrations in the document so that there is a straightforward way to understand what the documentation is trying to tell you. It's very verbose. Trying to relate what's in the documentation to what's in front of you doesn't always go well. Documentation doesn't seem to move as quickly as the interfaces.

We're certainly not a large data center by any sense of the word. We have about 20 hosts. If we were to do it starting from scratch and moving up, the setup would take about two weeks.

It takes two to three hours per host but there's a lot of carry-on between the time you spend working on the hosts. There's preparation and various other things. Overall, it takes around one to two hours per host.

When we started, we installed vROps, linked it to vCenter, picked a group of hosts, and set up monitoring on that group of hosts and on the VMs in that group of hosts. We worked out all of the kinks from the configuration and setup. Then from there, we just rolled it out to the rest of the hosts and set it up so that at the beginning of a test, we can deploy what we need for a given host. It's not just vROps, but it's also the support things that need to be in place for us to quickly turn around a testing environment.

The initial setup was straightforward, very easy.

Initial setup is straightforward. We set it up in-house.

It's straightforward and I find easy to use it.

The initial setup of this solution was easy.

The initial setup is quite complex although it's becoming easier with each new version. 

The setup is a simple process. In our company we have a system, BMC, which makes it possible to deliver information and to integrate BMC and vROps, using the SDT and VMware. This process, the integration between BMC and VMware took two years. 

The initial setup was straightforward. The documentation is online, so I was able to deploy it before the training. The deployment took me three weeks. 

We don't have a test environment, so everything that I deploy has to go straight to production. However, when deploying vROps, I knew that it would not break service nor cost me downtime, so I decided to give it a shot.

The initial setup was straightforward. We used an integrator and they did everything for us,  there were no issues. It was just a case of going in, looking around, learning it, and just getting a little bit of initial help for a few days. It's been fine since.

The initial setup was straightforward.

The initial setup can be complex, but it is not too complex for me. I consider it straightforward.

The initial setup is straightforward. It is an OVA deployment, connect to the virtual center, and add some plugins. Then, you're done.

I was in the room for the initial setup but was only slightly invovled. Some others guys were there doing it. But it wasn't that bad, probably took us about four hours to get it up and going.

The initial setup was pretty easy. It's an appliance so the deployment is quite easy. The documentation is excellent.

I was not involved in the initial setup.

It is a simple appliance deployment and a simple one-off configuration for a standalone setup. It takes slightly more effort to scale out deployment configurations.

Initial setup was straightforward, and I found that the upgrades were quite simple. They took a couple of days, maybe three days.

I am the one that set it up. I followed the documentation that came with it and it was straightforward.

Very straightforward even in a multi-networked environment which is what you tend to find from service providers. The install itself is wizard driven and asks you for the information needed to configure the software step by step.

The initial setup for the demo is very easy. You have 60 days to use the trial version and see what the tool has to offer to you. You only download the URL, then configure some parameters, IP, and sizing. Also, in the wizard, you have an option where you can see VMs with more CPU, memory, and disk. 

The deployment was first a demo version, which was standalone with one VM. Then, we needed to add more vCenters to vROps, so we needed to add more VMs. Finally, we had three VMs to maintain the database of vROps.

We started with a demo version to see what the tool has to offer our organization in regards to the VM's efficiency and health. This is very common for our company. They ask you, "What if you put more workload in our infrastructure? How will this impact a new workload in our environment?"

You have two options to deploy VMs. 

1. You have thin space. If you use VMs, then there is space to increase. However, if you decide to choose VMs with thin space, probably for an SQL database, there is no other good option from a performance perspective.
2. You have thick space. For example, you have a disk of 100 GB, and you say, "All" in the first deployment.

The initial setup is straightforward. It is just a matter of installing the appliance, setting the IPs, etc, and then performing the integrations between other VMware components. The configuration took approximately two hours.

The initial setup was pretty easy. It's like setting up any other VM. It's a few clicks and you're ready to go. 

We use a large installation of this solution with multiple nodes and so the setup was pretty complex. 

We mostly use this solution for troubleshooting because just getting information from vCenter is not enough. In vCenter you have information about the current state so a lot of the metrics are not collected but if you need to collect more metrics, you have to expand the level of collection. We would like to get a separate solution.

It is very easy to set up.

The initial setup is fairly straightforward. I had a few questions for support, but it was relatively easy.

I've done the initial setup a few times at other companies, so it wasn't too bad. It does have a learning curve to some of the more advanced features.

It's a straightforward install. Getting all of the collections and making sure your data is coming in is a little time consuming, but the install itself, getting it up and running, is pretty simple. 

It's fairly straightforward. There was initially, when I set it up, a version 5, and it had a little bit of different components that you had to configure and put together. I believe it's a little easier these days.

It's pretty straightforward. We didn't have any trouble setting it up.

I did the deployment at my site. It's very straightforward. It's deploying an appliance and just connecting it to your vSphere environment. You need to let it sit for a bit, to make sure it gets baselines for everything, but it was really easy. Took me more than about a day or two to get it fully running and to get everything connected that I wanted to get connected.

It is a straightforward architecture, but you can make it complex based upon your architecture. Based upon where and how you want to deploy.

All the architecture is based upon your datacenter layout. It's a pretty straightforward process but you have to consider your layout.

I was not involved in the initial setup. I heard it was straightforward for us.

The initial setup is actually quite easy because you just go through the wizard and you deploy your different nodes: your master and your slave secondary, and then your data nodes. It's pretty easy to deploy these days, and then they've got different versions. They've got a version that will run on Red Hat; I've got one customer that uses that. I've got most of my customers using the Windows version.

I'm usually involved in all the initial setups that we do for customers; just not the tool itself. I set the tool up for customers. It's not complex to deploy. Complexity comes with the fine tuning of the policies and what you want to monitor, so you see what you need to see and not a plethora of information that you don't need to know. Setup is easy.

At my previous job, I started to set up vROps, but then I left. When I arrived at my current job, it was already configured and everything.

There is a little bit of complexity initially to set the right metrics and put in certain alerts and tweaks.

The initial setup of the solution is easy. 

The deployment takes less than 20 minutes.

The initial deployment of vROps was straightforward. We deployed ESXi, vCenter, and then vSAN. After that, we deployed vROps on-premises to monitor our VMware vSAN cluster. There was nothing special or complex about it.

It took four to five days to deploy vROps.

We have three people who are using and managing vROps and we are monitoring about 500 virtual machines with the solution.

The initial setup is easy.

It's pretty straightforward. In the latest versions, after 6.4, the deployment has improved. It has simplified a lot. It gives me a programmable interface to automate my entire deployment. I can simply run a job and deploy the entire vRealize Operations solution quickly.

We learned that we had the licensing for it, I downloaded the file, and just ran with it. It was very straightforward, just downloaded the file from the internet, uploaded into vCenter, ran it, IP address, log on to the web console and go.

I was involved in the initial vROps setup. It is very straightforward virtual appliance deployment, configure it with the IP, and point it to your various ESXi hosts. It can get a bit complex when getting into the endpoint monitoring, but it is still not overly complex where it makes it difficult to deploy.

The initial setup is complex. There's a lot of planning that goes into it. You could go through the wizard really fast and install it, but to really get a validated and resilient design, it takes a lot of practice in going through and making sure everything is hooked in right.

It's fairly straightforward.

The vRealize Operations setup, installation, and configurations are pretty straightforward. We, as a customer, actually did two of our environments ourselves. We used an implementation service for the first. Then, we used that as a blueprint and a pattern to deploy our other two environments.

The initial setup is straightforward.

Just follow the documentation.

I was not really hands on in the setup but I was there. I think it was pretty straightforward. Although, my guys are really smart, so what they make look easy may not be as easy as I would think.

VMware did come out for us, they did help us. We have a pretty good relationship with them. But I thought it was pretty straightforward.

Straightforward. I did it myself.

It was very complex. That were a lot of the calls to tech support. A lot of the documentation wasn't accurate or it was outdated. And a lot of dead-ends, so we ended up calling support to get the installation complete.

I wasn't involved in this.

I have set it up in another site, initially, starting it off with Horizon View.

It was real straightforward. There are lots of guides out there. VMware helps you with it, guides you on how to set everything up. All you're doing is installing a management pack file for the vCenter. Then, to connect to your vCenter you have to have a username, password, and the fully qualified domain name name, and that's it.

I was not involved.

The setup was very straightforward. The wizard-based install is self-explanatory. It's probably one of the best examples of VMware product installations.

Upgrading it from vCOPS to version 5 was pretty straightforward. It was pretty easy.

I was not involved in the initial set up, but I have been involved since then. The solution was already stood up by another team member of ours. He's no longer there, so I inherited the solution, but I have expanded the cluster and I've incorporated additional BUs that we have all over the U.S. and they're reporting into vROps now.

Initial setup was straightforward. It was very simple; right out of the box, it worked. We've been using vROps since they first came out with 5.0 and 5.5. It's come along way with 6.0.

I don’t have any issues with configurations. Once you understand how the templates and the reporting stuff works – once you understand how that comes together – then it's pretty simple to do the reports.

Initial setup was straightforward. It wasn't that complex.

Initial setup is super easy. All of the OVA appliances - as far as what I've used - from VMware are easy. What's even easier is - I don't remember which release it was - but it's now a single appliance. Whereas before, there were multiple appliances. It could get somewhat convoluted because you had to get multiple IPs, but they've really streamlined the deployment model with one appliance, one VM to run it.

The initial setup is easy. It can be deployed in any environment. It's a very dynamic product.

We were already customers for vROps, but at first we were not using a lot. Then we needed to do an upgrade and it was not an easy path to follow. But in terms of the setup and configuration, it was straightforward and much better than the old versions. The last version I used was v4 and, compared to that, it was completely easy.

The deployment, even though I was doing other stuff, took one or two days.

The initial setup was moderately complex.

After a few earlier iterations, I think the latest version was very easy to deploy. I didn't have to problems with the setup at all, it was very easy. 

I now find it to be user-friendly but initially it wasn't. It was just an entirely different look and feel, so we had to break our habits from previous environments. A lot of the monitoring that we've done was with SolarWinds, which is entirely different. But even inside of VMware, with the C# Client and things like that, as we moved into using VRealize with 6.0, it was how the badges worked, how the color stratifications worked and the like. It took a long time to get comfortable glancing at it, and then educating management on their dashboards.

Setup's a little complex at first. But once you actually know what you're doing, and when you're setting up some of the other nodes - besides the primary one - the collectors and everything, it tends to go a little bit better.

I was involved in the setup. It was straightforward.

It was just that the dashboard is a little hard to understand at the beginning, but after you get used to it, you're fine.

It was straightforward.

Then the deployment of it is not as simple as it should be sometimes. To do it correctly, it's very complex. When you do it right, it becomes a very useful tool but if you don't do it right, it just becomes another nagging monitoring tool. One of the hardest parts is rightsizing it. There are tools out there to do that. Each environment is unique and it's not as simple as some of the competitive products out there. If you don't tune it, you're going to see a ton of red.

We've seen some customers deploy things for remote offices and they know that they're going to have some kind of slowness in the product. Instead of fixing itself, the baseline's there and it's not as intelligent as it should be.

The initial setup was very straightforward. Basically, unpack it, turn it on, and tell it where to start looking. The follow on and ongoing setup is still a bit complex; as I’ve mentioned, it's a very deep product. The more you figure out what you're doing with it, the more you discover what you can do with it; it's an ongoing cycle. It could very easily be a dedicated job for one or two people.

I was the one to set it up. The new setup environment's pretty straightforward. Setting up the alerts, definitions and actions were kind of tricky because there's a lot of false positives. A lot of things it alerts you on are not really problems, so you have to go in and tweak the policies around to see the actual real issues. Sometimes the notifications can be too aggressive, where it notifies you of almost every little thing that can possibly be wrong but in reality, it's not an issue. That tweaking does take a while to get figured out. It's an ongoing process. I'm still doing it to this day. It takes a while.

The initial setup was easy, but what came after that was complex, due to the fact that we needed to have multiple modules.

There are some choices with initial setup. The most difficult thing was to figure out how to go back and change those initial choices that you made because they might have not been great. When you're looking at it and going through that initial setup, there are a couple of questions – whether you're allowing memory over-allocation and CPU over-allocation. If you picked a choice and it's not giving you the results you want, you then have to figure out how to go back and adjust it.

Initial set up was straightforward. We follow the PDFs that you get from VMware; pretty straightforward.

We had some initial setup issues; I think there was some kind of a shim driver we had to install, if I'm remembering correctly. We had some issues with that shim driver initially. He did it remotely; he called in and we got over it quickly, the initial problems.
The full install was a few hours.

The initial setup is straightforward and intuitive. If you have all the data, networks, IPs, etc., then everything is easy.

The customer also has a chance to migrate some of their physical infrastructure onto the virtual environment.

The setup is pretty easy. It takes 20 minutes and it's up and running. It's pretty straightforward.

The latest version of it has been a much easier installation. The previous version I had installed needed a lot of resources, a lot of time to sit and mold it. The new one, not so much. It's been a much easier installation.

We didn't work with VMware to install it. That's how intuitive it is now. You simply download it and install it. There is obviously some molding that needs to happen with it, but the installation on this current version is much more intuitive and much easier than the previous ones. They've definitely made some improvements. It's pretty straightforward.

It was deployed when I got there, back in the vCOPS days, and I basically abandoned that installation and did a fresh vROps deployment because we were so far behind it was easier than trying to do the stepped upgrade.

Some of the earlier releases were a bit more complex to get deployed. Newer versions have been really easy. I think I did one other complete redeployment again because we left to get out of scope, and I had a lot fewer questions and a lot fewer issues the second time.

Overall, vROps is a very mature product. It is stable. It's got a lot of features in it and sometimes that's the downside. There is so much power to it it's hard to know how to use it completely.

If you are going to deploy vROps, make sure that you've got time to dedicate to learning it. The deployment is relatively easy. The learning how to leverage all the features of it afterwards can take some time. Leverage educational resources, whether it be through VMware or leveraging a partner if you need to. It is a really good product, it can just be a little overwhelming when you first get a hold of it.

I was not involved, a partner of mine did it. But for him it was really easy, he didn't have any trouble, did it all by himself.

I thought the setup was straightforward. However, someone else was trying to do it before me, and they thought it was complex.

We did not receive any in-house support.

The setup was straightforward. There were certain bits which were complex partly due to the way we do things. But again, with VMware's support and guidance, I think our roll out was pretty smooth and we hit all the targets in terms of our project turning; so, it was green all the way through.

I installed it. It was fairly easy. We just upgraded and the user interface is much better.

Initial setup very straightforward: install the virtual application, and let it start monitoring. Getting the web interface and all that set up wasn't that difficult. There's plenty of documentation out there on it. It took a couple of days, on and off. While I was working on it, I would get pulled off on something else, so it took a couple of days.

Actually, both five and six were pretty easy to setup initially.

The initial setup itself is not complex. It's not something that I would consider complex. However, the time it takes until it is useful is very long and it's something that I've seen people take issue with. They want their information, they want to use their new toy, and they want to do it now, and they don't really care about the other stuff. They don't care that you need more data, that you can't just make predictions off of a day's worth of data, because that has no idea what you're actually doing.

Initial setup was straightforward; you just import the OVF file. Give it a name, IP, and so on; connect it to vCenter and you're all set.

The installation was straightforward. It followed VMware principles that result from working with vCenter and VMs. It's easy to implement.

At a maximum, it takes 20 to 30 minutes to set up, but the configuration can take one or two hours. Building deep reports can take even longer.

The tool is user-friendly, but you need to study to learn about the many features that the tool offers. It is not a tool that you can just start to work with when it comes to capacity planning. You need to study the documentation. But for monitoring, you can start using it right after installation because the data is easy to understand.

The initial setup was complex. There's no wizard to install it. We have to read a lot of documents then there's a whole other guideline to install the next part. There are a lot of steps. The documentation was great but there's a lot of pages, around three to four hundred pages of documentation. 

The initial setup was very complex. We've been using it for a while now and realized that it's pretty logical. Upgrades are pretty straightforward. We had a lot of problems originally deploying it, between some certificate issues, but we had an engagement with VMware so they were able to help us get a poof of concept environment set up as well which was helpful.

The initial setup is straightforward. The installation process takes you through in a simple, easy to deploy manner. We were had everything up and running within the space of a day. Then, we have just evoled the product ever since.

The initial setup was complex. 

The initial setup is straightforward.

When we first started the process of learning about VMware and the virtual infrastructure, there was definitely a learning curve associated with it. The documentation that was available online presented challenges in terms of confusing of terminology. So ESXi: is it vSphere, is it vCenter? There's a lot of technical jargon that's used to refer to specific components of the architecture. The more we work with it, and the more we're using it, the more we are able to connect the dots.

Very straightforward.

While I was not involved in the initial setup, upgrades have been pretty straightforward.

Absolutely straightforward. As I said, we have a full SolarWinds environment and we're trying to move away from it. And then we finally realized we have licensing for the login site and vROps. So I went ahead and installed and configured it and got it running and rolling. Because of it being straightforward, plus the setup, we're probably going to get rid of most of our investment in SolarWinds products, which is a big bonus for our company.

It was straightforward.

I wasn't involved in this, the systems guy was.

I know our predecessors went through a whole rip and repair, new hardware as well as software, and they eliminated a lot of servers they didn't need. It's a big project. You have to go through and see what you have in the company and probably eliminate a lot.

Was not involved.

I wasn't involved in the setup.

I was not involved.

My team did everything from ground up. Initial setup had medium complexity. It's not intuitive initially, so you have to go through a level of training to be able to get where you want to go.

There's some complexity to the initial setup, to do it right. We did have an engagement with VMware, for them to actually install it, because we knew there was some complexity to it.

I set it up, and it was pretty straightforward. It took about a week, off and on. It wasn't too difficult.

Initial setup was straightforward; very easy to set up. We did some PoCs or optimization assessments. Customer liked the way it sets up. Simply, setup is real good.

Initial setup was really straightforward because we just use the virtual appliance deployment.

Initial setup was pretty easy. I just ran into a problem involving a previous version or two versions behind, called support and it was solved.

I was the one that set it up. With any new technology, there's always complexity that you have to account for. Before I deployed the technology, I went to training and I got myself training about the technology. It was easy for me to set up because I already knew it.

Initial setup was pretty straightforward. We followed the best practice guides and everything else that were already published out there. It was pretty good. The wizard was pretty helpful and everything, so we just followed the wizard. It was really what the best practice guide said to do. It was really well done.

I manage the group that set it up. The grouping by application was pretty complex, but as far as bringing it in and getting the foundation set up, it was fairly simple.

The initial setup was quite straightforward. It was quite simple. To get benefits you have to dig deeper. 

The initial setup was straightforward.

I was involved in the initial setup. It was straightforward.

Initial setup is quite straightforward, but you do have to find out some things. There is the step-by-step process, but it’s not just clicking Next and OK. You have to set-up some things. If you’re using virtual appliances, you have to know what to do in those appliances.

Setting up the infrastructure behind it was a little bit challenging, trying to figure out what we needed for horsepower. It wasn't overly complex to set up. Again, we had a TAM at the time, and he was great. He just worked with us through the whole thing. The implementation of it went really well.

The setup was straightforward and easy.

The initial setup was straightforward. It was a simple deployment. 

We didn't do the first setup. Everything was integrated for us, and we just use it.

It was straightforward; next, next, and we were finished.

The initial setup was straightforward.

The setup was pretty easy. It was an appliance, you just follow the bouncing ball, get it installed.

The initial setup was really straightforward. One of the biggest things that our TAM did was make it a simple process. 

I was involved in the initial setup. It was very easy. I had assistance from our SE and our sales rep on a call, and we set it up as a PoC. Then, we just roll out that PoC and licensed it after.

Right now, my team is involved in the upgrade process. It is in the middle, i.e., neither simple nor complex. From the process point of view of the workflows, we found it a little complex. At the same time, we don't have the expertise, so we are really dependent on VMware to do a lot of the operation, provide their expertise on the technical side of it, so that's why we find it a little complex at the moment.

Initial setup is really easy, especially with the appliance. You just deploy the appliance, and point it at vCenter. I had one issue that was a little bit non-intuitive as far as setup, which was the ability to pull in vSphere tags. If you want to pull in tags, you have to give it more permission than what you would do for a normal vROps appliance.

For our operations manager, initial setup is complex, so you can't just have someone who just deploys ESX hosts. You have to research it and then move forward. Or, it has to be configured properly upfront before you move forward.

I was involved in the initial setup; it was not that complex. To get it all up and running, stood it up for all our systems, with the assistance of an outside vendor, it took three days.

vROps is easy to set up, deploy, and start using, with no need to spend time doing custom things.

The initial setup is straightforward. You just download the OBA and—"Bob's your uncle." The installation guide is also very helpful. They give you a step-by-step guide for how to deploy it. If you read the document, you'll be okay from the beginning until the end. You shouldn't have a problem.

If it's just a basic deployment, and if you've already got the OBA, it should only take a good 30 minutes, and that would be a lot. I'm just covering my bases, in case there is anything that may not have been taken into consideration. But plus/minus 30 minutes should be enough to do a basic deployment.

Currently there are five of us in the company who are using the product or who are familiar with the product. From a maintenance perspective, the dashboard does most of the job. One person can have a look at it and there are the rest of the guys on the back-end for support. I don't think it needs 10,000 people looking after the product. The product is an automated, driven process. You just need to look at the dashboard and understand what it says and it should make the job a lot easier. You shouldn't need more than one or two people looking at the product every day.

The initial setup was very simple. We have a relatively small environment we were running it against and we didn't have to plug multiple components. We just employed everything all at one server VM stack.

The initial setup can be straightforward depending on what you want to achieve. Overall the deployment of the vROps cluster is pretty straightforward. You set DNS records, set the IP address, then just click deploy and go through the wizard.

The initial setup was very straightforward.

Straightforward, I did it myself.

I was involved in the initial setup. It was straightforward.

I was involved in the initial setup. It was straightforward.

The setup was complex. A lot of their terminology is not what we use; it's very technical, but it's not what a lot of the people use in the field. Actually, I had to set it up myself. I couldn't let one of my juniors do it.

My team was involved in the initial setup. It was straightforward, but again, it didn't work at first because of some decisions we made with the architecture. So after talking to VMware, they kind of led us in the right direction. We made some changes and things started working really well after that.

Pretty simple.

It was pretty straightforward. We downloaded the appliance, installed it, and it was really pretty painless. One thing that we did do, we consulted our VMware TAM to assist us with the initial setup, and understanding which reports we wanted to see and that type of customization.

It wasn't complex, but I've spoken to other people who thought it. So for me, personally no, it was pretty straightforward, but I've been working in the VMware world for a while. I would say, it was very straightforward.

It was very straightforward. Right out of the box you install it and you let it run for 30 days, and it starts giving you back data.

Initial setup was actually pretty straightforward. I pretty much launched the VM, went into the web query and set it up from there; set up all the sensors, took you through a wizard. That was pretty much it. I didn't have to read about any customization.

I think initial setup is real straightforward, because with the vApp, you just deploy it; you basically plug in your vCenter information, create a user for it, and go. It's pretty simple and it starts just collecting the data. That's only 15, 30 minutes. While it takes about a month to start getting valuable data about oversized and undersized VMs in the environment, you just set it up and let it do its thing.

Initial setup was straightforward. The only issue we ran into was replacing the certificate on it with an internal certificate. It was pretty painful, but once I got support on the line, we figured it out.

I have not been involved in the initial setup the last two times that we've done it. I set it up probably two years ago. Since then, someone else on my team has set it up. Initial setup is at least straightforward. There was nothing difficult about setting it up. We were able to get it up and running in just a matter of minutes, and then just waited for it to start collecting data.

The initial setup was very straightforward. From the web interface, you can literally just go straight into actually installing vROps with very little previous knowledge required to get it up and running.

I was involved with one out of two of the setups we did. It wasn't very complex. We had a little bit of trouble in the beginning but nothing was significant enough that prevented us from moving forward. 

The initial setup is not complex because we had a team help us and they helped with the beginning of the installation. Around one hour after we could already start seeing what we could do with it.

The initial setup was straightforward. We had someone from VMware helping set it up.

I had some issues getting things set up in the beginning. I don't know what I did differently but somewhere in there it just clicked and it worked.

It is simple: Deploy WVF file, put in an IP address, and go live.

The initial setup of operations was very simple. All I had to do was fire up the appliance, then give it the credentials of our stuff.

We have our own team which is quite knowledgeable. So, I'll be probably upgrading to the latest version soon.

I helped, but I was not the main person.

Complex. I think it takes a lot of insight into the product. You have to spend a lot of time preparing for it. And if you do that, then you'll see that things go pretty seamlessly.

I was involved in the initial setup. Originally, it was pretty rough. We first put it in about four years ago and it wasn't terribly intuitive at the time. Updates, especially recently, have been pretty straightforward.

I did the initial build. The setup was extremely easy, I feel. The original documentation about sizing was incorrect. That's why the system failed after I got it set up initially. Outside of that, the setup was extremely easy.

Initial setup was very easy for installing the whole configuration part. We're not using that because we're basically accepting all of the default numbers and thresholds for the learning. I think if we had more time and resources, we would probably go in and tweak it to make it more customized for our company. That's probably the most difficult part - the configuration - but setting it up was real easy.

Anyone can install this product!

If you have the proper knowledge, it's easy to set up vROps. 

The initial setup was complex. 

The initial setup was straightforward. It took us half a day.

The initial setup is straightforward. I was able to do it with little to no initial reading.

The initial set-up was relatively straightforward. It was just an appliance to deploy. The setup took a little while to get right, but it wasn't that bad.

The setup was fairly straightforward. There's a little bit of a learning curve to use it, but once you get it, it's pretty easy to use.

As for difficulty, it was probably medium. It's much better than the old Operations Manager. I put in one of those as well and it was a lot more complicated. I think the most complicated thing for our deployment was that we had to externalize our platform services controller. It only took us a couple of days though and then it was deployed.

I thought it was very easy. Easy to follow instructions. Got it deployed within an hour or two. Not hard at all.

I wasn't involved.

The setup was a little complex because of our part, i.e., where it's going our network and how our network is set up, so it was a little challenging.

Pretty straightforward. There were some questions regarding rightsizing when setting it up, but overall it was good.

It is easy, but for best practice go through the VMware official documents.

Overall, the initial setup was straightforward. There are many ways to do this life cycle. We have many different views.

The initial setup is very straightforward. It is very intuitive to install.

The initial setup was easy. We installed the appliance, gave it an IP address, and assigned the relevant passwords.

The initial setup is extremely straightforward, as I train the product.

People coming on training courses for the vRealize Suite find the setup extremely straightforward after being on the training course.

The initial setup was not complex at all, it was pretty straightforward. Just deploy.

It's fairly straightforward, obviously, with their initial installation. The more you become an automated system, the more you really delve into the dynamics of vROps, it can become more complicated, but no more so than any other product line. I feel like it's the easiest of any product line to get through. Obviously, there's intricacies with any of this technology.

I set up my own environment. I didn't set up the customer's.

Once you understand the layout, then it's not as complex. It seems to be, but it's not really, because there's a lot of moving parts. You need concentrate on the moving parts which would pertain to your environment.

I recommend to anyone looking to implement: Have a stable environment. If you don't have a stable environment, you still can implement it, but you're really putting yourself at a disadvantage, because you want to ensure your environment is stable. You don't want to keep concentrating on fixing something stuff. You want vROps to be able to show you, not just what's broken, but what can be scaled out and how to improve your environment. The less you have for it to do, the better it is for you.

For this company, I was involved in the initial setup. It was mostly straightforward.

Even if you Google it, you will find the implementation steps. I didn't have any problems doing the installation. I think if you're a virtualization administrator, you should be able to manage.

I wasn't involved with the initial setup, but I have done upgrades (by myself) and they have been very straightforward. Upgrades take about an hour to an hour and a half to complete.

I didn't do the original vCOPS installation.

I did do the 6.2 installation. The actual out-of-the-box installation's not terribly difficult. Some of the certificate pieces for getting that plugged in is a little more cumbersome than I'd like, but that's a global thing with VMware in general; the certificate management is not where it needs to be.

Initial setup was pretty straightforward. The Horizon adapter had some interesting licensing part to it. You just had to follow the white paper but it was a little tricky at first. Once I got the hang of it, it was no big deal.

Initial setup was very straightforward, very easy. I wish all the other VMWare products scaled out and were deployed and configured as easy.

Straightforward, as stated before it is one appliance you deploy.

The initial setup was easy to set up. I didn't have any problems with this product.

The initial setup was straightforward. 

The initial setup was a bit complex but not really complex. If you take the time to look through the documentation you can figure it out. 

The initial setup was straightforward. In our company, we have a service provider and iOS platform, and they built the application.

I don't think there were many problems setting it up.

The initial setup is easy.

The initial setup was fairly easy. It's an appliance, so you just build it up and then turn it on.

There is a learning curve because it's a complex program. There is a lot to consume in terms of the metrics inside of it. That's the biggest hurdle: trying to understand all the places to go look.

Another guy and I pretty much set up the solution over here in North America. We have other guys in the UK who set it up there.

The install is extremely easy. The VMware products are designed pretty well to do installs. The actual configuration to ensure you show what you need to show; that's where the difficulties lie.

It was really easy to set up.I set it up myself.

I was not involved with the initial setup for this organization, but I have set it up in other organizations.

It is really easy to set up. You just deploy the OVA, and it's done. Give them an IP address, point it at your environment, and you're good.

It was easy. It was simple. It took an hour to install one of our virtual machines, tied into our vCenter server, and that's it. It's a straightforward product. It's really easy to use.

We upgraded and that was really easy, too. Just a couple of clicks and it goes through.

It was straightforward. It was easy. It's a powerful product. It gives us a lot of data. It took a little bit of time to get through some of it, to understand what features we needed to turn on, but that's more of a, "How do we tune it for our environment" issue and not a product-setup issue. Once you understand what you needed to do to set up the product, it's fairly straightforward. The documentation's fairly good, but the interface itself is also pretty self-explanatory.

I did the implementation of it and did it on my own. It was pretty straight forward.

Fairly straightforward, straightforward as any anything.

The initial setup was very simple. Tuning it is harder.

Initial setup is 9/10; it was nearly flawless. Some minor configuration services were complex; how you connect it out across, or how you actually connect two different services.

It was very easy. They installed it using the vROps Wizard.

I was not involved in it.

I was not involved in the initial setup. It was seven or eight years ago.

Upgrading the solution has been simple, though.

It's pretty complex. There's a lot of tweaking to get it to either report on something, or not report on something. There isn't a good set of templates built into the system to really make it go fast. You can install it quickly, you can get it logging quickly, but then it's just a glorified log system.

I was involved in the initial setup. Part of the initial purchase was to have VMware come on site to help install vRealize. An in-house team was sent too.

It's complex, but as long as you follow all the steps and don't miss anything, it's fine.

Initial setup is easy. It deploys as an appliance; wasn't hard at all. Configuring the agents was a little complicated, but once we figured that out, it wasn't bad at all.

Initial setup was straightforward. I actually converted from version 5 to version 6. It worked well.

I was involved in the initial setup. It was very easy, straightforward to install, get running and start getting data.

The installation is a medium level of difficulty.

We had an existing setup, but we have upgraded it. The latest version upgrades have been pretty straightforward. Some of the earlier upgrades were a bit more involved.

Initial setup was pretty straightforward. It wasn't a big deal. Just getting it installed, pointing vCenter to it and then monitoring and capturing all the information. It was pretty straightforward. It didn't take us that long.

It is pretty straightforward.

I've done expansion of it but I have not been involved in the initial build. What I have done is pretty easy. I've had some guidance but the documentation is online and a lot of it is easy to find.

I was involved in the initial setup. It was straightforward.

Before implementation, review best practice guides. There are a lot of them out there. It will make the process easier.

An engineer came to us from their end to help us to install and deploy the solution for us; it was a piece of cake for us.

Initial setup was pretty easy. It took couple of hours.

The initial setup is very straightforward. The platform and add-on solutions are straightforward.

It was intermediate. You had to understand exactly what you were deploying, so you could actually click all the right buttons.

I wasn't involved in the setup.

I was involved and it was very straightforward.

It was easy to set up.

I was involved in the initial setup. It wasn't straightforward. They need to make it more user-friendly.

It wasn't very good.

Somewhere in the middle of straightforward and complex. I remember setting it up and dashboards would have empty data, and I'd have to do Google searches to figure out how to fix it.

I was involved in the initial setup. It was complex.

We have 11 different pieces of the VMR environment. We had to go through and upgrade them all getting everything done in the right order.

It's simple to deploy, it's an appliance. You just go into your vCenter and deploy it and it's up and going pretty much. You go in and you put in your information for your vCenters, it goes out and collects the data and you're off and going.

It was straightforward.

Installation is simple.

The initial setup is easy and takes about four hours.

I was involved in the setup and it was really straightforward. It's like any other virtual appliance. You just deploy it and it just works.