5 hours 8 minutes
kind of main point say
if you're going to be using Hyper V server
or a new copy of Windows Server, you have to remember that it needs to run directly on the hardware. ESO. If you're using a computer system that already has an operating system installed, it will generally need to replace that. Unless, as you notice, there might be some people in the chap who are saying that you can install it
within itself. So you consort hyper V within hyper V.
You wouldn't really want that in Maine environment. It's just usually for testing purposes, but yeah, generally only to replace the operating system on the hardware if you're using an existing installation off Windows server or you'll be enabling
client Hyper V inside an existing installation of Windows 8.1, Windows 10.
it's like *** like point. Microsoft stopped Windows eight from having this functionality because they wanted people to move to 8.1. So if you haven't moved to 8.1, you may actually have lost the capability to use client hyper V. You need to move from 8 to 8.1. If you do want to use it in that environment,
I don't believe they actually support with those eight
job. Ooh, Yes, Absolutely so old you're bolting. Would do Just go is it allows you to pick up on
effectively When your boot sector kicks in, it will allow you to pick up which one you'd like to load and effectively. You're loading the operating system that's handling that environment. If you've got hyper V server or Windows Server installed, you can basically just say what I want. I want the hyper visa that a load on dhe set itself as the type one hyper visor
between the hardware and the software environment.
So, yes, you could do a boot in a professional environment. I wouldn't generally use that. I've not used it at all. Actually, in my in my professional career, I've done dual booting out hope with if I have, like, a Lennox environment and then I want a hyper V set up later on.
But that being said Lennox is actually supported in hyper V now as well. Microsoft have done huge strides to support
third party operating systems within their hyper V system on Dad, actually, recently on the news they actually said that they had been open sourced over because we're over 40,000 intellectual property, I p. Infringe like copyrights that they just opened up. So there's been quite a push towards
getting different operating systems toe work with hyper the general
with existing installations
you would need the replacement generally will be seamless, and you tend to lose no files or settings. However, a big one on this for Windows Server enabling the hyper V inside and in sick existence session replacement will be seamless. As we mentioned, however,
any sleep modes will be disabled for window service Here. You can't put
your Windows server to sleep if hyper V is set up on it
on Dhe. That's something that some people might be, you know they might want. Especially if, like there's a business that's looking to reduce its carbon footprint or anything along those lines as well.
So carry on with the hardware. So the minimum requirements for hyper V server they pretty much close to Windows Server itself. Your heart, your hardware needs to have the following. Okay, so I'm just gonna list these out on the screen here. We can go through them a little bit,
so at least have 1.4 gigahertz. 64 bit process. Er s o I would hope everyone is using 64 bit processes these days. If you're no, you're really missing out. They are much, much more powerful. The technology is tremendous. Now it needs half a gig of RAM. So not a lot. All
And it needs about 1st 2 gig of hard disk space.
That being said,
that's the minimum. I generally wouldn't recommend that you run a hyper V server on this environment.
It also needs data execution prevention. So what, these are is
Oh, I miss those parts out. I do. Apologise s o. I'm supposed to put them in there. I don't know why they're where they've gone. S O data execution prevention allows the
The baby is one of my pre next boys. Look, here
it is. I do apologize. You know what? I actually I mis titled this so it shouldn't have said detail on this one. It should have just said the date or execution. Regine, I got confused. I do apologize. So data execution prevention. We're gonna go through those two that just sits explained below. They're supposed to be a line below each one, but that's me. So
the system, as I said, the system needs to support data execution prevention.
It is very rare for current systems to not support these features, but different systems will refer to them by different names. So you'll find the settings in the computers by us or you e F I u Effie configuration.
If you guys have got a machine that's happened in the last few years, you'll notice that the BIOS doesn't exist anymore.
It's called a unified extensible firmware interface. It means that you can have a mouse pointer in there, and it's very swanky, and you've got graphs and things that show you what's going on in the machine. And it's all real time. Rather than just worrying about using your kind of arrow keys on your keyboard and pressing into enough to
the old style stuff, which is very much close to a command problem.
you will find that data execution prevention in some motherboards, whether it's you Effie or in bios, they will actually refer to it as either no execute or an ex or executed Prevention x d. Now you think, where's the pea its its execution denial. But for whatever reason, they figured that
execution prevention should be ex D.
Don't ask me.
I don't make this stuff up.
So the hardware virtualization setting is usually easily recognized as well. If you're not certain, please do check with the manufacturer of the motherboard. They should be able to give you guidance on on where it is now.
Day to execution prevention itself or depth.
It's a security feature, so it helps prevent damage to your computer from viruses and other security threats out there Effectively. What it does is when a program tries to attack your Windows environment on Dhe tries to execute code.
What it will do is it. The program tries to execute code inside the memory locations that are primarily reserved for Windows and other kind of high level authorized programs.
If it can run code in that memory location, chances are Windows will try and access it, and then it affects the operating system.
S O D p. What it does is it sits there and says, Hey, these areas here, they're off limits. It's kind of like a bouncer at a club. Your name is not on the list. You're not coming in now. You can add programs to that list. Say, I don't mind if they do that. But generally in day to day environments, you don't really need thio. Add anything to it.
So that's what that's what DP gets involved with on that side of things.