As I began to look at HyperV in depth, it became apparent that there is a rather steep learning curve. As the advertising slogan goes, “If you can read this and use it, then you need HyperV”, well I can now add “if you can’t read this and don’t use it, then you are really missing out!” If you find yourself on that short list, I suggest you take the advice of the best-selling author of “HyperV Windows 2020 Installation Guide”.
The best HyperV Windows 2020 Installation Guide will give you a sneak preview
of what will be coming in the second part of this series; that is where I will discuss things you should be aware of before you begin any kind of HyperV project. For those of you who have never had to do a HyperV deployment before, I will describe some of the things you should know before you start on your journey.
First off, HyperV allows for multiple domain controllers per forest. Your example in part one of this series will not work if you have more than one domain controller. In addition, HyperV will require that you use the domain functional level (DFRL) virtualization so that you can access the VDI, Virtual Hard Disk (VHD), and Hyper-V Manager screens. To get this working you will need to create a DFS Namespace in each domain that meets the necessary requirements.
It is not hard to get HyperV working if you already have vSphere installed on your computer. You just need to create the vmware/hyperv.Conf file and give it the proper permissions. You will also need to make sure that the hostname is set correctly and you have connected to your vCenter Server and logged in. Once that is done, you can begin building the Hyper-V hosts.
Hyper-V is also not going to work without virtualization. When building a Hyper-V cluster, you must determine whether or not you want to use a pool for each physical machine that you want to share your storage. Hyper-V also requires that you select the virtualization type and the type of disk and LUN on which the virtual machine will run.
Finally, there are some pitfalls that can be associated with Hyper-V. One is that it is not easy to manage the network. There are many issues such as lost of domain controllers and the fact that Hyper-V is not supported by Microsoft Exchange Server for mail-boxes.
Even if you have Exchange running on your machines, that does not mean that you have managed it properly.
You must keep up to date the mailbox content and the schema and you will need a great deal of patience and knowledge.
Another pitfall of Hyper-V is that the best way to get it working is by using IIS (Internet Information Services). This will not work properly without the correct version of PHP, JSP, or HTML.
By the time you reach this point in the Hyper-V guide, you will be able to download and install the necessary software packages and have a working environment. You can now decide what it is that you want to do next.
If you decide that you would like to get started in managing your Hyper-V deployment, you can use these Hyper-V tools and systems. There are both Windows-based tools and third party ones that you can use to manage Hyper-V and you can also share your existing information.
For example, when I first used Hyper-V with my company, I was not familiar with DNS and managed DNS was something that I did not know how to do.
- So I turned to the best selling Hyper-V Windows 2020 Installation Guide and learned all about DNS.
- Hopefully you will find the series of articles to be of use to you.
- In future articles I will discuss management, application integration, and how to take your Windows-based Hyper-V deployments to the next level.