vRA version 7 was very complex to set up. vRA version 8 is pretty straightforward, whereas version 7 was very complex. It could have been better, but they are on the right path with things.

It has been a very major upgrade. We are doing a lot of other customizations and a strategy session, along with this vRA 8 migration, bringing all our storage solutions to a single vendor. All of this is happening in the background. Earlier, we had a different backup solution for different locations, like APAC and the US. That is why it is taking a very long time to do our migration to vRA 8.

This vRA 8 migration is just one part. There are any number of other things that are coming together with this vRA 8 upgrade. So, it has been complex and happening for over two months. We are hoping to combat it by next month.

We have an internal architecture team. They decide how a deployment should go at a high level. Once the decision is made, only then we will implement it. They considered options, like there should be a single portal for global customers' entry within Allianz. Whenever they choose a location within the portal, the request should go to that location. That is why they went for a single distributed deployment this time. Earlier, it was an entirely different instance for each location, which was totally not connected in any way.

Now, it's a distributed deployment, which means if a customer logins in using a single portal. They just use the drop-down location for wherever they want the VMs to be, then the request will go towards the deployment of that location and dispatch properly on the front-end. 

The initial setup is moderate. There could be some trouble connecting multiple VMs to a single master node, but eventually, after getting some hands-on practice, one can leverage tools easily. During the initial period when the team struggled, they took around two hours to deploy. When everyone understood VMware, it took around 30-40 minutes. It was an in-house setup.

We require around three to four people consolidated into a single and deployment teams. They have multiple aspects of others. One was having all the monitoring logs. One was handling VM files or configuration files that need to be maintained. One was looking after all sorts of needs to maintain for every stage. One was a developer looking after all these team members and managing the deployment completely.

I rate the initial setup an eight out of ten, where one is difficult and ten is easy.

The deployment is easy. It takes a day to complete. It requires two to three executives from the network, data center, reporting, and implementation department to work on it. It can be integrated on-premises and on the cloud. 

The product is easy to maintain. One executive can maintain 500 virtual machines. It needs two more executives to manage more than 500 different cloud accounts.

I rate the initial setup process a seven out of ten. It takes ten days to complete. We build the platform according to the specific requirements of customers. Later, we transfer operating systems data on virtual machines.

We used to rely on VMware for assistance when setting up and deploying our infrastructure. The initial setup is complex. It is deployed on-premises for us by VMware teams. In the case of customers, it is dependent on the user's requirements. I would rate it four out of ten.

The initial setup is difficult. I would rate my experience with the initial setup a six out of ten, with ten being easy. 

It is difficult because of load balancing and we need to prepare information and certificates, and there's a learning curve involved. In the past, this product didn't require any load balancers to deploy or certificates for deployment, but now it does.

The initial setup is relatively straightforward. 

From the time that a customer enters into an agreement to using the service, it takes two to three weeks minimum because it takes time to design the whole network.

You need to have a basic cloud infrastructure in place. With an existing cloud infrastructure, the initial setup takes a couple of days. Most of the time, it is a deployment where you are also building the cloud with it, then all kinds of things are required, like the network topology, routers, security, etc. That takes time.

In the initial setup, I took care of the hardware part, but the software layer and other things were taken care of by my engineers. It was straightforward.

Currently, we are upgrading the environment. Compared to the earlier versions, from my experience, the upgrade process is easier; for example, the compatibility checks. I also don't need to go and find out the resources that are required. It tells me in one report what the current environment is like and, if I want to go to the next level, what things I need to take care of. Based on that I can make things happen.

We can automate your workloads both on-premises or any software data center where you want that to be in. If we want that to be in the cloud, it's fine. If we want to provision it on-premises, it is fine. The installation is mostly done on devices. But as with AWS, if we want to use Google, if you want to use Azure, we can use those as endpoints to the VLS automation. And from the same console, we can automate workloads to be provisioned either on VMware Center, that is our own premises or onto our public cloud. So, VMware Aria Automation is there to automate your provisioning or any day one and day two operations. We can do it from one pane of glass to any endpoint, let it be cloud, or let it be our own premises.

