Pass Microsoft Desktop MD-101 Exam in First Attempt Easily

Introduction

1. (BONUS)A Foundation of Active Directory Domains

So I want to start out by doing a drawing to help everybody understand some of the fundamentals of where the industry was, where it is, and kind of where things are flowing right now, especially from the standpoint of Microsoft. So I want to kind of take you back in time a little bit and help you understand—it'll really help you understand—where things are moving right now if you can also sort of look at where things were at one time. So if you went back far enough, then, of course, I'm not going to go back too far. You had the 1960s. You had mainframes. And as we moved into the 1970s, you also had mainframes, these massive computers that were like room-size or at least refrigerator-size in most cases. And then, as we moved into the 1980s and standardisation occurred in computers, the pricing of computers went down, and companies could actually afford to buy what is called a personal computer. And of course, with the invention of that concept, you had what was called peer-to-peer networking. So this little thing that I'm drawing is going to represent a few personal computers. Let's say that in your organization, your company has 1000 computers. Okay? And again, I'm drawing this out. A lot of times people ask me, "Why don't you just have it all drawn out?" Because I'm going to draw a bunch ofthings and it kind of gets overwhelming whenthere's a bunch of things on the screen. So I like to kind of draw it out as I talk. Okay, so we start out with a bunch of computers. Let's say we have 1000 computers now, looking at it from an IT person's standpoint. As we moved into the 1980s and companies wanted to share resources with each other, there were different companies that played a role in this. Microsoft played a role in it with DOS and the land manager. And then a company called Novelplay had a huge role in it. Of course, there was also UNIX. And then we moved into the 1990s, and this became more and more popular as time went on. And as companies grew and started needing to be able to manage more and more computers, they needed a system for doing that. And at the time, all we had was what was known as a peer-to-peer network, which meant every computer was sort of on its own; every computer was its own boss. And that meant that you had to sit down and configure each computer individually. Imagine doing that with 1000 computers. One solution to that was to create scripts—log-on scripts—that would automate the process of setting these computers up. But it was still a lot of work. And if you had to change one thing on one machine, you had to change it on the other. And every computer had to have usernames and passwords that were separate from the others. And it just got crazy. So what Microsoft did, and again, we were kind of focused on Microsoft here, is they created the concept of what is called a domain. Their concept was based on some concepts that Novell had implemented and Unix had implemented. And by the time we reached the late 1990s,by the time we reached the late 1990s, microsofthad released Nt Four and had domains and thegoal of a domain with centralization. Microsoft has created a new directory service and a new concept for domains. In fact, the symbol of what is called a Microsoft domain is the symbol of a triangle. OK? So they created this triangle, this domain, and the domain would act sort of as the security boundary for your company, all right? for your computers. So your computers would go inside the security boundary. You had 1,000 computers here. Part of the security boundary, of course, is something that you do need to deal with, and that is servers that could help you manage these computers. So with that, Microsoft had what was called a domain controller. The domain controller is a server that has a special database. All right? This little cylinder-looking thing that I'm drawing is going to be the symbol of a database right here. and that database is called Active Directory. Okay? Ad Active Directory is the directory service structure that manages our Microsoft domains. Now that directory service is where your user accounts, password groups, and all of that stuff is going to live. And with the creation of domain controllers came these things called group policy objects. GPOs allow us to deploy restrictions and settings out to all these machines. So I have the ability to implement this thing called the GPO. And the GPOs can apply to all of these computers, and they get configured based on the GPO. And of course, generally speaking, when it comes to a domain controller, a DC, you want to have more than one of those. And why do you want to have more than one domain controller to manage everything? Well, it's kind of the same reason that we want If you go to the grocery store and get a cartload of groceries, check out, and take your cart load of groceries to the front of the store to check out, the last thing you want to see is one cashier open, one cash register open to check you out. What do you want to see when you get up there? You want to see a lot of open aisles of cash registers with people working those cash registers so I can check out and buy my stuff and leave. What I don't want to do is get to the front and find only one cash register open and a line of people waiting to get out. Well, here's the thing. All of these computers right here, these 1000 computers that I have, need to talk to these domain controllers. If I only have one, then you've got one machine that's basically having to manage everybody. so you want more than one. There are basically two main reasons why we have more than one of anything, right? redundancy, also known as fault tolerance and load balancing. So if one domain controller fails, we've got another one running. And the other reason is for performance. We don't want all of these clients and all of these machines to have to just go to one domain controller. We prefer that they visit several places. Now, the other great thing about domain controllers, when you think about domain controllers, is that domain controllers replicate. So, let's say that this little smiley face guy that I'm going to create here, okay, kind of a jacked up smile, this little smiley face guy that I'm going to create here, is a user account, all right? So what will happen is that your user account will be deleted. You created this user account on this domain controller. Guess what? It's going to replicate to this other domain controller over here, and it synchronises that way through what is known as Active Directory replication. So this little arrow that I'm drawing is just kind of indicating to you that they're replicating together and all that stuff. So if you were to come to me and say, "Why do I need to have a domain?" Why not just stick with the old style, which is peer-to-peer networking? This is what I would tell you. I would say centralization. That's why I can tell you why ActiveDirectory is so important in one word: centralization. A lot of people would say security is important, but centralization is why this is such a key thing we use in our environments. I can manage everything I want using these domain controllers I want.My company can actually have multiple domains. There's this thing called trees and forests. I'm not going to get into that right now, but I can manage my infrastructure using Active Directory. Now, there are some other key fundamentals to understand about Active Directory. First off, the naming system that Active Directory uses, the domains used for managing everything, is based on the DNS domain name system. Okay? Your domain's name will have to be named based on a DNS style name. But on top of that, you have to have a server that's going to manage all that. So we have to have something called a DNS server, a domain name system server. And what's that going to do? Well, we need domain name servers for the same reason you have an address book with your phone. You don't really like having to memorise lots of phone numbers, right? So you have an address book, you're able to type somebody's name and their phone number in, and then later you can access their name and get access to the phone number and make the call. Well, DNS does that, except it does it for IP addresses. All these devices have IP addresses, and they're going to be registered into your DNS database. Saying that database implies that there must also be a database on that DNS server. The DNS database is often called a zone database. It's often called a namespace database. We had to have DNS. Now what's going to happen is that these computers are all going to boot up, including if I had a server; these computers are all going to boot up, and they're going to register with DNS, including this file server guy here that I'm making. I'm going to call him a file server. So they're going to boot up, and they're all going to register their names in DNS. The domain controllers are going to register. The file servers are going to register. Everything's going to register inside DNS. This is a topic known as dynamic DNS. And this is going to allow computers to all register. Now what happens is that every one of these machines—your client computers and your servers—all have to locate DNS by their IP settings. And they're going to ask DNS who these guys right here are so that they can all authenticate. So these clients, when they boot up, are going to say, "Hey, DNS, do you happen to know who my domain controllers are for my environment?" And DNS is going to reply back with this information, known as service records SRV information). and it's going to point the client to these domain controllers. The other great thing about Active Directory is that Active Directory supports the ability to point people to the nearest domain controller so that they can log on and get authenticated. The authentication system that Active Directory uses is based on a protocol called Kerberos. When you hear that name, protocol, I want you to think language. It's basically like the language they speak. And Active Directory security and querying language are built off of two protocols, really. One of them is called LDAP (Lightweight Directory Access Protocol), which is basically a query language; the other is Kerberos, which is going to be the security authentication language that it uses. Okay? So as we moved into the year 2000, Active Directory was released. And this is the big thing everybody's doing. And of course, the big thing, too, is that we also have to have an Internet connection. So this little cloud thing that I just made here is going to be my Internet connection. And so we've got an Internet connection coming into our company here, and we're also going to have to protect our Internet. So we're going to have a firewall. So this little guy right here will be my firewall. And my firewall is connected to my internal network as well as my outside Internet connection. Of course, routing is involved there and all that stuff as well. All right, so the Internet is the big thing. Everybody wants to be on the Internet, be secure, and build access resources. Microsoft is making technologies that are available to do this, though LDAP and Kerberos are both internal-based technologies that are not really stuffed. something that you are exposed to on the Internet, which is why you have to have protection and all of that.

