Hello again as you know I am Eli the computer guy in today's class is installing Active Directory DNS and DHCP to create a Windows Server 2012 domain controller so now we are finally getting into actually doing stuff with our Windows Server 2012 computer so as I've talked about
before when you install Windows Server2012 for the first time you've installed that operating system basically it's
just there it has no more real functionality than a Windows 8 computer
does these server services are not installed and turned on by default you have
to go in there and do that so if you want to set up a DHCP server you have to
set that up if you want to install and set up the DNS server you have to
install that and set it up
if you want to install Active Directory and
run Active Directory you actually have to install that and set it up so today
what we are going to be doing is installing those different server services
onto our server so that we can go forward in this track so all we are doing
today is installing the services we are not actually going in and configuring
any of them because those are their own 30-minute classes unto themselves so
right now we have the Windows Server 2022
server sitting there and we are going to
install Active Directory DNS and DHCP now remember all these different server
services do specific things so remember Active Directory is our security
service is the is the service that allows us to create users and groups and
organizational units and assign resources to those users and groups so
basically this is where we can create a user and very easily give them
permission to use a printer on the network or very easily give them the ability
to use a shared file or folder or to restrict their access Active Directory is
what it gives us the ability to say that call center employees are able to
change the background at all on their computers
but geeks running around are able to
do anything that they want other computers that is what Active Directory allows
us to do DNS is the domain name services server this is what Maps IP addresses
to fully qualified domain names so if you're trying to get to a computer named
server DNS
is what will turn a server into 192 dot 168 1 3
so that your computer can actually access it again with DNS you will see in the
book where it says you don't have to use Microsoft
Windows Server DNS services I suppose you don't have to if you really
want to deal with a lot of pain a lot of
frustration and a lot of anger, in general, I would say always use Microsoft
Windows DNS server services again unless you're a high-level geek like me and
you really know what you're doing for your new guys just use the built-in
Microsoft DNS server and the same is true with DHCP DHCP is what gives out the
dynamic
IP addresses so so so just use Microsoft's
DHCP server it will save you a lot of time at the end of the day because if you
don't it'll just get stressful and nasty and it's all bad so let's go over to
the whiteboard for a second because I just want to explain a couple of things
before we actually go and start working on the computer so we're at the
whiteboard here um and the basically what we are doing today by creating this
Active Directory
the server is we are creating the domain so
whenever you see one of these little triangles that are a domain now the domain
the thing that we need to create a domain is at least one DC or one domain
controller now in order to create a domain controller we have a Windows 2012
server and we install Active Directory on it a D we install Active Directory
on that windows 2012 server now in order for
Active Directory to work we also need DNS and just to make our lives easier
also DHC now these are all different server services it's very important to get
that through your head Active Directory DNS and DHCP are entirely separate
server services and they can be on their own physical servers or virtual
instances of servers if you have a big enough network so it is possible to have
simply had Active Directory servers and DNS servers and DHCP servers well if
you're like
a
lot of the small business clients or if you're like yourself where you only
have a certain number of computers in your lab you may only have one laptop or
two computers it's not worth your it's not feasible to have Active
Directory DNS and DHCP be on separate servers so what you can do is you can
install Active Directory DNS and DHCP
all on the exact same server now for most
environments this will be ok if you're dealing with enterprise environments if
you're doing with ten thousand users a hundred thousand users you want Active
Directory DNS and DHCP to be on multiple different servers you don't want them
on the same box but for them for a small environment if you're dealing with an
office of a hundred users or even maybe a thousand users having all
these services are on one server or instance is
as fine as long as the hardware is good enough so today what we're going to be
doing is we're going to be installing Active Directory DNS and DHCP on to our
server and that will give us a domain controller ADC and that is what gives us
the start of our domain so as I talked about before and the other classes and
infrastructure you can have multiple domain controllers you can have 50 domain
controllers if you wanted to spread all around the world at different sites with all kinds of weird replication
strategies so you can have numerous domain controllers but you only need one so
like the small office environments that I dealt with if they had 50 users they
would just simply have one domain controller with Active Directory DNS and DHCP
all on that one domain controller and then they will be able to do whatever it
is so so make
sure that you do understand this they may be
these services may be on separate boxes but if you're dealing with small
environments where you're a lab environment they can all be on the same
computer so let's go over back to the back to the desk so again so so I have my
Windows Server 2012 server here it's a fresh install and just so you guys
understand I've installed this within Virtual Box which is a piece of
virtualization software
on my laptop so this is a fresh install the
only weird little thing about it I say it and it was it's in a virtual machine
but for all intents and purposes when you are administering your server it will
act the same way so let's go over and let's take a look at the server now so we
are sitting here
it's Windows Server 2012 again I'm using the
trial version is free gives you all the functionality that you
need so what we're going to be doing now the tool we are going to be using
today is server manager so we go down to the lower left-hand corner and we
click on that little toolbox thing and this takes us to server manager so
server manager basically gives us some of the tools that we need to administer
the server now when it first opens up we'll see over on the left-hand side it says the local server of
all servers and file and storages
services now as we install more services onto the server we will get more
options over here on the left-hand side the same is true over on the right-hand
upper corner under the Tools menu so since we have certain services installed
on the server right now we get a certain listing of tools as we install more
services on this server we will get more tools basically what we're going to be
doing today is we're
going to be going up to this manage
toolbar here and doing add roles and features but for I add a role and feature
to this computer I want to change the name of this server so let's go over here
to a local server now you'll notice when you install Windows Server 2022 it
does not give you the ability to say what the server's name should be so, unfortunately, you get really horrible it automatically gives you really
horrible computer names such as this win - HBM 6 8 8 l bla right are you going
to
remember this name when you have to go
administer your network when you have to connect to the server are you going to
remember this name no you're probably not so the first thing that we want to do
with this server is we want to change its name to something that we are going
to remember now in order to do that all we do so we go to local server then we
just click
the current computer name that will open up
the system properties window and then what we're going to do is we are going to
go over here and we will click the button called King from here we can now
change the computer name so instead of wine - I don't like that I can simply
call this server so you decide what name you want to make your server be called
and then you can rename it there once you have renamed it what you're going to
do is you're going to click OK and it's going to go in and it's going to change
the name
now in order to fully change your name what
we're going to have to do is we're going to have to restart the computer so
we're going to close and we are going to do a restart now so this is
going to go in and this is actually going to change the name of the server this
is very very important again when you start doing a higher-level administration
when you're doing things like mapping drives when you when you're trying to
connect to this server
if you have a really long horrible name it's
just going to be a pain in the butt to use so the first thing that I would say
that you should do is to change this that this server name so it's rebooting now so whenever you're doing anything with the server you do have to
keep in mind that you may have to reboot the server so whenever you're changing
services
whenever you're you change the computer name
do those types of things you may have to reboot the server why this becomes
important as you start administering servers in the real world is because if
any users are currently connected to the server when you have to reboot it well
obviously they will be kicked off the server when the system reboots so this is
something that you should just keep in mind as a professional as
you go on with your professional career is
anytime you are doing any kind of maintenance to a server you may have to
reboot the server so always make sure the users know you may have to reboot the
server and you know so nobody hates you at the end of the day before you reboot
the server in a real-world environment make sure to go out and actually talk to
all the users and tell them in ten minutes the server is going to be
rebooted so make sure you've saved any files
that you need to have saved so now we can go over to the local server and
we can see that our computer name our server name is now called server so we've
changed the server name for this particular server so from here now to add the functionality
we're going to add Active Directory DNS and DHCP
all we do is go up and we click on this
manage button now the manage button gives us the ability to add roles and
features so we will click on that and then we basically just walk through the process
so we click Next we leave the default role-based or feature-based installation
next we leave it to this server next and now it is going to ask us
what we want to be installed so what we are going to
do is we are going to select Active Directory domain services DHCP server and
DNS server so we'll collect Active Directory domain services and then when we
do that it will ask you it will tell you all these other things have to be
installed so we just say yep add features then we go down and we select DHCP
again add features we just say continue right
now because we thought the warnings that we will get during this process
basically we will fix all of these problems in the future and we also select
DNS we add features again it's going to give us a problem we do continue and
now we are going to hit next so Active Directory domain services DHCP and DNS
then from here we just leave it as it is
and we click Next and then now we're going to click Next Next and then we're
going to do install so this process is going to install all of the services
that we need for Active Directory DNS and DHCP really now all you do is you sit
back and you wait for a little while generally this process takes about 25
minutes so so
with me with it though the fancy tools
of video editing we're going to fast forward through this process when
you do this expect this whole process to take probably about 25 minutes to it
to install the DNS the DHCP and the Active Directory services so I'll come back
in a second when this is all finished ok now that the installation process has
completed
Active Directory DHCP and DNS is now installed
it is telling you that you need to do a couple of things so for today's class
all we are going to be doing now is we're going to promote this server to a
domain controller so this will is what will actually make this server domain
controller so once the installation process is done you just look and see what
things it tells you that you have to do for today able to just do this promote
the server so all
we do is we click on that and this takes us
through the process for turning this into a domain controller now a lot of this
is again you have to be thinking about what you're doing you have to think
about what you're trying to accomplish and if you think about what you're
trying to accomplish all of these questions that will ask become pretty simple
so what it's asking right now is we want to add a domain controller to an
existing domain well
the answer is no because we don't have a
domain yet do we want to add a new domain to an existing forest again we don't
have a domain yet we don't have a force we don't have anything so what we're
going to do is we're going to add a new forest so although this may seem a
little odd you may be thinking well Eli we're creating the domain well the
answer is to add a new forest because that the other two answers basically are
incorrect now
it's going to be asking you what is the root domain name so for me, I'm just going to say e TCG dot-com so if you have a domain name you would put that here so if you have Billy Bo com Bob calm you would put that here whatever your company's domain name you could be calm org.net the only thing with two--this server 2012
is it does have to have a dot something or other in order to create this root domain name you can't do just eat ECG with the new system you have to do eat ECG comm or.net or dot biz then we're going to click Next now realize you don't actually have to own the domain name so I don't actually own eat ECG comm this is all internal to your internal network so you can use whatever you want you could use Microsoft com it wouldn't matter because right now it is all internal in your using this in the lab environment when you're
when you're in an actual real business environment
you want to use whatever their domain name is because just because of email
service is that kind of stuff but right now in this lab environment you could
use any domain name you want now at this point it is asking us.the functional level for this server now as I've talked about Active Directory has
now been around for a long time in the windows world all the way back to
Windows 2000 so there's Windows 2000
Windows 2003 Windows 2008 and now Windows 2012
server now as with with with all computer stuff when the next version comes out
there are more features there are more as there's more functionality so so
Active Directory now does much more than Active Directory did way back with
Windows 2000 but again you're dealing with large corporations that may have
what is called legacy pieces of equipment what legacy means is these are old
servers that have been around for ten years doing something and they
still use let's say Windows 2000 or Windows
2003 so they don't have the full functionality of Windows 2022 server so if you have old servers on your
network you will have to select a different functional level depending on those
servers now for us since we are simply building out a brand-new network we can
say that the functional level is Windows Server 2012
but do realize if you're dealing with a real
enterprise environment if you're dealing with a real corporate environment and
you have two thousand servers two thousand three servers you would have to make
sure go through and make sure you use the right functional level here so as we
can see if I select this I could say Windows Server 2003 or 2008 or 2008 r2
again we will leave this as 2012 now down here it is also going to ask you a
couple other things and their
checkboxes we already it's going to ask what
the capabilities of this server are so we installed DNS before so DNS is
checked off again this is the first server on this domain so the global
catalog the GC will be installed by default and again since is the first server
we can't make it a read-only domain controller that would just simply be kind
of dumb so all of these boxes have already been checked off as they should
since this is the first server on the network it is then going to ask you for a
D SRM password so as always create whatever password you want it has to be one
of those complicated passwords an uppercase letter a lowercase letter a number
and a special character but just put that in and then do next to make sure you
write that down somewhere again this is going to give you warnings because we don't
have things like the DNS
the server is already set up so just basically ignore
those warnings for now we will deal with those later and a different class we
click Next now it is going to ask us for the NetBIOS name so again NetBIOS was
used way back when but if you have legacy equipment if you have Windows
equipment sometimes it will need the NetBIOS domain name so the NetBIOS
a domain name is the basics like a
domain name from the old days so here and the domain name is just e TC g
the one warning that I will give you for the NetBIOS domain names is they can't
be over fifteen characters long so I cannot do Eli the computer guy because
that's over fifteen characters so whatever NetBIOS domain name you pick just
make sure it's under fifteen characters and generally what Windows will do is
we'll take
whatever domain name you gave it
originally and just take off the dot-com or dot biz or not whatever you put
there and now we're going to do next so now again as we've talked about before
Active Directory is a database so it's going to be asking you where information
for this database should be stored now some people and I really do hate this
feeling that you should
create multiple partitions on your
server hard drive and store different types of data at different places on
those partitions so shared files and folders would go on let's say partition D
and things like the database would go on like partition e so on and so forth I
think you should just create a one really big partition and leave it at that's one of those preferences things
I've done it for a long time I say stick with
one partition and leave all of the databases and log files and sysvol folder at
what the default is if you decide to put things on different partitions this is
where you will go in and select where this information should be stored but
then all we do is click Next I would say leave that a default now it's going to
ask you do you really want to do all this so I mean this is basically all the
configurations you put in it's just saying do you really want to do this you do
so now all you're going
to do is you're going to click Next and then
this is going to take you through the process for doing everything's
basically everything from here is an automatic process so again through the powers of video editing we're going to like a time warp to a
couple minutes from now but basically, this will go through it will do
everything it needs to do it will reboot and then we'll come back so for the
server actually before it actually runs the script to install everything it
goes through and it checks to make sure all
the prerequisites for installing everything
are there you will notice that it does give some warnings here again as long as
none of the warnings are our red stop signs you will just go ahead and leave everything as it is so so some of these warnings that are giving there
are things that we'll have to deal with in the future but we don't worry about
them right now so we just take those we understand that there are some warnings
but all we're going to do right now is we
right-click on and the install and now it will go through and they'll actually
install all of us so now the server has rebooted and so Active Directory DNS
and DHCP have been installed so if we look over on the left-hand side we will
see that we now have new options Active Directory domain services DHCP and DNS
again right
now we are not going to get into these
but just realize that these options are now available to us as I talked about
we go to tools now we will see that we now have new options under the Tools
menu so there are Active Directory domains and trusts Active Directory sites and
services Active Directory users and computers DHCP DNS and so on if we go over
to the
the local server we will also see that under
domain it now says et Cie com so it's now the computer name is a server at eating
ECG comm now you'll notice up in the right-hand corner there is a little
warning
on the notifications area if we click on
that we will see that we need to complete the DHCP configuration but as I
talked about before we will do that in another class just realize that this
little flag area here is where you will be shown when you need to do things so
basically it will give you a little warning and then it will give you a link to
the tool you need to fix whatever the problem is so that's all we need to do to
install Active Directory DHCP
and DNS now that we've done that in the
future we can actually go and with Auto there we go in the future now we can go
forward and now we can configure DHCP and we can start adding users and
computers to the network and we can start building out this domain but it's
important that you install these this functionality first so that we can do
everything later do you realize so when you have the domain in order to create
the domain
you need the Windows Server Server 2012 server
you need to install Active Directory you need to install DNS and you really
should it's a really good idea to do DHCP again even if you have a DNS server
or a DHCP server already for this Microsoft Windows environment it's really
better to use Windows for the DNS and DHCP I did a class previously on how to
create your own lab network and at this point, you really need to put your 2012
server
on a lab network we're going to go forward
we're going to set up DNS we're going to set up the HCP and if you try to set
that up on a network that already has another DNS and DHCP server running
you're going to run into all kinds of problems it's just going to be very very
very bad so this was the class installing Active Directory DNS and DHCP to
create a Windows Server 2012
domain controller, we install those
services we created the domain we now have the domain controller so now we can
move forward and we can actually start adding functionality to this domain as
always I feel I the computer guy I enjoy teaching this class and look forward
to seeing it the next one By By By