
The routing VM would be represented in that image as the Dual-Presence VM. This is the same image that I used in that article: If you’re not clear on how this would work, you can refer to one of our articles on the Hyper-V virtual switch. Because we’re talking about isolation using a Hyper-V internal or private switch, such software would need to be inside a virtual machine on the same Hyper-V host as the isolated guests. For most small, and even many medium-sized organizations, this is an unwelcome burden not only in terms of financial expense, but also in training/education and maintenance.Ī simpler solution that’s more suited to smaller and less complicated networks is software routing. The biggest buzzword-friendly solution today is network virtualization, but that currently requires additional software (usually System Center VMM) and a not-unsubstantial degree of additional know-how. There are a few ways to facilitate this sort of connection. Oftentimes, these isolated guests still need some measure of access to the outside world, or they at least need to have access to a system that can perform such access on their behalf. Like any security measure, this can be a double-edged sword. This grants them a layer of protection that’s nearly unparalleled. Now you must include/select this file as the virtual hard disk/ medium file as shown in the answers above.One of the great things about the Hyper-V virtual switch is that it can be used to very effectively isolate your virtual machines from the physical network. This file is also used if you actually want to install the particular OS on your PC/laptop. This file can be found on the website of the OS you want, and must be downloaded. An external file called the ISO or system image file is needed.This is the "bootable medium " referenced above. When you install VirtualBox, it does not automatically come with the ability to run all the listed operatings systems (as I used to think ).

So I will try to answer it as simply as possible, for anyone in my position :. Primarily because Ubuntu had been installed on my PC by a friend, and I had zero experience there. I remember it taking me a while even after reading them.


Although I have accepted the answers above, I realize that from the point of view of a complete noob to linux and operating systems in general, the concept of images ,ISO files etc is still confusing.