2. (BONUS)A Foundation of RAS, DMZ, and Virtualization

So occasionally, you might find yourself in a situation where somebody from the outside world needs to get in. And there are two real ways to approach that. One would be somebody who is part of the company, like maybe this guy here. And he needs to access resources inside the network here. So maybe the file server or some of these clients or something like that So what we could do is set up this thing called a Raz server, or Ras Remote Access Service. Raz supports something called a virtual private network). VPNs would allow people to securely connect to that Raspberry Pi server remotely. They could then access things like the file server and other things like that. And so, that's all wonderful and great. The one thing VPN users must do is authenticate; they must prove their identity. What about this situation, though? What if your company wanted to host a Web server? All right, they want to host a Web server like this little box that I'm drawing here. And they need to make that Web server available to people anonymously. In other words, individuals who are not employees of our company. Well, you run into a slight issue there. The issue you run into is where do you put this web server? If you put this web server here on the internalnetwork with your stuff, you're basically letting someone who isnot part of your company, you're letting someone who isnot part of your company access that web server. If this person right here is not an employee and is just an anonymous person on the Internet, we don't want that person to be able to gain access to this web server. Hackers can do this thing called pivoting. Pivoting is where a hacker gains control over this server and then is able to actually pivot to other servers. So that would be a bad thing. We don't want that. So one thing we could do is store this Web server on the outside. We could store it out here, outside our firewall. Of course, the problem you run into there is that you've not left the server any protection. Basically, the server is outside your firewall. And at that point, it's completely exposed to things on the Internet. So the general rule of thumb that everyone followed was that they would get another firewall. So you'd get a second firewall. just going to copy this guy right here. And we would put that firewall right here. And that is called a DMZ, a demilitarised zone, also known as a perimeter network. And what you would then do is put rules in place on these firewalls so that people out here could get in through this firewall and access the server. But you have this firewall acting as an additional layer of protection to stop things from getting in from the outside world to the inside world. Okay? So this was a pretty traditional approach. This is the way we've done things for years. We've centrally managed things through ActiveDirectory domains in the Microsoft world. And it's a fantastic solution that has worked flawlessly. Another thing that we've had for years is the concept of having internal servers that do different jobs. For example, we might have an Exchange Server,which is an email server that Microsoft supports. It's their email product, actually. And we'd have an on-premise email server where people could check their email and everything from the outside to the inside. There were some things you had to implement to do that. Another thing we had was SQL Server. SQL is Microsoft's database product. So we'd have SQL Server handling databases for us, and we would have something called SharePoint, which allows us to set up some different types of sites that employees can use for things. And we could do Skype for Business—all of these different things. Skype for Business has been Microsoft's voice-over-IP product for the longest time. And we would have—I'll just put "Skype for Business" to represent that we would have all of these servers in our internal environment. And guys, this is the traditional approach. The way we've done things for decades, if not years, is the way things have always been done. So now what I want to talk about is moving into the future. As time went on, as we moved into the end of the 2000s and the early 2000s, there was a concept known as "virtualization." Now I want to warn you guys that the concept of virtualization is not a new one. A lot of people think it is; it's actually not. The term "virtualization" has been around since the 1970s. There actually was a Unix-based operating system that had a thing called a hypervisor that could do virtualization. It's just that virtualization really didn't blossom until the early 2000s, when a company called VMware discovered and created some really awesome features that could allow companies to take advantage of something called elasticity. So I want to talk about that for a minute, the concept of virtualization. So what I'm going to do is move these servers over here for just a minute. We're going to move them out of the way. And what happened was that, using the concept of this company called VMware, they discovered that instead of us having to buy four different servers, they could create a way for us to take one physical server with a lot of power, a lot of performance, CPU, memory storage, and put all of that on this one server. And the server is known as a hypervisor in Microsoft World, which is the world we're living in right now; it's called HyperV. Okay? So there's VMware, which is a third party, and there's Microsoft HyperV, which is sort of what we learn about in this course. So HyperV's hyper-virtualization allows us to virtualize these servers. Think about it. If you can emulate hardware, okay, CPU, memory, storage, and networking, then you could technically set up and operate systems that run on that emulated hardware. Well, those are called guest operating systems. These right here are virtual machines running guest operating systems. Of course, the scary thing about that, the thing a lot of people freak out about, is they're like, "Well, if one of those servers fails, okay, if the Hyper-V server fails, I should say if it fails, you lose all access to all your servers." Well, see, that's the beauty of virtualization. It's very easy for us to actually just get two servers, okay? And we can do something called clustering, where we connect these together and have a duplicate. Now, if one server fails, we still have that other server. In fact, these two servers can actually even be in two completely different offices if we want, okay? So I can have them in two different branch offices if I want. So notice that this is going to save us a lot of money on hardware and all of that. Here's the other beautiful thing about virtualization that they created. It's called elasticity. Elasticity involves the ability for your virtual machines to be able to request more resources when other virtual machines aren't using them. So, for example, if the Exchange Server is using, let's say, 20 gigs of RAM and the SQL Server needs 30 gigs of RAM, And the Exchange Server currently does not need all that extra RAM; it can release that memory that it's not using. And the SQL Server can use it, benefit from it. And then if the SQL Server no longer needs that memory, it can release that memory, and the Exchange Server can get it. And this is what elasticity is all about. And what you're going to find is this. This is the forerunner of cloud computing.

3. (BONUS)A Foundation of the Microsoft Cloud Services

Okay? So I want to talk with you now about the concept of cloud computing. Okay? So first and foremost, the concept of cloud computing is really not a new concept concept.A lot of people think it is a new concept. It's not. First off, the term "cloud" has been around for a very long time. Although the term "cloud" now definitely means a few different things than it used to 20 years ago, the concept of "cloud computing" now is that you are hosting something as a service on the Internet. Now, this is not a new concept. I like to use this analogy, okay? Essentially, think about the cars that I own. So I have a wife, and I have some daughters. My daughters have their own vehicles. And so I've got to deal with a bunch of vehicles in my driveway. And of course, my vehicles sometimes break metimes brSo let's say that I want to manage the repairs on my vehicle myself. My vehicle. What I could do is purchase all the equipment needed to make myself an auto mechanic shop out of my garage. I could turn my garage into an auto mechanicshop, and I could deal with the repairs myself. I could get a hydraulic lift. I could buy all the tools. I could get all the training and everything that's needed to do these auto mechanic procedures myself, okay? Or instead of me spending the money to do all that and get all the knowledge and keep the equipment updated and all that, I could pay an auto mechanic shop that does that job as a service, okay? And I don't have to deal with it, guys. That's what cloud computing is. You're basically paying somebody else. You're paying for a service to be hosted for you. So here's what's happened. Companies like Amazon, Microsoft, and IBM have built these huge data centres full of equipment. So you're talking about lots of server blades. You're talking tonnes of processing power, tons of RAM, and tonnes of storage. You're talking about the best fiber-optic network equipment—load-balancing equipment, firewall equipment. Everything is built in these warehouses that have been placed strategically all over the world, okay? so that they get a tremendous amount of redundancy. And so from there, these data centers are what make up what these companies are calling their cloud. This is connected. These clouds are connected to the Internet. All these data centres are connected to the Internet. and they're all connected together. and it's an ever-changing thing. It can grow. It can shrink. Different locations can be opened up. Now, Microsoft's main cloud technology is called Azure. Now, I'd like to introduce you to an acronym related to IaaS. IaaS is infrastructure as a service. And Microsoft Azure is Microsoft's infrastructure as a service product. I also want to throw out that "show" about how I pronounce the word Azure. Some of you guys may pronounce it "Azure." Azure One time I actually went out and tried to research the proper way to say that word, and I was watching the developer videos of the Microsoft guys who created it. And guess what? They all pronounce it differently, too. Some people call it Azure. Some of them refer to it as "your Azure." So, tomato, tomato. But Azure is Microsoft's infrastructure-as-a-service cloud product. And what it is is that, basically, you will get access to their cloud if you get an Azure tenant subscription, and you can host virtual machines out on their cloud. So if I wanted to, I could actually host all of these things that you see on premise. I could host them on their cloud if I wanted to, in their cloud environment. And they give me access to a directory service called Azure AD (Azure Active Directory) that's going to let me link to all of my user accounts, passwords, and all that. If I wanted to link these two together, MyOnPrem Active Directory and Azure Active Directory, I could, but I'm not going to get into that just yet. So I get access to virtual machines. I get access to Azure ads. And the great thing about it is that I just pay for what I use. I pay for the CPU usage I use, the RAM I use, storage, networking, and some of the appliances like load balancers and things like that that I use. And they give me access to all that. Now there are two other cloud terms that I want to introduce you to. The first is PaaS and the second is access toPaaS is platform as a service, okay? And SaaS is software as a service. Now. Microsoft originally referred to their PaaS and SaaS technologies as PaaS and SaaS, respectively. They were calling it Office 365. But this confused everybody because when you hear the term "Office 365," everybody thinks of Word, Excel, PowerPoint, and all that. This cloud environment is a lot more than that. So what they ended up doing in the last year or so was renaming this to Microsoft 365. So what you're going to find is that when they are referring to the IaaS portion of their cloud, they use the term "Azure." When they're referring to the PaaS and SaaS version of their cloud, they're talking about Microsoft tion of tSo what do you get with those? So platform as a service means they're hosting a software-based platform for you that you can use, manage, deploy, and all that. So for example, I get Office 365. I get the platform behind that for deploying Office 365. But I also get something called Office Online, which is the software-as-a-service version of that, which is where I have apps that users can access in the cloud. I also get the Exchange Online platform. So I get Exchange, email, and all that stuff hosted in the cloud. I get SharePoint online. Okay. So I essentially get SharePoint made available to my people. I get Skype for Business, which of course is now called Teams, which is their big collaboration technology that you're going to use for collaborating and chatting, video conferencing, voice over IP, and all that good stuff. As part of the deal, I get this thing called Intune, which is Microsoft's MDM technology that gets into the concept that you can control smartphones, tablets, laptops, and even desktops in your own environment. And this is very similar to what SCCM does, if you know what that product is: System Center Configuration Manager. But it doesn't necessarily completely replace that. It's a cloud solution for managing your devices. And you even get a feature called Autopilot that I'm going to talk more about, which is being able to automate the deployment of your computers. Okay? So you get a tremendous amount of capability. You get something called "Security as a Service," where you get access to all these tools for managing classifications and encryption and being able to do eDiscovery for forensics and evidence collection. There are so many things they're giving you. I don't have enough room, honestly, in my little cloud diagram to draw everything that you get because you just get so much. You also get one drive for business. I'll just put Ford B-One Drive for Business, which is a cloud storage solution. You get so many things with it,and it acts as a subscription service. Now, the other thing I want to mentionis that you can link your on PremEnvironment, which is Ads'your on Prem Environment iscalled from Active Directory standpoint, is called ription sestands for active Directory domain services. Okay? Active Directory Domain Services. That's what that acronym stands for. And so what you can do is connect Active Directory Domain Services with Azure AD if you want, and you can synchronise things. I can set up a server called Azure AD Connect. All right? Azure AD Connect is a special server that you can use to synchronise your on-premises Active Directory user accounts' passwords into the cloud. Now, do you have to have a separate server? It can actually be a domain controller, but it is recommended that it be a separate server. Okay. And that server is going to synchronise whatever you want. Do you have to synchronise all of your user password groups out to the cloud? Absolutely not. You have control over what actually gets synchronized. They call this a hybrid solution. A hybrid solution is where we link our on-premises Active Directory with our cloud scenarios and cloud functions and synchronise whatever we want to synchronize. This gives you an idea of where Microsoft is going. Microsoft is definitely heading towards the cloud now. Are they just abandoning everything on premise? Absolutely not. We still have access to all of that stuff. It's still available. But what they're trying to encourage everybody to do is utilise their cloud environment. Now, one thing I want to point out real quick—that's different. With Azure, the IaaS service that they're using, you're going to pay for the usage of the CPU, the memory, and the storage. With Microsoft 365, you're just paying a subscription fee for these products, and you can use them as much as you want. There is no such thing as CPU memory limitation. You're going to actually find that the two technologies complement each other. So when you actually get a Microsoft 365 account, you're going to still have access to some of the Azure stuff. and if you want to host things like VMs and all that, you can. So the great thing about the cloud is that, with the creation of virtualization and elasticity, this is what cloud computing really is all about. You're able to host this stuff online, and it can use elasticity. You need more CPU. Power. It can give it to you instantly. You need more RAM; it can give it to you instantly. You need more storage, whatever it is; they can scale you out. And then when you're not using all those resources, they can scale you back. Okay? So hopefully this gives you a really good foundational understanding of where things were in the past, where we are now, and where Microsoft is going. And, as you can see, their heads are in the clouds right now, as they say. They're definitely trying to coerce people into moving into clouds, and even in all their different exams and courses, this is sort of the big thing that they're focused on right now. It's.

