- [Instructor] The first thing you need to do
is enable Hyper-V because it's disabled by defaults.
And this is an 8.1 Pro System,
so what we're gonna do is
we're gonna go to the Control Panel,
Programs and Features,
and turn Windows features on or off,
and here we see Hyper-V.
And if we hit the plus sign,
you'll see we have Hyper-V management tools,
and you see Hyper-V Platform is grayed out.
And the reason is because
Virtualization Support is disabled in the firmware.
And so that needs to be turned on
in the BIOS or UEFI before we can actually use this.
So we'll go ahead and make that change in the UEFI,
so that we can use the Hyper-V Platform.
So we're in the BIOS of the AV Editor Computer,
and this is the ASUS UEFI BIOS utility.
We've shown this previously in the 901 course,
and here we are again.
We need to enable Intel virtualization,
so we're gonna go to Advanced Mode
down here on the bottom right,
we'll go to Advanced and we want CPU Configuration.
So click on that, and we'll scroll down
to Intel Virtualization Technology,
and you can see it's disabled,
and on some other boards it is disabled by default.
So I'm gonna click on that, enable it,
and we're going to exit outta here,
and save the changes and reset the system.
And it tells you the change you made.
Intel Virtualization Technology went
from disabled to enabled.
And that's what we want so that we can run Hyper-V properly,
the Hyper-V Platform.
So click, okay.
That'll reboot the system
and we'll jump back over to Windows and install Hyper-V.
So we booted back into Windows.
We're in the Control Panel
go back to Programs and Features,
turn Windows features on or off,
Hyper-V hit the plus sign for that,
and you'll see that this is no longer grayed out.
Hyper-V Platform,
we're good to go, 'cause we enabled it in the BIOS.
Now in some cases you have to enable
those separate extensions, all those VT extensions,
but with our ASUS BIOS and a lot of the new UEFI systems,
you just enable Virtualization
and they make it easy for you.
And then the Hyper-V platform is enabled.
So we got it.
We're gonna click okay,
and go through the installation for that,
and restart the system.
So Windows 8 restarted a couple times,
and now we're back in the system.
I remoted into the computer here,
and we're gonna go to our Hyper-V Manager.
So we're gonna go to the Control Panel
and Administrative Tools and I go to Administrative Tools
a lot, and so quite often I'll right click this
and pin it to start.
So that's here permanently.
So click that now and you'll see we have the Hyper-V Manager
here and double click that to open him up.
And it says no virtual machines were found that's
'cause I haven't created any yet.
The great thing about this program is you can work
with multiple computers.
You can connect to other systems that also have
Hyper-V running and create virtual machines
on any of those systems.
Now, before you do create a new virtual machine
you're gonna wanna have a networking connection.
By default, you won't have a networking connection
out to the physical network.
You'll have networking connections
to other virtual machines, but not to the physical network.
So if you want that chances are you will,
for what you're doing.
If you're doing studying, you want to go
to the Virtual Switch Manager and then set up
a new virtual switch and you'll want an external one
and that'll bind the network adapter of this system
to the virtual machine.
So you can actually get to the physical network,
access the internet and so on.
So you may wanna create a virtual switch first,
once that's done, you'll go to your computer
AV Editor in this case.
Right click it and go to New and Virtual Machine.
That'll bring up the virtual machine wizard
we'll click next.
You name it.
You select which generation you want.
Generation one will allow it to work with any versions
of Hyper-V, generation two takes additional functionality
into accounts, such as secure boot, PXC boot
and things like that.
So I'm gonna use generation two
but you have to be careful with that
'cause you can't change the generation
once you create the system.
Once you create the virtual machine.
So you may want generation one for your purposes.
And click next, you set the memory.
We might want 2048 or two gig click next.
And then you see that virtual machine network
adapter setting, it's not connected because we didn't
set up the virtual switch yet.
Now this gets more into the Microsoft side of things
and isn't as important to know exactly step by step
for the exam.
But you get an idea here.
You want to have a networking connection, usually
click next, create your virtual disc.
In this case, it's a VHDX.
And we'll just leave it as a default click next.
And we'll say install an operating system later
but you could do this from an image file, from an ISO file
which could be on your hard drive.
This way you really don't have to deal
with any discs at all, which is beautiful.
And click finish, that configures that guy
and it shows our new virtual machine, which again
we could call this whatever we want
and we could even change the name now.
And then to run this guy,
you could double click him and then run him from there
or you could go to Action and go to Start.
So this guy is running
and then to see it, we double click on it
and you'll see it here.
So you could have it running in the background
without actually seeing it on the screen,
which is a beautiful thing
especially if you're gonna run servers
or systems that are storing data
or have media files or whatever databases.
This way it runs more in the background.
Now, remember this is Hyper V for Windows 8.
So it's running within the OS.
It is not a Type 1 hypervisor.
If you want to Type 1 bare bones hypervisor,
a true to form Type 1, you have to run it on server
and you have to set up the server properly
to make that happen.
You have to set it up as a Hyper-V System
from the get go when you install server.
So that's important.
If you wanna run a Type 1, it's gotta be installed correctly
regardless of what software you're using.
When you're in Windows 8, Windows 8.1 or newer,
you're running it as a Type 2.
So let's show a little bit of that.
The server side for virtualization is not really
that important for the A+ exam.
They're concerned with the client side virtualization
but I figured I'd just show this real fast
'cause I have two different types running here.
I've got a Windows Server 2012 here,
and if we scroll down we'll see
it's an active directory domain services box.
That means it's a domain controller.
Runs DHCP runs DNS, it's a file server and it runs Hyper-V.
So this is Hyper-V for server.
However, this is running as a role
as a service on the server.
So you have to differentiate that
with a true bare metal Type 1 Hyper-V.
So let's take a look at it though.
Let's go to Tools and we'll go down to Hyper-V Manager
and you can see here it shows
pretty much the same type of thing.
Here's the name of the computer
and here's the virtual machines that we have in there.
Kali Linux, another Server 2012 that runs virtually
and Windows 7 which is actually running right now.
And you know what?
That's gonna use up a lot of resources.
So I'm actually going to turn that off
so that it's not using those resources right now.
And I mentioned a virtual switch,
here we have our Virtual Switch Manager.
If we click on that you'll see we have
a virtual switch right now
which is acting as external network
which means our virtual machines that use this switch
can go out to the external network
but we can have multiple switches.
We could create another switch
one that's internal where the virtual machines
can communicate with each other and with the host computer
but not outside of that.
And then private where the virtual machines
can only communicate with each other.
So more security as you go down the line here.
And it's pretty cool 'cause you can have
multiple virtual switches.
So there's an example of Hyper-V running
in server effectively, it works the same way.
A little bit more powerful, little bit more capability
but effectively the same as one that runs
in Windows 7 or 8.1 or Windows 10 or what have you.
Now, if we go back to VMware workstation
just to confuse the issue a little bit more,
here is windows, this is my Windows 10 computer I'm in
and inside that I'm running VMware workstation
and inside of that we have Hyper-V bare bones.
This is the bare bones version.
So to get into this you have to unlock it first
and type in the password.
Two windows there, a little tight here
but it's a menu driven system.
It's a menu driven system and you'd go through these
to work with the system and to create new machines.
And you could do it directly
within the command line as well.
So you get those two windows that are running here
but there's really no gooey to speak of.
It's bare bones.
That's what you wanna run if you wanna have
a true Type 1 hypervisor, the bare bones version of Hyper-V.
And that's separate altogether in the Server 2012
that I have, this is one of the roles.
It's only one of the roles within the server.
So you're not gonna get nearly the effectiveness
in this as you would with a bare bones.
Now, of course, this is running as a virtual machine.
That's just so I could show it to you
'cause it's a little tougher to show on an actual system
but this is what you would install to an actual system.
And this way you don't have all that overhead of the gooey.
And there's an example of a true Type 1
virtualization system.
So a little bit about all kinds of virtualization out there.
And a lot of times my go-to tool, VMware Workstation
'cause I can run all this stuff in there
and really concentrate on the client side stuff
for the A+ exam.
That means working with Virtual Machine software from VMware
also Hyper-V for Windows 7, Windows 8.1, Windows 10
and also Virtual Box.
So check those out, practice working with virtualization
and that's about it for this sub lesson.