It's scalable and stable. Working on Hyper-V is a wonderful experience. It supports our systems in parallel, providing us results that meet our needs. Moreover, providing more and more new features everyday such as Live Migration, CSV and so on.
Also, assigning physical NICs to each VM is wonderful with Hyper-V, as it distributes load and performs well. Otherwise, all VMs bottleneck to a virtual switch which is bound to just one physical NIC.
The main improvement to our organization is its scalability and the ability to support our system by running our applications simultaneously. It ultimately helps us with customer satisfactions and productivity, Failover clustering is another amazing benefit to my organization as we have dramatically reduced the downtime.
The networking component of the setup needs to be less complex.I have one physical server with four built in LAN ports (NIC1, NIC2, NIC3 & NIC4) and I want three more VMs on it. In order to distribute the traffic load, I want to assign one NIC to each VM with one for the physical server. This means whenever L needs remote access for management purpose it will utilize NIC4, but this needs to be simpler to setup.
I've used it for more than two years.
We have four physical cards in a Poweredge R710 server with three VMs on it. We have assigned one NIC to each VM, with one for management purposes and remote access.
Initially we were using only one NIC for all VMs, physical servers, and for remote purposes as well. After assigning one NIC to each machine, the performance improved and is now excellent and reliable.
We've scaled sufficiently.
8/10
Technical Support:8/10
The initial setup and configuration is not too complex, but completing the networking part is a bit complex.
All implementation was done in-house.
You should evaluate this product as it’s very easy to manage.
Sorry I have not had time to comment, I stay rather busy at my job and studies.
First, a little about my background.
I've only been in the IT field professionally for almost 2 years as of this comment. I graduated in May of 2013 with two Associate Degrees; Computer Network Management and Computer Network Engineering. I obtained my role of a Technical Support Specialist back in April of 2014, I started out with basic help desk support and quickly got thrown into the deep end of server management, virtualization, networking, and SAN technologies without warning or support. I may not be very experienced by most tech standards, but I certainly have a talent and aptitude for this career path. I have quite a few experienced techs who will attest to my abilities. My company's IT department consists of me and my boss. My boss handles high level infrastructure needs and planning where as my jobs consists of everything under the sun any my job constantly pushes my boundaries of experience.
I use Hyper-V at home to basically study for MCSA/MCSE certifications. I setup an AD infrastructure, DHCP, DNS, WDS, NPS, RRAS, as well as many other services and I have a virtual machine just for VPN connections to my office. I constantly use snapshots to test new services and I have a base VM that I exported and I copy when I need to setup a new one.
I was asked to write a review on Hyper-V so I did. I work with many software developers and I have turned them on to Hyper-V for home use on several occasions and have yet to hear anything bad about it. I do have a preference to VMware ESX and if asked to write a review on that, I would sing it praises. But as for Hyper-V goes, I think that it is viable alternative to VMware and best suited for home or small to medium business use, larger business could also use and would be complimented very well with the whole SCCM application suite.