What is our primary use case?
As a cloud service provider, we offer infrastructure as a service using VMware components.
To centrally manage all ESXi servers, we use vCenter. Its features, such as high availability (HA), Distributed Resource Scheduler (DRS), and vMotion, make vCenter a unique and valuable product. These features significantly aid my team in delivering superior services to our customers.
As a cloud architect, I'm involved in designing and implementing various solutions, mainly with VMware for virtualization from the computing perspective.
This includes VMware vCenter, ESXi, VROps, vRealize Automation (vRA), and NSX for networking solutions. My team also works on storage, backup, and security.
I also have experience with VMware vRealize Automation (VRA), which integrates with Center.
In the past, my team deployed virtual machines for our customers because we couldn't offer a self-service portal or automation solutions.
With vRealize Automation, we're not only able to automate tasks but also manage vCenter resources efficiently. It allows us to assign resources to customers as needed and provide them with a self-service portal.
Now, customers can complete tasks independently thanks to automation and workflows in VRA, significantly reducing the need for direct support from my team.
How has it helped my organization?
The primary benefit is its user-friendliness. It's not overly complex, allowing new team members to quickly get up to speed.
Centralized management of ESXi servers and virtual machines is another key advantage, enabling control from a single console.
This centralized administration, along with vCenter's integration with other VMware products, simplifies the management of our virtual infrastructure.
The integration of vCenter server with any software, whether from VMware or a third party, is smooth and straightforward. We know the required ports and credentials for integration, allowing us to easily integrate vCenter with various products, enhancing our cloud infrastructure.
However, there was a challenge we faced with vCenter, and tried to fix it. Initially, vCenter had its own client console, which was deployed on our laptops to connect to the vCenter server. This client was amazing because it offered a clear view and direct access to vCenter without dependencies.
However, VMware transitioned from this client software to a web-based console, aiming to eliminate dependencies and make vCenter more accessible. This change introduced challenges, such as the need for patches and browser console errors requiring restarts.
The web-based interface felt cluttered and complicated compared to the cleaner, more straightforward client interface. This complexity can be overwhelming, especially for those not highly technical.
This abundance of options on a single screen can be overwhelming, unlike the simplicity of a Google web page where you just type and search.
What needs improvement?
There is a feature called Fault Tolerance (FT), which has been part of vCenter servers since the product's inception.
However, it has a lot of complexity, and when my team tested it, we found it difficult to manage. It also has some bugs. Consequently, we decided not to offer any fault tolerance features to our customers.
So, there are a lot of things that need to be improved in fault tolerance.
For how long have I used the solution?
I have more than ten years of experience with vCenter and still use it daily. It's a core product for us, something we engage with regularly.
Buyer's Guide
VMware vCenter
May 2024
Learn what your peers think about VMware vCenter. Get advice and tips from experienced pros sharing their opinions. Updated: May 2024.
787,817 professionals have used our research since 2012.
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?
On-premises
Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor. The reviewer's company has a business relationship with this vendor other than being a customer: Reseller