I use VMware vCenter and VMware vSphere 7.0, as they provide another level of management.

Apart from our limited experience with Global Cloud, AWS, and Azure, we primarily focus on implementing vCloud platforms within our company's premises, specifically within our data center.

We use vCloud and Microsoft.

One thing I like about AirWatch is that we can create different profiles and assign them to the devices. And when some application is not being deployed from the console, we can select and manually push for it. 

In Intune, we don't have these options. So, we create a profile, and then we hope that the other profiles are landing on the devices. And if there are some devices not running, then we are not able to force or reinstall. This is one of the big differences that I see between one and another.

Intune is more complex than AirWatch. AirWatch is more accessible. It's easier than than Intune.

Our company previously used OpenStack. 

I previously used Morpheus, but I switched to vCloud Director due to integration issues after upgrading. Specifically, Morpheus had challenges integrating with another solution we were using, prompting the switch.

We previously used VLS Automation earlier and multi-tenancy was also quite simple over there, but the only thing was the SSO integration with the multi-tenancy was not consistent. That's the reason we switched from VLS Automation to the private cloud, vCloud Director.

I previously used Azure and AWS databases for cloud management. The main reason I switched to VMware, particularly vCloud Director, was the need for better flexibility and stability in managing my infrastructure.The product is inexpensive compared to AWS, Azure, and GCP.

We were using VMware already, then some of our customers asked if we could give them a cloud solution

We decided to automate our actions.

We analyzed the markets and our clients. We gathered some feedback from our clients and after that, we decided on this solution. 

We've been in the hosting business for fifteen years, so it was a natural evolution for us when it came time to switch. In a way, we are growing together with VMware.

We picked up this solution because we needed to provide new services.

We went with VMware because we have a lot of VMware experts in our business, it's something that we're quite skilled at. We are partners as well. VMware is generally the first protocol for these sort of things.

Most of our clients are using classic solutions from the vSphere, 6, 5.5, or even older. We give them vCloud Director as an option for their business. 

We used rented servers running VMware ESX/vSphere on SoftLayer and decided to switch to VCloud Director because we got tired of the hardware issues we had with those servers (RAID controller failures, HDD failures).

Yes; Microsoft's Azure for cloud and Hyper-V for virtualization. The reason for switching was indeed the efficiency crisis with Hyper-V resulting in subsequent service issues ->service tickets-> increased number of troubleshooting tasks -> increased number of breaches in the SLAs

We did not use a previous solution.

The main reason that we switched solutions was that we were running a legacy based infrastructure as a service. Customers had to submit a ticket and then we did something in the background for the customer. They requested self-service capabilities, so that was the main reason we knew it was time to switch.

Our customer wanted to deliver a host and new services. We discussed what would be good solution and thought that vCloud Director would work.

We were using Lab Manager, and when VMware discontinued it, we needed to switch.

No, but in the future, we are planning to install Open Stack as it's simpler.

In the past, I evaluated multiple products, such as CloudBolt.

We decided to go with vCloud Director because of its onApp features. Other products are totally different. CloudBolt will be integrated with the VMware vCenter, a license being needed for VMWare, as well. 

Another reason we did not go with the alternative is because it is not a multi-tenant platform.