- [Dave] Hey, Dave here.
Let's talk about some types of virtualization software.
Previously, we shared Virtual Box,
which is a nice program, it's free,
but I wanna show some others.
VMWare Workstation and also HyperV.
So VMWare Workstation, I use this a lot,
and you can see I have a lot of virtual machines
inside of here,
and it works great for testing purposes, for customers,
and also for training purposes
whenever I'm doing webinars or that kinda thing,
and just for learning purposes.
So let's take a look at one of these.
This is a Windows 10 virtual machine,
and you can see we have basically a snapshot here.
It's frozen in time,
and that's the great thing about it.
You can power down virtual machines
but you can also suspend them at a specific point,
wherever you're working at,
and then resume them when you're ready.
So this is suspended right now.
Let's look at some of the details.
I've associated eight gigabytes of memory for this
because Windows 10 is pretty powerful.
Especially when it runs as a virtual machine.
My hosting system is a Core i7 with 32 gigs of RAM
and so, I can afford to give a little bit more memory
and also more processors.
One processor with one core is not really enough
for something like Windows 10 Pro to run as a VM,
so I have six here,
and you can see I have 60 gigabytes for the hard disk space.
Now again, the beauty of virtual machines
is they only use what they need
and it can go as high as 60 gigs
but it's not nearly that much.
Right now I think it's about a gig that's being used.
The network connection is NAT, Network Address Translation,
so this virtual machine gets an IP on the internal network
which is decided on by VM Workstation
and you can set that as well
and it also has a connection to the external world via NAT
so you get a little protection there.
And more information.
So, lots of stuff you can configure
when you're working with a virtual machine,
and what I wanna do is I wanna start this guy back up
but we're not going to be able to.
There's gonna be a little bit of a conflict
and let me show what I mean.
Let's click on Resume This Virtual Machine.
And it tells us, "VMware Workstation
"and Device/Credential Guard are not compatible."
So we can't run this VM until we fix this problem.
What is the real problem?
I enabled HyperV previously
so I could show that in another video.
And the two basically,
quite often, virtualization software
from different manufacturers don't play well.
They don't wanna coexist or cohabitate.
So, we're gonna have to disable that
and on this system, I use VMware workstation the most
so it's gonna do that anyway,
but I just wanted to show this because
the troubleshooting section of the A Plus
doesn't really get into virtualization very much.
And this is a sort of common error that you'll see.
So I just wanted to show this.
A little bit of troubleshooting for this.
So this is a problem with a Windows service
but it's really HyperV based.
And to fix that, we could do one of two things.
We can disable this particular policy
for the Credential Guard,
or we could disable HyperV altogether
which is what I'm gonna ultimately do.
But to disable the policy, what we do
is we go to our local group policy editor
with a GP edit.msc,
and if I haven't shown that before,
you can just go to your Run prompt
and do a gpedit.msc.
That brings up the local group policy editor,
and then we'd go to the Computer Configuration,
Administrative Templates, System, and Device Guard.
And then here's the policy.
Turn On Virtualization Based Security
which is enabled right now.
If we double-click that and bring up the policy,
we'll see that it's enabled.
Now in some cases, this might not be configured.
And the only way to fix the problem
is to disbale HyperV altogether.
In other cases, you'd have to disable it here.
Then you can see here it says,
"Virtualization Based Security
uses the Windows Hypervisor
"to provide support for security services."
And that means HyperV.
So a little bit of a conflict between HyperV and VMware
which, and you can understand why that would happen
quite often between two companies.
So again, one of the things we could do
is we could disable here, apply it, and click OK.
The other option is to disable HyperV altogether.
And to do that, we bring up the Run prompt again,
go into the Control Panel.
That's Control.
All Control Panel items, programs and features,
and then go to Turn Windows Features On or Off.
And here we have HyperV.
So I'm gonna deselect that, click OK,
and that's gonna need to pull files out,
it's gonna need to turn things off, turn services off
that HyperV controls,
including things like things that connect
with Windows Defender and Credential Guard and so on
and then we'll have to reboot.
So I'm gonna reboot the computer and be back in just a bit.
Okay, I've restarted the system
and actually, it was a double restart
to get all the HyperV stuff uninstalled,
and so we're back here now
and started everything back up
and we've got VMware Workstation backed up here.
So, we're back in the Windows 10 Virtual Machine
that I've created,
and so let's resume it now.
And (mimics fanfare)
our troubleshooting techniques appear to have worked
and so again, you either have to shut down
that Credential Guard or shut down HyperV all together
to make VMware Workstation work once again.
And you'll get this kinda thing back and forth.
You know, be ready for conflicts between these systems.
Okay, and so here is Windows 10.
I got other stuff on it too, Windows Server 2016,
and Windows 7 Ultimate and various versions of Linux
and blah, blah, blah.
So let's just take a look at one real quick
and we can maximize the screen for this
and we'll log in.
All right, and here it is, Windows 10.
And you can see my IP here.
And this is the internal network, 192.168.4,
that I've created within VMware.
So we're using this but we're utilizing that
to get out through the computer's main network adapter.
Now if I go to my main system, this is my main system,
and if we do an IP config for that,
you'll see the main IPs I'm using to get out.
They're on completely different networks.
So network address translation's happening
between those, between the two of those.
To create a new one,
we just go to File, New Virtual Machine, or do it here,
then actually version 15 is out.
Now there's a cost involved with Workstation Pro
but 15 is out.
I'll be upgrading to that one soon as I'm done
with this video series.
But we'll go to Custom and just go through this real quick.
You can choose hardware compatibility
with various different systems.
For example, you can do it for just Workstation
or you can do it for any XXI server,
which, I'm building one of these
and we'll show more of that in other videos,
but I'm just gonna leave it as Workstation 14 right now.
Click Next.
We'll say we'll install it from a disk image.
Now we've got a Windows 10 image here,
so we'll just show that.
We're not gonna go through the whole thing,
but look at the different options of things
that you could install.
We'll leave it as Windows 10, click Next,
and now you wanna browse to where this guy's gonna go.
Now by default, it wants to put it in
a virtual machine's folder in your C drive
within your user profile, but I don't want that.
I wanna go down to my Media folder,
my Media drive, I should say
'cause this is an M.2 drive.
And then inside here, I have a VMware folder
and that's where all my VMware virtual machines
are located.
Better to keep this on something fast.
Now a regular solid state drive is fine.
That's what the C drive is, but the faster the better.
We'll make a new folder in here.
We'll just call this test.
And we'll bring that up, click OK.
That's gonna be our location
where this will be stored to.
Click next.
Then it says what type of firmware are you gonna be using?
Well for older systems,
if for some reason you wanted to install say Windows XP
or an older version of Linux or DOS or who knows what
you'd select BIOS.
But generally, you're gonna select UEFI.
Okay and you may wanna select Secure Boot as well.
Click Next.
Then we select the number of processors.
Now that can be one, two, four, eight, 16,
but that could really bog down the system.
Generally what I'll do
is I'll select X amount of cores to use
and quite often what I'll do is I'll say
okay, what does this system actually have?
This system has a hex core.
It's a core i7 with six cores.
So I might choose to go with six or half that to three.
But you actually saw that I was using six
on this other Windows 10 VM before.
So I'll select that.
It actually does run pretty well.
Then you wanna select how much memory you're gonna use.
Now, two gigabyte, that might not be enough.
And I've got 32 gig available on the physical system,
so eight gig is probably gonna be good enough.
8,192 megabytes.
Click Next for that.
Then you have to select a networking connection.
You can use bridged networking
but this can really be a security vulnerability
because what happens here is this guest virtual machine
has to get its own IP address
on the local area network.
You know, meaning here's my main network, 192.168.41.
They would have to get an IP on that network directly.
So this is like a direct connection to the land
and so there's no separation,
and so that could be a security risk
when we go directly to the security network.
So generally and the default is to use NAT.
And it would get an IP on the IP network
that Workstation has selected, 192.168.4
and you can change that again with the virtual switch,
with the virtual networking section in this program.
You can also use host-only networking
which means that the virtual machines within here
can talk to each other but they can't go out
to the external network
or if you have some really confidential stuff,
you could select do not use the network connection at all.
So, I'm gonna leave it as NAT, click Next.
Then you can select how this is gonna connect,
the recommended virtual method is SAS as a SCSI controller.
So I'll leave it as that.
But you can change to disk type.
Generally, SCSI is the one that's recommended
because it's robust.
Now I'll create a new virtual disk for this.
Now you could use a physical disk too
to get direct access to the local hard drive
and in that way, it kind of acts like a Type 1 hypervisor.
Not that big of a deal,
but it can be if you have an M.2 drive
but I found that it works fairly well
just doing it as a virtual disk.
Okay so we'll do that
and we'll leave it as the default 60 gig, click Next,
OK, and that vmdk, the initial one,
we have to specify where that's gonna go,
and 'cause by default, that's gonna put it in the documents.
We don't want that.
We want it to be in the same place as our virtual machine.
So VMware\test save.
And Next.
And there is our detail.
So we wanna make sure you go through this.
You can customize the virtual hardware.
There's lots you can do here.
Very in-depth.
We'll click Finish,
and that'll create our new Windows 10 virtual machine.
Now there's nothing there yet.
We would have to power it on
and start that install from that iso file
or we'd have to make use of a premade virtual machine file.
That's the basics for that
and we can always edit these virtual machine settings.
That's the beauty of this.
You can edit, if it doesn't seem to be performing that well,
you can increase the processor cores
or the processors themselves,
or the amount of memory that it might need,
or decrease it if you think you don't need that much
and you're gonna have a lot of virtual machines
running here.
You could change the type of network connection
and if we go to the advanced section,
you could make additional changes here.
You could throttle it, and so on,
so if you need to have a direct connection,
you can change that here.
But I'm gonna cancel out, not gonna make any changes.
We can also go to Edit and the Virtual Networking Editor.
Okay, this is your virtual networking,
and you can add additional networks if you wish,
the default that we had here was 192.168.213,
and that creates a separate virtual network adapter
that we saw on this system, VMnet1.
There it is.
And on the actual physical system
with the actual operating system,
and then we have this one
which is Network Address Translation, 192.168.4.0
and that's what I'm using for all the main VMs.
But we could do more, we could change it,
and we could create additional networks.
You have to have administrative privileges to do so
but you can modify all that here,
and that's kind of like configuring the virtual switch
or switches in HyperV.
It's the same type of thing.
So there you go, little bit of VMware Workstation
got everything running here,
got Windows 10 running in here, Windows Server,
Windows 7, Ubuntu, Kali Linux for testing.
All kinds of good stuff.