What is our primary use case?
Our primary use case for VMware vCenter Server is to centrally manage our virtualized datacenter infrastructure. We run a mixed environment of Windows and Linux VMs across a TIA Tier-3 certified datacenter on VMware vSphere clusters, with Cisco networking, Palo Alto firewalls, and F5 load balancers integrated.
vCenter allows us to manage hundreds of VMs and ESXi hosts, streamline provisioning, enforce resource allocation policies, and monitor performance from a single pane of glass. We also rely heavily on vCenter for high availability, vMotion, DRS, and lifecycle management of hosts and VMs.
How has it helped my organization?
VMware vCenter has significantly improved our organization by providing a centralized management platform for our entire virtualized datacenter. Earlier, managing multiple ESXi hosts and VMs individually was complex and time-consuming. With vCenter, we can now:
-
Perform seamless vMotion and DRS to balance workloads automatically.
-
Ensure high availability and resilience, reducing downtime for mission-critical applications.
-
Simplify patching and lifecycle management of ESXi hosts.
-
Gain end-to-end visibility into performance, storage, and networking through a single interface.
This has improved our operational efficiency, reduced escalations from support teams, and increased uptime for services we provide to customers through our public cloud platform.
What is most valuable?
The features we find most valuable in VMware vCenter are:
-
vMotion & Storage vMotion – Seamless live migration of workloads without downtime has been critical for maintenance and load balancing across our clusters.
-
Distributed Resource Scheduler (DRS) – Ensures optimal resource utilization by automatically balancing workloads, which is especially useful in our multi-tenant cloud environment.
-
High Availability (HA) – Provides resiliency for critical business applications, reducing downtime and meeting SLA commitments.
-
Lifecycle Manager – Simplifies patching and upgrades of ESXi hosts, improving compliance and security.
-
Centralized Monitoring & Alarms – Single-pane visibility of performance, storage, and networking health enables faster troubleshooting and proactive management.
These features together have improved uptime, operational efficiency, and customer experience in our datacenter and public cloud platform.
What needs improvement?
While VMware vCenter Server is a robust and mature platform, there are several areas where it could improve:
-
User Interface Performance – The HTML5 web client has improved over older versions, but performance can still lag when managing large-scale environments with hundreds of hosts and thousands of VMs. A more responsive and intuitive UI would help.
-
Native Backup & Restore – vCenter still relies heavily on third-party solutions for full-featured backup and restore. An integrated, enterprise-grade native backup tool would add value.
-
Reporting & Analytics – The built-in reporting is limited. More advanced dashboards, historical trends, and predictive analytics powered by AI/ML would be beneficial.
-
Simplified Upgrades – Upgrades and patching, while improved with Lifecycle Manager, can still be complex. A more automated, zero-downtime upgrade path would be ideal.
-
Cost Optimization Features – As organizations move toward hybrid/multi-cloud, native cost visibility and optimization tools within vCenter would help IT teams manage budgets better.
Suggested Features for Next Release:
-
AI-driven capacity planning and predictive analytics to proactively avoid performance issues.
-
Integrated backup and DR orchestration without needing third-party tools.
-
Role-based dashboards tailored for operations, management, and security teams.
-
Enhanced API integrations with public cloud platforms (AWS, Azure, GCP) for hybrid cloud management.
For how long have I used the solution?
I have been using VMware vCenter Server for more than 13 years, starting from version 3.x, and have continuously upgraded through versions up to the latest 9.0 release
What do I think about the stability of the solution?
From my experience, vCenter server has rarely been a point of major concern regarding availability. It mainly provides centralized administration, so its unavailability doesn't directly affect the functionality of our cloud infrastructure.
I've encountered a few instances where vCenter was unavailable or crashed, but the impact was minimal since ESXi servers and the virtual machines on them continued to run smoothly, although features provided by vCenter were temporarily unavailable.
What do I think about the scalability of the solution?
Initially, when vCenter was introduced, scaling it to support a certain number of ESXi hosts and virtual machines was quite challenging. This was around 2012 and 2013.
However, it has become increasingly scalable over time. Nowadays, we can deploy multiple vCenters in a cluster formation to scale extensively. I haven't reached the maximum capacity of vCenter because it's huge.
How are customer service and support?
I've been working with VMware for about 10 years now.
Earlier, VMware support was very good. The technical guy on the call used to understand the issue from their side. And then, if that issue was beyond their expertise, they generally called other guys or used to forward our call to the next escalation team or something like that. We just used to call them once, and then we got our solution during that one call.
But in the last four to five years, there's been a kind of 360-degree change in terms of customer support from VMware. And most of it's going in the negative direction, which we are not happy with.
The technician now says, "Okay, this is beyond my expertise. I'm going to escalate it to the next team, and they will be in touch with you in a couple of hours or maybe the next day." And trust me, nobody contacts us until we open another ticket, reference the ticket we opened previously, and ask them to give us priority one support. And again, they start troubleshooting it from scratch. Again, "This is beyond our expertise, and we will forward this call to our next escalation team, and they will get in touch with you." We get stuck in this kind of loop most of the time.
If I'm using ten tickets with VMware, three to nine times it happens when we, you know, keep chasing them for the technical things. Even though they fixed the issue, we ask them to provide a complete justification, the root cause of why this issue occurred, what exactly we did to fix it, and how we can make sure that this issue will not come again in the future. They don't have a clear answer for us. But since things start working for us, most of the time, we don't bother about that.
But for our reference purpose, we want to keep RCA (Root Cause Analysis) and other documents updated so that we can fix those issues from our side or take any preventive action even before we hit the same situation again. But in the last four or five years, we've been lacking there. Because we're not getting that much good support from VMware, which we used to get back in 2012, 2013, 2014, or so.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
We have one of the Microsoft Hyper-V solutions.
How was the initial setup?
I've installed it on servers and provided regular support, so I do have experience with the initial setup process.
Earlier, it was a bit difficult because it required a separate database server installation before installing the central server, and then the database had to be integrated during the vCenter server installation.
However, this process has been significantly simplified now. vCenter now includes its own database, eliminating the need for separate database installation. We just follow a single setup to deploy vCenter along with its required database, which we are quite pleased with.
The deployment takes approximately 30 minutes to 45 minutes, depending on the infrastructure where it's being deployed, so generally less than an hour.
What about the implementation team?
When I was part of the deployment team, I was the only one responsible for it. Now, we have a dedicated team for installation and deployment, but only one resource is required to deploy the vCenter server.
Assistance from VMware is not really required because the process is very straightforward and simple.
We just need to follow the instructions provided in the setup wizard, enter the required values, and the installation completes smoothly and straightforwardly.
I have mostly deployed it on-premises and haven't had the opportunity to deploy it in a hybrid environment.
What's my experience with pricing, setup cost, and licensing?
The licensing model was a bit complex, but thanks to the vCenter product usage program, which VMware introduced, it's kind of easy for us to use a pay-as-you-go model. So, it's streamlined now, and we are okay with that.
What other advice do I have?
I would advise that at least you should be very well aware of all the functionalities you are going to offer to your customers. Then, you should see whether those functionalities are there in the vCenter server and working as per the documentation provided by VMware. You should be very well aware of it.
One example is the fault tolerance problem. Although VMware said it was fine, practically, we haven't seen it working as expected. So features need to be identified in advance before choosing vCenter server.
Overall, I would rate the solution a nine out of ten because I'm very much happy with all the features provided by vCenter.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Other