So it doesn't have to be specific on AWS cloud or Azure cloud.

The product's deployment process is much simpler than it used to be, especially with the latest version. While previous versions had multiple components and pillars, the latest version has significantly reduced complexity, improving the deployment process. It took a few weeks to complete. You would need two to four resources to complete the deployment. 

The tool's integration with the existing VMware infrastructure is easy due to product similarity. 

Setting up Aria Automation is difficult. The complexity varies depending on the environment size and infrastructure. It has a lot of prerequisites. For example, it has to have a firewall prepared before installation. Aria Automation is deployed through an installer called vRealize that integrates VMware identity manager, Aria Automation, and the vRealize Lifecycle Manager. The deployment takes about three days.

I was involved in the initial setup and the PoC. It was very complex on the initial setup because we started with the 6.x version and eventually migrated to 7. The way it was architected, with the Orchestrator being outside of the vRA appliance, was difficult to set up and configure. The next versions made it a much more straightforward configuration.

We did not do an upgrade. We did a parallel build. Several upgrades actually blew up and failed and destroyed the environments, so we gave up attempting to upgrade a 6.x environment and built a brand new 7.x. At the time, we did not have Code Stream so we could not laterally migrate. An important component of this is Code Stream. For the ability to scale and have multiple automation instances, Code Stream is essential to be able to move that back and forth. If you already have an existing automation environment, you should look at Code Stream very heavily, rather than redevelop.

The initial setup is pretty easy and deployment takes about an hour. 

There are a lot of prerequisites to fill before attempting installation. If something is not right, the solution may not work the way it is expected. 

I rate setup an eight out of ten. 

The initial setup was complex, although I wouldn't necessarily say that it is because of the solution. Rather, there is complexity because of our environment. I was not part of the implementation team so I do not know all of the details.

It took approximately one month to deploy.

Its initial setup is of medium complexity. It is not too straightforward, and it is not extremely complex. It can improve. There are technicalities that are involved.

We have done some deployments that have taken us less than a week. We have also done deployments that have taken us months. On average, it takes three to ten days.

The deployment strategy depends on the requirements. We like to have a repeatable model, but most of the time, customers have different needs. Wherever possible, we utilize a repeatable model. 

I rate vRA eight out of 10 for ease of setup. The previous version of vRA was harder to deploy, but they have simplified it considerably. 

After the deployment, daily maintenance doesn't take more than one day a month. There is nothing much to be done once it's set up. The upgrading is sometimes a headache, and it takes longer. For deployment and maintenance, we need at least one network engineer, one platform engineer, and three storage people. That's because our team is split into three different tiers.

Setting up the primary components is easy, but sometimes scripting is complex. It is not a simple product. It is vast. Deployment, planning, mapping to the business requirement, and including the stakeholders take a lot of time. Modifying the product according to the business is challenging. Business is very dynamic, and we must tailor the features based on the business needs. We use a private cloud.

A lot of information gathering is required to deploy the product. We need to understand the business requirement, demonstrate various features, integrate many endpoints, customize the tool, integrate backup, and integrate scripting to auto-install various software. Deploying and configuring the solution takes a lot of time. It is a full-time job. It requires a dedicated team of people. There are a lot of components. It is challenging.

The basic installation is quite easy. If you have all of the prerequisites ready, then within two to three working days the basic foundation can be created.

Two people could probably deploy and maintain one foundation of the solution.

Our upgrade experience was good.

I was involved in the initial setup of our environment.

The vRealize Automation team, when they released version 7 awhile ago, made immense improvements as far as being able to install and deploy the product, which has been super helpful. 

We track vRealize automation versions pretty closely. There are always new features which are of interest to us, bugs which have been fixed, and the upgrade process has been really smooth lately.

I was involved in the initial setup but not as an engineer. Before I hired Alex, we had a guy put the stuff up. He did it in a couple of days. It was straightforward and it was functional, it worked really well. Then we got this new guy and he had so much insider knowledge. He worked out of Moscow. He was doing all the work for the all the other customers and we hired him in.