Hide

(OPTIONAL)Setup a trial account with Microsoft 365 and Windows VMs

1. (OPTIONAL)Creating a free Microsoft 365 Azure AD Account

The first thing you should do is create yourself a free email account. So Outlook.com, Gmail, Yahoo—just create yourself an email with any of those companies or whatever. Throw away any email address you want. And then from there, you're going to visit this URL that I've got for you. Tryoffice three, six, five, and eight at tinyurl.com. You're going to go to that link. So type that all out. Make sure you don't capitalise anything. It's all got to be lowercase. At least this part of the name, okay? And the great thing about it is, once you do this, it's going to require you to verify, but it's just going to make you verify with your cell phone. It'll send a text message to your cell phone, verify it for you, and then you're in. You do not have to put a credit card in, so don't worry about that. and you're going to have yourself a free account. You're going to be able to try all of the cloud-based scenarios that I go over in the course, okay? So I highly recommend that. Let me just quickly jump over here and I'll show you what it looks like. So I'm in my Web browser now. I'm going to tryofficethree, six, five, and eight with tinyurl.com. I'm going to hit Enter on that.

And then from there, notice the site I come upto, it says Office three, six, five, e five. They tell you it's a monthly fee and everything. But this is a free trial. You're not having to put a credit card in, you're not having to worry about them hitting you and costing you money, and all that. So I'm just going to go to the trial here. At that point, I'm going to put in the information. I'm going to put in my email address that I've got. It's going to have you fill in some personal information. You're going to have to put a cell phone number in. It's going to send you a text message. And at that point, you are going to be able to go at it, all right? So you'll be able to get access, and it will create your Office 365 E-5 account, okay?

