Introduction to Active Directory Directory Services Structure in Windows Server 2012

hello again as you know I am Eli the computer guy and today's class is introduction to Active Directory directory services structure in Windows Server 2012 try saying that three times fast so basically today we are going to be doing an overview of what is Active Directory directory services why is so important in the Windows environment and in corporate network environments and give you an idea of the overall concepts that you have to understand about them now when we are talking about this you are probably going to recognize some words that you have heard from certification classes or if you've been studying things on the Internet so we're going to be talking about domains today we are going to be talking about trees you're going to be talking about forests and we're going to be talking about trusts what all of these things mean so Active Directory is why Windows servers are so important Active Directory is you know how they say that Cisco equipment is what makes the internet work well Windows servers Active Directory is what makes businesses work this is a very very very fundamental technology in almost every enterprise so it's very important that you understand what's going on now I know a lot of you guys I get all these like little snarky comments talking about Oh who wants a Windows Server why would you pay those stupid fees I'm going to use a Linux and you know what using Linux is great if you have some kind of web service using Linux is great if you want to set up some Samba file server for an office of 10 or 20 users but when you start dealing with offices of corporations that have tens of thousands or hundreds of thousands of users the fact of the matter is is that Windows Active Directory is about the only thing that will cut it so what is Active Directory active directory directory services as it is now called is the server service for security and permissions in a Windows environment so if you want to set up computers and create security policies for those computers you would use Active Directory directory services if you want to set up a VPN connection and only allow certain users to be able to connect into the corporate network using that VPN connection the security the the the ability to connect to that will be through Active Directory directory services so basically Active Directory directory services is at the pinnacle of what is called single sign-on so what happens is you sit down at your computer in the enterprise world you log in once and all of the sudden all of the network resources are either available to you or are blocked up to you from that single sign-on so you sign on once you get access to the computer and you get access to the shared files and folders and you get access to the shared printers and if you're allowed you get access to be able to VPN into the network and you get access or not to SharePoint and you get your emails basically what Active Directory directory services allows is that administrators can sit down and essentially at one console give users and individual computers permissions to do things on the network and do things on individual computers that is what makes it so powerful again when you're dealing with ten thousand or a hundred thousand computers you can't sit down at every single computer and try to configure you know the security policies for every single computer that just won't work with Active Directory directory services you can create policies within the domain controllers the the servers that control Active Directory directory services and those policies will go out throughout the network and will populate out that way Active Directory is the only way really nowadays that this can happen the amazing thing why this is so powerful is because not only can you do the things that you probably think about such as you can give users permissions to files and folders you can give users permissions to a printer maybe you can give users whether or not they can connect in through a VPN or such but you can also walk down security policies on computers so you can say whether or not users are able to take the background image on their computer are they able to access the CD Drive are they able to access control panel you can use security policies to lock down what users are able to do not only that but you can actually lock down based off on computers so if you have a corporate environment where you have kiosk computers so kiosk computers kiosk systems are computers that kind of sit out in public areas and can be used for for public or semi-public purposes so let's say you have a computer that allows people to find out what offices certain employees are in or you have a computer that shows you know again some kind of directory well what you be worried about is if this computer is in a public place what happens if somebody trying to be a hacker goes up to the computer and tries to infiltrate your network from that computer well using security policies what are called group policy objects you are actually able to secure that computer and say that kiosk computer has access to one very specific file on the network and no others so if you log in to that computer even as the CEO of the company you will only be able to access that one a single file because everything else has been restricted so this is what makes active directory directory services so powerful now when I'm talking about Active Directory and I'm talking about other things in this Windows Server 2012 class I I'm going to try to talk to you in the specific verbage or words that Microsoft wants me to talk to you in but I will warn you that if you are planning to take a test make sure you go out and pick up a book to learn all the words that you should learn so so when I learned Active Directory way back when we called it Active Directory now with I think was actually Windows Server 2008 Microsoft started calling it Active Directory directory services now I know that doesn't seem like a big deal to you right now but if you sit down at a test Microsoft gets very specific on the words you use if you say that the security policies and all that are controlled by Active Directory you might be wrong whereas if you said Active Directory directory services you would be correct so one of the warnings that all gave you the more we delve into Windows Server 2012 is I will try to use the proper words I will try I will try but but again if you're going to be taking the Microsoft test make sure you go out and buy a book like I say this is my workbook that I'm using Windows Server 2012 unleashed by Sam's cost 60 bucks at Barnes & Noble but make sure you go out and buy a book and read the book because some of the words that I use may not be absolutely correct so let's go over the whiteboard now and so I can start explaining to you guys really how cool Active Directory is because it really is just it's an amazing thing especially if you've ever worked in an environment that doesn't have Active Directory then you'll realize just how wonderful Active Directory is so basically when we are talking about Active Directory these servers that control Active Directory are called domain controllers or D C's so domain controllers or DCs are what control Active Directory services so just like an exchange server controls Microsoft email services or at Samba server is a type of file server a domain controller is an active directory server the domain controller is what stores all of the information for the user accounts and computer accounts so basically you start with what is called a DC or a domain controller now within the DC or the domain controller what you what you add to the domain controller DC is you add user accounts and you add computer accounts I think they're called accounts but basically you add user accounts and computer accounts into the database for the domain controller now when you add information to that database you're adding information to what is called the schema so you will hear the word schema and it will sound very scary but don't don't get scared by the word schema schema is simply the database the scheme for how data is stored in the domain controller what information is stored in the domain controller about users and computers and other things so the schema states that for user accounts there will be a user name and there will be a password and there will be an email address and there might be an office number and there'll be a whole bunch of different pieces of information the user account schema the the schema holds lots and lots of different data about the user account then for the computer account it will have such as the computer name it will have I think it's a SID it'll have the identifier and it will have other information so the schema is the scheme the types of data that are stored for the different user accounts and for the computer accounts and the schema is in the domain controller and is part of Active Directory directory services now one of the things that makes this schema powerful what makes this whole Active Directory a system powerful is that the schema is what is called extendable right so what extendable means is that in many systems they will create something for a user account and let's say a computer account they'll tell you what data you can add and then you're done you can't add any more data than what the original vendor or programmer or manufacturer told you you could add well with the schema with Active Directory directory services is extendable which means you can actually add more to it so when you install a domain controller for the first time there's a certain amount of data that is stored for all users and computers but then as you go such as if you install exchange server on the network it will then add the different types of data that can be stored in the schema for the user accounts and the computer accounts so let's make sure we've got this so domain controllers are the servers that control Active Directory directory services then the main points in the domain controllers are the user accounts and the computer account so user accounts are you me anybody sitting down at the computer the user accounts is you actually add computers to the domain to make them members of the domain so computers have their own accounts and this becomes very important later so the user accounts and the computer accounts the types of data that are stored for the user accounts and the computer accounts is in what is called the schema the schema basically says like I say for user accounts you store the user name password email address office blah blah blah blah blah blah and for computers you did the computer name the unique ID blah blah blah blah blah blah so all these different points of that is just like you would in any kind of user database the main thing with a schema that makes it so useful is again it's extendable so you can add some type of third party software and that third party software can go into the domain controller and add additional bits of information that it will collect or it will distort about the individual user accounts and computer accounts on the network so now that there were that far so we understand we've got to use your accounts and we've got computer accounts on this domain controller now here's one of the problems though is again we're talking about user accounts we're talking about computer accounts and we're talking about networks one thing about big networks we're not talking about hundreds of users we're not going about thousands of users and computers we're talking about tens of thousands of using users and computers or hundreds of thousands of users singing peers now one of the big points with this Active Directory directory services is security so saying who has access to what who has access to what file or folder who has access to what VPN connection who has access to what website right well if we had to go and do every single user account and every single computer account and actually give every single user and computer these rights and permissions that would take forever again we're talking about tens of thousands hundreds of thousands of users so for security purposes we can add users and computers into what are called groups groups what you can then do is you put users into the groups and then you assign the groups permissions to the different resources on the network so if you have a file that only the accounting people that are in the accounting department should have access to so you know this file over here and only the accounting department should have access to it nobody else should have access to it right well what you do is you put all the members of the accounting group all the users who are in the in the accounting department into an accounting group and then you give that accounting group permission to the accounting folder now they have access into the folder you can block everybody else from being able to see it so that makes it a lot easier if you have an accounting department again let's say of a hundred employees then when somebody gets hired you simply add them to the accounting group and they get all the rights permissions that an accounting person should get if somebody gets fired you simply take them out of the accounting group and then that automatically takes away all of those rights and permissions so the first thing that you need to think about is groups and groups are used for security then the next thing you do in order to deal with all these people and all of these computers is you have what are called Oh use or organizational I'm a horrible writer unit organizational units are groups but they're for administrative purposes so basically you can create oh use or a organizational units for administrative purposes now what does this mean why are we talking about when we're going to be creating groups for organizational purposes well when you go into the corporate world what you're going to find out is most employees when you go in there it is an administrator you can lock them down you can tell them exactly what they're going to do with their computers and they just got to do it right here the computer network administrator and then you've got to suck it up and do whatever it is you tell them they can do with the computer such as let's say if you're in a company that has call center employees basically you may have a thousand call center employees and you go in there and you can very simply lock those call center employees down to only be able to use let's say two applications they're not allowed to get to the internet they're not allowed to change the background on the screen they're not allowed to do anything to their computers they are locked down and those computers are super secure and super stable and just super super because that's administrators that's what we like to do we like to lock things down that makes our life a lot easier well the problem is is like for all those call center people sad as it is to say they are incredibly replaceable if they don't like the fact that their computer is locked down well then they get fired and other they get replaced by somebody else and the world goes on that's how it works in the corporate world but as I talked about the reason why you want to be a professional the reason why you want to be a highly skilled professional is because when the company hires highly skilled professional they don't treat them the same way basically of highly skilled professionals say they want their computer to do X Y or Z they want to be able to install something they want to be able to continue the background image on their computer well by golly they are going to do it right if you go to the marketing department if you walk in as the administrator to a marketing department and you tell them you're going to lock down their computers they are going to get up and open revolt literally those folks are going to quit the company because they are not going to tolerate being told what to do with their computers and frankly the company finds them very valuable so they don't want them to quit so the problem comes up is you have these organizational units that need to be dealt with by their own people sometimes so what you can do with organizational units is you can create let's say the marketing department organizational unit oh you and then you can give one person in the marketing department administrative permissions for that marketing department organizational unit so he can be like the marketing and admin right so if software needs to be installed if things need to be changed whatever instead of the marketing department always calling you because these needs things need to be done every day a few times a day you just don't have time for all the stuff they need done what you can do is you can delegate the administrative tasks to a marketing administrator and then that marketing administrator has permissions over all the computers and user accounts within the marketing organizational unit so if passwords need to be reset that marketing administrator will be allowed to do that it programs need to be installed you can set it up so for that the marketing administrator to be able to do that so on and so forth this can be very useful if you have things like remote sites so again back when I was in the corporate world I had what did I have 12 offices I had to deal with all all over the place all over the place all the way from Washington DC to Boston right so one of the problems was I was thinking only God with the administrative account and you don't want to give out your password you know so somebody in the Boston office calls you and you're in Baltimore you don't want to give them your password in order to make a change on the local network but you also don't want to actually have to grab a flight up to Boston to fix whatever is going on so again with these Oh use or this organizational unit if you have remote offices you can create a Boston admin organizational unit or administrator who has permission to deal with all the user accounts and computer accounts that are in the Boston office so that if there are any problems they can try to fix the problems before you have to grab a flight and actually fly out to Boston now the nice part with the organizational unit is what that means is that Boston administrator has access to whatever you allow him to have in the Boston office but if he tries to hack in to Philadelphia it won't happen because he's not allowed to have permissions in the Philadelphia office so you as an administrator you are global I don't know what they're called anymore they used to be called global administrator so you're a global administrator which means I as Eli the computer guy I control all this I control all the servers I can log into Boston I can log into Philly I can log into DC I can log into Syracuse I can log into Long Island I am allowed to do all that right because I'm a global administrator the problem is is again that you know people do dumb things you don't want to give a lot of power to any one person unless you have to because they might damage something they may do it in variously or they might do it just because they're trying to be a good person and they don't realize how much damage they're doing so for global administrators for administrators I have control over everything you want very few of those but what you can do with these organizational units is again the Boston office can have a Boston Administrative Philadelphia office can have a Philadelphia administrator the DC office can have a DC administrator those administrators can only administer what you give them permission to administer within those particular offices and that is all set up with the organizational unit so with the organizational unit you populate it with whatever computer accounts so computers on the network that they should be able to access an administrator and administrate and then you add all the user accounts that they're allowed to administrate and then you say exactly what they're allowed to do and then they're allowed to do all that work with the organizational unit again as we go on this stuff will make a lot more sense but remember the domain controller is the server that controls an Active Directory directory services the domain controller contains user accounts and computer accounts the information that is stored on these user accounts and computer accounts is based on the schema you create groups for security purposes so that you assign use assign rights and permissions to the group and then you add users and computers to the group to make your life easier for administrative purposes you then create these oh use or organizational units and then again you can say one person in the Boston office is allowed to administer the Boston computers so this is some of the basic concepts of what you need to know for Active Directory directory services now the next thing that we're going to be talking about so we have the DC we have the domain controller right we've talked about the domain controller and then we have the user accounts and we have the computer accounts while the domain controller then creates what is called a domain right so the computers are tied to the domain controllers domain and the user accounts are tied to the domain controllers domain so basically the domain is all the computers and user accounts that are tied to the domain controllers active directory directory services domain so this is what a domain is domains are basically they're just they're used for administrative purposes so okay so we know everybody here is in the UI the computer guy com domain so now we need to start talking about domains trees forests and trusts and this is where things can get a little complicated so we have this domain here and so we're just for this example today we are going to be talking about Google because it just Google is a name you guys probably know and you can probably follow along with with with the information about that why I'm talking about Google so let's say we create a domain for google.com right so we have google.com so google.com is Google everybody knows what Google is google.com is Google so Google creates their company they get domain controllers or added users they add computers and they have their domain google.com and this is essentially this right here is really what most of you guys are going to be dealing with you guys are going to be dealing with single domains for the most part but the this is a real class I've got to teach you all the rest of us so in the beginning we have google.com now as Google grows right Google starts expanding into more dia graphic areas so Google expands into Asia Google expands into Europe Google expands into Africa now one of the problems is is that when Google expands into let's say Europe Europe has a lot more regulations than the United States has so Europe may have a requirement about how the security on the domain and certain specific things about how the domain is administered so again as I talk to you guys about nowadays the real technology world it is you know it's as much as much to do with laws as it does technology anymore so you have to be thinking about things like laws so the so the thing is is so when you go into Europe Europe may have a very specific set of laws and security that you have to deal with for the domain now now google.com is sitting in the United States and they're like man man you know we don't want to have to deal with with all these security requirements for the rest of the company you know if in order to get into Europe we have to have some improved security that's fine that's fine but but we don't we don't want to have to pay for that improve security over the entire company so what they will do is they will create a sub domain so they will create a sub domain and this sub domain might be Europe Europe google.com and this is actually its own domain with its own domain controllers but it is a sub domain of google.com now the reason that is a sub domain that it'll be created as a sub domain of google.com is because of what we talked about before with the schema the schema right all of the data the types of data that are stored for a user or for a computer Google has come up with a very specific schema for their users and for their computers and they want to make sure that that schema is used throughout all the company so what they do is they create this sub domain Europe google.com which uses the schema for google.com but otherwise they can lock it down and they can make it more secure then let's say they go over here and they're going into Africa so they create Africa google.com so these domains again have their own domain controllers have their own user accounts they have their own computer accounts and so on so domain controller user computer using the same schema now one of the reasons why this is a very useful structure is because then we have something called two-way implicit trusts transitive so when we create a sub-domain from another domain so google.com and we're creating Europe google.com we get we create what is called a two-way implicit transitive trust so let's just let's just break this down for a second so what we're talking about two ways we're talking about Google and Europe google.com both what it what is called trust each other we'll talk about what Trust is in a second we also when we create the sub domain of Africa google.com that also creates the implicit two-way transitive trusts so Europe google.com trusts google.com google.com trusts Europe google.com then we create the sub domain Africa Africa google.com trusts google.com and Google com trusts Africa google.com so that's two-way trust but then it's transitive when it what transitive means is if Europe google.com trust google.com it also will then trust Africa google.com so transitive is means any sub domain created here will trust the other domains now you're thinking okay Eli what does it mean to trust another domain why is this important why this is important is that means you can give user accounts so if you're down at Europe google.com you could create permissions for users from google.com so if I am let's say I'm somebody from the marketing from the corporate marketing department up here at google.com and they want me to send me to Europe so I can fix some big mess right well the cool thing with Active Directory is without Active Directory basically down here at Europe now Google komm they would have to create new user accounts at F create new computer account they would have to do a lot of a lot of work they'd have to do a lot of effort well because there is a trust here what you can do is you can actually just give permissions to use your account from google.com so if I have to go down into Europe google.com they can simply give me permission so they can add my user account from google.com to let's say the marketing department at Europe google.com and now I'm able to access all the files and folders permissions and security that I need so that is what the trust relationship means the transitive trust means that I could also if I had a user a Europe google.com they could go over to Africa google.com and Africa google.com could give my user account from Europe google.com permission to resources on their particular domain so this is what the Trust's are and this is why it's so useful is because you can go into a different domain and using your same username and your same password that the administrators on that domain can give you permissions to do stuff on that particular domain so I know this may seem like but it really really really really really really is important in the real world now why we're using Google is to explain to you how this how this continues to expand out and again why Active Directory directory services is so important and why if you're like I would never use that well what you're saying is you really never want to work in the real enterprise world so here is the domain so this is google.com and then under it we have these subdomains Europe dot-com and our Europe Google and Africa google.com right so we have the Google comm and then the subdomains well when we start talking about trees and forests this is a tree it kind of looks like a tree kind of looks like a Christmas tree right so you won one of these units one of these domains is the domain when you create subdomains from the original domain that is what is called a tree so a tree is when you add subdomains to the original domains that is what a tree is now when you create a forest what happens and since we're using Google this is why we're using Google let's say you know Motorola is over here right and this is the Motorola dot-com domain and it has subdomains of let's say us Motorola comm and I don't know Asia that Motorola com so we had the google.com tree and then we had the Motorola dot-com tree so now these are entirely different trees which means the schema is different the schema is different the different types of information that are being collected and used for the user and computer accounts are different because basically there are two entirely different companies again why we're talking about Google you have Google not cambia Motorola com they're entirely different companies they're doing their own thing Google does search Motorola does hardware they have nothing to do with each other all the way up until when google buys Motorola and now they become one company right now when we're dealing with with again big companies tens of thousands of users this could become a problem because Google needs to send lots of their people over to Motorola in order to do work but Motorola is a different company under entirely different domain so what would normally have to happen is you have to create new counts new user accounts add them into the whole mess and then it's just annoying because then the Google employee has Google credentials and they have Motorola credentials it just becomes tedious well what you can do is you can start creating what are called explicit one-way trusts so what we can do is we can have Motorola calm when Motorola calm gets bought by Google calm the administrators from Motorola calm can create a one-way explicit trust to google.com what that means is as soon as they create that trust relationship they can then give user account from google.com permission to do stuff on the Motorola network so you can have let's say um google.com slash Bob is a user account and you can give google.com slash Bob permissions to files and folders now on the Motorola network you don't have to create new user accounts you don't have to do anything you simply take that user account and you put it into a group as we talked about before and now they have access to all the files and folders permissions and resources so again we talked about those marketing people so Google com sends a number of marketing people over to Motorola dot cause marketing department to try to - to knit the departments together well now the people that came over from google.com those user accounts can simply be added to the marketing department group in the Motorola comm domain and now they can use all of the resources that they would before so when we were doing this in when we're connecting different domains you do one way explicit trust basically that what the explicit means is you actually have to create this connection and then when you create it only goes one way so what you can do is you can have Motorola trust Google but you can say but Google can say man we don't know about these Motorola we know is one way we don't know if we want motor roll people coming into our corporate headquarters we bought Motorola so you're darn tootin our people will be going to Motorola and doing work but we don't know if we want motorola employees coming over to our headquarters in doing work so it's one way so you can have it so motorola comm trust google but you can leave it in that Google does not trust Motorola if you wanted to make this a two-way you then add and then you add the trust from Google to Motorola again it's still one way but basically you have to one way trust Google within trust Motorola Motorola trust Google so on and so forth then with transitive trusts if if if Google trusts Motorola Europe Google comm trust Google then what you can do is you can have a user account from Europe Google com go over to Asia Motorola comm and then be able to do work there so it's all about very easily being able to give users and computers permissions security so on and so forth within this Active Directory directory services environment and this is what we call a forest so we have the Google comm tree here the Motorola comm tree here when we connect these with trusts then this becomes a forest so you know there's that Kansas City fiber thing that Google is doing so let's say Kansas City dot fiber calm and that's its own domain with its own sub things so if we create trust here and that just expands the forest so that is what we're talking about with domains trees and forests when you create a sub domain that automatically creates a two-way transitive trust which means somebody from Europe com can also do things over Africa comm if they're given permission when you connect trees together it's one way implicit trust so you can have it so own so Motorola trust Google but Google does not trust Motorola or you can have it going both ways but then when we add those domains together that becomes forests so that is the basic overall concept of what we're talking about when we're talking about the Active Directory directory services structure and why it becomes so powerful that essentially you can take some user at a Europe google.com you can add them to a group over in asia motorola comm and then they can sit down at a computer and then they have access to printers and folders and email and everything that they need access to they don't need numerous accounts they don't need numerous passwords they don't need numerous all that kind of stuff basically the administrator just adds them to the account if these trusts have been set up and and they're good to go so these are the very important things that you have to understand about Active Directory directory services in order to really go forward and understand the power of the Windows servers if you take Active Directory away from Windows servers then yeah frankly Linux and UNIX do a lot of things better than the Microsoft I'm not even gonna argue with you about that but the power of Active Directory means that for these Enterprise worlds these corporate worlds when you're talking about Motorola's you're talking about google's you're talking about exons you're talk about these major corporations Active Directory just does something that no other service does so the servers that do Active Directory directory services are called domain controllers they contain user and computer accounts the information that is stored about those user or computer accounts is based on this schema the schema is extendable which means you can add bits of information that you want the schema to store and then as we go into forests and trees and trusts that have already repeated three times I think you understand what's going on so let me go back over to my to my own little desk over here so we can wrap up so so that is what you need to be thinking about when you're thinking about Active Directory again one of the biggest problems with most people that are go for their MC SES or their MC essays is frankly they have never worked or been involved in a computer or technology environment large enough um for any of this to make sense you know I mean if you if you haven't been in a position to be in a company where you see the tens of thousands of employees or the hundreds of thousands of employees and be responsible for any component of that you may not really realize why Active Directory is so so valuable you know even if you are in a very large company you may be in an apartment of 20 people or 10 people or a hundred people and you don't understand the administrative headache of having to deal with tens of thousands of users of having to deal with corporations that buy other corporations so again the question is is if your corporation buys a different corporation in your attack all of a sudden your boss is going to be sending you over that company that you just bought to start doing technical work you notice to start aligning their technology with what your company uses well if you go there makes life a lot easier if you can simply use the same user account that you've been using for the past five years at the company you're with you can just go there you can log in under your own credentials your given permissions and you can go about your day you get your email you can use SharePoint now you can use Skype all of that stuff is just the single sign-on you don't have any additional problems whereas if you didn't have these trust relationships if they sent you over let's say to Motorola comm they would have to create a new user account for you that have to create a new computer account for you they'd have to create a new email address for you they'd have to create all of this additional information so now you have your original company's user account and a profile and all that plus the company you're at did this new company you're at user account and profile and then if they have you running around between like multiple different companies that the parent company may own it can just become a mess all of a sudden you've got like five accounts passwords to remember it's just like I said if you've done this stuff in the real world it just becomes an absolute and utter nightmare so this is the overall concept for Active Directory directory services again I kept saying Active Directory directory services because that is now what microsoft says you should remember so if you see that in a test remember this is Active Directory directory services as we go forward in this this Windows Server 2012 track again I am going to try try to use the proper words that Microsoft wants me to use but just realize again I'm a professional technician I I don't take certification tests all the time so I might use some some incorrect words if you are going to be taking the certification test make sure you pick up certification study books to make sure you know I say the right word you know the right words that we're talking about so this was the latest class in the Windows Server 2012 track we're going to be having a lot more so the next one we're going to be talking about the infrastructure involve with Active Directory directory services we're going to talk more about the domain controllers clustering domain controllers sites basically how all of this stuff gets built out but you need to understand you need to understand what domains are you need to understand what trees are the Internet's need to understand what forests are what user accounts computer accounts groups and organizational units if you don't understand though that that basic terminology everything else is going to get really confusing really fast so if you didn't understand how I talked about it again go to google or grab a book and sit down and make sure you understand what these concepts are because if you don't it's all going to turn into a mess to say so so so as you know IP lie the computer guy this class was introduction to Active Directory directory services structure in Windows Server 2012 as always I enjoy teaching this class and I look forward to see what the next one you

Channel: Eli the Computer Guy

Views: 1,694,919

Keywords: Eli, the, Computer, Guy, Active Directory (Software), Windows, Tutorial

Id: lFwek_OuYZ8

Length: 46min 30sec (2790 seconds)

Published: Fri Feb 22 2013