We're on 7.4, we're going to upgrade to 7.5 after Labor Day. Since we've gone live, we've done three upgrades and they've all been really good. No issues.

An experienced person will find the on-premises deployment easy to do. I would rate the initial deployment at nine out of ten for an experienced person. For one who is new to the solution, I would rate it at seven out of ten.

The initial setup may take anywhere between 40 minutes to one hour.

The initial setup was complex because we have a high availability cluster. Especially when it comes to upgrades, we have a lot of downtimes and problems. The upgrade experience has been painful. 

I was responsible for the upgrade. It was very complex. One the reasons was that we were going version to version. We learned that some of the objects that were supported in previous versions were duplicated across the board. So we had to clean a lot of the databases to get the new versions.

The setup is very easy. We performed the installation with the customer.

The initial setup is pretty straightforward. I've done it many times though, so at this point I can almost do it without documentation.

The initial setup was straightforward. From a product point of view, it is seamless. The code runs. The software is built into all the appliances, then everything is deployed automatically and integrated with the scripts.

There are commercial implications to start up vRA if a company has no hardware nor knowledge of the product.

Our deployment was one month. Integration and completion of the migration took another two months. Put together, it took us a total of 90 days to implement and start using it. 

The deployment of it is not overly intuitive. It does require some knowledge about putting it out there and deploying it.

I have had the opportunity to upgrade it and that is definitely not the easiest of things to do, generally. As long as you follow the checklist, and which product line you're updating in the specific order, you won't break your system. But if you don't follow the sheet or "the law," you will definitely mess yourself up big-time.

Upgrades have been extremely simple with their Lifecycle Manager product.

Complex. Part of the reason it's complex is that it's like a blank slate. You have to go out there and make your own environments. It doesn't really do anything for you, so if you've got an idea of what you want to do, you have a path forward. But if you don't, if you're just sitting there looking at the blank screen, it could be daunting for some people.

We kind of knew what we wanted and it just took a while to get all those things setup. You have so many different components. Nothing within in our environment was simple, so every management product that we use was probably different than what anyone else would use. So getting all that to work, finding an interface that worked well, that was really why it became complex. It was the complexity of our environment behind it.