After your account is created, there are a few more minor steps you must complete. So I want to show you what that is. So, all right, I'm going to Portal Azure.com. Okay. So now, once I'm on the portal, Azurecom is logged in. It says, Welcome to Azure. Okay, I'm going to click on the little menu button here. We're going to go to Azure Active Directory. This is something you need to do after you've set up your free trial, okay? You're going to go to licences here, all right? Then go over here to the right; it says "Get a free trial." So you must click that and activate this enterprise capability as well as security. This subscription is going to be needed for some of the hands-on work I'm going to do. Go ahead and activate it. Keep in mind that it may take about 15 to 20 minutes or more sometimes before this licence officially gets activated.

Okay? Let me tell you how you can immediately tell whether or not your subscription is ready. This is how you can tell. All right. If you open up a new tab and you go to portal dot Microsoft.com, let it log on, right? You're going to go to show all. You're going to click "Security." Okay. Once you get into security, you're going to see all these options here, and you need to see an option called eDiscovery. If you don't see Ediscovery, your licence is not ready yet. You need to give it more time. So make sure you activate EMS, and then you can come in here to the Security and Compliance Center just like I showed you, and you can make sure that your discovery is there. If you see all this stuff, you're in the right spot. You've got everything you need. You're going to be able to do all the cloud-based scenarios and all that stuff with me. Okay? So I encourage you to do that. Set that up, though you guys can obviously watch me do everything during the course. It also helps you to do it as well. And I try to teach this as though you were doing it with me. So I encourage you to do that.

