3.10 Virtual Machine, Network, Hard Disk Creation Part 10

Video Activity
Join over 3 million cybersecurity professionals advancing their career
Sign up with
Required fields are marked with an *

Already have an account? Sign In »

5 hours 8 minutes
Video Transcription
Obviously I have it on my machine already because that's how I got to demonstrate stuff to you with networks. But I'm gonna show you how you go about doing it yourself. So whenever you see this play button, it means we're gonna actually demonstrate something. So all you would do
open up your start menu. Whatever you have running Windows
one, Windows 10
make sure it's professional or higher home. Unfortunate doesn't have this. And all you would do nice and simple,
like the word optional features all one word, no space,
whatever case sensitivity you like. And it will pop up on here with the best match,
and then all you do is just click on it or presente,
and this will pop up the turn Windows features on off
system. You could also get to this through the control panel. This is just way, way quicker. And
once you know this way, it's like, Why bother going through six different screens to get to the same point
and you can see straightaway? It's listed here. Hyper V provides service is of management tools for creating and running virtual machines, and their resource is
so all you would do. If you were installing this is put a tick in that box. Click OK, it will say it needs to reboot
and then you reboot. And then when you come back, you're good to go. It's It's literally that simple. There's nothing more to it. It will find the right files.
It will configure everything for you, and then you just basically restarting machine and you're up and running. And if you do want to expand it to see what else is going on there, you can see the underneath. It's got the management tools. So these air the graphical interface on the command line, tools for dealing with it
and then the platform itself. So these are the actual service is that run the background stuff? So you got the hyper visor on Ben. The service is in the background that run things for you. While you're maybe not dealing with things
on under the heart management tools, you got your GeoEye tools and the module for power shell. So if you guys, if any of you are power shell maestros,
I'm still years into power shell and I don't consider myself a maestro, but I'm sure there are people out there
millions of times better than I am,
Then you might prefer power shell on. That's that's where you do it. So you make sure all of these attacks from there down
and then just like, Okay, it will reboot the machine. I will ask you to reboot the machine. It want to do it for you, and then you just carry on from there, come back in, and then you would carry on.
All right, so that's nice and easy. That one.
Let's go on to creating a virtual switch.
All right, So once you come back on and you've got your machine up and running, just do a search for hyper V Manager, as you can see here,
click on that. And then that Load up the manager itself. Oh, I actually have to open. I'm gonna get rid of one. There we go.
All right. And you'll get this screen.
All right. So what I'm gonna do is I'm actually gonna show it to you without machines. So we're gonna delete those machines. Off they go. You see how simple it is to actually manage machines? You you delete them like a file. Basically because that's what they are like we've discussed in previous episodes. So from here,
we're gonna create a virtual switch. So you make sure that your servers selected on the left hand side and you can either choose virtual switch manager on the right or you could just directly right click on the server here and choose virtual switch manager
That will bring up your virtual switch manager environment, which we've already seen here. We're gonna go ahead on Let's just say we don't wanna make another external one because we've got a default switch which comes with it. Let's make an internal network so that we can talk with our machine to the V M on back and forth as well.
We're gonna hit, create virtual switch. We're gonna name it. So I'm just gonna name it Internal Network.
Nice and simple. You can add any notes. This is quite handy if you're doing building networks where you want to know who's on what network rather than going off from going Oh, that machine's connected to it. Or is it that one? Is it the other one? You could just make it put the names of the virtual machines on here makes it nice and simple, but you would use it for anything that you like. Basically
down here, you can actually switch between them. So I think Eric was the person who said that you cannot change it. You just come in here and go. I don't want it to be internal anymore. I want it to be external or prime,
and you just choose it quick, okay? And it just makes a change for you.
If you did have external, you would be able to hear pick the network adapter that it's going to connect to the physical. Nick. Remember how we explain how it will turn the management operating system into a virtual nick? And then
it will then put it alongside all the V EMS, and then they will connect to this switch. And then this switch connects to the physical nick. And then that physical Nick connects to the rest of your network.
Bit convoluted. But hopefully you followed that. It's can be a bit to get around,
And then you've got the tick box underneath that says aloud management operating system to share this network a doctor.
So it just means that you're You're saying that I don't mind
that the management operating system will receive its own virtual Nick from this.
A word of warning. When you do this, you will experience a brief disconnect on your management operating system because it's literally removing its current connection and rebuilding a new one in its place. So just keep that in mind. You might If you're running something while you're doing this like a transfer, it might get interrupted. In fact, it it will get interrupted.
So because lots of things change when you do it.
So we're gonna do internal. We're gonna click internal. We could if we wanted to enable the virtual land identification for management. We're not gonna do it because, well, we're not. We don't really have more than one network at the moment, but this is where you would put your number if you want.
As I mentioned, some people prefer to go up in
in tens. But literally any number do doesn't really matter.
We're gonna turn that off for the moment
and that's it. That's is easy. Is it? You click. Okay,
It's gonna go along, make a few changes, and that's it. When the box disappears. It's ready to go. If we go back into a virtual switch manager, Here's our internal network. We can go in. You can see networks extensions underneath. Discussed these already. If we need to forward data or filter it, look at what's coming through. If you got packet capture, they allow me to
engaged the extensions here.
Global Network settings. This option here basically means that you could define the range off the Mac addresses that can be assigned to virtual network adapters.
Generally, you wouldn't touch this
unless you're going into masses and masses of the EMS, or you have a specific range that you want to use for your Mac addresses.
But this is where you would change it if you do need to do that for whatever reason,
so yet this is where we've got our internal network set up.
So that's nice and easy. That's literally what it takes to create a virtual switch.
Nice and simple. As I said, if you build an external switch, you might find that you will get disconnected while it's occurring, but that's absolutely normal and fully expected.
All right, so
Up Next