VMware Workstation Player and Pro are now free for Small Businesses, but Pro used to be paid and quite expensive. There are compatibility issues between those products and Windows hosts, giving that Microsoft has their own hypervisor platform already. Also, if you use Linux, …
Considering the maturity of ESXi, Hyper-V is something I would definitely consider using in future jobs or organisations. We selected Hyper-V after many years of using ESXi; several factors led us to this change, including a poor support experience with VMware, and the lower …
ESXi, to me, seems to do things better in almost every way. It is much quicker to deploy ESXi compared to Hyper-V. I also feel like Hyper-V requires more frequent updates so I'm not sure if that is a good thing or a bad thing.
VMware is the pioneer of virtualization but when you compare it with Hyper-V, VMware lacks the flexibility of hardware customization and configuration options Hyper-V has also GPU virtualization still not adequate for both platforms. VMware has better graphical interface and …
I switched to VMware Workstation Pro, after using Hyper-V for several years. The thing I missed in Hyper-V was the network management which has too less configuration options compared to VMWare Workstation Pro. Also managing the snapshots was more user-friendly in VMWare …
The ease of use and essentially free license made the adoption of Hyper-V in some parts of my current and one of my previous organizations a no-brainer. For sure it's not the best product on the market, but it will do the job just fine in a lot of use cases. Automated …
Though Docker provides cross-platform support and isolation, Hyper-V provides true virtualization over the host OS and creates boundary over guest OS that protects the security threats, resource-hogging on the host OS.
While many have additional features or lower overhead the ease of use and low-cost licensing make Hyper-V our preferred choice for most clients. And because we are mostly a Microsoft shop and it is built on Windows when we need to troubleshoot the hypervisor itself we already …
It is much cheaper and has at least the same functionality as what we use. It integrates better in our Windows environment and it works more familiar with similar tools that we already use. And it is on fewer vendors, much easier for support. Very happy with the switch from …
Overall, VMWare appears to be more full-featured and perhaps a bit more robust, but the integration and no-cost factors of Hyper-V won the day. We have had no issues with Hyper-V since instigating it five years ago and do not regret the decision.
President, Engineering Architect for Virtualization and Computing Systems.
Chose Hyper-V
Hyper-V is much cheaper and does not have the license requirement of VMware. Hyper-V is not a product that scales like VMware and not well suited to a large datacenter.
Hyper-V is well suited for environmental testing purposes. Let's say you want to learn or test a new OS for a product or just for learning purposes. You are able to boot up this os in just a few mins on Hyper-V and then start working, testing, and learning with no money out of …
I used VMware vSphere at another company. However, for infrastructure with only two virtual machines, the VMware license cost is not worth it, because with the Windows Server Standard license you have the possibility to install two virtual servers at no extra cost.
We selected Hyper-V because it was built in to Windows and had no licensing costs. The functionality was similar, VMware seemed like a more premium product, and had support. But those are the bare minimum when competing with an embedded solution. VMware is reported to be …
Hyper-V performs very well in environment running windows operating systems and performs well under various workloads. The replication and recovery features of hyper-v work well but lack some of usability of tools such as Zerto, VMware replication and site recovery manager to …
You already have to purchase the licensing for Windows Servers so why not bundle that in with the cost of the hypervisor. VMware seems to be a better virtualization platform with a better dashboard, but if you aren't managing hundreds of physical servers across multiple data …
We went with Hyper-V since it's backed by Microsoft. Most of our businesses use MS, so going with supported products helps when we need to open a case if we run into issues. There are other alternatives, but the ease and support of Hyper-V make it our go-to product for …
Microsoft's virtualization with Hyper-V has given us a great opportunity to increase the availability of services, thus increasing the satisfaction of our end user. With Microsoft virtualization, we have increased availability as follows:
Hyper-V is not only a free virtualization solution for businesses, but it's also a very stable and very intuitive environment. The learning curve for Hyper-V is very simple and there are a lot of resources online for Hyper-V. VMWare is actually the leader in the virtualization …
Hyper-V is powerful and virtualizes Windows exceptionally well, with less tweaking. It is also cheaper, and allows our clients to budget more for more frequent expansion. Its only real competitor in my opinion is VMware, and that is because vCenter is much more intuitive than …
I really do not have a bunch of experience with VMWare or VirtualBox which I know are two other well-known Virtualization software. I have used VirtualBox a few times when I was in college to learn other operating systems, but I don't recall them being as easy to get going and …
It is really all about application support. The only option we really have is Windows Server, and where we can choose we continue to use it for consistency as well as compatibility with the systems where we are forced to use Windows Server).
We've utilized docker and debian for very specific applications and they have been useful - overall Windows Server provides a better package. I would choose VMware ESXi over Windows Server for virtualization as it's far more reliable in our experience. I can't imagine using a …
There are plenty of other server solutions out there which may be better suited for certain tasks, but Windows Server is the way to get a Windows environment going. For simple setups, there are many alternatives, but often there are key features lacking, or a restriction on …
Windows Server is more cost-effective and skills are easier to find to support the products. The deployment and management of the product can be automated with Microsoft SCCM. In my opinion, Linux seems to be more secured but takes more time and effort to learn than Windows …
These are just very different products. They can all have the same functionality but the specific product knowledge with Linux is much higher. This slows down troubleshooting and can leave you with limited options for high end support. There are absolutely good use cases for …
I didn't use any other system which gives the same functionality and I am not aware of any. The full integration between all components and especially the ability to integrate mail via Exchange or even via a hybrid setup with the Ofice365 cloud, including the ability to …
For our more experienced users and for simple web apps we will go the RHEL route but with Windows Server such an industry standard the the ease of use of the GUI it just makes more sense for most applications that use it. It also generally has a lot more interoperability …
Linux is great, but support is harder to come by. You also need to pay linux admins more as it is a much smaller group of people that can support it. Windows is the industry standard with the most support available. Going with another platform just didn't seem to make sense …
I have some basic experience using various builds of Linux and have always found myself coming back to Windows. Perhaps after years of working with Microsoft products they all have a similar feel and configuration options. Microsoft products are my typical first choice where …
We have various servers or appliances that run on various flavors of Linux that do their jobs well, but we configure and manage them very lightly at the OS level. Most of the admin on these devices is sone inside the applications themselves. We don't shy away from new …
All the other products I have used in the past OS2 servers, Novell Netware, Banyan Vines etc don't show up in the search list, which i guess goes to show that the best wins.
I have used/administered several servers using systems like Ubuntu, Debian, and CentOS. While these systems are great in their own rights, you are typically using a command-line interface or shell in order to administrate the system. This requires a lot of commands to be …
For our purposes it came down to picking between Windows and Linux and at the end of the day we picked both. We use Windows for 80% of our server needs to run our Web, File, Print, DHCP, Internal DNS, Active Directory, SQL, Web and other windows based servers. We use linux …
Windows Server has become one of the industry standards for providing file and directory services for the majority of users because of the ease with which it interacts with the common desktop OS, as opposed to needing to provide esoteric support for users to be able to work …
About any linux distro can be setup to handle services that a Windows Server can do, except I have not personally found anything nearly as convenient of a replacement for Active Directory, Group Policy, or an RD Gateway. There are alternatives to those services, they just …
Windows Server is by far the easiest server option to get started with because they offer the same kind of interface with windows that most users are already familiar with. Plus, it's the most graphically friendly option, so it is easy to navigate. Lastly, it is the most …
We were comparing Windows Server with Hyper-V to VMware ESXI, and decided on Windows Server as we are primarily a Windows server/workstation shop, and the familiarity allowed us to spin up new Hyper-V servers quickly without much additional training required. We also have a …
We have used various flavors of Linux as it is the only other real competitor in the small to large business world. In most cases it is harder to find technical expertise in the Linux server world verse Windows Server. For this reason Windows has remained our go to operating …
Windows runs some applications better and is easier for junior admins and non-technical users to administer and get started with. It obviously does not run everything better, so other operating systems are preferable in some situations. Compared to OSs like RHEL, they both have …
Windows Server is the only one that has an upfront cost for licensing before hardware is considered. Windows Server is generally better suited for multi-faceted approaches; however, for just backups, TrueNAS and Synology are cheaper and just as good. For standalone services …
Windows Server is the most Enterprise/Business server around, easy to deploy and configure and to co-exist with other servers. Most if not every other server technology is usually very good for a very specific purpose but fail in the coexistence and integration when compared …
Because Hyper-V is a Microsoft product and based on Windows OS, creating virtual Windows servers and clients are easy. When we want to test our group policies it it best to do it on hyper-v environment then implement to production clients. The same goes with operating system quality and features updates as well as operating system upgrades.
If you have one user or 1000's of users (especially using Windows), Windows Server is a no-brainer! The only reason I would suggest going with a Linux server is if you have old hardware (Windows Server is more process intensive than Linux). But, Linux is open-source, so anyone can publish updates/security updates, but on the flip side, malicious people also have full access to Linux's codebase allowing for much easier writing of exploitations/viruses/malware/ransomware.
Virtualization - Hyper-V does this well and I feel like it might be the best and easiest software out there to use. I am able to spin up virtual environments very quickly. Hyper-V also has a "quick" add feature where you don't even need to have the OS ISO on your computer and you can choose between Windows 10, Server or Ubuntu.
Setup and Management - Hyper-V is pretty straight forward. When I first started using this it seemed a bit confusing, but after a couple of days of playing with it you end up finding out everything is pretty straight forward and really not that complicated.
Just turn off the VM and go into the settings and you can manage the Storage, Memory, and CPU's.
Setting a VM up on a Domain is super easy and you can create a static mac address for the machine so in Windows DHCP you can use that static mac address to give that VM an IP it can use every time it boots up.
I think the best feature is the ability to create "Checkpoints" - If you are going to be doing something over and over and you need to start from the same point with each test you can setup your VM the way you need it prior to testing. Create a Checkpoint. Do your tests and then revert back to the Checkpoint so the system will be exactly how you had it setup prior to testing. Then you can go on and do your second set of tests and so on.
Another great thing is the ability to just backup the vhdx file.
As I mentioned at the beginning of this review we run most everything from Hyper-V. I make weekly backup of the vhdx files which are the Virtual Environment files.
This is an extreme example, but if the building ever caught on fire I could go out and buy like 15 PCs at Best Buy and load up Hyper-V on them and just import the vhdx files and be back up and running fairly quickly.
User and device management out of the box. Active directory is a proven system for doing this and works just as well as it always has.
ADFS providing integration into many third-party applications using SAML authentication. We use this heavily to make user experience as simple and straightforward as we can.
Local DHCP. It's another one of these systems that is very easy to setup and use out of the box and requires very little maintenance, if any. The system is almost unchanged throughout the years and so anyone with server experience can manage it.
I would love to see Hyper-V add a better remote control feature. As it is, it uses RDP to connect to any VM in the host. This is old technology and slowly deprecating. It would be significantly more useful to have a controlled interface for remoting to the VM's that is much more like Teamviewer, LogMeIn, etc.
Windows Server is extremely complex, and while newer versions have eased the initial setup process, setting up a server is still a very time consuming and difficult task.
The complexity of Windows Server also makes troubleshooting any problems that arise extremely difficult, both in tracking down the actual issue and then resolving the issue. Often times a problem can manifest itself in more than one way, making searching for the specific problem also difficult.
Windows Server is also very expensive, with complex and confusing licensing terms. In fact, Microsoft provides a 32-page PDF guide on Windows Server licensing, which is in and of itself dense and confusing to follow. To make matters more complicated, there multiple different version of Windows Server itself - Nano, Essentials, Standard and Datacenter edition, and each edition has different licensing terms. Licensing terms include items such as the physical processor's cores of the server, how many users will be accessing the server (called a CAL - client access license), and a plethora of other items.
Microsoft's support for Windows Server can be extremely frustrating at times. While Microsoft hosts a very active user forum, Microsoft employees who frequent those forums often provide only stock answers to questions (without actually reading the details) or no answers at all. For more in-depth - phone support can be quite expensive.
Upgrading a Windows Server from one major version to another (i.e. 2012 to 2016) is a frustratingly complex and dangerous procedure, as many things can go wrong during the upgrading, essentially breaking the entire setup. In fact, Microsoft doesn't even suggest doing an in-place upgrade, but to perform a backup of the existing server, doing a clean install of the new version, and migrating the information from the older version to the new version. In general, it is not even recommended to upgrade from one version to another as the risk significantly outweigh the benefits.
Cheap and easy is the name of the game. It has great support, it doesn't require additional licenses, it works the same if it is a cluster or stand-alone, and all the servers can be centrally managed from a system center virtual machine manager server, even when located at remote sites.
I've carefully reviewed the servers and services currently running on Windows Server 2012, and given the opportunity would renew them as is going forward. There are two systems I currently have in place, one is a very large Linux implementation for a large ecommerce site, and one is a very large backup solution front ended by FTP servers running Linux. Neither are well suited for Windows, but the overall network infrastructure is and will be Windows Server for the foreseeable future.
It is very easy to configure new virtual machines and manage them. But you have to use different interfaces to perform various tasks. Especially as soon as it comes to clustering you have to use at least two different interfaces (Hyper-V Manager and Failover-Cluster Manager) to perform all necessary tasks. The newly released Windows Admin Center is a way into the right direction to get all management tasks into one single interface.
Everything can (and should) be done through the easy to use/navigate GUI. There is no need for archaic command prompt use to administer the server. But, it is there if you have very specific needs for batch files, etc. that are not covered in the all extensive GUI.
In the past 2 years our Hyper-V servers have only had a handful of instances where the VM's on them were unreachable and the physical Hyper-V server had to be restarted. One time this was due to a RAM issue with the physical box and was resolved when we stopped using dynamic memory in Hyper-V. The other times were after updates were installed and the physical box was not restarted after the updates were installed.
Hyper-V itself works quickly and rarely gave performance issues but this can be more attributed to the physical server specifications that the actual Hyper-V software in my opinion as Hyper-V technically just utilizes config files such as xml, and a data drive file (VHD, VHDX, etc) to perform its' duties.
Most of the time, you can find support on the thousands of websites, blogs and community sites that are out there. Very much Internet supported, and if you don't stray too far away from the standard setup of Hyper-v, you shouldn't go wrong. I've had to call a couple of times, and Microsoft was very good at resolving my problem. it seem that Microsoft has heard from people and their support system, and are doing a much better job in this
It has been my experience that unless there is a flaw or bug with Microsoft Windows Server, you will have to pay extra for support beyond the support web site. That said, unofficial support on the thousands of technical websites makes self-help support readily available to any technician with an internet connection. Microsoft's support website is also fairly robust, but I find using a popular search engine often returns knowledgebase articles more quickly that Microsoft's search.
We had in person training from a third party and while it was very in depth it was at a beginner's level and by the time we received the training we had advanced past this level so it was monotonous and redundant at that point. It was good training though and would have provided a solid foundation for learning the rest of Hyper-V had I had it from the beginning.
The training was easy to read and find. There were good examples in the training and it is plentiful if you use third party resources also. It is not perfect as sometimes you may have a specific question and have to spend time learning or in the rare case you get an error you might have to research that error code which could have multiple causes.
initial configuration of hyper-v is intuitive to anyone familiar with windows and roles for basic items like single server deployments, storage and basic networking. the majority of the problems were with implementing advanced features like high availability and more complex networking. There is a lot of documentation on how to do it but it is not seamless, even to experienced virtualization professionals.
Make sure that you have detailed processes in place for every server instance you plan to install/upgrade, if possible get the base OS loaded and Windows Updates applied ahead of time, and if using a VM take a snapshot prior to installing each role, as well as along the way.
Considering the maturity of ESXi, Hyper-V is something I would definitely consider using in future jobs or organisations. We selected Hyper-V after many years of using ESXi; several factors led us to this change, including a poor support experience with VMware, and the lower cost of Hyper-V. We looked at other options including Nutanix and Hyper Converged Infrastructure, however with such a busy team we didn't have the time to learn this completely new technology stack, whereas (whilst also new) Hyper-V had a much easier learning curve.
Windows Server is more cost-effective and skills are easier to find to support the products. The deployment and management of the product can be automated with Microsoft SCCM. In my opinion, Linux seems to be more secured but takes more time and effort to learn than Windows Server. However, there are more Windows Server skills available in the job market.
Nothing is perfect but Hyper-V does a great job of showing the necessary data to users to ensure that there is enough resources to perform essential functions. You can also select what fields show on the management console which is helpful for a quick glance. There are notifications that can be set up and if things go unnoticed and a Hyper-V server runs out of a resource it will safely and quickly shut down the VM's it needs to in order to ensure no Hardware failure or unnecessary data loss.