So it's not necessarily vRA, it's just that if you don't already have something that's out-of-the-box which says, "Oh, we do all these things..." (I'm harkening back to vCloud Director, because vCloud Director was an all-in-one that did everything).

It was easy to set up this product.

The setup was fairly simple. It's a matter of integrating it with all the other systems and then getting all the sorts to match with the certain policies we've got.

I wouldn't say the initial setup was straightforward but it wasn't complex.  

The upgrade experience went well. It's working well.

I've deployed multiple versions of it, but I have not upgraded. It's not the simplest deployment, but the documentation is there and it's easy to follow. Googling helped with the implementation as well.

The software setup is fairly easy but does require knowledge of the VMware product suite. The complexity comes in whether this a service or a dedicated infrastructure. Normally in service oriented infrastructures which are purpose built for multi-tenancy where you have multiple customers hosting multiple sub-tenant customers which require many layers of micro-segmentation and security to be built in. In a dedicated infrastructure you are building for one business or a single customer even though they have segmented sub-tenants such as account, IT, Operations etc it is all internal to that business. The level of micro-segmentation and security is much less in complexity to provide a final solution.

We have another department that is involved in the initial setup. But I understand it's not straightforward and it's not complex. They have gotten the required training and they've been utilizing it for some time now. They, themselves, are quite knowledgeable in the solution. Clearly, they have been trained professionally. They work with VMware to do the initial setup.

You have architectural design questions that you have to address. We have multiple sites, multiple data centers. One of the fundamental questions is, how do you get HA in vRA? Do you have active-active, active-standby? Today, for vRA, we deploy it out of one site and we use remote execution managers at the other site. We're kind of in an active-standby mode, if you will. We're semi single-point-of-failure, in that respect. We probably should move to get an active-active scenario, but we're not there today.

But the setup was not too bad. It's nothing like a vROps, for example.

The initial setup was complex from beginning to delivery. The current version is a bit more complex than version 7 to deploy.

Our deployment took two days.

The setup was complex in many ways. The first reason is that we have many teams who work on it so it gets complicated gathering all of the people needed. The second reason is that it can be complicated to install it quickly, and within a reasonable amount of time.  

The setup that we have implemented in our enterprise is complex. It's not the exact set up that VMware recommends by default to their customers. We get a lot of help from their consultants to help us with our non-standard design. The entire setup took more effort but it's understandable because it's non-standard.

The initial setup was complex. There were a lot of steps. I would suggest for them to cut back on the number of steps to make it easier. Although with every version, the steps are becoming easier. For example, the certificates in the previous versions were a lot more complicated. It has improved. 

The setup process is good.

My team did the upgrade, but I did not hear anything bad about the experience.

The initial setup was pretty straightforward. Everything was connected. There were little "gotchas" here and there, but either they were easy to resolve with tech support or the documentation usually had some comments about them.

It was straightforward, but it needed technical expertise in this particular area. For those competent in the field that could help us, we utilized them to set it up.

The initial setup of VMware Aria Automation was not difficult.

Without the right technical expertise, the initial setup can be a little more cumbersome, but with the knowledge and the backing of the infrastructure and the engineering, it's fairly simple.

We have upgraded many times. We know how to do it. It's fairly simple for us. We don't get the admins involved. The engineers take care of it all.

We have had the opportunity to upgrade the solution multiple times. The upgrade to vRA 7.3 was painful. The most recent upgrade we did to 7.4 was very sleek, it was smooth, it went really well.

I was not involved in the initial setup but I have been involved in the upgrade process. It was very easy. The whole process was too easy.

We upgrade it anytime we do a technical refresh. It's just like anything else. We're in a complex environment, so to upgrade it, it's almost like you have to migrate the data that is utilized underneath. It's not simple, but it is done periodically.

We did hire VMware to come in and do it, of course. I was not there, in this role, at the time. They came and it works.

We haven't gone through an upgrade process yet. That's on the roadmap. We'll do that before the end of the year but we also have to do vSphere and the rest of VMware stuff.

I was not involved, my team was. We did not bring in VMware to help. We have some knowledgeable folks. They knew it pretty well, so I think they liked the hands-on approach a little bit more. They got it up. It wasn't quite perfect but with some support, they were able to round it out and make it the great solution it is today.

We've got education credits through VMware, so we are training on this constantly. I think it's a matter of using the resources that are out there and focusing on this.

I was involved in the initial setup of the older version. It was extremely complex and difficult to get right.

In evaluating the newer version, it's super simplistic, and they did a fantastic job of all the changes made to automate the automation pool.

It's extremely easy, very straightforward, and has good documentation.

No way was the initial setup straightforward. We scrapped it multiple times. Going through some of the sessions today, here at VMworld 2018, we see that they're incorporating some of the certificate management and so forth. That's where our biggest challenge was.

Upgrading was pretty straightforward. In-place upgrades worked really well for what we've done. There wasn't a whole lot to that. It worked well.

Really, it's all about the initial setup and making sure that it is set up right.

The initial setup was straightforward.

The setup, the installation, is straightforward, but only with the latest releases.

Upgrades are one of the points where incidents are happening. Every time we want to upgrade, a ticket needs to be created and moved to engineering because GSS is not able to help us. We are able to upgrade, but it takes quite a number of retries, which are very costly.

It's not a smooth upgrade process. For a DTA environment, which is very simple, it is a smooth process, but for our production environment, which is quite enhanced and has a lot of dependencies, it's not easy at all, and it results in a lot of errors.

We are trying to set up this new 7.4 in a distributed environment. Every time it was failing with different errors. Finally, we were able to finish it with notes that we had taken, and the help of VMware. However, later on in the product cycle, when applying the same procedure into our production environment, we followed all the guidelines and it still failed. This used to be a one day job, and it has been a one week job.

We have something that is very simple to set up: a single instance with minimal infrastructure. However, we have quite some customization.

Always something breaks when we do upgrade them. We tried to install the latest artifacts two weeks ago, then we had to rollback. We sent the log to support, and we're still waiting for a response.

The setup process isn't intuitive and user-friendly, but once it's set up everything after that is easy. It can be as hard as you want it to be, or it could be as easy as you want it to be depending on how you're setting it up. 

It is completely upgraded to the newest right now. 

We have gone all the way from version 5.5 to version 8. VMware provided us the steps that we needed to do to go from this version to this version to this version, the progression we needed. From there, it was very straightforward.

I was involved in the initial setup and it was complex. The certificates, the distributed install, wasn't straightforward, I'll just leave it at that. We had Professional Services come in for the first round of install. During the second round of install, when we tried to do the update ourselves, there were multiple points of failure. It was not easy. The install, the upgrade features, are not easy at all. The administration part is what is very problematic with vRealize Automation right now.

The upgrade experience is horrible. It's not straightforward, there are a lot of failures, a lot of support interactions. It's not something that we are able to pull off ourselves. I've been with vRA since it was termed vCSA. We've gone through multiple rounds, and it has never been easy.

Setup in the previous version was not so straightforward. They have made big improvements in the later versions. The first one was a pain but the new one is fine. A couple of versions back, they added an automated install that did not exist in the earlier versions that we deployed.

Upgrading took a little while because we did a side-by-side upgrade. There was a code migration, all our custom code needed to be migrated, so it took a little bit of work. But, overall, it was fine.

I thought the initial setup was straightforward. The biggest thing, once we had it set up, was to integrate it with the vCenter, but that was pretty straightforward. That was part of the workflow. It is automated within the product as part of the initial deployment, which is really handy.

The upgrade experience was also quite easy.

The basic setup is pretty easy, but then into the next phases it all really depends on what services you want your end customers to subscribe to. Depending on that, the complexity will vary.

The end-user portion is user-friendly. When you're actually building it, it's a little complicated in setting it up.

For example, in vRealize Automation, there are a lot of different areas where you have to go in and set up key components that have to link to other areas. We had a consultant come in and build our system. If I had to do it on my own, I'd have been spending a couple of hours trying to figure it out. And whether it would work or not, obviously I'd be testing it. But once I actually get to know the product it would be a lot quicker.

It was somewhat complex. The documentation is very long, and I was able to install it based on a blog that I found online. Someone had already previously installed it. They went step-by-step. I thought that was more useful than the documentation.

It's very not straightforward. Perspective: I just deployed the newest version 7.3. It took me about a week total, just a solid 40 hours of work, to get it deployed fully. There are issues with some of the documentation. Mostly, it was fine, but there's a bug with the installation wizard that I spent a long time trying to sludge through by myself, but after opening a support case, they were able to get it taken care of really quickly.

I didn't set up this environment, but I have done the setup previously.

The process has gotten better. It's still a bit of complex. Once it's setup, you shouldn't have to touch it much.

Upgrades have gotten easier as the solution has progressed. It used to be much more difficult. Now, the process is a lot more streamlined.

The initial deployment of vRealize Automation was not complex, but it was tedious and error prone. This was the 6.2.0 version and these issues have been fixed in the 7.x versions.

Being that we have been involved since some of the early 5.x days, we compare a newer installation to the previous, and each time it gets better.

In terms of upgrades, we're just starting to use Lifecycle Manager, which assists with upgrades. I haven't been impressed, so far, with the maintenance of an existing complex infrastructure. But LCM has allowed us to deploy new vRA instances very rapidly, which is helpful for some of our LCM Code Stream movement between our Dev stage and Prod. But for maintaining the existing environment, we just use the out-of-box upgrade capability of the tool, which is so much easier now than it used to be.

We no longer have the significant issues we had in the past. Things are just getting better with each version.

The product has come a long way. Now, it is more streamlined and GUI-based. 

I have done parallel upgrades, then used my grade settings for it.

It's much more straightforward now that it was in version 6.x., to the Nth degree. They have made it so that you can do either a proof of concept or fully distributed version of vRA with a wizard-driven GUI, which is amazing. Now, there are still some little quirks with that wizard, but it being there makes it much simpler than going it manually and installing each component and linking them all together after the fact.

It was a pretty straightforward implementation, but it was just mostly customizing it. We house somewhere around 3000+ virtual machines in our environment. It's hard to customize for that large of a footprint. We have a team who handles the automation piece, since we have such a large virtual footprint.

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

vRA requires a lot of development work. It's not something you just set up, then it works. You have to tailor it to your environment and develop stuff to do with it. There is a lot of development effort with the product.

I have done all the version setups. For one year, we could not get the first version to work. I think this was version 6.0, but the latest version 7 is good.

It's pretty straightforward. You can read some of the white papers on it. It's not difficult.

I personally have not upgraded the program, but the people that actually manage it have not had any issues with it. That being said, it's still a fairly small installation, or a very small group of people that use the product. We haven't expanded it to be able to know, with the installation, how it has gone.

The setup is straightforward. There are plenty of hands-on labs and guides. It's more the, "What can I do with this?" As a project engineer, I try to translate from the vendor to the customer, according to whatever they're doing at their end.

We haven't really had any bumps in the road deploying it.

It is straightforward. It's not very complicated. Most of the tools that VMware develops are pretty straightforward. You just click off buttons. It's easily understandable, and it's easy to implement and use it.

There is complexity to the setup. You have to custom write code for any integrations. It took six months to make it end user ready.

The setup was complex. It's a lot of independent components that are put together that make up a software-defined data center. So, it's really complex. They sent an in-house team.

The setup was straightforward. We upgraded to a newer version seamlessly. It worked really well. 

The initial setup is straightforward. Not for us, again, because of the bureaucracy, but, in and of itself, it is very straightforward. I've done a lot of it in the lab, and hands-on training. It's pretty straightforward and simple.

Early on with version 6, it was very complex. When 7 was released, it was easier. Now, with 7.3 and cloud foundations (and everything), it's a lot easier.

It was complicated. 7.0 was a lot easier.

We're doing cross-training now, so the guy that actually took over for 7 is cross-training the rest of us, and it's been a lot easier for us.

With 6.0, it's just less Windows machines.

vRA setup now is pretty straightforward in a simple deployment. I do most of the functionality, then you just do service mainly. There was one time where I was working and I had to rip out the whole deployment, but I was able to rebuild the whole deployment within a day. That's pretty awesome.

It's very simple, in a very time efficient manner. It deploys the whole environment infrastructure.

I was not involved in the initial setup. I was involved in the upgrade, which was fine with support.

I wasn't involved in the initial setup but we just went through an upgrade. It was not without its challenges. Some of the challenges were probably on our side, being able to support the newer infrastructure. But I seem to recall there being some issues importing some of the old settings and from vRA 6 into vRA 7 so that you could destroy VMs that were built in 6 from within the 7 UI. There were some challenges in getting that done. It's done, but I believe that there were some speed bumps to that.

Once I understood what it was trying to do, and what it was requesting of me, it was simple. But originally, it took me by surprise. I was not used to the setup yet. One of my main issues was having multiple SSL domains. It took me a while to see how those play a part.

The first version that we deployed was not long after VMware had acquired the product. This was with version 6 or 6.2 for a production deployment. There was a lot of work to do with certificates, etc. However, the setup is getting better with each version. 

If you do a deployment for a proof of concept, it is simple. When you start to do a deployment where you need higher availability and more resiliency, then the complexity goes up drastically.

It's fairly complex. The documentation continuously evolves and the product seems to change every couple months. It's trying to piece together different forums and documentations to figure out how to get a working solution.

Complex. We deployed the original version of vCAC and there wasn't a lot of documentation at the time. There are a lot of disparate parts that have to be deployed on multiple machines that involve a bunch of load bouncers. Issues like that.

We purchased PSO resources.

I was not involved.

The installation has been greatly improved in the latest version. There's now a lesser based installation, which has made it many times easier. It is still something that requires a bit of knowledge and time (if you've never used the product before). It is probably going to take you a week or so to get familiar with the concept and try the installation maybe one or two times before it works for you. Once you've used it a few times, you can probably do an installation in a day or two. So maybe a seven out of 10, for ease of installation.

