I know that it's got some capabilities that we're not using at this time, but the one that comes to mind is the ability for us to see how our VDI environment was performing for some classrooms, so that we knew what kind of resources we needed to allocate better to our VDI pools for our students to get good experience in that classroom.
It's taken the questioning out of what's going on. You're not pointing fingers anymore at software or hardware for no reason. You're actually able to dig into the troubleshooting and see the trends, to see the analysis overtime. You can say, "Well, this is when it started. Before that date, everything seemed fine." Or, "Well, this was when we had more students online, it looks like we need to reallocate some resources." It's taken a lot of the guesswork out. It's allowed us to be more proactive instead of reactive, which is nice.
From a personal perspective, I would like it made clearer what options are available in the suite that the customer is not using. I know that I'm not using all of the capabilities for our environment, so being able to know where I could improve, or gather more data from - easily, in the interface - would be a big help. Without than I just have to go through tech support or read more of the documentation, dig in to get it out. If the system itself actually said, "Here are other options" that were easily visible, that would help people actually use the power of the product.
We haven't had any problems with it. It's been a great product. When we need to go to the portal, the portal's there. If we need to pull the data out, it's there. We haven't had any issues accessing the system, keeping the system up and running, and setting the system up overall was really simple. I'd say it's a rock solid system.
It scaled out really well, the first time that we needed it to. We had vROps in our regular computer infrastructure, and then we needed to scale it out so that we could bring our VDI environment in. We did that very easily. We stood up another collection node, tied that into our VDI system, and then added that into the main cluster, and it was just straightforward and streamlined. It definitely scales out as needed.
We have not had to use tech support for vROps.
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.
We decided to use it because we're licensed for it. There wasn't a larger discussion around it.
The most important criteria when selecting a vendor are communication, availability, and the ability to really understand your needs as an organization. Can they put aside some of the business talk and really understand your organization and the solutions that you may need? Whether they're able to work with a higher education institution, in our case, was also important. Those are some of the biggest considerations for us.
There's no solution that's absolutely perfect. It's great for a trend analysis and a growth tool, if you want to do growth projections and things like that. Using it for what it's intended for, it's perfect. Does it give you all of the goodies that you might want in a monitoring software? No, but that's not really what it was designed.
If you have the license for it, install it. Put it together, even if it's in a test environment. Let it gather some data for a couple weeks, and then look at what data has been collected, what it says about your environment. You might be surprised by what it's telling you. You might be able to see some things that you can improve on, or it may just reinforce that your environment is tuned really well. Again, if you're licensed for it, I'd say install it and use it.