2. (OPTIONAL)Setting up a Windows 10 and Server 2019 Virtual Machine

Okay, so just go to a search engine, and you're going to type "download Windows 10 trials." All right? So just search those keywords, and you're going to notice that Microsoft has a link here that says, "Try Windows Ten Enterprise, Microsoft Evaluation Center, basically for free." You click on that, it's going to load up this evaluation centre here, and then you can actually download the ISO file from Microsoft. Okay, so the ISO file is basically like a DVD of Windows Ten. The Enterprise addition is the one I recommend you use. The long-term servicing channel is for critical machines that want to push updates off for ten years. Anyway, that will be something covered more fully later. But the Enterprise Edition is the one I recommend you get.

So you're going to download that. All right? Now if you want to get a copy of Server, you're going to need an ISO file for that as well. So what you're going to do is go out there to Google or whatever search engine you want and type "download Server 2019 trial. Okay? Search those keywords. And here it is, right here. Windows Server free trial So you're going to click on that same kind of deal. You're going to go right here, where you're going to download a free trial and get access to the ISO. Now once you get access to the ISO, at that point you're going to need to install HyperV on your machine. If you have a Windows 8 Pro machine or a Windows 10 Pro machine that you want to install this on, or maybe even a server, you can install HyperV. Or you could go out there and search for VirtualBox, and you could do VirtualBox, or some of you may have VMware. You can do that as well. Okay, so now what I want to do is show you real quick how to install this if I'm on a Windows Ten machine and how I can install HyperV. Okay? So I'm in front of my computer here. I'm simply going to Control Panel and searching for Control Panel. Okay, here's the search bar, and if you're in category view, just go up here and say large icons under the category. And then you're going to go to Programs and Features. So we're going to click that, and then I'm going to go here where it says install or turn Windows features on or off.