The initial setup was straightforward. However, the more advanced capabilities of the tool are more difficult to understand and implement.

The installation was complex and time consuming.

The initial setup was straightforward. It's easy to deploy. 

The upgrade experience was a nightmare. I upgraded from 7.4 to 7.5 and it's been terrible. 

I came in about halfway through the initial setup. It was very complex. We had VMware projects going on, so we had a couple of consultants giving us full-time personnel to help us through it. We had VMware there, and AdvizeX was another one. Then we had the specialty people from VMware that they deployed out to our place.

The setup was complex. Even with the Professional Services, it took days and days to try and get it installed and working right.

We have had the opportunity to upgrade and it failed. We're having troubles with that. We're still working on it.

The implementation for vRealize is straightforward. The upgrade experience is pretty good, satisfactory.

The initial setup was not straightforward. It was not simple, and we had a PoC. We had VMware help us deploy it, and it took them an exorbitant amount of time.

Upgrading hasn't been without its pain. We've had our issues, we've lost some data. There have been some hiccups along the way. We're confident that this next upgrade will be smoother, since it has been getting more stable over time.

The initial setup is very complex. You will deploy at least three VMs, a Linux appliance, a Windows IIS server, and a Microsoft SQL server. If you want high availability, you will deploy two of the appliances and IIS servers. The deployment process requires specific versions of .NET and Java, as well as some specific config file edits. After the actual VMs are deployed and ready to go, you will then be required to set up tenants, and all the associated permissions and groups which are required for this. You will need to set up connections to your vCenter servers, and reservations based on these connections. Creating blueprints can be simple or very complex depending on your needs.

