- One-window management of servers
- Less down time in case of a disaster
- Easy to use and manage
- One-window management of servers
- Less down time in case of a disaster
- Easy to use and manage
After deploying this, we have saved hardware and electricity costs.
Not yet rectified.
I've used this technology since 2010. It is a really amazing product. By shifting almost my all physical servers into one Box "Host Machine", I am relaxed now.
Not yet
I have also deployed VMware.
My primary use case of this solution is for virtualization.
The most valuable feature of Hyper-V is that it's very intuitive.
Setup is very simple, and you can follow along without any documentation.
With Hyper-V, you don't have any issues about making license payments as it's a Microsoft product.
I would rate this solution as eight out of ten.
We provide services, such as virtualization, website hosting, and some infrastructure services. We provide all the services to the public companies.
The product is a great option for enterprise-level organizations.
The solution comes in many languages. We can have it set up in Portuguese, for example.
The interface is quite good.
The setup is pretty straightforward.
The product can be a bit difficult to use. I find, for example, Citrix to be much less difficult.
It's hard to calculate how long we've used this solution. It's been a while.
I also work with Citrix. In my opinion, Citrix has the more complete online material.
The initial setup is pretty straightforward. It's not a difficult process.
I was not involved in the acquisition of the solution, so I do not have exact details about the pricing.
We are a public company, a government company, and, due to legislation, most of the time, we can't simply choose a vendor. If we need to acquire a contract solution, we make a technical study where the features are evaluated and the final specifications are always based on features, not on vendors, or manufacturers.
We are service providers. We don't provide products. We are implementors.
In this company, we work mostly with on-premise solutions, such as hypervisors. For example, the Microsoft Hypervisors, Citrix Hypervisors, et cetera. Here in the company, we don't use exactly cloud solutions, or not entirely cloud. We use many hybrid solutions.
We didn't exactly choose this product. It was more a question of legacy. We've just kept using it over time. When I came to the company, they were using it, and we've continued to do so.
I'd rate the solution at a seven out of ten.
In general, based on my little experience with Hyper-V, I see a lot of obstacles. I think it falls behind the other competitors.
There are several areas that can be improved. The network configuration, for example, can be improved. The storage as well, can be improved. I find it very dependent on the active directory as a service, overall. I think they have to review that. I understand that active directory is an integral part of that infrastructure for authentication and logging, etc..., but it can be an obstacle. I think they should review that mechanism.
They have to review the overall architecture of that solution. It is a Type-2 virtualization, which means it is not bare metal. That is one problem or one issue that has to be reviewed. In my view as an engineer, the best solutions in this domain are those which are bare metal. Those that are deployed directly on the hardware get the most out of the hardware. But in Microsoft, this is not the case, it is implemented on Windows. If something goes wrong with the Windows machine, all the VMs on it are in trouble. And we all know that Windows has always been a target for viruses and bugs. So in my opinion, they have to review that, to remove that design.
I don't personally have strong experience with Hyper-V, but as a company we are reselling it.
Based on my experience, it is stable.
It is not that scalable or flexible.
On a scale from one to 5, I would rate the scalability a three.
The initial setup is easy.
I think Microsoft is a little better in pricing. But as I said, I'm not a pricing person, and I can't speak with great confidence on that. But in general, Microsoft is a little lower than BMI.
I do not highly recommend Hyper-V.
On a scale of one to ten, I would rate Hyper-V a six.
In terms of advice to people looking to implement Hyper-V, I would tell them not to rely much on the Hyper-V solution in terms of flexibility and scalability. It is a stable solution, but overall, considering the backup, the replication, and the whole range of features that VMR offers, I think that it's better if they look at VMR or other contenders, in this technology.
We are mainly using Hyper-V in the financial sector.
The ease of use of Hyper-V is the most valuable feature.
Hyper-V could improve the management tools.
I have been using Hyper-V for approximately ten years.
All the newer versions of Hyper-V are stable.
The solution could improve scalability.
The support from Microsoft is very slow.
The initial implementation was difficult because there are not enough management tools. The time it took was approximately three days.
We installed the Hyper-V on bare-metal hardware, created the VMs, and attached the storage, et cetera.
We have four to five staff members for the implementation of Hyper-V. The maintenance includes server management, creating VMs, and backups.
My advice to others implementing this solution is there are no implementation management tools available, they will have to do it all themselves.
I rate Hyper-V a seven out of ten.
Recently while working with a customer that was migrating from Hyper-V 2008 R2 to Hyper-V 2012, I came across an issue where VMs on the original host were having odd intermittent network connectivity issues. As I dug into the problem, I realized that when I ran arp -a on any of the Hyper-V hosts, VMs on the original host were showing up in the ARP cache with a MAC address of the physical host, instead of their virtual MAC address.
As it turned out, it was the drivers for the Broadcom NICs in this particular system. Windows Server 2008 does not support NIC teaming natively, and instead relies on the 3rd party drivers to support teaming. Due to a bug in some versions – possibly all, I have not been able to confirm this as of yet – of the Broadcom drivers, Hyper-V 2008 hosts using a Broadcom teamed interface will advertise the hosts’s MAC address to the physical switch rather than the VM’s virtual MAC.
The workaround was to break the team, and only use one physical interface during the migration to 2012. This resolved the MAC issues, and since Windows/ / Hyper-V 2012 supports native NIC teaming, the issue did not occur on the new hosts.
Disclosure: The company I work for is partners with several vendors - http://www.latisys.com/partners/strategic_partnerships.html
Hyper-V has made great strides since it was first released alongside Windows 2008. If I were a SMB/small enterprise running mostly a Windows shop and looking into virtualization, I would definitely give it a serious look - it can do most everything I would need for a lot less than vSphere. However, vSphere is still the king as far features, specifically when it comes to availability and DR.
That said, the growth of KVM & Openstack and the community surrounding them excite me more than anything coming down the pipe for either Hyper-V or vSphere.
Disclosure: The company I work for is partners with several vendors - http://www.latisys.com/partners/strategic_partnerships.html
But you have all of these features in Hyper-V (like HA, Clustering, Live Migration and others) for free! If you use ESXi you don't have! You have to go to the pay version to get those features!