VMware vRealize Automation (vRA) Previous Solutions

Sr Virtualization Engineer at a healthcare company with 1,001-5,000 employees
We were manually spinning up clone templates and building them. We recently took over and built our IT after 50 years of being under HPE. About five years ago we decided to internalize our IT and take everything back. We built a new IT organization literally, out of this solution; it is one of the tools that made us successful. Once we virtualized our infrastructure, automation is what made us be able to work with it. Our important criteria when looking at any vendor are support and communication. View full review »
Allen Nussbaumer
Systems Administrator at a tech services company with 51-200 employees
We weren't using much. This was right at the beginning of when we were starting to automate things. We saw the VMware automation and decided that, since we had VMware, it would be the logical choice. And then we started with Jenkins for a lot of our other operating system features. Jenkins, of course, has plugins that talk to VMware natively, so it was a natural fit. When selecting a vendor, the biggest thing for us is multi-operating system support. There is the classic divide. I'm on the Windows side. We have a Linux department also. When looking at different tools, something might be better for Linux but we have to have something that will work for both of us. We don't want to have two different tools for two operating systems. Whereas the Linux team wanted to use Puppet instead of Chef, Chef supports Windows and Linux both, better. The nice thing about VMware, aside from it being a lot more OS-agnostic, is that both teams can use the product. One product for both operating systems. That was one of the primary things. We could have a tool that runs great, but it might be a situation where, "Oh yeah, your Windows support is lame." That's the big thing for us, the interoperability between operating systems. View full review »
Product Engineer at a tech company with 5,001-10,000 employees
Before vRA, we were using a combination of Chef and Ansible. We moved to vRA because I'm on the VMware side of the house, so naturally, that was part of it. Also, we switched because we foresaw the need for hybrid cloud and wanted to be relatable to VMware, so we could have an answer to compete with business units. We wanted to say, "We have vendor-supported vRA that does the same as your third-party or your open-source." We wanted that name brand with it because that's the department I'm in. Compared to the previous solutions, while I don't have too much experience with them, from what I understand, from what I have heard from the people I work with that helped me on that side, it is a lot quicker. In the small test bed that we have, it is performing better as far as being able to deliver, and being consistent in its delivery. View full review »
Learn what your peers think about VMware vRealize Automation (vRA). Get advice and tips from experienced pros sharing their opinions. Updated: April 2020.
430,905 professionals have used our research since 2012.
Bob Plankers
Solutions Architect at a university
We came to the conclusion that vRealize automation was right for us as part of an effort on our campus to consolidate IT from a real distributed model into a less distributed model, but still retain a lot of local control with departments. A lot of higher education institutions have similar problems. People want to retain local control, but all the IT is spread out all over campus. This is a real problem. As we talked to people, a private cloud was the way we felt we needed to go: To be able to do self-provisioning and self-service for groups who really wanted it. We also wanted to be able to add additional advanced features, workflows, integration points, and approval processes, and vRealize Automation could do all of that. We were able to span from our simplest customer to our more complicated customer in the same product. This is why the product appealed to us. View full review »
Craig Debban
IT Director at a tech vendor with 201-500 employees
Before, it was piecemeal. We had templates. We had some VDI pools for some of these things. It was just a constant revision of that and it would sit idle for too long. So, for the whole pool, if one or two people were using it, great; but if 10 were using it, then it was not the most efficient way to operate. When selecting a vendor the most important criterion is the relationship, to be honest. Pricing, you can beat people up and have negotiations on it. Pricing, obviously, at some point was an issue, that factors into it. And we need to make sure all the technology fits. But having a relationship with the vendor that can be with you through the good times but also the bad, that makes it worthwhile. View full review »
James Jones
IT Manager at a individual & family service with 10,001+ employees
I brought VMware into the company in 2004. Before that it was manual, bare metal boxes. View full review »
David Gangwish
Systems Engineer at a insurance company with 1,001-5,000 employees
We had no automation engine before we started vRA a couple of years ago. It was something that our directors and our management really wanted to get into our environment so we could automate some of these processes that are very redundant. When selecting a vendor, interoperability - whether it can operate with the other solutions that we've already implemented - is important. Also, how much the vendor is willing to help and work with us to make their solution viable is another factor. View full review »
Alain Dalis
Technical Manager at a pharma/biotech company with 5,001-10,000 employees
It was a logical and smart decision for us to have this solution in place. It makes sense for my business. We used Orchestrate, the original version. It was the first automated system that could deploy complete solutions. We decided to go with this solution because it was evolving and I just followed the evolution. We switched to vRealize three years ago. View full review »
Sr. Manager, Open Systems Service Desk at a healthcare company with 501-1,000 employees
Previously, we used a product called LiveManager. It was not across the entire organization, it was just a subset, so there was nothing really prior to this. When looking at a vendor, the most important criterion is how good a partner will they be? Will they be around? Is it somebody that we can trust and that has been utilized in the marketplace? In addition, is the solution scalable? And then we'll look at cost. View full review »
Brian Wurtzel
Systems Administrator at a manufacturing company with 1,001-5,000 employees
Previously, it was just me manually building VMs. When my workload started increasing and I started getting more tasks, my manager noticed that it took longer to deploy VMs. At which point, our senior admin knew about this product and suggested that we move forward with putting it into the new environment. View full review »
James Thomas
Customer Apps Manager at TSTT
We didn't have a previous solution. Regarding this solution, I don't think the cost was a major factor in its selection, based on what it offers. It was more of, "Can it meet our growing needs, as well as what is the experience that is out there?" Based on those issues, I am sure that is why it was selected. View full review »
Ashok Padmaraju
Technical Manager at Gilead Sciences, Inc.
We are a VMware shop. We also have Citrix and Microsoft hypervisors but, compared to both of them, VMware is the best for us, for our environment. When selecting a vendor, price is not the only criterion. The product availability and how much better their support is, are also important. View full review »
Brian Wurtzel
Systems Administrator at a manufacturing company with 1,001-5,000 employees
I was doing it by hand. View full review »
Senior Associate at a consultancy with 10,001+ employees
We just had vCenter. Ultimately, we were looking to take that to the next level. We wanted to allow our customers to be able to potentially consume the catalog items and to better leverage things, and to give more transparency to what we can provide. At the same time, we wanted them to not have to go through all of the ticket-raising process. We wanted to be able to allow them to get right to it. View full review »
Principal Engineer at T-Mobile
The solution we were using, technically, was ServiceNow but it wasn't as good for our environment. It was very good at creating small cookie-cutter, but not for large-scale. When looking for a vendor the most important thing is support. Absolutely. If I don't understand the product, I need to make sure I can get an answer as quickly as possible. View full review »
Systems Engineer at a insurance company with 1,001-5,000 employees
To my knowledge, I don't think there was a previous solution. View full review »
Systems Admin at a consultancy with 11-50 employees
We didn't have a solution that does exactly the same. For other systems, we use Chef, but I know that that is more for the application side of things. We haven't used anything like this. What's important when looking for a vendor, for me, is that they take their time to actually see what we have and what we are trying to do, before pushing an agenda. If they could see what we have and create a design out of that, before suggesting anything else, that would make me want to work with that vendor more because then I would know that they are not pushing something, that they are giving me what is better for me. View full review »
System Engineer at a retailer with 10,001+ employees
We didn't have a previous solution. We were doing manual. We still are, but we're within 15 to 20 days of deploying it. We went with this solution because of the partnership with VMware. We have vCenter, we have a bunch of their products, so it just made sense to try to go with a simple approach. The most important criteria when looking to work with a vendor are the ability to adapt to us and our needs, and that the vendor be quick on responses. View full review »
Senior Systems Admin at a retailer with 1,001-5,000 employees
There were other solutions that were used previously, but this one is the main one I have used, personally. Before coming to Bass Pro, where I am working now, it was a lot of VMware on bare metal and dealing with it directly. vRealize wasn't there. View full review »
Principal Vendor Manager at a healthcare company with 501-1,000 employees
We've been with VMware for such a long time, in excess of a decade, and because of that, I wasn't working here when they had an earlier solution. View full review »
Systems Engineer at a tech services company with 1,001-5,000 employees
We were using Lab Manager before but that was decommissioned so this was the next solution. We chose it because it did everything we needed it to do, it was the logical step from Lab Manager. The criteria for the selection process included that we needed to have a self-service environment for our developers, that Customer Care be able to deploy machines, destroy machines, complete the entire VM lifecycle - and this does it. View full review »
Technical consultant at a comms service provider with 10,001+ employees
We work a lot with VMware and were using vCloud Director previously. VMware architects came to our office and, after much discussion, vRA popped up as the best solution that fit our needs. View full review »
IT Solutions Architect at a financial services firm with 1,001-5,000 employees
We had a little homegrown thing but that doesn't really count. When selecting a vendor, if we already have an established relationship with the vendor, it's easier than going to a new vendor and establishing a new relationship. View full review »
DevOps Engineer at a pharma/biotech company with 5,001-10,000 employees
We brought in vRA as part of a new product offering for our customers. It's what we have used from the ground up to provision virtual machines. View full review »
Daniele Ulrich
Cloud Architect at Swisscom
We switched because we don't want to focus on the cloud management platform. We want to have this resolved and supported by a vendor because we are system integrators and want to supply the services and the knowledge above that. View full review »
Principal Systems Engineer at a tech company with 10,001+ employees
We switched because VMware canceled the Lab Manager products. So, we were looking for something, then we started with vCloud, but VMware canceled vCloud too. Thus, it has been a very rocky road. My one message to VMware, "Stick with one direction and stop cancelling products all the time." View full review »
Network Lead at a tech company with 10,001+ employees
We were previously using a product from CA that CA no longer supports. They got out of the business. View full review »
Virtualization Engineer at a financial services firm with 1,001-5,000 employees
There is a war on wasted initiative and on waste of time, more than a concern about environmental resources, unfortunately. The war has been identified on multiple levels, especially deploying in our realm. When looking to work with a vendor, the important criteria we look for are * professionalism * the value of the product for the return on investment * personally, I look at energy costs and savings as well. View full review »
Head of Cloud and Technology with 1,001-5,000 employees
We used the Orchestrator that was free, but started to build some automation on top of it, then we needed to evaluate different tools in the market. View full review »
Solution Architect at a tech services company with 51-200 employees
We knew we needed a new solution when we were falling behind and could not deploy what the business units needed. View full review »
Systems engineer
We also looked at Cisco. View full review »
IT Infrastructure Manager at a consultancy with 10,001+ employees
For the virtualization part, we have previously used Veeam. We licensed VMware a long time ago. Now, we are moving from our legacy infrastructure to have a proper, private cloud environment. View full review »
Robin Naundorf
Systems Engineer at a university
We did not use another product previously. We had to invest in a new solution because we had to react faster to customer demands. Previously, it took a long time from requesting a new virtual machine to provisioning it. Now, it is much quicker for the customer. View full review »
Solutions Architect at a comms service provider with 10,001+ employees
I was a VMware consultant for years and I saw successes with it in other people's environments. View full review »
Laurentiu Coica
Team leader infrastructure at Asseco SEE
We knew that we needed to switch to this solution because our customers asked for it. View full review »
IT Architect at a consultancy with 10,001+ employees
We were not using anything previously. We have been using VMware for quite some time. View full review »
Engineer at a tech services company with 501-1,000 employees
I am not aware of a previous solution. We moved to vRA because the business wanted quick, repetitive deployments. View full review »
Edgar Voss
Information Technology Services at TUI InfoTec GmbH
We had another product before this, but we moved away from it to use vRealize Automation. The UI, administration possibilities, and the integration of the overall system were better than the former system, which was not up-to-date. View full review »
Computer Repairman with 5,001-10,000 employees
We used a little bit of everything. View full review »
Head of IT at Interswitch
We are highly virtualized, so we like anything related to VMware because we need the visability their products provide. We need to know what is going on, so we can supervise our operations. View full review »
Learn what your peers think about VMware vRealize Automation (vRA). Get advice and tips from experienced pros sharing their opinions. Updated: April 2020.
430,905 professionals have used our research since 2012.