The installation for vRA 6.x was complex, but for vRA 7.x was simple.

The initial setup was very easy. The upgrade was also pretty easy. It was not quite as easy when I piloted it through Lifecycle Manager, but that was in its infancy. It has probably gotten better.

The solution itself has a learning curve to get used to building the Blueprints, but once you've done it, it gets much quicker.

I was involved in the initial setup.

The initial setup for the 6.2 environment was a little bit painful, because you have to have a separate the IAS server and different things, like a Windows server. Now, with the new 7, I know it's all appliance-based, which is beautiful.

It's easy to set up. I have a PoC environment right now we're toying with, and it's a lot more simplistic than the prior versions were. I'm more familiar with the old architecture of it, but I'm looking forward to really implementing the new architecture of vRealize Automation.

I would give the latest version of vRealize Automation a 10 out of 10 because it helped minimize the setup time.

The initial setup is very complex because we have a bunch of customization workflows. They were built-in features that we had to program as code with Orchestration. 

We haven't upgraded because we had to set up the entire environment with the vRealize Orchestration scripts. We have to do it again from the scratch.

The initial setup was straightforward. My mom could install it. 

The initial setup is complex. There are too many components to integrate, especially when we integrated with different storage types and backup vendors. All the integration made it more complex.

We haven't upgraded yet.

The setup is fairly complex, but we've been using it for a while so I'm pretty knowledgeable about it now. Upgrades are pretty straightforward. We had a lot of problems originally deploying it, with some certificate issues. We had an engagement with VMware so they were able to help us get a proof of concept environment set up as well. So that was helpful.

I was involved in the setup. In the original version 5, it was very complex. Version 6 got a little better. Version 7 is much more improved.

It's a quite straightforward setup in comparison with products in the same domain.

It was straightforward but they still need to improve the IaaS components.

Straightforward.

It was a complex setup. We had to use the consultant from VMware to make the solution work well.

The upgrade was a very difficult task. We had to break everything down and build it up new in a new version.

The initial setup was complex. It's improving now.

It was complex; the certificate was the worst part.

Installation was straightforward and simple .

The setup is difficult. You need a technical person to help you set it up.

We have not upgraded yet.