All right, so let me zoom in on that for you so you can see that a little better. Turn the Windows feature on or off. Okay? So we're going to click that, all right? And we're going to install HyperV. So you'll choose that, you're going to go ahead and install it, and you'll be able to set up your virtual machine. So I'm going to just click Okay. At that point, it's going to install it, all right? I'm going to fast forward through this, and we will load up HyperV. Okay, so here I am in HyperV. All I had to do to open HyperV was just go and search for the word hyper. And then I was able to click the HyperVicon, which is this little icon right here. And then it's going to open up. Now you guys will see that I've already got a couple of virtual machines set up. I've got an Nycdc One, which is a server2019 box, and NYC Clone, which is Windows Ten. All right? Now, let's say I did not have these machines and I wanted to go ahead and create them. So I'm just going to go here to the right. I'm going to click "New." I'm going to click "virtual machine." It's going to bring up this little wizard here. I'm going to click Next and give it a name. I would just call this a Windows 10 client. Or, to follow in my footsteps, Nyccl One. All right. And then I'm going to click next. It's going to stick with Generation 1. I'm not going to explain the differences right now, so click Next.

Give it some memory. Okay. I gave mine each four gigs of RAM just so my demonstrations would try to be a little quicker. The more RAM you can give it, the better. 2048 is probably going to be the bare minimum, though. So I'm going to turn off dynamic memory, click Next, and you can connect it to your little network. Now, when you first set up Hypervig, you're just going to have a default switch. So you can just select that. Okay. I'm not actually going to configure the network right now, though. I'm going to click next. It's going to ask me to create a virtual hard drive. I'm just going to go with the default here. All right. And then at that point, I'm going to click Next. It's going to ask me if I want to load the operating system. So this is where you're going to point to the ISO file that you downloaded off the Internet. So I'm going to go ahead and point to that ISO installation and operating system, bootable CD, click Image file browse, and this will take you to your desktop. And then from there, you will see the Windows ISO. So I'm just going to load that. Going to click Next, going to click Finish. I'm ready to start my virtual machine. just going to right-click it and click Start, and then I'm going to connect to it.

Now notice it's going to say I don't have enough memory. And the reason I don't have enough memory is because I'm using all my memory on these machines. But when you guys start it up, it's going to ask you to install Windows Ten. And if you don't know how to watch how to install Windows 10, just stay tuned. All right. So that's how you would get Windows Ten up and running. Okay, actually, if you want to see me start it, I'll just turn this guy off. It's not going to hurt anything for him to get shut down. So we'll go ahead and start him up. All right, hit Connect, and you're going to see this loading up on the screen. I'm not going to go through the full install right now, but it's pretty self explanatory.Once you're booting up, you're going to just install Windows 10 just like you would install a normal machine. Okay? So as you can see, that's loading up to the Windows install screen. And you're just going to answer the questions that it's going to ask, all right? Just like you normally would on a normal computer. Now for servers, it's really the same process. You go, new virtual machine Next.Just call it Server 2019. All right? Next generation, give it some memory. We'll say 2048-bit megs, and Next will join it to the network you want to join it to Next.And then we'll give it the default virtual hard drive. We're going to point to the ISO file. So we'll go here, point to the ISO browse. This time we're going to point to the server. Thousand and 19 ISO next finish. And then at that point, we are going to start this up and connect. Same thing. You're then going to install your server. So from there you will be able to install your server, get it configured, and get ready to go. You don't even have to have them activated to really work and mess around with all this stuff, okay?

The only other thing you can do on your server is, once you get it booted up, pop up a server manager tool. You go to Manage AD Roles and Features and install something called Active Directory Domain Services. But I'm not going to get into all that right now. As you can see, though, you can run through this installation and you'll have yourself a couple of VMs. Keep in mind, you can do this with VirtualBox as well. I don't cover that in this video, but there are a lot of, like, little YouTube videos that go over how to set up VirtualBox if you don't have access to HyperV. Okay? So hopefully, that gives you guys a good understanding if you want to get down and dirty with these VMs and play around with everything. Now you know how to set it up.

Hide