@HewittAve Gave you a brief breakdown, but i got some time and will expand on it and give you some practical examples.
ISO's: think of as digital CD disks. think of the term creating an iso, as in "burning a digital CD". You can get ISO's on the web either legally or illegally or you can create an iso if you have a secondary bootable device.
Your ISO can be of anything, Windows 10 OS, Windows Server OS, a Linux OS, a video game you pirated, etc.. In this case we'll be using an ISO of Windows Server 2012 R2. The ISO is important because you'll need it to create your Virtual Machine(VM). So if i wanted to create a Windows 10 VM, i would use a Windows 10 OS ISO. You catch my drift?
AD: Is Active Directory, in simple terms its a collection of your PC's, users, groups, etc in your organization AKA your domain. in this case our domain will be thecoli.local.com.
Lets say we start a company called, 'TheColi Inc.' and we hired you as our 10th employee. Now before you can start, you'll need a computer, a work email address, a user account & password.
First things first, we'll need to go in Active Directory and create your user account. We type in your name, title, email address, etc then create a password for you. This allows you to be able to sign in to any computers on the domain. So if i let you borrow my computer, because its on the domain and you are on the domain, you can just use your account to sign in. But if neither were on the domain it wouldn't work unless your account was on the domain and is now cached on that pc.
Now lets say we buy your computer from Best Buy. We'll need to rename it from the default name to our standardized convention. let say all of the PC's on our domain follow this naming convention, COLI-#. Number sign being the computer number. Our first computer would be COLI-1 and because yours is the 10th it will be COLI-10. so in AD i will create a computer called COLI-10. Then we'll physically go to your computer rename it to COLI-10 then change it from workgroup and enter in our domain name, which is thecoli.local.com. And Viola there you go. Now there's Image deployment tools that we can use to remove the need for decent amount of this stuff, but that's irrelevant to this right now and there are domain trust relationship errors that can happen as result of having pc's on the domain rather than the workgroup, but you'll learn this stuff as you progress.
Now having PC's on the domain is great because it opens up so much opportunity for us. If wanted every pc to have a shortcut to JBO, because all the pc's are on the domain i can create a group policy in Group Policy Management that puts the shortcut on everyones desktop when they log in rather than manually going to each pc and doing it one by one
DHCP: Handles IP addressing, Once i plug a device onto our network unless i specify in the settings of the pc adapter or its console if a printer to use a static IP, DHCP will lease it a random IP. keep it mind LEASE not give. this means that once the lease time is up, DHCP may lease it another address. Only way around this is by either creating a reservation in DHCP that says always give this IP to this System, you typically do this for printers OR Exclusions, which are IP's DHCP is not allowed to give out. So if i made a exclusion of 192.168.10.1 - 192.168.10.10. DHCP will start handing out IP's starting from 192.168.10.11. without DHCP we would have to manually enter in a systems IP, Subnet mask, and Gateway.
You would have know all the different IP classes. 192, 10, 172, etc. then would have to know subnetting then would have to know how to find the range you can give out. This would take ages. All the numbers of the IP address mean something a 10.109.120.60 /24 is not the same as a 10.109.120.60 /16 address. DHCP is a protocol that handles all the heavy lifting for you. You will have to know this kind of stuff in networking though especially when dealing with VLANS.
DNS: Every computer on the network has an IP address. in our organization yours might be 192.168.10.15 this is how they communicate. However though having to remember the IP address of all the computers is trivial. also remember DHCP may give it a different IP once the lease is up. Lets say for some reason computer COLI-2 cant access our file server. if i wanted to troubleshoot by pinging this host from the server, I can simply just use a Ping COLI-2 command, because DNS has now attached the IP to the Full Qualified Domain Name(FQDN) This is called Forward lookup zone. the reverse is called the Reverse lookup Zone. which retrieves the host name from the IP. Correct practice is to configure both of these.
Things in red are things to research on your own. don't say we've never helped you....
Last edited:
